CAIIB – BFM

CAIIB BFM – December 2026

Article

90/174

Liquidity MIS, RBI Reporting, Controls and Decision Cases - Article

This article explains liquidity MIS, RBI regulatory reporting, internal controls and management decisions through practical banking cases. It covers the information that should reach the Board and ALCO, Structural Liquidity Statements, Basel Liquidity Returns, reporting frequency, data quality, limit breaches, escalation and independent review. It helps CAIIB BFM learners distinguish reliable liquidity information from mere regulatory return preparation.

Free preview 14 min read 4 views English
Published
In this article

Introduction

Liquidity management depends on information.

A bank may have:

  • sufficient deposits;

  • a large investment portfolio;

  • an adequate LCR;

  • available borrowing lines; and

  • a Contingency Funding Plan,

but management can still make a wrong decision if its liquidity information is:

  • incomplete;

  • inaccurate;

  • delayed;

  • too highly aggregated; or

  • based on unrealistic assumptions.

A sound Management Information System (MIS) should therefore tell management not only where liquidity stands today but also where problems may develop.

The current 2026 IIBF BFM syllabus specifically covers Management Information System, Reporting to the Reserve Bank of India and Internal Controls within Liquidity Risk Management.

The current regulatory framework is the Reserve Bank of India (Commercial Banks – Asset Liability Management) Directions, 2025, issued on November 28, 2025 and effective from that date. It contains requirements relating to liquidity MIS, controls, Structural Liquidity Statements and Basel III liquidity reporting.

For CAIIB case studies, remember:

Good liquidity management requires the right information, reaching the right authority, at the right time, followed by the right action.

Learning Objectives

After studying this topic, you should be able to:

  • explain the purpose of liquidity MIS;

  • identify the information that liquidity reports should contain;

  • distinguish internal MIS from RBI regulatory reporting;

  • understand current SLS and Basel Liquidity Return requirements;

  • explain the role of internal controls and independent review; and

  • solve liquidity-reporting and decision cases systematically.

What Is Liquidity MIS?

Liquidity MIS is the information framework used by the bank to:

  • collect liquidity data;

  • measure exposures;

  • identify trends;

  • compare positions with limits;

  • communicate risk to management; and

  • support decisions.

RBI's current Commercial Banks ALM Directions require banks to maintain a reliable MIS providing timely and forward-looking liquidity information to the Board and ALCO under both normal and stressed conditions.

The MIS must cover:

  • currencies in which the bank operates;

  • branches and subsidiaries;

  • aggregate group position;

  • contingent liquidity risks;

  • risks from new activities; and

  • more granular, time-sensitive information during stress.

What Should a Liquidity-Risk Report Contain?

Under RBI's current framework, liquidity-risk reports should contain sufficient information to assess how the bank may be affected by changes in:

  • market conditions;

  • its own financial performance; and

  • other material risk factors.

RBI identifies eight important areas.

1. Cash-Flow Projections and Gaps

Management should know:

  • expected inflows;

  • expected outflows;

  • maturity mismatches; and

  • cumulative liquidity gaps.

A single current cash balance cannot show the future liquidity position.

2. Asset and Funding Concentrations

MIS should reveal excessive reliance on:

  • large depositors;

  • particular funding instruments;

  • short-term wholesale markets;

  • currencies; or

  • particular asset classes.

3. Critical Assumptions

Liquidity projections often depend on assumptions about:

  • deposit withdrawals;

  • loan repayments;

  • rollover of funding;

  • utilisation of credit lines; and

  • marketability of assets.

Management should know which assumptions drive the reported liquidity position.

4. Funding Availability

A report should distinguish between:

  • funding that is genuinely available; and

  • funding that is merely expected to be available.

5. Compliance with Limits

MIS should show compliance with:

  • RBI requirements; and

  • internal liquidity limits.

A breach should be clearly visible.

6. Stress-Test Results

