Revenue Recognition - Subscription / Recurring is where ERP discipline either begins or breaks.
Subscription and Usage-Based Revenue Recognition 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 regardless of invoice timing; variable consideration estimates within 5% of actuals on average; zero over-recognized variable revenue in audited financials.
The control flow a finance team actually needs.
Step 1
Flat, Tiered, Volume, And Per-Unit...
Step 2
Variable Consideration Estimation...
Step 3
Accrual Journal Auto-Reversed On Actual...
Step 4
True-Up Calculation When Actuals Differ...
Step 5
Revenue Constraint Rule Prevents...
The ERP surface involved.
Module
Revenue Recognition - Subscription / Recurring
Actors
Billing System, 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 8, 2026
Support flat, tiered, volume, and per-unit usage pricing models; variable consideration estimation method configurable (most-likely-amount vs. expected-value); accrual journal auto-reversed on actual invoice posting; true-up calculation when actuals differ from estimate; revenue constraint rule prevents over-recognition of variable consideration; usage data import via API or CSV; multi-currency support with functional currency conversion; revenue by product line reporting.
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 flat, tiered, volume, and per-unit usage pricing models | Given a SaaS customer with flat platform fee plus usage-based pricing |
| Control 2 | variable consideration estimation method configurable (most-likely-amount vs. expected-value | when monthly metered usage data is pushed and revenue is recognized using the most-likely-amount method |
| Control 3 | accrual journal auto-reversed on actual invoice posting | then an invoice is generated, revenue is posted for the period, and variable consideration accrual auto-reverses when actual invoice is posted |
| Control 4 | true-up calculation when actuals differ from estimate | negative) when usage data import contains negative usage quantities then the system rejects with 422 and error code INVALID_USAGE_DATA. |
| Control 5 | revenue constraint rule prevents over-recognition of variable consideration | Revenue recognized within two business days of period close regardless of invoice timing; variable consideration estimates within 5% of actuals on average; zero over-recognized variable revenue in audited financials. |
| Control 6 | usage data import via API or CSV | Revenue recognized within two business days of period close regardless of invoice timing; variable consideration estimates within 5% of actuals on average; zero over-recognized variable revenue in audited financials. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A SaaS customer is billed monthly based on API call volume (usage-based) plus a flat platform fee. Each month, the billing system pushes metered usage data to the ERP. The ERP calculates the variable consideration using the most-likely-amount method, applies any usage-tier pricing, generates the invoice, and posts revenue recognized in the period. Estimated variable consideration is accrued at month-end when actual usage data is delayed. |
| Control rules | Support flat, tiered, volume, and per-unit usage pricing models; variable consideration estimation method configurable (most-likely-amount vs. expected-value); accrual journal auto-reversed on actual invoice posting; true-up calculation when actuals differ from estimate; revenue constraint rule prevents over-recognition of variable consideration; usage data import via API or CSV; multi-currency support with functional currency conversion; revenue by product line reporting. |
| Acceptance proof | Given a SaaS customer with flat platform fee plus usage-based pricing; when monthly metered usage data is pushed and revenue is recognized using the most-likely-amount method; then an invoice is generated, revenue is posted for the period, and variable consideration accrual auto-reverses when actual invoice is posted; (negative) when usage data import contains negative usage quantities then the system rejects with 422 and error code INVALID_USAGE_DATA. |
| 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
`subscription_contract` { external_id: string, customer_id: string, pricing_model: enum(FLAT,TIERED,VOLUME,PER_UNIT), platform_fee_minor: int64, currency_code: char(3), variable_consideration_method: enum(MOST_LIKELY,EXPECTED_VALUE), status: enum(ACTIVE,SUSPENDED,TERMINATED) }; `usage_record` { external_id: string, contract_id: string, period_date: date, quantity: decimal, unit_price_minor: int64, currency_code: char(3), actual: bool, estimated: bool }; `variable_consideration_accrual` { contract_id: string, period_date: date, estimated_amount_minor: int64, currency_code: char(3), reversed: bool, journal_entry_id: string }; (reference, product may differ).API and events
`POST /v1/subscription-contracts` { external_id, customer_id, pricing_model, platform_fee_minor, currency_code, variable_consideration_method } -> 201 { contract_id }; `POST /v1/subscription-contracts/{id}/usage` { external_id, period_date, quantity, actual } -> 201 { usage_record_id, calculated_amount_minor }; `POST /v1/subscription-contracts/{id}/recognize` { period_date } -> 201 { invoice_id, journal_entry_id }; `GET /v1/subscription-contracts/{id}/revenue-by-product-line`; emits `revenue.subscription_recognized` and `revenue.accrual_reversed` events; idempotent via `external_id`.State transitions
`ACTIVE -> SUSPENDED -> ACTIVE`; terminal `TERMINATED`; guard: variable consideration over-recognition blocked by constraint rule; accrual reversal auto-triggered on actual invoice posting.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.