Ask a developer when they discovered a project had gone over budget and the answer is almost never "while it was happening". Costs are usually reconciled after the fact, by which point the money is spent and the only remaining decision is who absorbs it.
Why spreadsheets find overruns late
A spreadsheet records what was paid. It rarely records what was committed. Between a purchase order being raised and its invoice being paid, the money is already gone in every practical sense — but it is invisible in the file. The gap between commitment and payment is where overruns hide.
What integrated cost tracking changes
- Commitments count immediately. A raised purchase order reduces the available budget the moment it is approved, not the month it is paid.
- BOQ is the yardstick. Actual consumption is compared line by line against the bill of quantities, so a variance shows up as a percentage rather than a hunch.
- Contractor bills are measured, not trusted. A running account bill is checked against work certified and against the retained amount before it is passed for payment.
- Site issues are recorded at the site. Material leaving the store is booked to a project and a cost head, which is what makes any of the above real.
The reporting that matters
Three views cover most decisions:
- Budget versus committed versus actual, per project and per cost head.
- Cost per square foot as it moves through construction, compared with the plan.
- Contractor exposure — certified, billed, paid and retained, per contractor.
A worked example
A project budgets ৳4.2 crore for structural work. Halfway through, the ledger shows ৳2.1 crore paid — apparently on plan. The commitment view shows a further ৳0.9 crore in approved purchase orders and unbilled certifications. The overrun is visible with half the work still to price, which is early enough to renegotiate.
Getting there
Cost tracking only works when procurement, store and accounting sit in the same system. Bolting a costing report onto disconnected processes reproduces the original problem with better formatting. Start by moving purchase orders and site issues into the ERP; the cost picture follows on its own.