Management should know what happens under:

  • bank-specific stress;

  • market-wide stress; and

  • combined stress.

7. Early-Warning Indicators

Examples include:

  • deposit outflows;

  • rising funding costs;

  • shortening funding maturity;

  • falling market access; and

  • negative publicity.

8. Contingency Funding and Collateral

Management should know:

  • which contingency sources remain available;

  • which assets are pledged;

  • which assets remain unencumbered; and

  • how quickly collateral can be mobilised.

These items are explicitly included in RBI's current liquidity-reporting requirements.

Process diagram showing how liquidity data is converted into MIS, reviewed against limits and used by ALCO for liquidity decisions.
Liquidity MIS becomes useful only when reliable information leads to timely management action.

MIS Quality: Five Important Characteristics

A good liquidity MIS should be:

Accurate

Incorrect cash flows produce incorrect gaps.

Complete

Important:

  • currencies;

  • branches;

  • contingent exposures; or

  • off-balance-sheet items

should not be omitted.

Timely

Liquidity information can lose value quickly.

A report showing yesterday's position may be inadequate during rapid deposit outflows.

Granular

Management may need detailed information by:

  • depositor;

  • currency;

  • branch;

  • legal entity;

  • product; or

  • maturity.

Forward-Looking

The bank should assess future obligations rather than only today's balance sheet.

RBI specifically requires the MIS to become more granular and time-sensitive during stress.

Internal MIS vs RBI Regulatory Reporting

These are related but different.

Basis

Internal Liquidity MIS

RBI Regulatory Reporting

Main User

Board, ALCO, Treasury, Risk Management

RBI

Main Purpose

Management and decision-making

Supervisory monitoring and compliance

Frequency

Based on management need; can be very frequent

As prescribed by RBI

Detail

Can be more granular

Prescribed return format

Stress Use

Can move to near-real-time monitoring

RBI may require increased reporting frequency

Result

Management action

Regulatory supervision

A bank should not conclude:

“All RBI returns were submitted, therefore our liquidity MIS is adequate.”

Regulatory reporting does not replace internal decision-making systems.

Current RBI Structural Liquidity Reporting

Under the 2025 Commercial Banks ALM Directions, a bank must prepare its domestic Structural Liquidity Statement (SLS) in rupees on a daily basis.

The regulatory Liquidity Return contains five SLS parts:

Part

Structural Liquidity Statement

Periodicity

A1

Domestic Currency – Indian Operations

Fortnightly

A2

Foreign Currency – Indian Operations

Fortnightly

A3

Combined Indian Operations

Fortnightly

B

Overseas Branch Operations

Monthly

C

Consolidated Bank Operations

Quarterly

These periodicities are prescribed under the current 2025 Directions.

The RBI Filing of Supervisory Returns Directions, 2024 provide the broader framework and timelines for submission of supervisory returns.

Basel III Liquidity Returns

The current Commercial Banks ALM Directions also prescribe Basel III Liquidity Returns.

Important BLRs include:

Return

Main Information

Periodicity

BLR-1

Liquidity Coverage Ratio

Monthly

BLR-2

Funding Concentration

Monthly

BLR-3

Available Unencumbered Assets

Quarterly

BLR-4

LCR by Significant Currency

Monthly

BLR-5

Other Information on Liquidity

Monthly

BLR-6

Intraday Liquidity Monitoring Tools

Monthly

BLR-7

Net Stable Funding Ratio

Quarterly

BLR-6 is reported on standalone and consolidated bases as applicable under the framework. RBI also requires banks to maintain the operational capacity to increase reporting frequency to weekly or even daily during stress if directed by RBI, with reporting delays kept as short as feasible.

The current BLR-1 format itself confirms monthly LCR reporting.

Why Multiple Returns Are Needed

