CISI Risk in Financial Services: Separate Cause from Consequence

Table of Contents

• • 1. Separate cause, exposure and consequence
• • 2. Read the incident as a timeline
• • 3. Answer the question asked in Risk in Financial Services
• • 4. Match each control to the failure it addresses
• • 5. Change one fact and explain what moves
• • 6. Use a four-line explanation to check understanding

In CISI Risk in Financial Services, identifying a risk type starts with identifying the question’s focus. A single incident can begin with a failed process, produce a cash shortage and end with a forced asset sale. Calling the whole sequence “operational risk” misses the later exposures; calling everything “liquidity risk” misses the initiating failure.

Work through the fictional incident below, then change one fact at a time. The aim is to connect the definitions you already know, not memorise another list. The current official CISI syllabus explicitly includes interacting risk drivers and relationships between financial-system risks.

1. Separate cause, exposure and consequence

Use three questions before looking at possible answers: What happened first? What could now go wrong? What loss or disruption followed? These are related, but they ask for different parts of the incident.

The Basel Committee’s operational-risk guidance centres on failures involving processes, people, systems or external events. The fact that a resulting loss is measured in money does not convert that failure into market risk.

Likewise, identifying an initial operational failure does not make the rest of the story irrelevant. Treasury may need to handle a cash shortage while operations restores the failed process. Different teams can therefore address different risks arising from the same incident without contradicting each other.

2. Read the incident as a timeline

Imagine a fictional financial firm with payments due this afternoon. Its cash forecast assumes an incoming transfer will arrive before those payments. A software configuration error prevents the instruction from being released. The counterparty remains able and willing to pay; the failure is in the processing sequence.

Stage	New fact	Risk interpretation
Morning	The payment instruction is not released because of a system error	An operational failure starts the incident
Early afternoon	Expected funds are unavailable while obligations fall due	A funding-liquidity pressure develops
Later	The firm seeks to sell bonds quickly, but buyers demand a substantial discount for the size	Market-liquidity conditions constrain the response
Possible separate development	Market yields rise while the bond position remains open	The position also faces market-price risk

The last row is deliberately conditional. Do not invent a yield change just because the story mentions bonds. Similarly, do not infer counterparty default from a transfer delayed by the firm’s own system. Correct classification depends on facts actually supplied.

The Basel Committee’s liquidity guidance discusses links between funding and market liquidity and the effect of operational disruptions on expected flows. Our timeline is an original teaching example of those relationships, not a report of an actual firm.

3. Answer the question asked in Risk in Financial Services

Now use the same incident for four different questions.

What initiated the disruption? The configuration failure. Operational risk is the relevant starting point; the subsequent need for cash does not rewrite the cause.

What threatens the firm’s ability to make its afternoon payments? Insufficient available funds at the required time. This focuses on funding liquidity, even if the firm owns valuable assets overall.

Why is selling the bond position expensive? In the stated example, the size cannot be absorbed without a substantial discount. That is a market-liquidity issue. A general rise in yields would be a different explanation involving market-price movement.

Which risk becomes central if the counterparty is actually unable to pay? Credit risk now becomes relevant. That answer requires a changed fact; it was not established by the original processing delay.

Try the native course sample below while applying the same discipline: identify the requested decision before selecting a familiar risk label.

4. Match each control to the failure it addresses

A sensible control is not automatically the best answer to every version of the problem. Change testing and release controls address the defective configuration. Payment-status monitoring can detect an instruction that has not progressed. A tested contingency-funding plan addresses the cash pressure that remains while the system is repaired.

Suppose the question asks which measure most directly reduces recurrence of the initiating error. Choosing a larger cash buffer may reduce the consequences, but it does not correct the configuration process. Conversely, if payments are due shortly and the question asks about immediate liquidity response, a future software-review policy does not meet today’s obligation.

Distinguish prevention, detection and mitigation in your explanation. Ask what remains exposed after the control works. Restoring the payment system may not instantly reverse an asset-sale loss or repair damaged client confidence. Avoid claiming that one control eliminates all risks in the chain.

5. Change one fact and explain what moves

Use these variations as a closed-book drill. They are original practice prompts, not official questions.

1. The instruction is released correctly, but the counterparty defaults. The initiating fact now supports credit risk rather than the original systems failure. Funding consequences may still follow.
2. The firm has enough cash and does not sell anything. The operational failure remains, but the stated funding shortage and forced-sale consequences no longer occur in this variation.
3. The bonds can be sold promptly at normal market prices, but those prices have fallen because yields rose. The adverse price move is market risk; do not label it an inability to transact simply because the sale crystallises a loss.
4. Management receives an accurate warning but nobody acts on it. The system is no longer the only issue. The facts now invite examination of escalation, accountability and control execution.

For each variation, keep unchanged facts unchanged. This prevents a common reasoning error: rewriting the whole story until your preferred answer becomes correct.

6. Use a four-line explanation to check understanding

Finish each scenario with four lines: the decisive fact, the requested risk or control, the closest competing interpretation and why that alternative does not fit. If you cannot identify a competing interpretation, revisit the boundary between the concepts rather than memorising only the correct label.

Keep calculation exercises separate when they test a different skill. Naming liquidity risk does not demonstrate that you can calculate a required measure, just as recalling a formula does not prove you understand the risk it measures. Cover the full syllabus alongside these linked scenarios.

Before your sitting, check the current CISI Risk in Financial Services qualification information and applicable learning materials. Use the course and practice tools to test unfamiliar cases. The useful sign of progress is that your answer changes for the right reason when a relevant fact changes—not simply that you recognise a familiar story.