Collecting cost against a job rather than a department — and seeing the overrun while it can still be fixed.
Project costing collects cost against a project or job rather than only against a cost centre: labour, materials, subcontract, expenses and overhead, structured through a work breakdown structure. It allows actual cost to be compared with budget at any level of the project, and committed cost to be seen before it becomes actual.
Departmental accounting tells you the business spent money; project costing tells you which job consumed it. Without it, a loss-making project is invisible until the whole department's numbers move, by which point the job is finished. The commitment view matters most — a purchase order raised against a project is money gone, and waiting for the invoice to see it is waiting too long.
The project decomposed into phases and tasks, each able to carry budget and cost. The depth should match how it will actually be managed.
Budget set at WBS level, by cost type, with a defined change process for revisions.
Timesheets, material issues, subcontractor invoices and expenses all coded to a WBS element.
Open purchase orders against the project, visible alongside actuals so the true position is known.
Cost to date, committed, and estimate to complete. The last of these is a judgement and should be owned by the project manager.
A project reports 42 lakh spent against a 70 lakh budget at the halfway point. On actual cost alone this looks comfortable — 60 percent spent, roughly on track.
Including commitments changes it. Purchase orders issued but not yet received total a further 14 lakh, so 56 lakh of the 70 is already committed. That is 80 percent of the budget spoken for at the halfway point, and the remaining work includes a subcontract that has not been ordered yet. The project is heading for an overrun that the actual-cost view will not reveal for another two months.
This is why budget checking must include commitments rather than only actuals. A system that checks the budget at invoice posting will approve every purchase order up to the moment the money is gone, and the overrun will be discovered by the finance team rather than prevented by the control. Committing the budget at order rather than at invoice is usually a configuration setting, and it is frequently left at the less useful default.
| Term | What it means |
|---|---|
| WBS | Work breakdown structure — the hierarchy costs and revenue are collected against. |
| Budget at completion | The total expected cost for the project, against which progress is measured. |
| Estimate to complete | The revised forecast of remaining cost, which is where overruns become visible. |
| Commitment | Costs ordered but not yet incurred, which a budget check must consider. |
| Capitalisation | Transferring project cost to a fixed asset when the project delivers one. |
A structure with hundreds of elements is coded inconsistently and reported on by nobody.
Labour is usually the largest cost. Weekly timesheets a fortnight late make the position permanently stale.
Reporting actuals only understates the position by every open order on the project.
Cost to date without a forecast tells you where you have been, not where you will end.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Actual plus committed against budget | The real consumption picture. Actuals alone are a lagging view. | |
| Estimate to complete movement | Whether forecasts are being revised honestly or held at budget until too late. | |
| Cost performance index | Earned value against actual cost, where earned value is measured rather than assumed. | |
| Unbilled work in progress | Costs incurred but not yet invoiced to the customer, which is cash sitting in the project. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.