Skip to main content
How-To · 7 min read

How to Validate Bank-Statement-Based MSME Underwriting Against Your Closed Loans Before You Rely on It

Before relying on synthetic financials or bank-statement signals for MSME credit, replay the tool on loans you have already closed and compare its view at application date with what actually happened. Judge whether it ranks risk in the right order across the book, not whether it was right on any single loan.

Terra Insight
Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 14 October 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Knowledge Card
Problem

Lenders adopt bank-statement-based MSME scoring and synthetic financials on the strength of vendor demos, without checking whether the tool's view at application would have ranked their own borrowers' later repayment correctly.

How It's Resolved

Replay the tool blind on around 200 closed MSME loans using statements held at application, group results into tool bands, compare 90-day delinquency by band, and note segments the tool cannot assess.

Configuration

Closed-loan sample with application-date statements, outcomes and the decision taken then; outcome fields hidden from the tool; a bias log covering survivorship and approved-only data; owners for each step.

Output

A band-by-delinquency table, a list of borrower types where the tool cannot form a view, analyst override patterns and a clear statement of how far the credit head can rely on the tool.

Before you rely on synthetic financials or bank-statement signals for MSME credit, replay the tool on loans you have already closed. Give it the statements you held at application date, keep the outcomes hidden, and compare its view with what actually happened. Judge whether it ranks risk in the right order across the book; no tool will be right on every single loan.

For background on how these figures are built, see synthetic financial statements for MSMEs and MSME credit without audited financials.

How do you build the back-test?

Pull closed MSME loans, typically disbursed 18 to 36 months ago so outcomes have had time to show. For each loan you need:

  • The statements held at application, exactly as received, not a later download.
  • The outcome: repaid on time, 30 days late, 90 days past due, restructured or written off.
  • The decision taken then: amount, tenor and any conditions.
  • Product and segment: for example term loans and working-capital lines, and borrower size under the MSME classification revised from 1 April 2025, under which a micro enterprise has investment up to ₹2.5 crore and turnover up to ₹10 crore, a small enterprise up to ₹25 crore and ₹100 crore, and a medium enterprise up to ₹125 crore and ₹500 crore.

Keep the tool blind to outcomes. Send only the statements and application data; hold outcomes in a separate sheet that only your risk team sees until the read-out.

StepData neededBias riskSafeguardOwner
Select loansClosed MSME loans, 18 to 36 months oldOnly approved loans are in the sampleState plainly that declined applicants are not testedRisk
Gather statementsApplication-date statementsLater statements leak outcome informationUse only files dated before disbursalCredit operations
Hide outcomesRepayment historyVendor tunes to known outcomesOutcomes held by risk until read-outRisk
ReplayStatements and application dataSurvivorship: loans sold or closed early drop outRecord excluded loans and whyVendor and credit analyst
Read-outTool bands and outcomesSmall counts of bad loansReport counts, not just percentagesCredit head

Remember throughout that synthetic financials are approximations built from bank flows. They are not audited statements and do not replace them.

What do you read from it?

Three things:

  1. Ranking quality. Do weaker tool bands line up with higher later delinquency? Look at the order across bands, not a single loan.
  2. Blind spots. Which borrower types the tool cannot assess well: cash-heavy traders whose sales never touch the bank, and proprietors who run business through a personal account. The personal vs business separation article explains why mixed accounts are hard.
  3. Overrides. Where your analysts approved against what the tool would have suggested, and how those loans performed.

Worked example: 200 closed loans

Illustrative figures. A lender replays 200 closed MSME loans across two products and groups the tool’s output into three bands.

Tool bandLoans90 days past dueRate
Strong8033.75%
Moderate70710%
Weak501020%
Total2002010%

Delinquency rises steadily from strong to weak, so the tool ranks this approved book in the right order. What the credit head can safely conclude: the tool’s bands are useful for pricing, limits and review intensity on borrowers like these. What the credit head cannot conclude: that the tool would have done well on declined applicants, or that a strong band guarantees repayment, since 3 of 80 strong-band loans still went 90 days past due.

Then split the result by segment. If 12 of the 50 weak-band loans are cash-heavy traders whose statements show little business activity, the tool may be saying “cannot tell” rather than “high risk” for that group, and the policy should route them to other evidence such as GST returns.

How should the result change your policy?

Write the conclusion as a reliance statement: which products and segments the tool may be used for, which bands trigger manual review, and which borrower types need other evidence. Repeat the back-test once a year on newly closed loans, because borrower mix and bank formats change.

To check the tool itself before the back-test, the same buyer test applies:

TestWhat to give the vendorWhat a pass looks like
Synthetic financialsStatements for 5 borrowers with audited accountsFigures labelled as approximations; differences from audited accounts explained
Account mixingA proprietor’s personal account used for businessPersonal and business flows separated, with the rows shown
Blind replayApplication-date statements onlyOutput produced without outcome data

How Terra Insight fits

TransactIQ builds synthetic P&L, balance sheet and cash flow from bank statements for MSME underwriting, alongside 40+ engineered credit signals, and runs as a managed service on Terra Insight’s AWS Mumbai infrastructure. These synthetic financials are approximations to read with other evidence, not audited statements. Evaluating teams can send a representative sample for a fit benchmark; see MSME lending.

Primary reference: Ministry of Micro, Small and Medium Enterprises — the official source for MSME classification thresholds revised with effect from 1 April 2025.

Frequently Asked Questions

What is a back-test of bank-statement-based MSME underwriting?
It is a replay of the tool on loans you have already closed. You give it the statements held at application date, keep the outcomes hidden, and then compare the tool's view with what happened: repaid on time, late, restructured or written off.
How many closed loans do we need?
Around 200 closed loans gives a usable view across risk bands, with enough delinquent cases to see a pattern. Fewer than 20 bad outcomes makes any band comparison unreliable.
What is the main bias risk?
Your closed loans are only the ones you approved. The back-test says nothing about applicants you declined, so it can show whether the tool ranks approved borrowers well, not whether it would have approved good borrowers you turned away.
Are synthetic financials a substitute for audited statements?
No. Synthetic P&L, balance sheet and cash flow built from bank statements are approximations. They help where audited financials are missing or stale but are not audit-grade and should be read alongside GST returns and other evidence.
What result should make us cautious?
If delinquency does not rise from the strongest to the weakest tool band, or if one borrower type, such as cash-heavy traders, sits mostly in bands where the tool cannot form a view, limit reliance on the tool for that segment.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.