Committed and incurred cost flows in from your ERP against the same WBS you planned on — so budget, commitment and actual sit on one line, and earned value finally has something real to measure against.
Actuals land against the WBS node they belong to, not a parallel ledger view, so the variance you see is the variance that exists.
POs and subcontract awards register as commitment the moment they are placed, long before an invoice arrives.
Invoices, timesheets and plant hire post against the WBS, sourced from the ERP and never re-keyed.
Budget vs committed vs actual on one row — no month-end reconciliation spreadsheet.
BuildOrch consumes cost from the system of record and maps it to the plan — every posting carries its ERP identity so nothing is double counted.
Every level of the breakdown carries its own budget, commitment and actual.
When commitment is visible the moment it is raised, the overspend conversation happens while there is still time to act on it.
See spend building against a package before the invoice lands.
Drill from a roll-up figure to the posting that created it.
Because it is the ERP’s number, finance and delivery never disagree.
Actual cost, on the same spine as the plan.