Regulatory Reporting Models
Executive Summary
Key Takeaways
- ✓ Regulatory reporting models translate a bank's underlying financial position into the specific format and definitions its regulatory returns require, and should reconcile explicitly to the same underlying calculations built across this domain rather than being maintained separately.
- ✓ A regulatory reporting figure that diverges from the equivalent management reporting figure without an explained reconciling item indicates either a genuine calculation error or an undocumented definitional difference — either way, an unreconciled gap should never be presented as an unremarkable discrepancy.
- ✓ Regulatory return definitions frequently differ subtly from internal management reporting definitions (a regulatory capital definition versus an internal economic capital measure, for example), and a reporting model should document these definitional differences explicitly rather than assuming the two are interchangeable.
- ✓ Regulatory reporting models should be built with the same segment-level detail as the underlying capital, liquidity, and credit models feeding them, not aggregated prematurely in a way that would prevent tracing a reported regulatory figure back to its underlying drivers.
- ✓ Timeliness and version control matter distinctly for regulatory reporting models, since a return submitted against outdated underlying data or a superseded regulatory threshold is a compliance risk distinct from any structural formula error within the model itself.
Objective¶
This guide covers how the models feeding a bank's regulatory returns should be constructed, within Regulatory Model Governance, reconciling explicitly to the capital and liquidity calculations built across this domain.
Reconciliation to Management Reporting¶
A regulatory reporting figure that diverges from the equivalent management reporting figure — a reported CET1 ratio different from an internally tracked capital position, for example — should never be presented as an unremarkable discrepancy. An unreconciled gap indicates either a genuine calculation error somewhere in one of the two models, or an undocumented definitional difference between them, and either possibility warrants investigation rather than being left unexplained.
Documenting Definitional Differences¶
Regulatory return definitions frequently differ subtly from a bank's own internal management reporting conventions — a regulatory capital definition and an internal economic capital measure, for instance, can diverge in what they include or how they weight specific items. A regulatory reporting model should document these definitional differences explicitly, consistent with Banking Documentation, rather than assuming the two figures are interchangeable or leaving a reader to discover the difference independently.
Segment-Level Detail, Not Premature Aggregation¶
Regulatory reporting models should carry the same segment-level detail as the underlying capital and liquidity models feeding them, rather than aggregating prematurely in a way that would prevent tracing a reported regulatory figure back to the specific underlying segment or driver that produced it. Premature aggregation makes it impossible to investigate a reported figure that looks anomalous without rebuilding the underlying detail from scratch.
Timeliness and Version Control¶
A regulatory return submitted against outdated underlying data, or a superseded regulatory threshold, represents a distinct compliance risk from any structural formula error within the reporting model itself — the model can be entirely correct in its formulas and still produce a non-compliant return if it was built on stale inputs or an out-of-date regulatory parameter. Version control discipline over both the underlying data and the regulatory parameters in use is therefore a distinct requirement from the model's own structural integrity, which Banking Model Audit addresses.
Common Construction Pitfalls¶
- Maintaining regulatory reporting models as a separate, disconnected exercise from the underlying management reporting figures, with no explicit reconciliation.
- Failing to document definitional differences between regulatory and internal management reporting conventions.
- Aggregating regulatory reporting figures prematurely, preventing a reported figure from being traced back to its underlying segment-level drivers.
- Submitting a regulatory return built on outdated data or a superseded regulatory threshold without adequate version control discipline.
Continue Reading¶
Prerequisites¶
- Regulatory Model Governance — the parent guide
- Capital Adequacy Models
- Liquidity Coverage Ratio
Related Technical Guides¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What is a regulatory reporting model?
A model that translates a bank's underlying financial position — its balance sheet, capital, liquidity, and credit exposure calculations — into the specific format and definitions required by its regulatory returns.
Why should regulatory reporting models reconcile to management reporting?
Because a regulatory reporting figure that diverges from the equivalent management reporting figure without an explained reconciling item indicates either a genuine calculation error or an undocumented definitional difference, and an unreconciled gap between the two should never be presented as an unremarkable discrepancy that does not need investigation.
Why do regulatory and management reporting definitions sometimes differ?
Because regulatory frameworks often define capital, liquidity, or exposure measures somewhat differently than a bank's own internal management reporting conventions (a regulatory capital definition versus an internal economic capital measure, for example), and a reporting model should document these definitional differences explicitly rather than assuming the two figures are interchangeable.
What level of detail should a regulatory reporting model carry?
The same segment-level detail as the underlying capital, liquidity, and credit models feeding it, not aggregated prematurely in a way that would prevent tracing a reported regulatory figure back to the specific underlying drivers that produced it.
Why do timeliness and version control matter specifically for regulatory reporting models?
Because a regulatory return submitted against outdated underlying data or a superseded regulatory threshold represents a compliance risk distinct from any structural formula error within the model itself — the model can be structurally correct and still produce a non-compliant return if built on stale inputs.
How does this guide relate to Regulatory Model Governance?
This guide covers the specific reconciliation and reporting discipline regulatory reporting models require; Regulatory Model Governance covers the broader inventory, tiering, and approval framework these reporting models should themselves be subject to as part of the bank's overall model inventory.
Related Articles
Regulatory Model Governance
Regulatory model governance is the framework a bank uses to inventory, tier, approve, and monitor every model it relies on for a material business or regulatory purpose. This guide covers the core components of that framework — a comprehensive model inventory, a risk-based tiering methodology, a formal approval process before a model is used in production, and ongoing performance monitoring — and why an incomplete inventory is the single most common gap regulators identify in bank model governance frameworks.
Capital Adequacy Models
Capital adequacy modelling represents the constraint regulatory capital requirements place on how much risk-weighted balance sheet a bank can carry against its available capital base. This guide covers how to structure a capital adequacy model — the capital tiers, the risk-weighted asset base they are measured against, minimum ratio and buffer requirements — and how it should be built as a live check against the balance sheet forecast rather than a standalone reporting exercise calculated after the forecast is already complete.
Liquidity Coverage Ratio
The liquidity coverage ratio (LCR) tests whether a bank holds enough high-quality liquid assets to survive a defined 30-day acute stress scenario. This guide covers how to model the LCR's two components — the stock of high-quality liquid assets and net cash outflows under the stress scenario — and how the deposit and funding behavioural assumptions built elsewhere in the model feed directly into the outflow calculation.
Banking Documentation
Documentation for a bank model must satisfy general model documentation discipline while also evidencing several bank-specific requirements: the sourcing and justification of regulatory-linked assumptions (risk weights, capital thresholds, liquidity run-off rates), the model's assigned risk tier and rating, and its validation and approval history. This guide covers what banking documentation needs beyond the general standard, and why undocumented regulatory assumption sourcing is one of the most common findings in a bank model review.
Banking Model Audit
A structural audit of a bank model tests whether the formulas and logic as actually built calculate correctly — whether the segmented balance sheet, interest income build, credit loss provisioning, and capital adequacy modules covered across this domain are internally consistent and free of the structural errors (broken links, hardcodes, inconsistent formulas) that affect any complex Excel model. This guide covers what a banking-specific structural audit should check, and how it differs from both model validation and any regulatory capital or liquidity calculation review.