Skip to Content
Blog (drafts)8. Why loans get rejected

Why Loan Applications Get Rejected at the Bank Statement Stage (and How DSAs Can Pre-Check)

The most common loan rejection reasons in a bank statement are a high FOIR, recent NACH or ECS bounces, a low average balance, unexplained large credits, heavy cash deposits, and a banking history that is too short to read. Most of these are visible the moment you open the statement. If you are a DSA, you can pre-check them before you submit the file, and stop burning good leads on rejections you could have predicted.

You sourced the lead. You collected the KYC, the income proof, and three months of bank statements. You packaged the file, sent it to the lender, and waited. Then the rejection came back over a bounce you never noticed, or a FOIR you never ran. The borrower is annoyed, the lender’s hit rate on your files drops, and you do not get paid. This post breaks down what lenders actually look for in the statement, and gives you a checklist to run yourself.

Why does the bank statement reject a loan so often?

Because the bank statement is the one document the borrower cannot easily dress up. Salary slips and ITRs can be optimistic. The statement is the ledger of what actually moved through the account: every credit, every debit, every failed mandate. Lenders treat it as ground truth, and they reject hard on it. For a full primer on how lenders read the statement, see our pillar guide on bank statement analysis.

For a DSA, the painful part is timing. The lender sees these problems in minutes. You only find out days later, after the file is already in their system and your conversion number has taken the hit. The fix is to look at the same things the lender looks at, before you submit.

What are the top rejection triggers visible in a bank statement?

These are the seven that come up again and again. Each one is something you can see yourself with a careful read.

#TriggerWhat the lender concludes
1High FOIRThe borrower is already over-leveraged; no room for a new EMI
2NACH / ECS bouncesExisting obligations are not being serviced cleanly
3Low average balanceThin cushion; account runs close to zero
4Unexplained large creditsIncome may not be genuine or repeatable
5High cash depositsIncome is hard to verify; possible undisclosed source
6Short banking historyNot enough data to underwrite confidently
7Suspected tamperingThe document itself cannot be trusted

Let me take each one the way a credit officer would.

1. High FOIR (the borrower is already stretched)

FOIR (Fixed Obligation to Income Ratio) is the share of monthly income already committed to EMIs and fixed outflows. If a borrower earns ₹60,000 a month and already pays ₹35,000 in EMIs, the FOIR is about 58 percent before your new loan even starts. Add a ₹12,000 EMI and you are near 78 percent. Most lenders cap FOIR somewhere between 50 and 65 percent depending on income band, so this file is dead on arrival.

The statement shows you the obligations directly: recurring EMI debits, NACH mandate hits, standing instructions. Add them up, divide by net monthly income, and you have the number the lender will compute anyway. Full method and worked examples in our FOIR guide.

2. NACH and ECS bounces (the borrower misses payments)

A bounce is a failed auto-debit. When an EMI mandate or insurance premium hits the account and there is not enough balance, the bank returns it and charges a penalty. Lenders read bounces as the single clearest behavioural signal: this person does not always have money on the day a payment is due.

One bounce eighteen months ago is noise. Three bounces in the last six months, or a bounce in the most recent month, is a near-automatic decline at many lenders. The penal charge lines (return charges, ECS return fees) sit right there in the statement, so the lender does not even have to guess. We cover how to read the pattern, not just the count, in NACH, ECS, and cheque bounces explained.

3. Low average balance (no cushion)

Average balance, monthly (AMB) and daily (ADB), tells the lender how much buffer the borrower carries. An account that swings to near zero before every salary credit and spends days in negative territory signals a borrower living paycheque to paycheque. A new EMI on top of that is risky.

Count the days the balance went negative or below the minimum. A statement with frequent negative-balance days, or a balance that is consistently a fraction of the requested EMI, will draw a no.

4. Unexplained large credits (income that may not be real)

A sudden ₹3,00,000 credit two weeks before the application, with no matching pattern in the other months, makes a lender suspicious. Is it genuine income? A friendly transfer to dress up the balance? A loan from elsewhere? Inflated credits to fake higher income are a known trick, and underwriters look for one-off spikes that do not repeat.

If your borrower has a large credit, get the explanation and the proof before you submit. A documented sale, a genuine bonus, a property advance: fine. An unexplained round-number deposit right before the application: a red flag.

5. High cash deposits (income that cannot be traced)

Cash deposits are not illegal, but a statement dominated by cash makes income hard to verify and raises both fraud and AML concerns. A lender cannot trace where cash came from. For salaried borrowers, heavy cash is odd. For self-employed borrowers it is common, but it still weakens the file because the lender cannot tie it to a verifiable source. See how to handle this for business owners in our guide on assessing self-employed income.

If cash is more than a small share of total credits, expect the lender to discount that income or ask for more proof.

6. Short banking history (not enough to read)

