Revenue Recognition - Contract Modifications is where ERP discipline either begins or breaks.
Contract Modification Handling (Scope Change, Price Change, Termination) 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: Contract modification processed within one business day; prior revenue unchanged; updated schedules reconcile to modified contract value.
The control flow a finance team actually needs.
Step 1
Modification Types Supported: Add...
Step 2
Modification Date Determines Treatment...
Step 3
Prior-Period Recognized Revenue Locked
Step 4
SSP Reallocation Computed Automatically
Step 5
Cumulative Catch-Up Journal Entry...
The ERP surface involved.
Module
Revenue Recognition - Contract Modifications
Actors
Contract Manager, 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 7, 2026
Modification types supported: add distinct goods/services (new contract), modify existing obligations (cumulative catch-up), and combined; modification date determines treatment split; prior-period recognized revenue locked; SSP reallocation computed automatically; cumulative catch-up journal entry generated with supporting memo; disclosure notes updated automatically; approval workflow required for modifications above a configurable threshold.
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 | Modification types supported: add distinct goods/services (new contract), modify existing obligations (cumulative catch-up), and combined | Given an active contract with locked SSP allocation |
| Control 2 | modification date determines treatment split | when a contract modification is recorded with additional scope, treatment type, and modification date |
| Control 3 | prior-period recognized revenue locked | then SSP is reallocated across all obligations, a catch-up adjustment journal is posted for the modification period, prior-period recognized revenue is unchanged, and all open revenue schedules are updated |
| Control 4 | SSP reallocation computed automatically | negative) when a modification above the configurable threshold is submitted without approval then the system rejects with 403 and error code CONTRACT_MODIFICATION_APPROVAL_REQUIRED. |
| Control 5 | cumulative catch-up journal entry generated with supporting memo | Contract modification processed within one business day; prior revenue unchanged; updated schedules reconcile to modified contract value. |
| Control 6 | disclosure notes updated automatically | Contract modification processed within one business day; prior revenue unchanged; updated schedules reconcile to modified contract value. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Mid-project, a customer negotiates an additional $50,000 scope of work and extends the timeline by three months. The contract manager records the modification in the ERP, selecting the treatment: prospective (new contract), cumulative catch-up, or combined approach per ASC 606 guidance. The ERP recalculates SSP allocation across all performance obligations, posts the catch-up adjustment, and updates all open revenue schedules. Revenue recognized in prior periods is unchanged; only the prospective amounts are restated. |
| Control rules | Modification types supported: add distinct goods/services (new contract), modify existing obligations (cumulative catch-up), and combined; modification date determines treatment split; prior-period recognized revenue locked; SSP reallocation computed automatically; cumulative catch-up journal entry generated with supporting memo; disclosure notes updated automatically; approval workflow required for modifications above a configurable threshold. |
| Acceptance proof | Given an active contract with locked SSP allocation; when a contract modification is recorded with additional scope, treatment type, and modification date; then SSP is reallocated across all obligations, a catch-up adjustment journal is posted for the modification period, prior-period recognized revenue is unchanged, and all open revenue schedules are updated; (negative) when a modification above the configurable threshold is submitted without approval then the system rejects with 403 and error code CONTRACT_MODIFICATION_APPROVAL_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
`contract_modification` { external_id: string, contract_id: string, modification_date: date, treatment: enum(NEW_CONTRACT,CUMULATIVE_CATCHUP,COMBINED), additional_value_minor: int64, currency_code: char(3), approved_by: string, approved_at: timestamp, status: enum(PENDING_APPROVAL,APPROVED,REJECTED) }; `catchup_adjustment` { modification_id: string, journal_entry_id: string, amount_minor: int64, currency_code: char(3), period_date: date }; (reference, product may differ).API and events
`POST /v1/revenue-contracts/{id}/modifications` { external_id, modification_date, treatment, additional_value_minor, currency_code } -> 201 { modification_id, reallocated_obligations }; `POST /v1/contract-modifications/{id}/approve` -> 200 { approved_at, catchup_journal_entry_id }; `GET /v1/revenue-contracts/{id}/modification-history`; emits `contract.modification_approved` and `revenue.catchup_posted` events; idempotent via `external_id`.State transitions
`PENDING_APPROVAL -> APPROVED -> APPLIED`; terminal `REJECTED`; guard: prior-period recognized revenue records are immutable after period close; APPLIED modification locks allocation update and prevents re-application.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.