Financial Statements is where ERP discipline either begins or breaks.
Consolidated Balance Sheet Generation 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: Balance sheet always mathematically balanced; equity roll-forward eliminates manual computation; IFRS/GAAP classification applied consistently without manual override.
The control flow a finance team actually needs.
Step 1
Balance Sheet Template Configurable Per...
Step 2
Equity Roll-Forward Computing Retained...
Step 3
AOCI Roll-Forward
Step 4
Minority Interest Line Populated From...
Step 5
Balance Check Assertion Enforced Before...
The ERP surface involved.
Module
Financial Statements
Actors
Group Controller, Reporting System, External Auditor
Tier
Tier 2
Finance area
Financial Close, Consolidation & Statutory Reporting
Region lens
US and UK finance teams
Publication date
April 4, 2026
Balance sheet template configurable per IFRS/GAAP with current/non-current classification rules; equity roll-forward computing retained earnings from prior closing balance plus net income less dividends; AOCI roll-forward including CTA, unrealized gains/losses; minority interest line populated from consolidation calculation; balance check assertion (assets = liabilities + equity) enforced before approval; drill-through from each line to GL; comparative prior-year column; note-disclosure tagging; export to PDF, Excel, XBRL; linked to income statement and cash flow as one package; locked version stored with auditor-accessible permalink.
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 | Balance sheet template configurable per IFRS/GAAP with current/non-current classification rules | Given an approved income statement and consolidated trial balance |
| Control 2 | equity roll-forward computing retained earnings from prior closing balance plus net income less dividends | when the balance sheet is generated |
| Control 3 | AOCI roll-forward including CTA, unrealized gains/losses | then assets equal liabilities plus equity (enforced assertion), equity section includes retained earnings roll-forward, AOCI, and minority interest, comparative prior-year column is present |
| Control 4 | minority interest line populated from consolidation calculation | approval locks the balance sheet as part of the financial package |
| Control 5 | balance check assertion (assets = liabilities + equity) enforced before approval | negative) when assets do not equal liabilities plus equity the system returns 422 BALANCE_SHEET_IMBALANCED with the difference amount. |
| Control 6 | drill-through from each line to GL | Balance sheet always mathematically balanced; equity roll-forward eliminates manual computation; IFRS/GAAP classification applied consistently without manual override. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | |
| Control rules | Balance sheet template configurable per IFRS/GAAP with current/non-current classification rules; equity roll-forward computing retained earnings from prior closing balance plus net income less dividends; AOCI roll-forward including CTA, unrealized gains/losses; minority interest line populated from consolidation calculation; balance check assertion (assets = liabilities + equity) enforced before approval; drill-through from each line to GL; comparative prior-year column; note-disclosure tagging; export to PDF, Excel, XBRL; linked to income statement and cash flow as one package; locked version stored with auditor-accessible permalink. |
| Acceptance proof | Given an approved income statement and consolidated trial balance; when the balance sheet is generated; then assets equal liabilities plus equity (enforced assertion), equity section includes retained earnings roll-forward, AOCI, and minority interest, comparative prior-year column is present; approval locks the balance sheet as part of the financial package; (negative) when assets do not equal liabilities plus equity the system returns 422 BALANCE_SHEET_IMBALANCED with the difference amount. |
| 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
`balance_sheet` { id: string, consolidation_run_id: string, period: string, reporting_currency: char(3), total_assets_minor: int64, total_liabilities_minor: int64, total_equity_minor: int64, balanced: bool, status: enum, external_id: string }; `bs_line` { id: string, bs_id: string, section: enum, classification: enum(CURRENT, NON_CURRENT), label: string, amount_minor: int64, currency_code: char(3), external_id: string }; (reference, product may differ).API and events
`POST /v1/balance-sheets` { consolidation_run_id, external_id } -> 201 { id, total_assets_minor, total_liabilities_minor, total_equity_minor, balanced, currency_code }; `POST /v1/balance-sheets/{id}/approve` -> 200 { status: APPROVED }; `GET /v1/balance-sheets/{id}/export?format=xlsx|pdf|xbrl`; emits `balance_sheet.approved` event; idempotent via `external_id`.State transitions
`DRAFT -> REVIEW -> APPROVED -> LOCKED`; guard: REVIEW blocked if balanced=false; APPROVED requires income statement to be APPROVED first; LOCKED on package sign-off.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.