Field guide
Regulatory reporting with governed context: from approved meaning to a line a reviewer can trace
From approved meaning to a Call Report line a reviewer can trace: MDRM codes, fixed metrics, period status, edit checks and evidence, on a fictional bank.
In brief
A line on a regulatory report looks like one number, but it rests on decisions about which loans count, what each source code means, which balance and period are used and whether the period is final. This field guide shows how to make those decisions once, with named owners, before an AI assistant helps prepare or explain a report. It works through a fictional bank whose data feed FFIEC 041 and FR Y-9C lines: each line keyed by its MDRM code, meaning approved before the number is computed, metrics compiled to fixed SQL, preliminary and final values never combined, edit checks that cite their sources, and a sealed record of every call. Each section says what RJL’s working implementation does today.
- Who it’s for
- Heads of regulatory reporting, finance and data leaders at US banks, and the architects who support them.
- You’ll be able to
- Key every line by its MDRM code, decide what each source code means before anyone asks, keep the arithmetic out of the model, label every value with its period and status, and give a reviewer the evidence behind a reported figure.
- Short on time?
- Read sections 01 and 03, then section 10, the readiness checklist.
Abstract
A line on a regulatory report looks like one number. Behind it sit decisions about which loans count, what each source code means, which balance and period are used and whether that period is final. This field guide shows how to make those decisions once, with owners, before an AI assistant helps prepare or explain a report.
It works through a fictional mid-size bank whose loan and deposit data feed lines of the FFIEC 041 Call Report and the FR Y-9C: lines keyed by MDRM code, meaning approved in Ontology Studio, metrics compiled to fixed SQL, preliminary and final values never combined, edit checks that cite their sources, and a sealed record of every call.
Each section says what RJL’s working implementation does today, using its own status words. It closes with a readiness checklist. Regulatory facts cite public sources, and nothing in it is legal or regulatory advice.
In RJL’s reference implementation
What RJL runs of this paper today.
- Live Each report line is fed by an approved metric and carries its MDRM code.Section 03 · Regulatory reporting: MDRM-coded FFIEC 041 and FR Y-9C lines with edit checks See it working (invited sign-in)
- Live The model never does the arithmetic: metrics compile to fixed SQL.Section 05 · Semantic layer compiled to fixed SQL See it working (invited sign-in)
- Live Preliminary, final and restated values are never combined.Section 06 · Values labelled with status and period See it working (invited sign-in)
Honest gap. The edit-check publications are not yet verified against the publishers, and the reporting product is in a managed sandbox, not certified.
Status as of 20 November 2026, from the product records; statuses never exceed a recorded live check. See every row for this paper or the whole reference implementation.
In the paper
Three passages, as published
Meaning first
The meaning has to be approved before the number is computed.
Fixed metrics
If the model computes it, it isn’t ready to report.
Who decides
An assistant can prepare, explain and check. A person signs the report.
Next step
Discuss this paper against your own program.
Set up time with Richard to discuss your top gaps. The first conversation is free.