Financial Statements is where ERP discipline either begins or breaks.
Statement of Changes in Equity 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: Statement of changes in equity produced automatically with full audit trail; opening-to-closing equity roll-forward eliminates spreadsheet reconciliation.
The control flow a finance team actually needs.
Step 1
Equity Component Columns Configurable...
Step 2
Opening Balance Sourced From Prior...
Step 3
Net Income Feed From Approved Income...
Step 4
OCI Components Sourced From Tagged JE...
Step 5
Dividends Sourced From Dividend-Tagged...
The ERP surface involved.
Module
Financial Statements
Actors
Group Controller, Reporting System
Tier
Tier 1
Finance area
Financial Close, Consolidation & Statutory Reporting
Region lens
US and UK finance teams
Publication date
April 5, 2026
Equity component columns configurable per reporting entity and standard; opening balance sourced from prior period closing balance; net income feed from approved income statement; OCI components (CTA, unrealized FX, pension adjustments, fair-value movements) sourced from tagged JE categories; dividends sourced from dividend-tagged journal entries; share transactions sourced from capital transaction module; minority interest column populated from consolidation; mathematical consistency with balance sheet equity section enforced; export to PDF, Excel, XBRL; IFRS IAS 1 / ASC 220 compliant structure.
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 | Equity component columns configurable per reporting entity and standard | Given an approved income statement and prior-period closing equity balances |
| Control 2 | opening balance sourced from prior period closing balance | when the statement of changes in equity is generated |
| Control 3 | net income feed from approved income statement | then each equity component column opens from prior closing balance, net income feeds from the income statement, OCI components are sourced from tagged JE categories, dividends from dividend-tagged entries, and closing balances reconcile to the balance sheet equity section |
| Control 4 | OCI components (CTA, unrealized FX, pension adjustments, fair-value movements) sourced from tagged JE categories | negative) when the closing equity total does not match the balance sheet equity then the system returns 422 EQUITY_RECONCILIATION_FAILED. |
| Control 5 | dividends sourced from dividend-tagged journal entries | Statement of changes in equity produced automatically with full audit trail; opening-to-closing equity roll-forward eliminates spreadsheet reconciliation. |
| Control 6 | share transactions sourced from capital transaction module | Statement of changes in equity produced automatically with full audit trail; opening-to-closing equity roll-forward eliminates spreadsheet reconciliation. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | System generates the statement of changes in equity as a matrix showing opening balances, comprehensive income (net income and OCI components including CTA and unrealized gains), dividends declared, share issuances, share repurchases, and closing balances for each equity component column (common stock, APIC, retained earnings, AOCI, treasury stock, minority interest, total equity). Each movement line is sourced from tagged journal entries or computed roll-forwards. Group Controller reviews for completeness and approves. The statement is locked as part of the statutory reporting package. |
| Control rules | Equity component columns configurable per reporting entity and standard; opening balance sourced from prior period closing balance; net income feed from approved income statement; OCI components (CTA, unrealized FX, pension adjustments, fair-value movements) sourced from tagged JE categories; dividends sourced from dividend-tagged journal entries; share transactions sourced from capital transaction module; minority interest column populated from consolidation; mathematical consistency with balance sheet equity section enforced; export to PDF, Excel, XBRL; IFRS IAS 1 / ASC 220 compliant structure. |
| Acceptance proof | Given an approved income statement and prior-period closing equity balances; when the statement of changes in equity is generated; then each equity component column opens from prior closing balance, net income feeds from the income statement, OCI components are sourced from tagged JE categories, dividends from dividend-tagged entries, and closing balances reconcile to the balance sheet equity section; (negative) when the closing equity total does not match the balance sheet equity then the system returns 422 EQUITY_RECONCILIATION_FAILED. |
| 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
`equity_statement` { id: string, consolidation_run_id: string, period: string, reporting_currency: char(3), status: enum, external_id: string }; `equity_component_movement` { id: string, stmt_id: string, component: enum(COMMON_STOCK, APIC, RETAINED_EARNINGS, AOCI, TREASURY_STOCK, MINORITY_INTEREST), movement_type: enum, amount_minor: int64, currency_code: char(3), external_id: string }; (reference, product may differ).API and events
`POST /v1/equity-statements` { consolidation_run_id, external_id } -> 201 { id, components[], currency_code }; `POST /v1/equity-statements/{id}/approve` -> 200 { status: APPROVED }; `GET /v1/equity-statements/{id}/export?format=xlsx|pdf|xbrl`; emits `equity_statement.approved` event; idempotent via `external_id`.State transitions
`DRAFT -> REVIEW -> APPROVED -> LOCKED`; guard: APPROVED requires income statement APPROVED and equity reconciliation to balance sheet passes; 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.