Different returns answer different questions:

  • SLS: When will cash-flow mismatches occur?

  • BLR-1: Is the short-term LCR position adequate?

  • BLR-2: Is funding excessively concentrated?

  • BLR-3: Which unencumbered assets could support funding?

  • BLR-4: Is there currency-specific LCR vulnerability?

  • BLR-6: Can intraday payment obligations be managed?

  • BLR-7: Is the longer-term funding structure stable?

No single return captures every dimension of liquidity risk.

Hierarchy explaining current RBI Structural Liquidity and Basel Liquidity Returns with their reporting periodicities for commercial banks.
RBI liquidity reporting combines maturity-gap, funding, collateral, currency, intraday, LCR and NSFR information.

Internal Controls over Liquidity Management

Accurate reporting requires controls over:

  • data;

  • assumptions;

  • calculations;

  • limit monitoring;

  • approval;

  • escalation; and

  • regulatory submission.

Under the current RBI framework, banks must maintain appropriate systems and controls to ensure:

  • compliance with liquidity-risk policies; and

  • adequate functioning of the liquidity-risk management process.

Top management must also ensure that an independent party regularly reviews and evaluates the process.

The independent review should examine compliance with:

  • regulatory requirements; and

  • the bank's own policy.

Material issues and non-compliance should be reported for prompt corrective action.

Control over Data and Assumptions

Liquidity numbers may be mathematically correct but economically wrong if the assumptions are poor.

Important controls should therefore test:

  • correct maturity bucketing;

  • behavioural assumptions;

  • deposit run-off assumptions;

  • loan repayment assumptions;

  • off-balance-sheet exposures;

  • foreign-currency positions;

  • collateral availability; and

  • completeness of branch data.

Example

A ₹500 crore corporate deposit contractually matures after six months.

However, the bank allows premature withdrawal and the customer has historically withdrawn deposits early.

Ignoring behavioural characteristics can distort liquidity projections.

The issue is not only calculation accuracy.

It is also assumption accuracy.

Decision Case 1: Green Dashboard, Stale Data

ALCO receives a dashboard showing:

  • comfortable liquidity gaps;

  • LCR above minimum;

  • no major limit breach.

However, the data are two days old.

During those two days, a large corporate depositor has withdrawn substantial funds.

Analysis

The dashboard may be numerically correct for its reporting date but unsuitable for the current decision.

During stress, RBI expects more:

  • granular; and

  • time-sensitive

liquidity information.

Correct Decision

Management should:

  • obtain updated liquidity data;

  • reassess funding gaps;

  • review available liquidity;

  • check EWIs; and

  • escalate if necessary.

CAIIB Lesson

Accuracy without timeliness can still produce bad liquidity decisions.

Decision Case 2: LCR Is Strong but Funding Is Concentrated

A bank reports a comfortable LCR.

However, its BLR-2 shows a rapidly increasing dependence on a few large depositors.

Management argues:

“No action is required because LCR is above 100%.”

Analysis

This is incomplete reasoning.

BLR-2 specifically monitors funding concentration. The current RBI format captures significant counterparties and top large deposits.

A bank can simultaneously have:

  • adequate short-term HQLA; and

  • an increasingly fragile funding structure.

Correct Decision

ALCO should assess:

  • depositor concentration;

  • stability;

  • maturity;

  • alternative funding; and

  • stress outflows.

CAIIB Lesson

Compliance with one liquidity measure does not remove vulnerabilities identified by another measure.

Decision Case 3: Return Submitted Correctly but Internal Limit Breached

A bank's SLS is correctly prepared and submitted to RBI on time.

The regulatory short-term mismatch limits are met.

However, the bank has breached a stricter Board-approved internal limit.

Management proposes no action because there is no RBI violation.

Analysis

The current RBI MIS framework requires reporting of compliance with both regulatory and internal liquidity limits.

Internal limits form part of the bank's own risk appetite.

Correct Decision

The breach should be:

  • reported;

  • investigated;

  • escalated according to policy; and

  • corrected where required.

CAIIB Lesson

