Committed Cost vs Actual Cost: Why Project Control Cannot Wait for Invoices

For construction companies, one of the most dangerous misunderstandings in project control is assuming that actual cost tells you whether a project is financially under control.

 

It does not.

 

Actual cost tells you what has already been recognized as incurred.

 

Project control, however, needs to answer a much more important question:

 

What are we already exposed to before the cost becomes an invoice?

 

That is where committed cost becomes critical.

 

Actual Cost Looks Back. Committed Cost Looks Forward.

 

Imagine a contractor has an approved budget of AED 10 million for a work package.

 

So far, only AED 2 million has been recorded as actual cost.

 

At first glance, the project may appear comfortable.

 

But what if another AED 5 million has already been awarded through purchase orders and subcontracts?

 

And what if another AED 4 million is still required to complete the remaining work?

 

The real exposure is no longer AED 2 million.

 

The project may already be heading toward an overrun.

 

This is why construction cost control cannot rely only on posted accounting transactions.

 

Proper project control needs to connect:

 

Actual Cost + Remaining Commitments + Remaining Uncommitted Cost = Forecast Final Cost

 

This is closely aligned with the concept of Estimate at Completionused in project control:

 

What Is Committed Cost?

 

Committed cost represents expenditure the contractor has already authorized through mechanisms such as:

 

• Purchase Orders
• Subcontracts
• Approved contract amendments
• Equipment hire agreements
• Other formally awarded obligations

 

But there is an important distinction.

 

The total committed value of a purchase order is not necessarily the remaining commitment.

 

Part of that purchase order may already have been delivered, consumed or recognized as actual cost.

 

If management adds the full purchase order value on top of actual costs, the project forecast can become overstated through double-counting.

 

This is why a proper construction ERP must distinguish between:

 

• Total Awarded Value
• Cost Already Incurred
• Remaining Committed Cost
• Uncommitted Cost to Complete

 

Oracle itself distinguishesbetween different commitment categories and transaction statuses in its project-costing documentation:

 

The lesson is simple:

 

The label “Committed Cost” is not enough. You need to understand exactly what sits behind the number.

 

Why Accounting Data Can Arrive Too Late for Project Control

 

This does not mean accounting systems are incapable of recognizing costs before an invoice arrives.

 

They can.

 

Through accrual accounting, companies can recognize obligations for goods or services already received but not yet invoiced.

 

See the IFRS treatment of accruals and payables:

 

Oracle also documents uninvoiced receipt accruals:

 

The real problem begins when project management relies only on posted accounting data for operational decisions.

 

By the time a supplier invoice reaches finance, several things may already have happened:

 

The material was requested.

 

The purchase order was approved.

 

The supplier was selected.

 

The delivery occurred.

 

The material may already have been consumed.

 

The work may already have progressed.

 

The commercial exposure existed long before the invoice appeared.

 

That is why project control must start earlier in the process.

 

Construction Cost Control Starts Before the Invoice

 

A contractor should follow the financial impact of a transaction from the moment the requirement is created.

 

A typical sequence is:

 

Requirement → Requisition → Approval → Purchase Order → Delivery → Consumption → Cost Recognition → Invoice → Payment

 

Each stage answers a different question.

 

A requisition shows demand.

 

A purchase order shows commercial commitment.

 

A delivery shows receipt.

 

Material consumption shows use.

 

An invoice creates a financial liability.

 

Payment shows cash movement.

 

These events should not be treated as interchangeable.

 

This is one of the central ideas behind project-based procurementin ProjectVIEW ERP

 

The purpose is not simply to digitize procurement.

 

It is to connect purchasing decisions back to the project budget and operational requirement that created them.

 

The Biggest Mistake: Double-Counting

 

Consider a subcontract with a total awarded value of AED 6 million.

 

AED 2 million of work has already been performed and recorded as actual cost.

 

The remaining commitment is therefore approximately AED 4 million, assuming no other adjustments.

 

If management calculates:

 

AED 2 million actual cost + AED 6 million committed cost

 

the forecast becomes AED 8 million.

 

But part of that AED 6 million commitment is already included in the AED 2 million actual cost.

 

The same work has effectively been counted twice.

 

The correct logic is:

 

Actual Cost + Remaining Commitment

 

This becomes even more important when accruals are involved.

 

If work has already been accrued and the supplier invoice later arrives, the accrual should be cleared or replaced—not counted again.

 

Oracle explicitly documents this type of accrual reversal logic

 

Why Committed Cost Still Does Not Tell the Full Story

 

Even committed cost is not enough.

 

A contractor may still have significant work that has not yet been purchased or subcontracted.

 

Consider:

 

• Future labour requirements
• Machinery usage
• Fuel
• Temporary works
• Site supervision
• Additional material quantities
• Extended project duration
• Unawarded subcontract packages

 

These costs may not exist yet as purchase orders.

 

But they are still part of the future cost of completing the project.

 

That is why the true project-control question is not:

 

What have we spent?

 

Nor is it:

 

What have we committed?

 

It is:

 

What is the project now expected to cost at completion?

 

Why Scope, Schedule and Cost Must Be Connected

 

To answer that question properly, costs cannot exist in isolation.

 

They need context.

 

At DANAOS Projects, we structure this through the relationship between:

 

BoQ ↔ WBS ↔ Cost Codes

 

The Bill of Quantities defines the commercial and measurable scope.

 

The Work Breakdown Structure connects that scope to execution and time.

 

The Cost Codes allow costs and resources to be classified consistently.

 

We explore this in detail here:

 

BoQ, WBS and Cost Codes: Connecting Scope, Schedule and Cost

 

This relationship allows management to ask more meaningful questions.

 

What scope does this commitment belong to?

 

Which activity is affected?

 

What quantity remains?

 

What resources are still required?

 

What budget remains?

 

What is the expected final cost?

 

Without this structure, the company may know how much it spent without understanding why it spent it.

 

Site Data Is Equally Important

 

Project cost control also depends on what actually happens on site.

 

A purchase order may say what was bought.

 

It does not tell you whether the resource was used efficiently.

 

Material delivered is not necessarily material consumed.

 

Labour present on site is not necessarily productive labour.

 

Equipment available is not necessarily productive equipment.

 

Progress recorded in accounting does not automatically reflect physical progress.

 

This is why site-data capture is fundamental to construction cost control

 

The objective is to connect financial exposure with operational reality.

 

How ProjectVIEW ERP Approaches the Problem

 

ProjectVIEW ERP connects procurement, site operations, subcontracting, budgeting and cost control within one project-specific operating environment.

 

• The ProjectVIEW ERP Cost Control module
• The Procurement and Purchasing module

 

The broader integrated architecture is explained here: How ProjectVIEW ERP Achieves True Cost Control

 

The purpose is not simply to create another cost report.

 

It is to allow project teams to understand cost exposure while there is still time to act.

 

Final Thought

 

Accounting is essential.

 

But accounting and project control serve different purposes.

 

Accounting tells the organization what has been financially recognized.

 

Project control must also understand what has been committed, what has been consumed, what remains to be delivered and what the project is now expected to cost.

 

For contractors, the most important question is therefore not:

 

“How much have we spent?”

 

It is:

 

“How much are we already exposed to, and what will this project realistically cost when completed?”

 

That is the difference between reporting cost and controlling cost.

 

---

 

About the Author

 

Christos Emmanouilidis is a Civil Engineer and Chief Customer and Commercial Officer at DANAOS Projects Software Solutions LLC

 

His work focuses on construction cost control, industry-specific ERP, project operations and digital transformation across project-based enterprises.