Committed Cost vs. Actual Cost: Why the Gap Matters

On this page

Committed cost is money the job is legally obligated to spend but has not yet been billed for: a purchase order issued, a subcontract signed. Actual cost is money that has hit the books: invoices posted, labor recorded. The gap between them is real spending that an actuals-only report cannot see.

That gap is where jobs get in trouble quietly. A budget line can look healthy for weeks while the money against it is already spoken for, and the report that finally shows the truth arrives with the invoice, long after the decisions it should have informed.

What is the difference between committed and actual cost?

The difference is timing and certainty. A commitment is created the moment an obligation exists: the PO goes out, the subcontract is executed. An actual is created when the cost is recorded: the invoice posts, the timesheet is approved. Between those two moments, the money is spent in reality and invisible on paper.

A worked example makes the gap concrete. A mechanical contractor is six weeks into a plant retrofit with a $300,000 equipment budget. In week two, the project manager issues an $80,000 purchase order for air handling units. The vendor will not invoice until the units ship, six weeks out. For those six weeks, an actuals-only job cost report shows the equipment line barely touched, and the job looks $80,000 healthier than it is. Nothing is wrong with the data; everything is wrong with what the report is allowed to know.

What goes wrong when you manage from actuals alone?

Three failure patterns, and every controller has seen at least one. First, the double spend: a PM checks remaining budget, sees room that is already committed, and orders against it. The overrun is created weeks before anyone can see it. Second, cost-to-complete becomes fiction: a forecast built on actual costs plus a guess ignores the portion of the remaining work that is already priced and signed, so the projection drifts exactly when it matters most. Third, the month-end surprise: invoices from old commitments land in a cluster, and a job that reported fine all quarter goes over in a single close.

The gap also reaches further than the job cost report. Cost-to-complete feeds percentage of completion, which means it feeds the WIP schedule your bank and surety read. Committed costs belong in cost-to-complete, not cost-to-date, and a WIP built on forecasts that ignore open commitments understates what the job still owes, which is the polite way of saying it overstates margin.

Where do committed costs come from?

Three documents create nearly all of them. Purchase orders commit material and equipment cost the moment they are issued. Subcontracts commit their full value when they are executed, relieved progressively as the sub bills. Approved change orders adjust both the budget and, where they carry buyout, the commitments against it. Pending change orders belong in a memo column, visible but not mixed in, because counting unapproved work as committed is a different distortion in the opposite direction.

Labor is the deliberate exception. No document commits labor in advance; it becomes actual cost daily as hours post. That is why labor discipline is about posting speed rather than commitment tracking, and why the forecast for labor lives in cost-to-complete judgment rather than a committed column.

What should a job cost report actually show?

Four numbers per cost code, read together: budget, committed, actual to date, and projected final cost. The line that changes behaviour is remaining budget calculated honestly: budget minus actuals minus open commitments. When that number is on the job cost report, a PM cannot spend the same dollar twice, because the report already knows the dollar is gone.

The discipline that keeps those columns truthful is closeout. A PO that was never closed after final invoicing leaves a phantom commitment inflating the committed column and starving the remaining budget. Commitment tracking is a habit, not just a feature: issue through the system, relieve as invoices post, close what is done.

How Jonas tracks committed cost

In Jonas, purchase orders and subcontracts commit cost against the job budget the moment they are issued, on the same ledger where actuals post. The job cost report carries budget, committed, actual, and projected final together, so remaining budget is calculated with commitments in it, and cost-to-complete starts from what the job already owes rather than a blank estimate. Field labor posts to cost codes the same day it is approved, which closes the one gap commitments cannot cover.

Because commitments and actuals live in one system, the relieving is part of the same entry: an invoice posted against a PO converts committed to actual, with no re-entry, and the report never counts the same dollar in both columns.

Plenty of systems display a committed column. The difference is whether the commitment, the invoice that relieves it, and the labor beside it live on one ledger, or arrive through a sync.

See your committed costs the day they are committed. Book a demo with a Jonas specialist.

Common Questions

When does a committed cost become an actual cost?

When the invoice posts against the commitment. The commitment is then relieved by the invoiced amount, so the committed column goes down as the actual column goes up, and the total expected cost of the line holds steady. A commitment that never relieves, or an invoice that posts without touching its PO, is how the two columns drift apart and stop being trusted.

Should labor appear as a committed cost?

Generally no, because no document obligates labor in advance the way a PO or subcontract does. Labor becomes actual cost as hours post, which makes posting speed the labor discipline: hours reaching the job days late distort the report the same way an untracked commitment does. The forward view of labor belongs in the cost-to-complete forecast.

How should change orders be handled in commitment tracking?

An approved change order adjusts the budget and any commitments bought out against it, so both sides of the comparison move together. A pending change order belongs in a visible memo column: hidden, it understates where the job is heading, but blended into committed cost, it treats unapproved work as money the job owes. The distortion runs both ways, which is why the memo column exists.

What happens when open POs are never closed out?

The committed column inflates with phantom obligations, remaining budget reads lower than reality, and eventually the PMs stop believing the report, which is the real cost. A monthly open-commitment review, closing anything final-billed or dead, is cheap insurance. The report is only as credible as the oldest stale PO on it.

Is committed cost the same as an accrual?

No, and the difference matters at month end. A commitment is an obligation issued for work or materials that may not have happened yet. An accrual is an accounting entry for work already performed but not yet invoiced. A subcontractor halfway through a milestone is an accrual question; the unbilled half of their subcontract is a commitment. One is about work done, the other about money promised.

Related Articles