Regulatory compliance does not permit management to ignore its own approved risk limits.

Decision Case 4: Overseas Branch Missing from MIS

Head Office liquidity MIS shows a comfortable consolidated position.

Later, management discovers that a material foreign branch's current cash flows were not included because of an interface failure.

Analysis

RBI requires liquidity MIS to cover branch/subsidiary positions, currencies and aggregate group liquidity.

This is both:

  • a liquidity measurement problem; and

  • an internal-control failure.

Correct Decision

The bank should:

  • correct the data;

  • reassess the liquidity position;

  • determine whether reports submitted externally were affected;

  • fix the interface; and

  • independently validate the corrective action.

CAIIB Lesson

A consolidated report is reliable only when the underlying entity-level data are complete.

Decision Case 5: Stress Test Shows Funding Shortfall

A stress test shows that the bank may exhaust usable liquidity much earlier than its approved survival horizon.

The result appears in the MIS, but no action is taken because the current actual liquidity position is comfortable.

Analysis

Liquidity MIS exists to support forward-looking decisions.

The bank should consider:

  • increasing liquid assets;

  • diversifying funding;

  • reducing vulnerable maturity gaps;

  • improving collateral availability; or

  • strengthening the CFP.

The presence of a stress-test result in the report is not enough.

CAIIB Lesson

Reporting a risk is not the same as managing the risk.

Decision Case 6: Expected Funding Treated as Certain

The liquidity report includes ₹2,000 crore of emergency market borrowing as available funding.

The facility is not committed and has never been tested.

Management therefore concludes that there is no projected shortfall.

Analysis

RBI requires liquidity reports to include funding availability and the status of contingent funding sources.

An uncommitted source should not be treated with the same confidence as cash already available.

Management should assess:

  • legal availability;

  • market access;

  • collateral;

  • activation time; and

  • performance under stress.

CAIIB Lesson

Potential funding and available funding are not automatically the same.

Decision Case 7: Independent Review Finds Repeated Errors

Internal review finds that several branches repeatedly misclassify maturity buckets in SLS data.

The total impact on the latest return is small.

Management proposes closing the issue because the bank remains within regulatory limits.

Analysis

Repeated errors indicate a weakness in:

  • data quality;

  • process design;

  • training; or

  • system controls.

RBI requires independent review to report weaknesses and instances of non-compliance requiring prompt corrective action.

Correct Decision

The bank should address the root cause through:

  • system validation;

  • procedure correction;

  • training;

  • automated controls; or

  • enhanced review.

CAIIB Lesson

A small current financial impact does not make a recurring control weakness unimportant.

Decision Case 8: Major Liquidity Event Waits for Normal Reporting

A bank suffers unusually high digital deposit withdrawals following negative news.

The normal ALCO report is due three days later.

The liquidity team decides to wait for the scheduled report.

Analysis

This is poor liquidity governance.

A material event should trigger:

  • enhanced monitoring;

  • updated cash-flow projections;

  • rapid management reporting; and

  • escalation.

The current RBI Directions expect banks to be capable of more frequent reporting during stress, including weekly or daily regulatory reporting where directed.

CAIIB Lesson

Normal reporting frequency should not delay action during abnormal liquidity stress.

MIS, Reporting and Controls Compared

Area

Core Purpose

Main Failure Risk

MIS

Support management decisions

Stale, incomplete or misleading information

RBI Reporting

Provide supervisory information

Incorrect, incomplete or delayed regulatory returns

Internal Controls

Ensure reliability and compliance

Undetected errors or policy breaches

Independent Review

Challenge the process

Weaknesses remain unidentified

ALCO Decision

Take balance-sheet action

Information is reported but ignored

The strongest system connects all five.

CAIIB Case-Study Framework

For liquidity reporting cases, use D–R–A–C.

D — Data

Ask:

  • Is it accurate?

  • Complete?

  • Timely?

  • Granular?

