Skip to content

User guideIntelligence

Scenarios

How-to + ExplanationDocuments: Scenarios

Actions saved against your own filing, each one run again when you open it — the filing in the first column and up to four scenarios beside it, with CSV and print per scenario.

A scenario is an action you put in front of your own numbers — a loan, a dividend, deposits leaving, securities sold — held as the action itself and never as the figures it produced. Opening one runs it again against the filing the product holds today. Your own institution

Nothing on this page was filed

Every figure beside a scenario is arithmetic over a call report, not a call report. The page carries the stamp SCENARIO — not filed, and so does every CSV and every printed sheet that leaves it.

Where a scenario comes from

You do not make one here. Put an action in front of the figures on an institution view — see Institution — read what it does, and save it. This page is where the saved ones are read back, newest first.

What a saved row holds

The name you gave it, the institution it was stated against, and the action as stated: its kind, its amount, and the few fields that kind needs — a loan type and its risk weight, how it is funded, a realised loss, an instrument. That is the whole row.

It holds no figures. A stored result would be a number that stopped moving when the filing underneath it moved, and nothing on the screen would say so. So the row is the action, and the figures are made fresh every time.

The comparison

The filing is the first column, always, headed As filed with the quarter it came from. Each scenario you tick adds a column beside it, up to four at a time. The rows are the seven measures a balance-sheet action moves — the two concentration screens, the four capital ratios, and loans to deposits — and the last column is the published line for each, where one is published.

  • A cell carries the figure and, where a published line was tested, the word for standing against it. Where no line was tested there is no word rather than a borrowed one.
  • A column header names the scenario, describes the action, says when it was saved, and states which published line the action reaches first.
  • A comparison runs against one base filing. A scenario stated against another institution says so and cannot join the table — otherwise As filed would name two different filings at once.

When the filing has moved

Call reports drop quarterly. A scenario saved against one quarter and opened after the next has landed is run against the new one, and its column says so in terms: saved against Q1 2026 · ran against Q2 2026. There is no stored copy of the earlier answer to show beside it, and that is the design rather than a gap — the earlier answer was arithmetic over a filing you can still read.

What you can do with one

  • Open — the institution view, in scenario mode, with the action in front of the whole register.
  • Download CSV — the seven measures before and after, the deltas, the lines, the standings and the assumptions, with the stamp on the first line.
  • Print — one page, with the stamp, the institution and the base filing in the running header. It is never a page of the board packet or the regulatory edition.
  • Archive — it leaves this page and stays readable on the account. Nothing is deleted, and you type the word to confirm it.

Both exports are built by running the action again on the server, so a file and the screen it came from cannot disagree.

What a scenario does not carry

There is no rate field, no yield and no date, and no earnings effect is modelled: income over time is a projection, and the product does not make one. A scenario says what an action does to the ratios a filing already supports, on the day it is opened.