How to Read a Bank Statement for Credit Assessment: Step-by-Step Guide
A structured guide to analysing bank statements for credit decisions — covering income verification, EMI detection, cash flow patterns, fraud signals, and MSME-specific nuances.
Gourav Dalal
Co-founder & CEO · Santulan
Bank statement analysis is one of the most important skills in credit underwriting — and one of the most poorly standardised. Most analysts learn it informally, absorbing the practices of whoever trained them, which vary widely across institutions and geographies. This guide sets out a systematic framework for reading bank statements for credit assessment that works across both retail and MSME lending contexts.
Step 1: Verify the Statement Itself
Before analysing a single transaction, verify that the statement is authentic. This step is not optional — statement fraud has become prevalent enough that treating every statement as potentially manipulated is the appropriate default posture.
Check: Is the bank name and statement format consistent with genuine statements from that bank? Is there a digital signature or security feature (watermark, QR code)? Are the fonts consistent throughout — mixed fonts on a text-layer PDF are a fraud signal? Does the stated period (opening date to closing date) match the transactions inside? If a statement was downloaded from netbanking, does it have a verified download timestamp?
For high-value cases or when something feels off, run a mathematical check: Opening Balance + Sum of All Credits - Sum of All Debits should equal Closing Balance. Any discrepancy, however small, is a definitive indicator of tampering.
Step 2: Identify and Verify Income
Income identification is the most consequential analytical step for credit decisions. The goal is to determine: how much money comes in, from what sources, and how reliably.
For salaried borrowers, look for salary credits: these typically appear on a consistent date each month (±2–3 days), from a consistent counterparty (employer payroll), with a consistent amount (or a predictable increase pattern). Common description patterns include payroll processor tags (HDFC PAYROLL, NETSALARY, SALARY), employer names, or NEFT with a company name.
For self-employed and MSME borrowers, income is more complex. Business receipts arrive from multiple counterparties, in irregular amounts, on no fixed schedule. Focus on: total inflow volume over the analysis period, the consistency of that volume month-to-month (high variance = higher risk), the diversity of income sources (single-customer dependency is a risk factor), and the correlation between inflows and outflows (is the business genuinely trading, or is most inflow immediately transferred out?).
Step 3: Map All Fixed Obligations
Fixed obligations — existing EMIs and regular committed payments — are essential inputs to FOIR calculation. Bureau data gives you bureau-reported EMIs, but bank statements often reveal obligations that don't appear in bureau records: private lender loans, chit fund contributions, regular family remittances, subscription payments, and lease obligations.
Look for: ECS/NACH debits with consistent amounts and dates (these are almost always loan EMIs or SIP/insurance premiums); regular NEFT/IMPS payments to the same IFSC code or beneficiary; recurring UPI payments of fixed amounts. Cross-reference these against the bureau obligations list — every item that appears in statements but not in the bureau report is worth investigating.
Step 4: Assess Cash Flow Patterns
Beyond income and obligations, the cash flow pattern of a bank account tells you a great deal about financial health and credit risk. Key patterns to assess:
End-of-month balance: Does the account consistently approach zero before the next salary credit? This indicates living paycheck-to-paycheck with no buffer — acceptable in some risk profiles, concerning in others.
Intra-month liquidity: For MSME accounts, does the business run out of operating cash mid-cycle regularly? Are there frequent intra-day overdraft events?
Savings behaviour: Are there regular transfers to recurring deposits, mutual funds, or savings accounts? Consistent savings behaviour is one of the strongest positive credit signals available from bank statement data.
Emergency events: Are there sudden large withdrawals or inflows that disrupt the normal pattern? Understanding whether these are one-time events (acceptable) or recurring stress patterns (concerning) requires at least 6 months of statements.
Step 5: Flag Anomalies and Risk Signals
Having mapped income, obligations, and cash flow patterns, the final analytical step is flagging specific risk signals:
Circular transactions: Money that goes out and comes back in from the same counterparty, creating artificial inflow volume. Common in MSME accounts where the proprietor transfers between personal and business accounts.
Sudden balance changes: Large credits or debits shortly before the statement period that inflate or deflate the apparent balance pattern.
Loan-before-loan signals: A large credit arriving shortly before an EMI starts appearing — often indicating a loan taken to fund the deposit on another loan.
Cheque bounces: Returned cheque events (RCHQ, INWARD RETURN) are a direct indicator of liquidity stress and should be counted and trended.
Unusual transaction timing: Transactions timestamped on bank holidays or at times inconsistent with normal banking operations may indicate manipulation of a digital statement.
Automating the Framework
The five-step framework above is what good credit analysts do intuitively. The challenge is that doing it thoroughly, on every file, consistently across a credit team, takes significant time — typically 45–90 minutes per file for a thorough analysis.
AI-powered bank statement analysis platforms like Santulan AI automate the extraction and initial analytical steps, reducing analyst time to reviewing a structured output rather than constructing it from scratch. This doesn't remove analyst judgment — it focuses it on the decisions that actually require judgment, rather than on extracting and organising data.
Gourav Dalal
Co-founder & CEO
See it in action.
Book a live demo.
Run a real analysis on your own sample statements in under 2 minutes.