Financial Statements is where ERP discipline either begins or breaks.
Consolidated Income Statement 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: GAAP/IFRS-compliant income statement produced automatically from GL; manual spreadsheet production eliminated; comparative view enables period-over-period analysis without additional preparation.
The control flow a finance team actually needs.
Step 1
Income Statement Template Configurable...
Step 2
For Single-Step And Multi-Step Format
Step 3
EBITDA And Other Subtotal Computations...
Step 4
Comparative Columns For Prior Period...
Step 5
Minority Interest Deduction Line For...
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
Income statement template configurable per reporting standard (IFRS, US GAAP, local GAAP) with account-to-line mapping; support for single-step and multi-step format; EBITDA and other subtotal computations based on line aggregation rules; comparative columns for prior period and prior year same period; minority interest deduction line for consolidated view; earnings per share calculation where share count is configured; drill-through from any line to GL balances and then to journal entries; note-disclosure tagging per line; export to PDF, Excel, XBRL; locked version stored per reporting period with approver metadata.
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 | Income statement template configurable per reporting standard (IFRS, US GAAP, local GAAP) with account-to-line mapping | Given a completed and approved consolidation run |
| Control 2 | support for single-step and multi-step format | when the consolidated income statement is generated |
| Control 3 | EBITDA and other subtotal computations based on line aggregation rules | then all GL accounts map to configured line items, EBITDA and subtotals compute correctly, comparative prior-period columns are present, and minority interest deduction appears |
| Control 4 | comparative columns for prior period and prior year same period | the finalized statement locks with approver metadata |
| Control 5 | minority interest deduction line for consolidated view | negative) when any active GL account has no income statement line mapping then the system returns 422 UNMAPPED_ACCOUNTS with the account list. |
| Control 6 | earnings per share calculation where share count is configured | GAAP/IFRS-compliant income statement produced automatically from GL; manual spreadsheet production eliminated; comparative view enables period-over-period analysis without additional preparation. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | On consolidation approval, the system generates the consolidated income statement mapping each GL account balance to the configured financial statement line per the chart-of-accounts mapping table. Revenue, cost of goods sold, gross profit, operating expenses, operating income, EBITDA, interest, tax, and net income lines are computed. Comparative prior-period and prior-year columns are included. Group Controller reviews the statement, annotates any lines requiring note disclosures, and finalizes. The finalized income statement is locked and included in the statutory package. |
| Control rules | Income statement template configurable per reporting standard (IFRS, US GAAP, local GAAP) with account-to-line mapping; support for single-step and multi-step format; EBITDA and other subtotal computations based on line aggregation rules; comparative columns for prior period and prior year same period; minority interest deduction line for consolidated view; earnings per share calculation where share count is configured; drill-through from any line to GL balances and then to journal entries; note-disclosure tagging per line; export to PDF, Excel, XBRL; locked version stored per reporting period with approver metadata. |
| Acceptance proof | Given a completed and approved consolidation run; when the consolidated income statement is generated; then all GL accounts map to configured line items, EBITDA and subtotals compute correctly, comparative prior-period columns are present, and minority interest deduction appears; the finalized statement locks with approver metadata; (negative) when any active GL account has no income statement line mapping then the system returns 422 UNMAPPED_ACCOUNTS with the account list. |
| 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
`income_statement` { id: string, consolidation_run_id: string, period: string, reporting_currency: char(3), status: enum, approved_by: string, approved_at: timestamp, external_id: string }; `is_line` { id: string, is_id: string, line_code: string, label: string, amount_minor: int64, currency_code: char(3), comparative_minor: int64, external_id: string }; (reference, product may differ).API and events
`POST /v1/income-statements` { consolidation_run_id, external_id } -> 201 { id, lines[], net_income_minor, currency_code }; `POST /v1/income-statements/{id}/approve` -> 200 { status: APPROVED }; `GET /v1/income-statements/{id}/export?format=xlsx|pdf|xbrl`; emits `income_statement.approved` event; idempotent via `external_id`.State transitions
`DRAFT -> REVIEW -> APPROVED -> LOCKED`; guard: REVIEW blocked if unmapped accounts exist; LOCKED triggered on package approval; LOCKED statement is immutable.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.