Bank Statement Analysis for Lenders: Spot Red Flags the Same Way Every Time
Turn bank statement review into a repeatable set of checks for income, obligations and red flags that every credit analyst applies the same way.
This is for credit heads and underwriting managers at NBFCs, small business lenders and co-lending desks who rely on bank statements to judge repayment capacity. When each analyst reads statements their own way, income gets overstated, existing loans get missed and fabricated statements slip through. This post sets out a consistent bank statement analysis routine, the red flags worth codifying, and a standard summary format that makes every credit decision easier to defend in audit and to a co-lending partner.
Two analysts review the same twelve months of a trader's current account. One counts every credit as business income; the other strips out transfers from a family member's account and a one-off loan disbursal. Their eligible income figures differ widely, and the credit committee has no way to tell which method was used.
Meanwhile the statement shows a recurring debit to another lender that never appeared on the application, and a cluster of inward and outward transfers with the same counterparty on the same day. Without a defined checklist these patterns depend on whether the analyst happened to look for them, which makes portfolio quality depend on individual attention.
A small business lender in Ahmedabad noticed that eligible income on similar files varied by analyst, and an internal audit found undeclared loans that statements had clearly shown. The credit head wrote income inclusion rules, a list of obligation patterns to extract, and a same-day matching test for circular flows. Statements fetched through the account aggregator route were preferred, and uploaded PDFs got a balance-continuity check. Every analyst now completes one summary template. Credit committee discussions became shorter because the method was visible, undeclared obligations were caught before sanction, and a co-lending partner's due diligence on sampled files went more smoothly.
How many months of bank statements should we analyse?
It depends on product, ticket size and your credit policy. Many lenders use six or twelve months for business loans. Decide the period by product, write it into policy, and check any partner or regulatory requirements with your compliance team.
Is account aggregator data better than PDF statements?
Data fetched through the account aggregator framework comes directly from the bank with consent, which reduces tampering risk and removes manual parsing. Keep a fallback route for borrowers whose bank or account type is not yet available.
What counts as a circular transaction?
Typically money that leaves and returns through the same or related parties within a short period, inflating turnover. Define your own window and amount thresholds, and treat a match as a question for the borrower rather than automatic rejection.
Should bounces automatically lead to rejection?
Not always. Record the count, timing and reason of inward and outward bounces in the summary. Credit policy should state how many and which types trigger a decline, a deviation or simply a closer look.
Want this fixed in your business?
Send the workflow. You get a scope and a fixed price within two working days — or a straight answer that it isn't a fit.