In real projects...

Capex in ERP dies in email threads unless requests, approvals, and project IDs bind to actuals. Compare rolling forecast discipline in rolling forecasts.

A common issue we see...

Approved projects without budget envelopes—or POs against projects that were never funded in the system.

For example...

  1. Enforce stage gates: idea → business case → approved budget → PO.
  2. Link asset capitalization rules to project tasks and receipts.
  3. Freeze unauthorized transfers between cost centers mid-year.
  4. Reforecast commitments vs actuals quarterly.
  5. Post-completion audits: did benefits materialize?

Common mistakes (and how to avoid them)

  • Letting IT projects bypass finance approval paths.
  • Ignoring asset tagging and physical inventory loops.
  • Weak linkage between maintenance capex and operations KPIs.
  • Spreadsheet “shadow approvals” after go-live.

Note: Representative scenarios for education; align with accounting policy.

Methodology: This article is an educational guide built from public ERP documentation and widely used implementation patterns. Any mini “scenario walkthroughs” are illustrative and not client-specific.

CapEx approval failures are usually process failures, not system failures. This walkthrough connects the investment request to a traceable commitment in the ERP so approved spend can be monitored from day one.

  1. Define the investment request template: budget code, project classification, expected benefit, total cost estimate, and sponsor name.
  2. Route requests through an approval workflow based on value thresholds—different tiers require different levels of financial and executive sign-off.
  3. Validate that the request maps to an approved budget line before final approval; unapproved budget line requests should trigger a separate budget modification workflow.
  4. Create a capital project or work order in the ERP upon final approval, and assign a unique project code that all subsequent expenditure must reference.
  5. Monitor committed and actual spend against the approved budget by project code, and generate alerts when actuals or commitments approach the approved limit.
  6. Close the project in the ERP at physical completion, reconcile final costs, and transfer completed assets to the fixed asset register.

Artifacts to expect:

  • Investment request with business case, cost estimate, and sponsor sign-off.
  • Approval record at each threshold tier.
  • ERP project or work order with approved budget and spend profile.
  • Commitment register updated as purchase orders are raised.
  • Project close report with final costs and asset transfer documentation.

What usually goes wrong (failure modes)

  • Spend begins before a project code is created in the ERP
    Invoices arrive before the project is set up, so they are posted to a suspense account or general cost centre without budget visibility.
    Mitigation: Make project code creation a mandatory step in the approval workflow before any procurement begins. Purchasing should not raise a purchase order without a valid project code.
  • Budget overspend is not visible until the invoice arrives
    Committed costs—purchase orders and subcontracts—are not tracked in the ERP against the project budget, so the apparent available budget is inflated.
    Mitigation: Configure commitment accounting so POs and contractual commitments reduce available budget at the point of commitment, not the point of invoice.
  • Approved projects are expanded in scope without a formal amendment
    Project managers add scope informally, and additional costs are posted to the original project code without re-approval.
    Mitigation: Require a formal budget amendment for any scope change that increases the approved total. The amendment should go through the same approval tiers as the original request.

Controls and evidence checklist

  • Require a valid ERP project code on all CapEx purchase orders and contracts.
  • Configure commitment accounting so POs reduce available budget at the point of raising the order.
  • Enforce approval thresholds by value tier with documented escalation paths.
  • Run a monthly committed versus budget report per project for sponsor review.
  • Require a formal budget amendment for any scope or cost increase above the original approval.
  • Close projects in the ERP at physical completion and reconcile to the fixed asset register.

Implementation checklist

  1. Define approval tiers and thresholds before configuring the ERP workflow.
  2. Map capital request categories to budget codes and ensure the budget structure supports project-level tracking.
  3. Configure commitment accounting and test with representative PO and invoice scenarios.
  4. Train project sponsors on how to monitor committed and actual spend by project code.
  5. Run a pilot with three to five active projects before enabling the workflow for all capital spend.
  6. Review the first full capital cycle and adjust threshold rules and reporting based on observed behaviour.

Frequently asked questions

Where do teams usually lose time in ERP CapEx approval workflows?

Most time is lost when investment requests arrive without a business case template, forcing finance to request clarifications before the approval workflow can even start. Defining a standard request format—budget code, project classification, expected benefit, and sponsor name—before the capital cycle opens eliminates the most common bottleneck. A standard template also makes comparative analysis of competing requests faster and more objective.

What should we review during the first two capital cycles?

Confirm that every approved request has a corresponding project code in the ERP, and that all expenditure is coded to the correct project before invoices are matched. Unapproved commitments and missing project links are the two most common audit findings in capital expenditure reviews. Also review whether commitment accounting is correctly reducing available budget when purchase orders are raised.

When should we adjust approval thresholds and workflow rules?

Adjust approval thresholds and escalation rules when the same categories of requests are consistently approved without challenge, or when approval queues are bottlenecked at the same level in the hierarchy. Review annually as part of the budget cycle to reflect changes in business priorities and risk appetite. A threshold that made sense three years ago may no longer reflect the current risk profile of your capital spend.

Sources

Conclusion and next steps

Capital expenditure control in ERP depends on connecting the approval decision to a trackable project commitment before any spending begins.

Start by enforcing project code creation at the point of approval for the highest-value projects. Once the pattern is reliable, extend commitment accounting and monitoring to smaller capital items.