How to Build a Decision‑Driven Procurement Ledger in 2 Hours with a Low‑Code Tool

Many companies maintain procurement ledgers that record dates, items, suppliers, unit prices, quantities, and amounts, yet managers still ask why a price is high or why a supplier was chosen because the ledgers are built as pure records rather than decision‑support tools.

To address this, the author rebuilt the procurement ledger in just two hours using the low‑code platform JianDaoYun , without introducing an ERP or complex BI system. The new system is organized as a set of interconnected modules that capture both results and the processes that generate them.

Step 1: Procurement Request

The request module collects core fields such as requesting department, material, estimated unit price, budget amount, purpose, and request date. Each purchase is anchored with a budget reference, ensuring that the reason, expected cost, and responsible department are clear from the start.

Step 2: Procurement Execution

This module records the actual purchase price, chosen supplier, and deviation explanations. The system automatically compares the requested price with the executed price, highlighting any significant variances so issues are visible immediately rather than discovered later.

Step 3: Financial Management

Invoices, payment orders, expense reimbursements, and receipt records are integrated into the ledger. Fields cover payable account reconciliation, invoice details, payment status, and links to purchase orders, enabling a unified view of procurement and finance data.

Step 4: Dashboard (Kanban) View

A dashboard aggregates key statistics:

Financial payment statistics : number and amount of payment orders, trends, and details.

Financial receipt statistics : number and amount of receipts, trends, and details.

Expense reimbursement statistics : count, amount distribution, trends, and details.

Cash flow statistics : net flow, inflow, outflow, and detailed account movements.

Three visualizations—table view for data entry, board view for status tracking, and calendar view for procurement rhythm—allow managers to see the whole picture at a glance.

Impact After Deployment

The new ledger changed three key aspects:

From questioning price to examining structure : Historical prices, comparison processes, and selection reasons are visible, so the data explains itself.

From post‑mortem analysis to process control : Budget, approval, comparison, and execution are monitored in real time, moving cost control forward.

From reliance on individuals to reliance on the system : Rules and data flow are embedded in the platform, preserving logic even when personnel change.

The system is not a full‑featured ERP, but it consistently saves money, time, and reduces risk. A downloadable template of the procurement management system is available at https://s.fanruan.com/3899w.

Future enhancements could include automatic budget overrun interception, full‑process approval integration, and connection to external financial systems for automated reconciliation.