TL;DR
Capital-project cost control requires more than comparing a budget with invoices already posted. A useful control view connects the approved budget, commitments, actual costs, approved and pending changes, remaining forecast and forecast at completion at the same level of the work breakdown structure.
Spreadsheet double-entry begins when the financial system records transactions but cannot provide that complete project view. Controllers export actuals, re-enter commitments, add forecasts and changes, then reconcile the spreadsheet back to the source systems. The better answer is a governed project-control model that preserves source-system ownership while connecting the information needed for decisions.
Written by Dr. Simon Wright, CEO of Optimality. Reviewed and updated 25 August 2026.
What should a capital-project cost-control system track?
A capital-project cost-control system should track the approved budget, awarded commitments and purchase orders, actual costs posted by the ERP, approved and pending changes, the remaining estimate to complete, forecast at completion, variance to budget, and the ownership and decision history behind each material movement.
These measures answer different questions. The budget records what has been authorised. Commitments show value already placed with suppliers or contractors. Actual costs show what has entered the books. The forecast estimates where the project is heading. Treating any one of them as the whole cost position creates a blind spot.
The control model must preserve authoritative sources: the approved baseline for budget, procurement or contract systems for commitments, the ERP for actuals, and accountable project owners for forecasts. The records should map to one governed control structure and remain reconcilable to the financial system.
The US Government Accountability Office describes credible cost estimates as a basis for management decisions and performance measurement, updated with actual costs. The US Department of Energy defines earned value management as the integration of scope, schedule and cost. The practical point is a consistent control baseline supported by evidence that reconciles to the financial record.
Why actual costs alone give a late view
An invoice is evidence of cost already incurred. It is rarely the earliest indication of where a capital project will finish.
Consider a construction package with a $5 million control budget. The accounting system may show $1.8 million in actual costs. That figure says little by itself. The team may also have $2.4 million in open commitments, a $500,000 pending change and $900,000 of forecast work not yet committed. The emerging exposure is visible only when those elements are considered together.
This is why project controllers ask both how much has been spent and how much has been committed. PMI’s published cost-control guidance makes the same distinction: commitments and actual costs need to be viewed together so that developing trends and likely outcomes can be understood.
The useful management question is not simply, “What have we spent?” It is, “Given the approved scope, contractual commitments, known changes, work completed and remaining work, where are we now likely to finish?”
The five-part capital-project cost-control model
Removing duplicate entry does not require every system to be replaced. It requires clear ownership of each data type and a common control structure through which the information can be connected.
- Establish a stable control breakdown. Budgets, commitments, actuals, changes and forecasts need a shared coding structure, normally aligned to a work breakdown structure, cost breakdown structure, control account or contract line item.
- Preserve source-system ownership. The accounting system remains authoritative for posted actuals; procurement or contract systems remain authoritative for commitments; the schedule remains authoritative for approved dates and progress logic.
- Separate recorded facts from forecasts. Actual costs and awarded commitments must remain distinguishable from estimates, pending changes and risk allowances.
- Reconcile through exceptions. Identify missing codes, budget overruns, duplicates, unreflected changes and unexplained forecast movements instead of manually checking every line.
- Connect cost movements to decisions and work. Give every material movement an owner, reason and link to the relevant change, activity, deliverable or dependency.
What cost-control software should—and should not—do
Capital-project cost-control software should reduce reconciliation effort, preserve traceability and help teams act on emerging exposure. It should not hide the accounting record inside an opaque proprietary calculation.
When evaluating a platform, ask whether it connects budgets, commitments, actuals, changes and forecasts at a common control level; keeps actuals reconcilable to the ERP; retains source identifiers and update history; distinguishes approved facts from assumptions; gives every forecast movement an owner and explanation; traces cost movements to the work and decisions that caused them; and supports exception-led review.
A platform that produces a polished dashboard while leaving the controller to maintain a shadow ledger has not solved the underlying problem.
Optimality is not an accounting system and should not replace the financial controls already held in an ERP. Its role is to connect the operational context around those controls: activities, deliverables, commitments, dependencies, decisions, ownership and governed changes. The ERP remains the source for posted actuals; Optimality helps preserve the execution context needed to understand what may happen next.
Frequently asked questions
What is the difference between committed cost and actual cost?
Committed cost is the value placed with a supplier or contractor through an award, contract or purchase order. Actual cost is the amount incurred and recorded in the accounting system. Commitments can reveal future exposure before the corresponding invoices become actual costs.
What is forecast at completion?
Forecast at completion is the current estimate of the total cost when the project or control account finishes. It normally combines actual cost to date with the estimate to complete the remaining work, adjusted for approved scope, known changes and relevant risk.
Why is spreadsheet double-entry risky?
Double-entry creates two versions of the same financial or project-control record. Manual copying introduces timing differences, coding errors and unclear ownership. It also makes audit trails and repeatable reconciliation harder to maintain.
Does cost-control software replace an ERP?
Usually not. The ERP should remain authoritative for accounting transactions. Cost-control software should connect those actuals with commitments, forecasts, changes and project context while maintaining reconciliation to the financial system.
A practical starting point
Before selecting another tool, take one live project and map the current reporting cycle. List every field copied into the cost workbook; identify its authoritative source; mark every field manually re-entered or transformed; record who owns each forecast judgment and change decision; identify the reconciliation exceptions consuming the most controller time; and choose one contract or control account for a controlled pilot.
The first goal is not to eliminate every spreadsheet. It is to stop using a spreadsheet as the only place where the project’s cost position can be understood and defended.
Sources: US Government Accountability Office, Cost Estimating and Assessment Guide; US Department of Energy, Earned Value Management and EVMS Implementation Guidance; Project Management Institute, The Top 10 Challenges to Effective Cost Controls.





