The Credit Underwriting Checklist: Everything to Verify in a Bank Statement

A bank statement checklist for loan underwriting is the fixed set of items you verify on every file before you approve, decline, or counter. The complete list runs to nine sections: identity and period coverage, income, obligations, FOIR and affordability, bounces and penal charges, balance trend, counterparties and unusual transactions, document integrity, and a red-flag summary. This credit underwriting checklist is built to be used, not admired.

Print it. Tape it next to your monitor. Nine sections, and not one approved loan should skip a line.

Why a written checklist beats memory

Underwriting from memory is how good lenders lose money slowly. The strong files are easy. It is the ordinary-looking file, the one with a clean salary credit and a tidy closing balance, that hides the problem you did not think to look for. A written checklist removes the variability. Every analyst checks the same lines in the same order, every file gets the same scrutiny, and the audit trail shows exactly what was verified.

The loan underwriting process here assumes you already have the statement in front of you, parsed into clean transactions. If you want the foundations first, start with what bank statement analysis is. This post is the checklist itself.

Section 1: Identity and statement period coverage

Before any number matters, confirm the statement is the right borrower’s, complete, and untouched at the edges. This is the KYC bank statement verification layer.

Account holder name matches the applicant: a statement in a relative’s or firm’s name underwrites the wrong person.
Account number and IFSC are present and consistent: missing identifiers are a sign of a scrubbed or partial export.
Statement period covers the full window you require (usually 6 to 12 months): a short window hides seasonality and recent stress.
No missing months or date gaps within the period: a quiet gap is often where the bounces or the overdraft lived.
Opening balance of each month equals the prior month’s closing balance: a break means a page is missing or edited.
Bank and branch are real and named: generic or absent bank headers belong on a fake.
The account type fits the income story: a salaried borrower running everything through a current account deserves a question.

Why it matters: if the statement is not complete and not the applicant’s, every downstream calculation is built on sand.

Section 2: Income verification

Confirm that money is actually coming in, that it is regular, and that it is the kind of income you can lend against. This is where most affordability decisions are won or lost.

Identify the income type: salary, business receipts, rental, interest, or government transfers each behave differently.
Salary credits land on a consistent date each month: a fixed payroll date is far stronger than scattered “salary” entries.
Credited amount is stable month to month: wild swings signal variable or inflated income.
Employer or payer name is consistent: a salary that arrives from a different name each month is not a salary.
Business inflows are recurring, not one-off lumps: a single large credit before the application is a classic dressing-up move.
Net income is computed after reversing inflated credits: strip out self-transfers, loan disbursals, and reversed transactions before you call it income.
For self-employed borrowers, average the inflows across the full period: see assessing self-employed income from bank statements for the method.

Why it matters: the income figure is the denominator of every affordability ratio. Get it wrong and the whole file is wrong.

Section 3: Obligations and existing debt

Map every rupee already committed before you add yours. Obligations are what turn an affordable EMI into an unaffordable one.

List all recurring EMI debits: NACH and ECS mandates, standing instructions, and auto-debits.
Identify the lender behind each debit: match against the credit bureau report; an EMI with no CIBIL trade line is a possible informal or undisclosed loan.
Flag credit card payments and BNPL settlements: these are real obligations even when they do not show as loans.
Catch loan top-ups or fresh disbursals inside the period: a new loan late in the window changes the obligation picture going forward.
Total the monthly obligation outflow: this is the number FOIR runs on.

Why it matters: an undisclosed obligation is the single most common reason a “comfortable” FOIR is actually stretched.

Section 4: FOIR and affordability

FOIR (Fixed Obligation to Income Ratio) is the heart of the affordability check. It measures how much of the borrower’s income is already spoken for.

The formula:


FOIR = (Existing monthly obligations + Proposed EMI) / Net monthly income

Compute FOIR with the proposed EMI included: affordability is about the loan you are about to give, not just the ones already there.
Compare against your policy cap: many lenders cap FOIR between 40% and 55% depending on income band.
Check disposable income in rupees, not just the ratio: 50% FOIR on ₹30,000 leaves far less room than 50% on ₹3,00,000.
Stress-test for income volatility: for variable earners, use the lower end of the income range.

Worked example: a borrower nets ₹80,000 a month, pays ₹22,000 in existing EMIs, and applies for a loan with a ₹14,000 EMI. FOIR = (22,000 + 14,000) / 80,000 = 45%. Disposable income after obligations is ₹44,000. The ratio passes a 50% cap, but you still verify the disposable figure covers living costs. For the full method and good-ratio benchmarks, see how to calculate FOIR.

Why it matters: FOIR is the number that decides whether the borrower can actually pay you back.

Section 5: Bounces and penal charges

Bounces are the clearest behavioural signal in any statement. They show how the borrower handles obligations under pressure.

Count NACH and ECS auto-debit failures: a failed mandate means an EMI somewhere did not clear.
Count inward cheque returns: cheques deposited that bounced affect declared inflows.
Count outward cheque returns: cheques the borrower issued that bounced signal cash-flow stress or worse.
Tally penal and bounce charges debited by the bank: these confirm the bounce count independently and quantify the cost.
Look at recency and clustering: three bounces last quarter is worse than three spread over a year.

Why it matters: bounces predict default behaviour better than almost any single declared number. Read more on what NACH, ECS, and cheque bounces tell you.

Section 6: Balance trend and average balance

A snapshot balance can be staged for one day. The trend across the period cannot. This section reads the shape of the account.

