Risk Reporting is the step after the models. It reads your scenario set and model runs, computes the credit losses and the CET1 walk, drafts the commentary from the figures and takes the report through four-eyes sign-off. Select any number to see the formula, the files and the people behind it.
kinds of input, recognised from the file itself: scenario set, model runs, portfolio, capital and last cycle’s report
commentary sections drafted from the figures, each one read and accepted by a person
people sign off: a reviewer who did not prepare it, then the named report owner
exports: the lineage package, every figure as CSV, a source grid for the EBA Filler and an A4 results pack
Add the scenario set from Scenario Creator, the model runs from Model Studio and your portfolio and capital figures. Each file is recognised from its content and hashed. The reporting agent proposes how segments and scenarios map to model results; exact matches are logged, the rest wait for you.

Credit losses per segment, the CET1 walk, the depletion and the headroom to your threshold. The calculation is plain and documented: exposure times default rate times LGD on a static balance sheet, then pre-provision profit, tax and payout into CET1.

Every figure stores its formula and operands. Follow a cumulative loss down to the year, the segment, the default rate, the model run and its approvers, and the input file with its SHA-256. Scenario paths show the macro part and any bank-specific overlay separately.

The agent drafts six sections from the figures, the scenario narratives and the model records. You edit and accept each one. If the figures change afterwards, the check list says so.

Checks flag what a reviewer would ask about. A reviewer who did not prepare the report approves the exact version, then the report owner signs it off. Any change after that makes a new version.

Reading the inputs, proposing the mapping, computing the figures, running the checks and drafting the commentary are fixed engine jobs. The same inputs give the same report.
It never approves a mapping, a section or a report, never changes a model result or an input file, and never writes a number that was not computed from the inputs.
A rewrite sends the section text and the key figures, never portfolio rows, inputs or bank overlays. You see the payload first and nothing goes until you consent.

Macro paths and bank-specific overlays, kept apart in the report.
Default rates bound to the data, the scenario set and the approvers.
Losses, capital and commentary, with lineage for every figure.
A source grid whose ranges never move, mapped once and reused every cycle.
Exposure × default rate × LGD per segment, scenario and year. The default rate comes from the mapped model result; a scenario-specific LGD can replace the base one.
Pre-provision profit minus losses, less tax on a profit, less the payout on what remains, added to CET1. The risk exposure amount stays at its reference value.
Depletion is the starting CET1 ratio minus the lowest ratio over the horizon, in bps. Headroom is the lowest ratio minus your threshold.
Changed hashes, unmapped segments, a model run on a different scenario set, unvalidated models and losses below baseline. They support the reviewer; they do not certify the report.
Not directly. It exports a source grid with fixed ranges. You map it once in the EBA Filler, which then fills the template with its own checker-approved mapping and lineage.
No. Results from models built elsewhere come in as a CSV and are marked as external. A Model Studio model run carries more: its gates, its approvers and the scenario set it ran on, verified by hash.
Its results are used and marked: a badge in the app, a dagger in the pack and a status field in the export. The reviewer sees it in the checks.
No. The engine runs locally. The only thing that can be sent is an optional AI rewrite of a commentary section, and you see that payload in full before you consent.