Fixed Assets - CIP is where ERP discipline either begins or breaks.
Construction-in-Progress (CIP) Tracking and Capitalization 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: All capital project costs traceable from originating invoice through CIP to placed-in-service asset; zero CIP balance for completed projects; depreciation begins in the correct period.
The control flow a finance team actually needs.
Step 1
CIP Project Tracks Costs By Project ID...
Step 2
CIP Aging Report Shows Projects By Open...
Step 3
Partial Capitalization Supported
Step 4
CIP-To-Asset Transfer Is A Single ACID...
Step 5
In-Service Date Be On Or After Last...
The ERP surface involved.
Module
Fixed Assets - CIP
Actors
Project Manager, Fixed Asset Accountant, ERP System
Tier
Tier 1
Finance area
Fixed Assets & Lease Management
Region lens
US and UK finance teams
Publication date
June 14, 2026
CIP project tracks costs by project ID with unlimited line items; CIP aging report shows projects by open days with drill-down to source transactions; partial capitalization supported (some costs capitalized, some expensed or remaining in CIP); CIP-to-asset transfer is a single ACID journal debit asset / credit CIP; in-service date must be on or after last cost entry date; system flags CIP projects open longer than configurable threshold (e.g., 180 days) for review; transfer audit trail links asset master to originating CIP project and all contributing invoices.
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 | CIP project tracks costs by project ID with unlimited line items | Given costs accumulated in a CIP project (vendor invoices, labor transfers, overhead allocations) with a project_id and CIP GL account |
| Control 2 | CIP aging report shows projects by open days with drill-down to source transactions | when the fixed asset accountant initiates a CIP-to-asset transfer specifying asset category, useful life, and in-service date |
| Control 3 | partial capitalization supported (some costs capitalized, some expensed or remaining in CIP | then the system creates the asset master, posts a single ACID JE (debit fixed asset account, credit CIP account) for the full capitalized amount, and places the asset on the depreciation schedule from the in-service date |
| Control 4 | CIP-to-asset transfer is a single ACID journal debit asset / credit CIP | negative) when the in-service date is before the last cost entry date then the system rejects with 422 IN_SERVICE_DATE_BEFORE_LAST_COST. |
| Control 5 | in-service date must be on or after last cost entry date | All capital project costs traceable from originating invoice through CIP to placed-in-service asset; zero CIP balance for completed projects; depreciation begins in the correct period. |
| Control 6 | | All capital project costs traceable from originating invoice through CIP to placed-in-service asset; zero CIP balance for completed projects; depreciation begins in the correct period. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Costs for a capital construction project are accumulated in a CIP project bucket: vendor invoices, internal labor transfers, and overhead allocations are coded to the CIP GL account and project ID. The fixed asset accountant monitors CIP aging monthly. Upon project completion, the accountant initiates a CIP-to-asset transfer: selects the CIP project, confirms total accumulated costs, assigns an asset category, useful life, and in-service date. The system creates the asset master record, debits the fixed asset account, and credits the CIP account for the full capitalized amount. Depreciation begins from the in-service date on the next depreciation run. |
| Control rules | |
| Acceptance proof | Given costs accumulated in a CIP project (vendor invoices, labor transfers, overhead allocations) with a project_id and CIP GL account; when the fixed asset accountant initiates a CIP-to-asset transfer specifying asset category, useful life, and in-service date; then the system creates the asset master, posts a single ACID JE (debit fixed asset account, credit CIP account) for the full capitalized amount, and places the asset on the depreciation schedule from the in-service date; (negative) when the in-service date is before the last cost entry date then the system rejects with 422 IN_SERVICE_DATE_BEFORE_LAST_COST. |
| 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
`cip_projects` { id: string, external_id: string, entity_id: string, project_id: string, total_cost_minor: int64, currency_code: char(3), cip_gl_account_id: string, open_days: int, status: enum(OPEN,PARTIALLY_CAPITALIZED,CAPITALIZED) }; `cip_cost_lines` { id: string, cip_project_id: string, source_invoice_id: string, amount_minor: int64, currency_code: char(3), entry_date: date }; `cip_transfers` { id: string, cip_project_id: string, fixed_asset_id: string, transfer_amount_minor: int64, currency_code: char(3), transfer_je_id: string }; (reference, product may differ).API and events
`POST /v1/cip-projects` { entity_id, project_id, cip_gl_account_id, external_id } -> 201 { id, status: OPEN }; `POST /v1/cip-projects/{id}/cost-lines` { source_invoice_id, amount_minor, currency_code, entry_date } -> 201 { id }; `POST /v1/cip-projects/{id}/transfer` { asset_category_id, useful_life_periods, in_service_date, transfer_amount_minor, currency_code, external_id } -> 201 { fixed_asset_id, transfer_je_id }; `GET /v1/cip-projects/aging-report`; emits `cip.capitalized` event; idempotent via `external_id`.State transitions
`OPEN -> PARTIALLY_CAPITALIZED -> CAPITALIZED`; guard: transfer_amount_minor must be <= total accumulated CIP cost; in_service_date >= last cost entry date; CAPITALIZED projects excluded from future cost accumulation.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.