Statutory statements
Goal
Generate country-conforming financial statements folded from the ledger for the tenant’s reporting standard, then optionally Finalize a run for filing archives.
Who it is for
Compliance and finance users with statutory.view. Finalizing needs statutory.file. Module: statutory_compliance. (Tax returns, jurisdictions, and exemptions are sibling screens — not this page.)
Preconditions
- Module statutory_compliance enabled.
- Permission
statutory.view(else Dashboard redirect). - Reporting standard and statement templates available from
GET /reports/statutory. - Valid From / To dates covering posted ledger activity you intend to include.
Open the screen
Operations → Tax & Statutory → Statutory statements (path /statutory/reports). Title: Statutory statements. Subtitle describes statements folded from the ledger per reporting standard. Header tag shows the reporting standard code from the API.
Steps
- Choose Statement (template select).
- Set From and To (date inputs).
- Click Generate (
GET /reports/statutory/{template}?from&to). Generating with no template selected is a no-op. - Review the statement title, Balanced / Unbalanced tags, node table (section / line / total), and currency footnote.
- If you have
statutory.file, click Finalize (finalize=1) to archive aStatutoryReportRun→ toast Statement finalized for filing.
Result
On-screen statement for the selected template and date range. Finalized runs are stored for filing history; non-finalized generates are review-only.
Hard stops
- No
statutory.file→ Finalize button hidden (API would 403). - Missing module /
statutory.view→ Dashboard redirect. - This is not a generic tax-return filer — use Tax returns and related statutory screens for returns/jurisdictions.
- Unbalanced results still render with the Unbalanced tag so you can investigate mapping/ledger issues.