Revenue Recognition - Over-Time Methods is where ERP discipline either begins or breaks.
Percentage-of-Completion (POC) Revenue Recognition for Fixed-Fee Projects 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: Revenue recognized within two business days of period close; overbilling/underbilling schedule ready for audit on demand; zero manual catch-up errors.
The control flow a finance team actually needs.
Step 1
Cost-To-Cost, Units-Of-Delivery, And...
Step 2
ETC Updates Are Versioned With Approver...
Step 3
Catch-Up Revenue Calculation Is...
Step 4
Deferred Revenue Balance Updated Each...
Step 5
Recognition Blocked Until PM Certifies...
The ERP surface involved.
Module
Revenue Recognition - Over-Time Methods
Actors
Project Controller, Revenue Accountant, ERP
Tier
Tier 2
Finance area
Project & Service Management (PSA) and Revenue Recognition
Region lens
US and UK finance teams
Publication date
June 5, 2026
Support cost-to-cost, units-of-delivery, and milestone-based POC methods; ETC updates are versioned with approver and timestamp; catch-up revenue calculation is automatic and auditable; deferred revenue balance updated each period; recognition blocked until PM certifies completion percentage; comparative period reporting shows progression; GAAP-compliant overbilling/underbilling analysis generated automatically.
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 | Support cost-to-cost, units-of-delivery, and milestone-based POC methods | Given a fixed-fee project configured for cost-to-cost POC recognition |
| Control 2 | ETC updates are versioned with approver and timestamp | when the project controller certifies costs incurred and ETC for the period |
| Control 3 | catch-up revenue calculation is automatic and auditable | then the ERP computes completion percentage, calculates cumulative revenue earned, posts the incremental catch-up journal, and updates deferred/accrued revenue balances |
| Control 4 | deferred revenue balance updated each period | negative) when revenue recognition is attempted without project controller ETC certification then the system rejects with 422 and error code POC_CERTIFICATION_REQUIRED. |
| Control 5 | recognition blocked until PM certifies completion percentage | Revenue recognized within two business days of period close; overbilling/underbilling schedule ready for audit on demand; zero manual catch-up errors. |
| Control 6 | comparative period reporting shows progression | Revenue recognized within two business days of period close; overbilling/underbilling schedule ready for audit on demand; zero manual catch-up errors. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A fixed-fee engineering project is configured for POC revenue recognition using the cost-to-cost input method. Each accounting period, the project controller certifies total costs incurred and re-estimates the cost to complete (ETC). The ERP calculates the completion percentage, applies it to the contract price, and determines cumulative revenue earned to date. A catch-up journal entry is posted for the incremental revenue earned in the period, with deferred or accrued revenue recognized accordingly. |
| Control rules | Support cost-to-cost, units-of-delivery, and milestone-based POC methods; ETC updates are versioned with approver and timestamp; catch-up revenue calculation is automatic and auditable; deferred revenue balance updated each period; recognition blocked until PM certifies completion percentage; comparative period reporting shows progression; GAAP-compliant overbilling/underbilling analysis generated automatically. |
| Acceptance proof | Given a fixed-fee project configured for cost-to-cost POC recognition; when the project controller certifies costs incurred and ETC for the period; then the ERP computes completion percentage, calculates cumulative revenue earned, posts the incremental catch-up journal, and updates deferred/accrued revenue balances; (negative) when revenue recognition is attempted without project controller ETC certification then the system rejects with 422 and error code POC_CERTIFICATION_REQUIRED. |
| 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
`poc_project` { external_id: string, project_id: string, contract_price_minor: int64, currency_code: char(3), poc_method: enum(COST_TO_COST,UNITS_OF_DELIVERY,MILESTONE), status: enum(ACTIVE,COMPLETED) }; `poc_period_entry` { external_id: string, project_id: string, period: date, costs_incurred_minor: int64, etc_minor: int64, completion_pct: decimal, cumulative_revenue_earned_minor: int64, certified_by: string, certified_at: timestamp }; `poc_catch_up_journal` { period_entry_id: string, journal_entry_id: string, incremental_revenue_minor: int64, currency_code: char(3) }; (reference, product may differ).API and events
`POST /v1/poc-projects` { external_id, project_id, contract_price_minor, currency_code, poc_method } -> 201 { poc_project_id }; `POST /v1/poc-projects/{id}/period-entries` { external_id, period, costs_incurred_minor, etc_minor } -> 201 { completion_pct, cumulative_revenue_earned_minor }; `POST /v1/poc-period-entries/{id}/certify` -> 200 { certified_at }; `POST /v1/poc-period-entries/{id}/recognize` -> 201 { journal_entry_id, incremental_revenue_minor }; `GET /v1/poc-projects/{id}/overbilling-analysis`; emits `revenue.poc_recognized` event; idempotent via `external_id`.State transitions
`DRAFT -> CERTIFIED -> RECOGNIZED` (per period entry); `ACTIVE -> COMPLETED` (project level on 100% recognition); terminal `VOID`; guard: RECOGNIZED period entry cannot be modified; recognition blocked until status is CERTIFIED.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.