Capex Invoice Processing: Why Capital Spend Breaks a Normal AP Workflow
One Approval, Many Invoices
Operating expenditure and capital expenditure look similar at the moment an invoice arrives. Both are a supplier bill with an amount, a date and a payment term. Almost everything else about them is different, and standard AP workflows are built for only one of the two.
An operating invoice is a self-contained decision. The service was delivered, the amount is right, someone with authority approves it, it gets paid. The approval question and the invoice arrive together.
A capital invoice is a fragment of a decision made much earlier. Someone built a business case for a warehouse fit-out, a production line, a fleet replacement or an ERP implementation. A committee approved a total value against an expected return. That approval may be eighteen months old by the time the fourth progress claim lands on an AP clerk’s desk.
At that point, the meaningful question is not “should we spend this money?” It was answered at business case stage. The question is narrower and harder: does this invoice belong to that approved project, does it fall within what remains of the approved value, and does the work it claims actually correspond to work performed?
Standard AP workflows cannot answer any of those, because they do not hold the project. So they fall back on what they can do, which is route the invoice to a manager for approval. That manager sees an invoice for a large amount from a supplier they may not recognise, relating to a project they may not own, with no visibility of what has already been billed against it. They approve it, because refusing is not a realistic option and the information needed to challenge it is not in front of them.
What gets lost
| Dimension | Operating expenditure | Capital expenditure |
|---|---|---|
| Approval point | Per invoice, at invoice time | Once, at business case, before commitment |
| Number of invoices per decision | Usually one | Many, over months or years |
| Validation basis | Goods receipt or service confirmation | Stage of completion against contract |
| Budget control | Period budget for a cost centre | Total project value, depleted over time |
| Accounting destination | Expense account, current period | Assets under construction, then depreciated |
| Timing driver for P&L | Invoice date | In-service date, via depreciation |
| Typical failure | Wrong coding or duplicate | Overrun found late, wrong capitalisation date |
The last row is the one with the largest financial consequence. An overrun on operating spend shows up in a monthly variance report while there is still time to respond. An overrun on a capital project routinely appears when the final invoice arrives and every pound of it is already committed and largely spent.
Controlling Commitment, Not Just Spend
The single most valuable change in capex control is measuring commitment rather than invoices. Capital projects are committed long before they are invoiced. When a purchase order is issued for USD 2 million of equipment, that money is effectively gone, even though nothing will be invoiced for four months.
A project tracked on invoiced value alone looks healthy right up to the moment it does not. A project tracked on committed value shows the overrun the day the order is raised, when options still exist: reduce scope, seek additional approval, or renegotiate.
This requires one piece of discipline that is easy to state and frequently missed: every purchase order raised against a capital project must carry the project identifier. Without that link, committed spend cannot be aggregated, and the live view is impossible. Where purchase requisition and PO processes already enforce structured data capture, adding the capex reference is a small extension. Where POs are raised ad hoc, it is the first thing to fix.
The live control view should show four numbers at all times.
| Measure | Definition | What it answers |
|---|---|---|
| Approved value | Total sanctioned at business case | What may be spent in total |
| Committed value | Sum of open POs carrying the project reference | What is already promised to suppliers |
| Invoiced value | Cumulative supplier invoices posted to the project | What has been billed so far |
| Remaining headroom | Approved less committed | What can still be ordered without re-approval |
Headroom, not remaining budget against invoices, is the number that should gate new orders. Teams operating this way catch overruns at commitment, which is the only point at which an overrun is still a decision rather than a fact. It is the capital equivalent of the real-time budget validation principle applied to operating spend.
Progress Billing: The Invoice Three-Way Matching Cannot Check
Conventional two-way and three-way matching compares invoice, purchase order and goods receipt. Capital projects frequently have no goods receipt, because what is being billed is not a delivered quantity but a stage of completion: foundations poured, first fix complete, thirty percent of the integration delivered.
This creates a validation gap that matters, because progress claims are where capital projects leak. Three controls close it.
Cumulative tracking against contract value. Each claim must be assessed against total billed to date, not in isolation. A claim for 20% looks reasonable until you notice that 95% has already been billed on a project that is visibly half finished.
Independent completion evidence. The stage claimed by the supplier needs confirmation from someone who is not the supplier, whether a project manager sign-off, a surveyor certificate or an inspection record. Approving a progress claim without it is approving the supplier’s own assessment of their own performance.
Retention tracking. Most capital contracts withhold a percentage of each payment until a defects liability period expires. Retention has to be tracked per contract and released long after the project closes, which is precisely why it is so often forgotten and becomes a dispute. This is the same discipline required in construction progress billing and retention, where the pattern is most developed.
| Capital invoice type | Validation basis | Control that must apply |
|---|---|---|
| Equipment purchase | Goods receipt against PO | Standard three-way matching |
| Progress claim | Certified stage of completion | Cumulative billing vs contract value, independent sign-off |
| Milestone payment | Contractual milestone achieved | Evidence the milestone was met, not merely invoiced |
| Variation or change order | Approved variation document | Confirm variation was sanctioned before work proceeded |
| Retention release | Expiry of defects liability period | Per-contract retention ledger, released on schedule |
| Professional fees | Engagement letter and deliverable | Test whether the cost is capitalisable or period expense |
Getting Capitalisation Timing Right
The accounting error with the largest profit impact is not miscoding a single invoice. It is capitalising the project at the wrong moment.
Costs accumulate in assets under construction while work is in progress, and no depreciation is charged because the asset is not yet in use. The transfer to the fixed asset register, and the start of depreciation, should happen when the asset is available for use in the condition management intended.
The threshold and criteria behind that judgement belong in a written accounts payable policy, alongside the related decision about when a multi-period cost becomes a prepaid expense rather than a capitalised asset. The common error is waiting for the last invoice. A production line commissioned in March but with a final supplier invoice disputed until September will, under that approach, carry no depreciation for six months. Profit is overstated throughout, the asset register is incomplete, and the correction when it comes is both material and awkward to explain.
The discipline is to decouple the two events. In-service date drives capitalisation and depreciation. Invoice settlement drives cash and the supplier balance. They are related but they are not the same event, and letting one wait for the other is how capital accounting goes wrong. Recognition principles for this sit in the property, plant and equipment guidance published by the IFRS Foundation, with interpretation available from IAS Plus and practical treatment from Corporate Finance Institute and Investopedia. Governance expectations for capital investment decisions are covered by the Institute of Management Accountants.
How Peakflo Helps
Peakflo carries the approved capital project through invoice processing as a control record rather than leaving it in a business case document nobody can see at approval time. Invoices are matched to their capex project automatically, and the approver is shown approved value, committed value from open purchase orders, cumulative invoiced value and remaining headroom at the moment of decision, so a progress claim is assessed against what the project has already consumed rather than on its own.
Cumulative progress billing is validated against contract value with claims exceeding expected completion routed as exceptions, retention is tracked per contract so balances are not forgotten when the project closes, and coding directs cost to assets under construction rather than to expense. Because budget management and approval workflows run on the same platform as invoice capture, with native connectors to systems such as SAP, overruns surface at commitment instead of at the final invoice. To see capex controls applied to your own projects, request a demo.
Our Verdict: Control the Project, Not the Invoice
After analysing where capital spend loses control, here is our recommendation.
Treat this as urgent if
- Capital projects regularly finish over budget without early warning
- Approvers see capex invoices with no visibility of the project or prior billing
- Progress claims are approved without independent completion evidence
- Assets sit in assets under construction long after they entered service
- Retention balances are discovered by supplier chasing rather than by your own records
Standard AP workflow is sufficient if
- Capital spend is occasional, low value and single-invoice
- Projects are owned end to end by one finance-literate manager
- No progress billing or retention is involved
Do not rely on invoice-level approval alone when
- A single project spans multiple periods and multiple suppliers
- Committed spend materially exceeds invoiced spend at any point
- The original approver has moved role since the business case
Our Recommendation: Start by making committed spend visible. Most organisations can produce approved value and invoiced value already; the missing number is almost always committed value from open purchase orders, and its absence is why overruns are discovered late. Adding the capex project reference to every PO is a small data discipline that converts capital budget control from a retrospective report into a live constraint.
Conclusion
Capital expenditure is governed carefully at the front end. Business cases are scrutinised, returns are modelled, committees deliberate. Then the approved project is handed to a process designed for a different kind of spending entirely, and the governance quietly evaporates between sanction and settlement.
The gap is structural rather than careless. AP workflows make one approval decision per invoice; capital projects make one decision covering many invoices. Nothing in a conventional workflow carries the project forward, so each invoice is judged in isolation by someone without the context to judge it.
Closing that gap does not require a separate capital management system for most organisations. It requires the approved project to travel with the invoice, committed spend to be tracked alongside invoiced spend, progress claims to be measured cumulatively against contract value, and capitalisation to follow the in-service date rather than the final payment. Those four disciplines convert capital spend from something reconciled after the fact into something actually controlled.
Frequently Asked Questions
What is the capex approval process?
The capex approval process is the authorisation of capital spend at project level, usually through a business case setting out the total investment, expected benefit and payback. Approval is granted once against a total value and an asset category, before commitments are made, rather than invoice by invoice as with operating expenditure.
Why do capex invoices break standard AP workflows?
Standard AP workflows assume one approval decision per invoice. Capital spend is approved once as a project and then invoiced many times over months or years, often as progress claims. The meaningful question at invoice stage is not whether to approve the spend but whether this invoice falls within an already-approved project and its remaining budget.
What is the difference between capex and opex?
Capital expenditure creates or improves an asset delivering benefit over multiple periods, so it is capitalised on the balance sheet and depreciated. Operating expenditure is consumed in the current period and expensed immediately. The distinction determines both profit timing and, in many jurisdictions, tax treatment.
What is an assets under construction account?
Assets under construction, sometimes called capital work in progress, is the balance sheet account accumulating project costs while an asset is being built or installed. Because the asset is not yet available for use, no depreciation is charged. The balance transfers to the fixed asset register when the asset is placed in service.
When should a capital project start depreciating?
Depreciation begins when the asset is available for use in the condition intended by management, not when the final invoice is received or paid. Delaying the transfer out of assets under construction until invoices are settled is a common error that understates depreciation and overstates profit in the intervening periods.
How do you control a capex budget overrun?
Track committed spend from open purchase orders alongside invoiced spend against the approved project value. Overruns surface at the point of commitment, when the order is raised, rather than when the final invoice arrives and the money is already spent. Controlling only invoiced value detects the overrun too late to act on it.
What is progress billing on a capital project?
Progress billing is a supplier invoice covering a percentage of work completed rather than a delivered quantity of goods. It cannot be validated by conventional three-way matching because there is no goods receipt, so it requires independent confirmation of the completion stage claimed and tracking of cumulative billing against the contract value.
What costs can be capitalised into a fixed asset?
Generally the purchase price plus any cost directly attributable to bringing the asset to its location and working condition, such as delivery, installation, site preparation and professional fees directly related to acquisition. Training, general administrative overhead and ongoing maintenance are normally expensed rather than capitalised.
Why is retention withheld on capital contracts?
Retention is a percentage of each progress payment withheld until defects liability expires, protecting the buyer against incomplete or defective work. It must be tracked separately per contract because it becomes payable long after the project closes, and forgotten retention balances are a frequent source of supplier disputes.
How should capex invoices be coded?
Capital invoices should be coded to the project and to assets under construction rather than to an expense account, carrying the capex project identifier so cost accumulates against the approved total. Miscoding capital spend to expense both understates the asset and distorts the period result.
What happens if capex is wrongly expensed?
Wrongly expensing capital spend understates assets and profit in the current period and overstates profit in later periods, because no depreciation follows. It can also create tax consequences where capital allowances differ from expense deductions. The reverse error, capitalising an expense, overstates profit immediately and is the treatment auditors scrutinise most closely.
Can capex invoice processing be automated?
Yes. Matching invoices to the approved capex project, tracking committed and invoiced spend against the approved total, validating cumulative progress billing against contract value, tracking retention, and routing only genuine exceptions for human decision can all be automated. What cannot be automated is the capitalisation judgement itself, which should follow a documented policy.