CapEx Planning is where ERP discipline either begins or breaks.
Capital Expenditure (CapEx) Planning and Approval looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Approved annual CapEx budget with project-level tracking, enabling CFO to monitor capital deployment against approved plans and project future depreciation impact.
The control flow a finance team actually needs.
Step 1
CapEx Requests Capture Asset Category,...
Step 2
Approval Workflow Sequential Or...
Step 3
Approved Budget Auto-Generate A...
Step 4
Monthly CapEx Actuals Be Imported From...
Step 5
Committed Spend Be Tracked Separately...
The ERP surface involved.
Module
CapEx Planning
Actors
Department Manager, Controller, CFO, Fixed Asset Manager
Tier
Tier 1
Finance area
Budgeting, Planning & FP&A
Region lens
US and UK finance teams
Publication date
April 10, 2026
CapEx requests must capture asset category, estimated cost (amount_minor + currency_code), expected in-service date, useful life in months, and depreciation method; approval workflow must support sequential or parallel approvals by department manager → controller → CFO with configurable thresholds; approved budget must auto-generate a projected depreciation schedule by month for the asset life; monthly CapEx actuals must be imported from the fixed asset module; committed spend must be tracked separately from invoiced actuals; CapEx budget must roll up to entity and consolidated levels.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | CapEx requests must capture asset category, estimated cost (amount_minor + currency_code), expected in-service date, useful life in months, and depreciation method | Given a CapEx budget envelope approved by CFO |
| Control 2 | approval workflow must support sequential or parallel approvals by department manager → controller → CFO with configurable thresholds | when Department Manager submits a CapEx request with asset_category, estimated_cost_minor, currency_code, expected_in_service_date, useful_life_months, and depreciation_method |
| Control 3 | approved budget must auto-generate a projected depreciation schedule by month for the asset life | then system routes through approval chain and upon CFO approval auto-generates a projected depreciation schedule by month for the asset life |
| Control 4 | monthly CapEx actuals must be imported from the fixed asset module | |
| Control 5 | committed spend must be tracked separately from invoiced actuals | Approved annual CapEx budget with project-level tracking, enabling CFO to monitor capital deployment against approved plans and project future depreciation impact. |
| Control 6 | CapEx budget must roll up to entity and consolidated levels. | Approved annual CapEx budget with project-level tracking, enabling CFO to monitor capital deployment against approved plans and project future depreciation impact. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | At the start of the budgeting cycle, Department Managers submit CapEx project requests including asset type, cost, expected useful life, and business justification. Controller reviews requests against the CapEx budget envelope and scores them by strategic priority. CFO approves or rejects individual requests, setting a total CapEx budget for the year. Approved CapEx projects are entered into the planning system with monthly spend profiles and depreciation schedules. Fixed Asset Manager tracks actual CapEx spend against budget each month. System generates a CapEx budget vs. actual report showing approved projects, committed spend, and remaining budget. |
| Control rules | CapEx requests must capture asset category, estimated cost (amount_minor + currency_code), expected in-service date, useful life in months, and depreciation method; approval workflow must support sequential or parallel approvals by department manager → controller → CFO with configurable thresholds; approved budget must auto-generate a projected depreciation schedule by month for the asset life; monthly CapEx actuals must be imported from the fixed asset module; committed spend must be tracked separately from invoiced actuals; CapEx budget must roll up to entity and consolidated levels. |
| Acceptance proof | |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`capex_request` { id: cr_*, budget_version_id: string, entity_id: string, asset_category: string, estimated_cost_minor: int64, currency_code: char(3), expected_in_service_date: date, useful_life_months: int, depreciation_method: enum(STRAIGHT_LINE/DECLINING_BALANCE), status: enum(DRAFT/PENDING_APPROVAL/APPROVED/REJECTED), external_id: string }; `depreciation_schedule_line` { id: dsl_*, capex_request_id: string, period: date, depreciation_minor: int64, currency_code: char(3) }; (reference, product may differ).API and events
`POST /v1/capex-requests` { asset_category, estimated_cost_minor, currency_code, expected_in_service_date, useful_life_months, depreciation_method, external_id } -> 201 { id, status: DRAFT }; `POST /v1/capex-requests/{id}/submit`; `GET /v1/capex-requests/{id}/depreciation-schedule`; emits `capex.request_approved` event; idempotent via `external_id`.State transitions
`DRAFT -> PENDING_APPROVAL -> APPROVED -> COMMITTED`; terminal `REJECTED`; guard: APPROVED requires CFO authorization; depreciation schedule generated on APPROVED transition.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.