Financial Statements Policy¶


Code	`REP-004`
Domain	Regulatory Reporting
Owner	Chief Financial Officer
Status	Draft
Applicability	External — The company's statutory financial statements are prepared externally. The platform generates the banking ledger which feeds into financial reporting; the consolidated company accounts are produced in an ERP outside the platform boundary.
Jurisdiction	NZ + AU
Business domain	BD02
Review date	2027-03-25

Outside platform boundary

The company's statutory financial statements are prepared externally. The platform generates the banking ledger which feeds into financial reporting; the consolidated company accounts are produced in an ERP outside the platform boundary.

Regulations: NZ Companies Act · Corporations Act 2001 · IFRS 9 ¶

Purpose¶

Govern the production of statutory financial statements, IFRS 9 expected credit loss calculations, Board financial reporting, and external audit engagement. Establishes the banking ledger as the authoritative source for all financial statement inputs and defines the controls that govern the path from ledger to published financial statements.

Scope¶

All statutory financial statements, management accounts, Board financial reports, and audit deliverables produced by or on behalf of the platform in NZ and AU jurisdictions.

Policy statements¶

The banking ledger, maintained in the Core Banking system (SD01), SHALL be the sole authoritative source for all financial statement inputs. No financial statement line item SHALL be derived from a source that is not traceable to a posted ledger event.

Financial statement production SHALL follow a controlled close process. The close process SHALL include: ledger reconciliation, IFRS 9 ECL calculation review, intercompany elimination confirmation (where applicable), and sign-off by the Chief Financial Officer before publication.

IFRS 9 expected credit loss provisions SHALL be calculated using approved models, applied to ledger balances as of the reporting date, and reviewed by an independent risk function before inclusion in the financial statements.

Board financial reports SHALL be produced on a monthly basis and SHALL include: income statement, balance sheet, capital adequacy position, and key risk metrics. Board reports SHALL be distributed within the Board-agreed reporting timeline.

The external audit engagement SHALL have access to ledger data, supporting documentation, and system audit trails as required. The platform SHALL maintain an audit-ready posture at all times — documentation required for audit SHALL not be assembled on demand but SHALL be continuously maintained.

Financial statement adjustments and journal entries outside the normal posting flow SHALL require dual approval and SHALL be documented with rationale before posting. Manual overrides to financial statement figures that are not traceable to a posted ledger event are prohibited.

Figures disclosed in external publications — including offer documents, disclosure statements, and investor reports — SHALL be consistent with the statutory financial statements. Any variance between disclosed figures and the financial statements SHALL be explained and approved before publication.

The platform SHALL reconcile the financial statement balance sheet to the ledger at each reporting period before sign-off. Any unreconciled difference SHALL be treated as a blocking issue until resolved or documented as an approved exception by the CFO.

All financial statement versions, sign-off records, audit deliverable packages, and adjustment journals SHALL be retained per the applicable retention schedule.

Satisfying modules¶

Module	Name	Mode	Description
MOD-001	Double-entry posting engine	`AUTO`	Statutory P&L and balance sheet sourced directly from ledger — no manual restatement
MOD-005	Daily accrual calculator	`AUTO`	IFRS 9 interest income recognised on accrual basis — automated and auditable
MOD-030	Stage allocation model	`AUTO`	IFRS 9 provision movements posted to GL automatically — no manual journal for provisioning
MOD-031	ECL calculation & GL posting	`AUTO`	Provision entries in GL sourced from validated model — no manual provision entries
MOD-080	Statutory financial reporting & ERP integration	`AUTO`	Statutory financial statements (P&L, balance sheet, cash flow) produced from the Snowflake analytical layer on the regulatory schedule — no manual extraction.
MOD-132	Loan restructure and variation workflow	`LOG`	Every loan variation event — request, assessment decision, disclosure dispatch, customer confirmation, and rejection — is logged as an immutable record for regulatory examination and responsible lending audit.
MOD-140	Chart of accounts and GL configuration	`GATE`	Changes to GL account codes used in regulatory reporting must be reviewed and approved before taking effect; any code used in an RBNZ or APRA return must have a valid regulatory mapping before it can be activated.
MOD-142	Deposit guarantee scheme disclosure	`LOG`	DCS/FCS disclosure events are logged for regulatory examination — RBNZ and APRA may inspect whether disclosure obligations have been met at account opening and in statements.
MOD-162	Loan facility & component manager	`AUTO`	Component-level cash flow data and stage transition events are published on every lifecycle change, feeding the IRRBB repricing gap view and ECL stage-allocation inputs automatically.
MOD-165	Synthetic swap book aggregator	`AUTO`	Daily IRRBB snapshots — repricing buckets, EVE sensitivities, and NII sensitivities — are written to the reporting store without manual intervention; no manual journal or analyst-prepared spreadsheet is required for the IRRBB position.

Part of Regulatory Reporting · Governance overview Compiled 2026-05-22 from source/entities/policies/REP-004.yaml