Revenue Recognition - Contract Analysis is where ERP discipline either begins or breaks.
ASC 606 / IFRS 15 Performance Obligation Identification and SSP Allocation 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: Zero manual journal entries for revenue allocation; revenue recognized in the correct period; disclosure reports pass external audit without adjustment.
The control flow a finance team actually needs.
Step 1
Multi-Element Contract Entry With...
Step 2
Enforce SSP-Based Allocation Using...
Step 3
Lock Allocation On Contract Inception
Step 4
Automatically Trigger Recognition...
Step 5
Generate ASC 606 / IFRS 15 Compliant...
The ERP surface involved.
Module
Revenue Recognition - Contract Analysis
Actors
Revenue Accountant, Contract Manager, ERP Revenue Engine
Tier
Tier 2
Finance area
Project & Service Management (PSA) and Revenue Recognition
Region lens
US and UK finance teams
Publication date
June 3, 2026
Support multi-element contract entry with unlimited performance obligations; enforce SSP-based allocation using relative fair value method; lock allocation on contract inception; automatically trigger recognition events (point-in-time vs. over-time) based on obligation type; generate ASC 606 / IFRS 15 compliant disclosure reports; prevent manual GL override without documented exception; audit trail records every allocation change with user, timestamp, and rationale.
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 multi-element contract entry with unlimited performance obligations | Given a multi-element contract with software license + implementation + support entered with SSP values per element |
| Control 2 | enforce SSP-based allocation using relative fair value method | when the contract is saved and allocation locked |
| Control 3 | lock allocation on contract inception | then total transaction price is distributed across obligations using relative SSP ratios, each obligation has a recognition schedule (point-in-time or over-time), and GL postings match recognized amounts per period |
| Control 4 | automatically trigger recognition events (point-in-time vs. over-time) based on obligation type | negative) when a manual GL override is attempted without a documented exception then the system rejects with 403 and error code REVENUE_MANUAL_OVERRIDE_BLOCKED. |
| Control 5 | generate ASC 606 / IFRS 15 compliant disclosure reports | Zero manual journal entries for revenue allocation; revenue recognized in the correct period; disclosure reports pass external audit without adjustment. |
| Control 6 | prevent manual GL override without documented exception | Zero manual journal entries for revenue allocation; revenue recognized in the correct period; disclosure reports pass external audit without adjustment. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A new multi-element customer contract (software license + implementation services + one-year support) is entered into the ERP. The revenue accountant identifies three distinct performance obligations and enters standalone selling prices (SSPs) for each element. The ERP allocates the total transaction price across the obligations using relative SSP ratios and locks the allocation. As each obligation is satisfied, the ERP automatically schedules and posts the recognized revenue to the correct GL accounts, generating a compliant revenue waterfall report. |
| Control rules | Support multi-element contract entry with unlimited performance obligations; enforce SSP-based allocation using relative fair value method; lock allocation on contract inception; automatically trigger recognition events (point-in-time vs. over-time) based on obligation type; generate ASC 606 / IFRS 15 compliant disclosure reports; prevent manual GL override without documented exception; audit trail records every allocation change with user, timestamp, and rationale. |
| Acceptance proof | Given a multi-element contract with software license + implementation + support entered with SSP values per element; when the contract is saved and allocation locked; then total transaction price is distributed across obligations using relative SSP ratios, each obligation has a recognition schedule (point-in-time or over-time), and GL postings match recognized amounts per period; (negative) when a manual GL override is attempted without a documented exception then the system rejects with 403 and error code REVENUE_MANUAL_OVERRIDE_BLOCKED. |
| 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
`revenue_contract` { external_id: string, customer_id: string, total_transaction_price_minor: int64, currency_code: char(3), status: enum(DRAFT,ACTIVE,MODIFIED,COMPLETED,TERMINATED), inception_date: date }; `performance_obligation` { external_id: string, contract_id: string, description: string, ssp_minor: int64, currency_code: char(3), allocated_amount_minor: int64, recognition_pattern: enum(POINT_IN_TIME,OVER_TIME), status: enum(OPEN,PARTIALLY_SATISFIED,FULLY_SATISFIED) }; `revenue_recognition_event` { obligation_id: string, period_date: date, amount_minor: int64, currency_code: char(3), journal_entry_id: string }; (reference, product may differ).API and events
`POST /v1/revenue-contracts` { external_id, customer_id, total_transaction_price_minor, currency_code, performance_obligations: [{external_id, description, ssp_minor, recognition_pattern}] } -> 201 { contract_id, obligations_with_allocated_amounts }; `POST /v1/revenue-contracts/{id}/lock-allocation` -> 200 { locked_at }; `POST /v1/revenue-contracts/{id}/recognize` { period_date } -> 201 { journal_entry_ids }; `GET /v1/revenue-contracts/{id}/disclosure-report`; emits `revenue.allocation_locked` and `revenue.recognized` events; idempotent via `external_id`.State transitions
`DRAFT -> ACTIVE` (on allocation lock); `ACTIVE -> MODIFIED` (on contract modification); `ACTIVE -> COMPLETED` (all obligations fully satisfied); terminal `TERMINATED`; guard: allocation cannot be re-locked once ACTIVE without a contract modification record; revenue posting blocked if obligation status is FULLY_SATISFIED.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.