Not yet independently checked — please confirm with the official RBI source below
Source: Reserve Bank of India · RBI/DOR/2026-27/211 · issued FY 2026-27 · ~1 min read
Quick answerRBI amended Small Finance Banks' Asset Liability Management Directions to replace paragraphs 197 (LCR) and 243 (NSFR) with references to the 2025 Financial Statements and Capital Adequacy Directions. Effective April 1, 2027.
The rule, in the simplest words
RBI changed where Small Finance Banks must look for LCR and NSFR disclosure rules.
Instead of the old ALM directions paragraphs, banks must now use the 2025 Financial Statements and Capital Adequacy directions.
This change starts on April 1, 2027.
The amendment is consequent to the Capital Adequacy Fifth Amendment Directions, 2026, pertaining to Basel Pillar 3 disclosures.
How it plays out — a real example
Priya, the ALM head at a small finance bank, updates her team's reporting checklist. She replaces the old LCR template reference with the one from the 2025 Financial Statements Directions, ensuring her report after April 1, 2027 matches RBI's new format.
What changed
Paragraphs 197 (LCR disclosure) and 243 (NSFR disclosure) in the 2025 ALM Directions were replaced. SFBs must now refer to the 2025 Financial Statements and Capital Adequacy Directions for LCR and NSFR disclosure templates and instructions.
What it means for you
SFBs need to update their reporting systems to reference the 2025 Financial Statements and Capital Adequacy Directions for LCR and NSFR disclosure formats. Banks should train compliance teams on the new cross-referenced templates before the April 2027 deadline.
What you must do
Review the 2025 Financial Statements and Capital Adequacy Directions for LCR and NSFR disclosure templates.
Update internal ALM reporting manuals to reference the new disclosure sources.
Train ALM and compliance staff on the revised cross-referencing requirements.
Prepare systems to adopt the changes from April 1, 2027.
Who it affects
Small Finance Banks, ALM teams at SFBs, Compliance and reporting departments
❓ Common questions
Why did RBI change the disclosure reference?
Consequent to the issuance of the Capital Adequacy Fifth Amendment Directions, 2026, pertaining to Basel Pillar 3 disclosures.
When must we start using the new references?
From April 1, 2027.
Do we need to change our LCR and NSFR calculations?
The source does not address calculation methods; only disclosure template references change.
📜 Read the original circular — full text as issued by RBI
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/DOR/2026-27/211 · issued FY 2026-27. The plain-English explanation above is BankPulse’s own independent summary.
Review the 2025 Financial Statements and Capital Adequacy Directions for LCR and NSFR disclosure templates.
Prepare systems to adopt the changes from April 1, 2027.
📜 Compliance
Update internal ALM reporting manuals to reference the new disclosure sources.
Train ALM and compliance staff on the revised cross-referencing requirements.
Grouped from the action items above — a single circular may involve more than one team.
Worked example & action-note template
Example: if you are an IT/Systems lead at a bank this circular applies to (Small Finance Banks, ALM teams at SFBs, Compliance and reporting departments), your first concrete step on “SFB ALM Disclosure References Updated” is: “Review the 2025 Financial Statements and Capital Adequacy Directions for LCR and NSFR disclosure templates.” (RBI issued this FY 2026-27).
Action required: Review the 2025 Financial Statements and Capital Adequacy Directions for LCR and NSFR disclosure templates.
Action required: Update internal ALM reporting manuals to reference the new disclosure sources.
Action required: Train ALM and compliance staff on the revised cross-referencing requirements.
Action required: Prepare systems to adopt the changes from April 1, 2027.
Owner: ____________ Target date: ____________
Board/committee approval needed? Y / N
Evidence filed in compliance register on: ____________
Built only from this circular’s own published fields — not legal advice; always confirm against the official RBI source.
💬 Banker Discussion
Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.
BankPulse Compliance Evidence Pack — generated 30 Jul 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly). Official RBI source: https://www.rbi.org.in/scripts/NotificationUser.aspx?Id=13653&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.