Calculate Average Monthly Balance (AMB) and Average Daily Balance (ADB): ADB is harder to game than a month-end figure.
Count negative-balance or overdraft days: frequent dips below zero signal a borrower living on the edge.
Check the balance trend direction: a steadily falling balance over six months is a warning even if income looks fine.
Watch for month-end spikes that vanish: a balance that jumps only on statement-cut dates may be window dressing.
Compare closing balance against monthly obligations: a borrower whose balance barely covers one EMI has no buffer.

Why it matters: the balance trend tells you whether the borrower has a cushion or is running on empty.

Section 7: Counterparties and unusual transactions

Who the money moves to and from often reveals more than the totals. This section is where fraud and hidden risk surface.

Review the top inflow and outflow counterparties: concentration in one or two names can signal a related-party or circular arrangement.
Flag circular transfers between own accounts: money moving out and back inflates apparent turnover without real income.
Identify large one-off transactions: a single huge credit or debit deserves an explanation.
Check the channel mix: heavy cash deposits, frequent UPI churn, or unusual NEFT/RTGS/IMPS patterns each tell a story.
Watch for high-value cash deposits with no clear source: unexplained cash is a compliance and income-quality flag.
Net out genuine self-transfers when consolidating accounts: across multiple statements, count income once, not twice.

Why it matters: turnover can be manufactured. Reading counterparties is how you tell real cash flow from theatre.

Section 8: Document integrity and tampering signs

Before you trust any number, sanity-check that the document itself is internally consistent. You are not running forensic forgery analysis here; you are checking that the arithmetic holds.

Re-add the columns: total debits and total credits should reconcile to the change in balance.
Walk the running balance row by row: each row’s balance must equal the prior balance plus credit minus debit. A single broken row is a tamper signal.
Check fonts and alignment within the statement: a single mismatched row in a PDF is a classic edit artefact.
Verify the totals on the statement match your own re-computed totals: a doctored summary line that does not match the rows is a red flag.
Confirm dates run in order with no inserted rows: out-of-sequence entries suggest insertion.

Why it matters: a statement whose own math does not reconcile cannot be trusted, regardless of how clean it looks. For the full method, see how to spot a tampered or fake bank statement.

Section 9: Red-flag summary

Before you sign off, run the consolidated red-flag pass. Any single hard flag should move the file to refer, not approve.

Period gaps or broken opening/closing balances
Income that does not survive netting of self-transfers and disbursals
Undisclosed obligations not on the bureau report
FOIR over policy, or thin disposable income in absolute rupees
Recent or clustered bounces
Falling balance trend or frequent negative days
Circular transfers or unexplained high-value cash
Statement totals or running balance that do not reconcile

Why it matters: the summary is your last gate. It catches the file where every individual section looked borderline-fine but the pattern across them is not.

How Obsrv runs most of this checklist in about a minute

Most of this checklist is mechanical, repeatable work, which is exactly what software should own. Upload a PDF or CSV statement to Obsrv and you get a decision-ready report in about a minute: income classified by type, obligations and FOIR and disposable income computed, NACH and ECS bounces and penal charges counted, AMB and ADB and negative days, top counterparties and channel mix, and a red-flag summary.

The trust architecture matters for a checklist like this. The AI only transcribes the statement. Every rupee of math is deterministic, computed by auditable code, and every row is reconciled against both the running balance and the column totals, so a doctored total or balance cannot slip through silently (Section 8). Anything uncertain is flagged for your review rather than passed quietly. The risk score is reproducible: the same statement always returns the same score, never a guess. A human still owns the decision; Obsrv is the engine that does the nine sections for you, then hands you a CSV export for the audit file or LOS.

Pricing is simple: 1 page = 1 credit = ₹5, prepaid, with no subscription, no seat fees, and no sales call. You can still tape the printed checklist next to your monitor. You will just find most lines already ticked.

Frequently asked questions

What should I check in a bank statement before approving a loan?

Work through nine sections in order: identity and statement period coverage, income, existing obligations, FOIR and affordability, bounces and penal charges, balance trend, counterparties and unusual transactions, document integrity, and a final red-flag summary. Each section has specific line items, and any hard red flag should move the file to refer rather than approve.

What is the difference between a credit underwriting checklist and the loan underwriting process?

The loan underwriting process is the whole workflow from application to decision, including bureau checks, KYC, and policy rules. The credit underwriting checklist is the bank statement portion of it: the specific lines you verify on the statement itself before deciding on affordability and risk.

What does KYC bank statement verification cover?

KYC bank statement verification confirms the statement belongs to the applicant and is genuine: the account holder name matches, the account number and IFSC are present and consistent, the bank and branch are named, and the period is complete with no missing months. It is Section 1 of the checklist and comes before any financial analysis.

How many months of bank statements should I review?

Most lenders require 6 to 12 months. Six months is the minimum to read income regularity and recent bounces; twelve months captures seasonality, which matters most for self-employed and business borrowers whose inflows vary across the year.

Which checklist item catches the most fraud?

Section 8, document integrity. Re-adding the columns and walking the running balance row by row catches doctored statements that look clean on the surface, because a tampered figure breaks the arithmetic somewhere. Combined with Section 7’s counterparty and circular-transfer checks, it covers the most common manipulations.

Can software complete this entire checklist automatically?

It can run most of it. Identity checks, income classification, obligation mapping, FOIR, bounce counts, balance analytics, counterparty analysis, and the reconciliation math are all automatable and reproducible. The credit decision itself stays with a human, who reviews the flagged items the engine surfaces.