uplyst.Understand the relationships behind an exposure
Understand how a change in one part of the business may affect exposures and responsibilities elsewhere.
Inspect the reporting perimeterExposure review · ENTITY-07
Funded principal · 09:00£85,000
Last confirmed funded position.
Includes £20,000 past due.Undrawn commitment£30,000
A separate facility measure with its own definition.
See where dependencies concentrate risk
An exposure can be distributed across legal entities, suppliers, customers, assets and contracts. A change that appears local may matter more when it affects several processes through a shared dependency. Risk teams need an understandable model of those relationships before an aggregate figure or alert can guide a decision.
Risk intelligence connects relevant operating evidence to the entities and controls that shape exposure. It supports investigation and review with explicit definitions. The assessment methodology, appetite and authority to accept a risk remain with the organization and its responsible specialists.
Keep risk measures and definitions together
Current balances, maximum contractual commitments and scenario estimates describe different exposures. The reporting scope, date, units and calculation rules explain how each measure relates to its source records.
BCBS 239 sets out principles for risk data aggregation and internal risk reporting, initially directed at systemically important banks. National supervisors may apply them more broadly. Risk and compliance teams assess the requirements applicable to their institution and reporting processes.
A newer receipt does not settle its allocation.
RECEIPT-21 · 09:20
£5,000 received
Allocation to the lending position has not yet been confirmed.
Keep the last confirmed funded position at £85,000, with its 09:00 observation time, until the authoritative source establishes the receipt’s effect.
Trace a change through the business
Start with a defined event such as a supplier interruption or a material change in counterparty status. Identify affected entities, active commitments and existing controls. Present the exposure with its assumptions and data gaps so the risk owner can review the appropriate response.
| Assessment element | Evidence to preserve |
|---|---|
| Entity scope | Included organizations, assets or relationships |
| Measure | Definition, units and calculation rule |
| Control | Owner, status and supporting evidence |
| Decision | Assessment, approval and review date |
Make assumptions and gaps visible
Dependencies can be inferred, incomplete or outdated. An aggregate may omit a source that was unavailable at the reporting date. These gaps affect how the risk owner interprets the result.
Scenario analysis separates observed conditions from assumed changes. The model version and assumptions explain how a scenario or calculated score was produced and how it differs from a forecast.
Reconcile changes in exposure
Missing entities, revised records and overlapping relationships can create differences in reported exposure. Comparing the contributing records with the approved baseline helps identify omissions, corrections and double counting.
Unresolved reconciliation items and time spent explaining a change show where the review process needs attention. Source links and shared definitions help the risk owner follow a movement back to the records behind it.
Discuss your priorities with us.
- Make exposure definitions and dependencies explicit
- Preserve evidence for risk assessment decisions
- Distinguish observed conditions from scenario assumptions