Lenders typically want three to six months of statements, sometimes twelve for business loans. If the account was opened recently, or the borrower gives you a fresh account with no history, there is nothing to underwrite. New accounts with a big balance and little activity look manufactured for the application.

Make sure you are collecting the borrower’s primary, salary-credited or business operating account, not a dormant one with a flattering balance.

7. Suspected tampering (the document is not trusted)

If totals do not add up, if a balance does not carry forward correctly from one line to the next, or if fonts and alignment look edited, the lender stops trusting the whole document. A statement where the running balance and the listed transactions disagree is the loudest tell. You do not need forensic tools to catch the obvious ones: pick three or four lines and check that each balance equals the previous balance plus the credit minus the debit. If it does not reconcile, do not send it.

How can a DSA pre-check a file before sending it?

Run this checklist on the statement before the file leaves your hands. It takes a few minutes and saves you a rejection.

The DSA pre-check checklist:

  1. Confirm the right account and enough history. Primary operating account, three to six months minimum, statement period continuous with no gaps.
  2. Add up the fixed obligations. Total the recurring EMIs, NACH mandates, and standing instructions. Divide by net monthly income to get a rough FOIR. If it is already above the lender’s cap, the file is unlikely to pass.
  3. Scan for bounces. Search for “return,” “RTN,” “ECS RTN,” “NACH,” “insufficient,” and penal charge lines. Note how many, and how recent. A bounce in the last month is a serious problem.
  4. Check the balance behaviour. Look at the average balance and count negative or near-zero days. A thin cushion relative to the new EMI is a risk.
  5. Flag large or odd credits. Any one-off credit much larger than the borrower’s normal inflow needs an explanation and proof, collected up front.
  6. Measure the cash share. Roughly what percentage of credits are cash deposits? High cash means discounted income, so set expectations with the borrower.
  7. Spot-reconcile a few lines. Pick three or four rows and confirm the running balance carries forward correctly. A statement that does not add up should never be submitted.

If a file fails any of the first three checks badly, you have a decision to make before you spend more time on it: counsel the borrower, route to a lender with a looser policy, or wait until the next month’s statement is cleaner.

What does it cost a DSA to skip the pre-check?

A rejected file is not free. You spent time sourcing and packaging it, the borrower’s experience sours, and your approval rate with that lender drops, which over time affects your payout tiers and the lenders willing to work with you. The math is simple: every file you submit that you could have predicted would fail is wasted effort plus reputational cost. Pre-checking is cheap insurance against all of it.

The self-serve angle: check a statement for ₹5 a page

You do not need a credit team or a software contract to run a proper pre-check. With Obsrv , a DSA can upload a borrower’s statement (PDF or CSV) and get a decision-ready report in about a minute. It pulls out FOIR, NACH and ECS bounces, cheque returns, penal charges, average balance and negative-balance days, cash share, and the large or unusual credits, the exact list above. The money math is deterministic and every row is reconciled against the running balance and the column totals, so a statement that does not add up gets caught rather than passed along.

It is prepaid and self-serve. One page is one credit at ₹5, CSV counts 40 rows to a page, there is no subscription, no seat fee, and no sales call. Check one file or check fifty. The point is to know what the lender will see before they see it.

Frequently asked questions

Why do loan applications get rejected at the bank statement stage?

Because the bank statement is the document a borrower cannot easily fake, so lenders reject hard on it. The common reasons are a high FOIR, recent NACH or ECS bounces, a low average balance, unexplained large credits, heavy cash deposits, too short a banking history, and any sign of tampering.

What is the most common bank statement issue that fails a loan?

A high FOIR and recent bounces are the two biggest. If the borrower’s existing EMIs already eat most of their income, or an auto-debit has bounced in the last few months, many lenders decline before looking further.

Can a DSA pre-check loan eligibility before submitting?

Yes. A DSA can run the same checks a lender runs: total the fixed obligations to estimate FOIR, scan for bounces and penal charges, check the average balance, flag large or cash-heavy credits, and confirm the statement reconciles. Doing this first avoids submitting files that will obviously fail.

How many bounces will get a loan rejected?

There is no universal number, but the pattern matters more than the count. One old bounce is usually fine. Multiple bounces in the last six months, or any bounce in the most recent month, is a serious risk at most lenders.

Does a one-off large credit cause a loan rejection?

It can, if it is unexplained. Lenders watch for one-time credits that do not match the borrower’s normal income and may treat them as income inflation or a temporary balance top-up. A documented, genuine source (a sale, a bonus, an advance) is fine; an unexplained round-number deposit just before the application is a red flag.

How much banking history do lenders need?

Usually three to six months for retail loans, and up to twelve for some business loans. A recently opened account with little activity gives the lender too little to underwrite and often looks manufactured for the application.


Stop sending files that bounce. Obsrv  gives a DSA a decision-ready read on any bank statement in about a minute, for ₹5 a page, self-serve, with every number reconciled against the statement’s own totals. Pre-check the file before the lender does, and keep your good leads working.