R — Risk

What does the information show?

  • Gap?

  • Concentration?

  • Limit breach?

  • Stress vulnerability?

  • Funding shortage?

A — Authority and Action

Who should act?

  • Treasury?

  • ALCO?

  • Senior management?

  • Board?

What corrective action is required?

C — Control

Ask:

  • Why did the issue arise?

  • Has the root cause been corrected?

  • Has independent review confirmed closure?

CAIIB Exam Focus

Remember these high-value points:

  • Liquidity MIS should be timely and forward-looking.

  • MIS must work under normal and stressed conditions.

  • It should cover currencies, entities and aggregate group liquidity.

  • Contingent risks and new activities should also be captured.

  • RBI identifies cash-flow gaps, concentrations, assumptions, funding availability, limits, stress tests, EWIs and contingency funding/collateral as important liquidity-reporting information.

  • Domestic rupee SLS is prepared daily.

  • Current SLS regulatory reporting has five parts.

  • A1, A2 and A3 are fortnightly.

  • Overseas Branch SLS is monthly.

  • Consolidated Bank SLS is quarterly.

  • BLR-1 LCR is monthly.

  • BLR-2 Funding Concentration is monthly.

  • BLR-3 Available Unencumbered Assets is quarterly.

  • BLR-4 Significant-Currency LCR is monthly.

  • BLR-5 Other Liquidity Information is monthly.

  • BLR-6 Intraday Liquidity Monitoring is monthly.

  • BLR-7 NSFR is quarterly.

  • Banks should be capable of more frequent reporting during stress when required.

  • Internal controls should ensure compliance with both regulatory requirements and internal policies.

  • Independent review is an important control.

  • A correct regulatory return does not automatically mean the internal liquidity position is acceptable.

  • A limit breach should lead to investigation and action.

  • MIS is useful only when management acts on the information.

Common Exam Traps

Trap 1: “Liquidity MIS and RBI liquidity returns are the same.”

Incorrect. Regulatory returns are only one part of the wider information needed for internal liquidity decisions.

Trap 2: “If the data are accurate, reporting delay does not matter.”

Incorrect. Liquidity changes rapidly, making timeliness critical.

Trap 3: “The SLS is prepared only when it is due for submission to RBI.”

Incorrect. Domestic rupee SLS is prepared daily while regulatory submission of specified parts follows prescribed periodicities.

Trap 4: “A strong LCR means funding concentration need not be monitored.”

Incorrect. BLR-2 separately monitors concentration risk.

Trap 5: “Meeting RBI limits means internal limit breaches can be ignored.”

Incorrect. The bank must also operate within its Board-approved internal framework.

Trap 6: “A consolidated liquidity surplus proves every branch and currency is liquid.”

Incorrect. Entity and currency-specific shortages can remain hidden.

Trap 7: “All funding shown in a contingency plan can be treated as immediately available.”

Incorrect. Availability, timing, collateral and stress-market access must be assessed.

Trap 8: “Internal audit or independent review manages liquidity risk.”

Incorrect. Management owns the liquidity process. Independent review evaluates whether the process is working and compliant.

Trap 9: “Reporting a stress-test weakness completes the bank's responsibility.”

Incorrect. Material vulnerabilities should lead to appropriate management action.

Trap 10: “Normal reporting frequency remains sufficient during every crisis.”

Incorrect. Liquidity monitoring and reporting may need to become significantly more frequent during stress.

Memory Technique

Remember M–R–C–D:

M — MIS: What is the liquidity position? R — Reporting: What must be communicated internally and to RBI? C — Controls: Can the data and process be trusted? D — Decision: What should management do?

For any case, ask:

Is the information Accurate → Timely → Complete → Actionable?

The central CAIIB principle is:

Liquidity reporting has value only when reliable data reveal risk early enough for management to take corrective action.

Back to Liquidity MIS, RBI Reporting, Controls and Decision Cases