Guides
Produce a regulatory report
Generation, validation, review, approval — and what the platform will and will not claim about filing.
Written for: MLROs
Written from docs/adr/0018, docs/adr/0034, docs/regulatory-reporting-workbook.md
A report is generated from a controlled mapping between the case record and the report format. The mapping is versioned configuration; the generation retains its validation evidence; review and approval history stays attached.
The sequencePermalink to this section
- 1
Generate
From the case, through the mapping in force. The mapping version is recorded on the report.
- 2
Validate
Structural validation runs and its evidence is retained with the report, pass or fail.
- 3
Review
A reviewer who is not the generator examines the content against the case.
- 4
Approve
Maker-checker, on the same primitive every other approval uses.
- 5
Record the filing
A submission record needs its channel, reference, timestamp, payload digest and acknowledgement state. Missing any of them, it is not a filing record.
Mixed-currency setsPermalink to this section
Where the activity behind a report spans currencies, the set is presented as such rather than summed. A single total across currencies would be a defect that looks like a number.