Financial Statements is where ERP discipline either begins or breaks.
Cash Flow Statement Generation (Indirect Method) 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: Cash flow statement produced automatically in under 5 minutes from approved trial balance; IAS 7 / ASC 230 compliant; ending cash always reconciles to balance sheet eliminating manual tie-out.
The control flow a finance team actually needs.
Step 1
Indirect Method Cash Flow Template With...
Step 2
Non-Cash Adjustment Line Items...
Step 3
Working Capital Change Computation From...
Step 4
Investing Activities Fed From...
Step 5
Financing Activities Fed From Debt...
The ERP surface involved.
Module
Financial Statements
Actors
Group Controller, Treasury Analyst, Reporting System
Tier
Tier 0
Finance area
Financial Close, Consolidation & Statutory Reporting
Region lens
US and UK finance teams
Publication date
April 5, 2026
Indirect method cash flow template with configurable account-to-section mapping (operating/investing/financing); non-cash adjustment line items configurable (depreciation, amortization, impairment, stock comp, deferred tax); working capital change computation from period-over-period balance sheet delta for each mapped account; investing activities fed from fixed-asset register disposals and additions; financing activities fed from debt schedule and equity transactions; ending cash reconciliation to balance sheet cash balance with assertion; comparative prior-period column; drill-through from each line to source transactions; export to PDF, Excel, XBRL; balance sheet changes in foreign-currency items show FX effect as separate line per IAS 7.
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 | Indirect method cash flow template with configurable account-to-section mapping (operating/investing/financing | Given an approved income statement and balance sheet with period-over-period movements |
| Control 2 | non-cash adjustment line items configurable (depreciation, amortization, impairment, stock comp, deferred tax | when the cash flow statement is generated using the indirect method |
| Control 3 | working capital change computation from period-over-period balance sheet delta for each mapped account | then net income ties to the income statement, working capital changes are computed from balance sheet deltas, ending cash reconciles to balance sheet cash balance (assertion enforced), and FX effect on cash is a separate line |
| Control 4 | investing activities fed from fixed-asset register disposals and additions | negative) when ending cash computed from cash flow does not reconcile to balance sheet cash the system returns 422 CASH_RECONCILIATION_FAILED with the difference amount. |
| Control 5 | financing activities fed from debt schedule and equity transactions | Cash flow statement produced automatically in under 5 minutes from approved trial balance; IAS 7 / ASC 230 compliant; ending cash always reconciles to balance sheet eliminating manual tie-out. |
| Control 6 | ending cash reconciliation to balance sheet cash balance with assertion | Cash flow statement produced automatically in under 5 minutes from approved trial balance; IAS 7 / ASC 230 compliant; ending cash always reconciles to balance sheet eliminating manual tie-out. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | System generates the cash flow statement using the indirect method by starting with net income from the income statement, adding back non-cash charges (depreciation, amortization, stock compensation), and adjusting for changes in working capital accounts (receivables, payables, inventory, accruals) computed from period-over-period balance sheet movements. Investing activities are populated from fixed-asset additions, disposals, and acquisition payments. Financing activities include debt draws, repayments, dividends, and share issuances. The system reconciles ending cash to the balance sheet cash balance. Group Controller reviews and approves; the statement is locked with the other primary financials. |
| Control rules | Indirect method cash flow template with configurable account-to-section mapping (operating/investing/financing); non-cash adjustment line items configurable (depreciation, amortization, impairment, stock comp, deferred tax); working capital change computation from period-over-period balance sheet delta for each mapped account; investing activities fed from fixed-asset register disposals and additions; financing activities fed from debt schedule and equity transactions; ending cash reconciliation to balance sheet cash balance with assertion; comparative prior-period column; drill-through from each line to source transactions; export to PDF, Excel, XBRL; balance sheet changes in foreign-currency items show FX effect as separate line per IAS 7. |
| Acceptance proof | Given an approved income statement and balance sheet with period-over-period movements; when the cash flow statement is generated using the indirect method; then net income ties to the income statement, working capital changes are computed from balance sheet deltas, ending cash reconciles to balance sheet cash balance (assertion enforced), and FX effect on cash is a separate line; (negative) when ending cash computed from cash flow does not reconcile to balance sheet cash the system returns 422 CASH_RECONCILIATION_FAILED 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
`cash_flow_statement` { id: string, consolidation_run_id: string, period: string, reporting_currency: char(3), net_income_minor: int64, cash_from_operations_minor: int64, cash_from_investing_minor: int64, cash_from_financing_minor: int64, fx_effect_minor: int64, ending_cash_minor: int64, reconciles: bool, currency_code: char(3), status: enum, external_id: string }; (reference, product may differ).API and events
`POST /v1/cash-flow-statements` { consolidation_run_id, external_id } -> 201 { id, reconciles, ending_cash_minor, currency_code }; `POST /v1/cash-flow-statements/{id}/approve` -> 200 { status: APPROVED }; `GET /v1/cash-flow-statements/{id}/export?format=xlsx|pdf|xbrl`; emits `cash_flow.approved` event; idempotent via `external_id`.State transitions
`DRAFT -> REVIEW -> APPROVED -> LOCKED`; guard: REVIEW blocked if reconciles=false; APPROVED requires balance sheet APPROVED; 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.