DEV Community: FinEye

How to Choose Bank Statement Analysis Software: 12 Criteria for Banks and NBFCs

FinEye — Tue, 06 Oct 2026 07:11:41 +0000

Most bank statement analysis software looks identical in a sales demo. A clean PDF goes in, a tidy report comes out in seconds. The differences only appear in production: on a scanned cooperative bank statement, a 300-page current account, or a PDF that someone has quietly edited.

For banks and NBFCs, the wrong choice is expensive. It shows up as rejected good borrowers, approved fraudulent ones, analysts re-keying data the tool got wrong, and an integration that takes two quarters instead of two weeks.

This guide sets out 12 criteria that separate a reliable bank statement analyser from a polished demo, along with how to test each one before you sign.

Why Evaluating Bank Statement Analysis Software Is Harder Than It Looks
Vendors usually demonstrate with statements they have already tuned their parsers for. Your portfolio will not look like that. It will include dozens of small banks, scanned pages, statements split across files, and borrowers with three accounts.

The core test is simple: does the software hold up on your files, at your volume, against the fraud patterns your channels actually see? Every criterion below is a version of that question. For background on how the analysis itself works, see our guide to bank statement analysis.

The 12 Evaluation Criteria
Data Capture

Extraction accuracy on your own files. Ask for field-level accuracy (date, amount, balance) on a sample you supply, not a vendor benchmark. A useful test: does every row’s running balance reconcile? Any tool that cannot report reconciliation failures will hide its own errors.
Bank and format coverage. Indian lenders see statements from public, private, small finance, cooperative and payments banks. Ask for the list of supported layouts and, more importantly, what happens when an unknown layout arrives. Generic table parsing with a fallback is better than a hard failure.
Scanned and image statement handling. If your channels include branch-collected or photographed statements, OCR quality matters. Test skewed scans and low-resolution images, and check whether the tool flags low-confidence fields rather than guessing.
Account Aggregator support. The tool should accept AA data (digitally signed JSON) and PDFs, and produce the same output from both. Lenders increasingly use AA where consent succeeds and PDFs where it does not. See Account Aggregator vs PDF bank statements.

Analysis Quality

Categorisation depth and accuracy. Check how the engine handles the hard cases: self-transfers between the borrower’s accounts, loan disbursal credits, informal loan repayments to individuals, and reversals. These distort income and FOIR when misclassified.
Underwriting metrics out of the box. At minimum: ABB on configurable dates, monthly net income, EMI and NACH obligations, inward and outward bounces, cash share, top payers and payees, and low-balance days. Confirm the ABB method can match your credit policy, since lenders use different sampling dates. See our guide to average bank balance.
Multi-account and multi-period consolidation. Borrowers, especially MSMEs, run several accounts. The tool should merge them, remove inter-account transfers and produce one view of income and obligations.

Risk and Fraud

Tampering and fraud detection. This is where vendors differ most. Ask exactly which checks run: PDF metadata (producer software, creation and modification dates), font and layout anomalies, balance arithmetic, duplicate transaction references, and circular fund movement. Then test with statements you have deliberately edited. Our guide on detecting fake bank statements lists the signals to test for.
Explainability. Every flag and metric should trace back to the transactions that produced it. Credit committees, auditors and the RBI’s expectation of auditable creditworthiness assessment all depend on this.

Integration and Operations

APIs, webhooks and LOS integration. Look for a documented REST API, asynchronous processing with callbacks for large files, and structured JSON output that maps cleanly into your loan origination system and rules engine.
Turnaround time at volume. Ask for p95 processing time, not the average, on 12-month current account statements. Peaks at month-end and during campaigns are when slow tools create backlogs.

Compliance and Commercials

Data security, residency and pricing. Confirm where data is stored and for how long, whether it stays in India, and how deletion requests are handled under the Digital Personal Data Protection Act, 2023. On pricing, check whether you pay per statement, per page or per account, since a 12-month current account can run to hundreds of pages.

How to Run a Proof of Concept
A proof of concept should take two to four weeks and answer three questions with your own data.

Assemble a test set of 200 to 500 statements. Include your top 20 banks by volume, at least 30 long-tail or cooperative bank files, scanned statements, multi-account borrowers and current accounts with high transaction counts.
Add known-bad files. Include statements already confirmed as tampered, plus a few you edit yourself: a changed salary credit, a removed bounce entry, an altered closing balance.
Score against a ground truth. Have analysts prepare expected values for income, ABB, EMIs and bounces on a subset. Compare each vendor’s output field by field.
Measure operations, not just accuracy. Record failure rates, manual intervention needed, p95 turnaround and how clearly flags are explained.
Test the integration path. Push results into a sandbox of your LOS or rules engine. Mapping problems found now cost far less than after go-live.
What a Good Result Looks Like
A strong vendor will show high reconciliation rates on your files, flag most of your seeded tampering cases with clear reasons, and handle unknown layouts gracefully. A weak one will perform well on major private banks and poorly everywhere else.

Mistakes Lenders Make During Vendor Selection
Judging on the demo file. Vendor-supplied samples prove nothing about your portfolio.
Treating fraud detection as a checkbox. “Fraud check: yes” on a feature list means little. Ask for the specific checks and test them.
Ignoring the long tail. If 15% of your files come from small banks, a tool that fails on them creates 15% manual work.
Comparing price per statement only. Rework, failed files and analyst time often cost more than the licence.
Leaving credit policy out of the evaluation. If the tool cannot compute ABB or FOIR the way your policy defines them, analysts will recompute them by hand.
Key Takeaways
Evaluate bank statement analysis software on your own files, including long-tail banks, scans and seeded tampered statements.
Extraction accuracy, analysis depth and fraud detection are separate capabilities. Score them separately.
Explainability and auditability matter as much as accuracy, given RBI expectations on creditworthiness assessment.
Check AA and PDF support together, since most lenders will run both for years.
Total cost includes rework and analyst time, not just the per-statement fee.
Conclusion
Choosing bank statement analysis software ishttps://blogs.fineye.co/bank-statement-analysis-software-2/ a credit risk decision, not a procurement exercise. The tool will shape which borrowers you approve, how fast, and how many fraudulent files slip through.

The lenders who choose well test on their own data, weigh fraud detection as heavily as extraction, and insist that every output can be explained.

If you are building your shortlist, download our vendor evaluation checklist, or book a FinEye demo and run your own statements through it, including the difficult ones.

Bank Statement Analysis for Lenders: How It Works in India

FinEye — Tue, 06 Oct 2026 07:05:25 +0000

A credit score tells a lender how a borrower has repaid credit in the past. It says very little about whether that borrower can afford the next EMI. That answer sits in the bank statement: every salary credit, every UPI receipt, every returned NACH mandate.

For banks, NBFCs and fintech lenders in India, bank statement analysis has moved from a back-office checklist to the centre of underwriting. It matters most for new-to-credit borrowers and MSMEs, whose real income rarely shows up neatly in an ITR or a bureau file.

This guide explains how bank statement analysis works end to end, which metrics lenders rely on, where manual reviews break down, and how to automate the process without giving up control of credit judgment.

What Is Bank Statement Analysis in Lending?
Bank statement analysis is the process of converting a borrower’s account statement into structured data and credit signals. Those signals cover income, existing obligations, liquidity, repayment discipline and signs of manipulation.

In personal finance, the term means tracking your own spending. In lending, it means answering four questions: how much does this borrower really earn, what do they already owe, how much cash do they keep, and is this statement genuine?

The regulatory context makes this more than good practice. The RBI (Digital Lending) Directions 2025, which consolidated the 2022 digital lending guidelines, expect regulated entities to assess a borrower’s creditworthiness from their economic profile in an auditable way. A documented, rule-based reading of the bank statement is one of the clearest ways to show that assessment was actually done.

How Bank Statement Analysis Works: The Five-Stage Pipeline
Whether an analyst does it by hand or a bank statement analyser does it in seconds, the work follows the same five stages. The quality of the output depends on how well each stage is handled.

Ingestion Statements reach lenders in four forms, each with a different level of trust:

E-statement PDFs downloaded from net banking, usually password-protected. These are the most common and the easiest to tamper with.
Scanned or photographed statements, often from cooperative banks or branch counters. They need OCR and carry the highest extraction error rate.
Net banking fetch, where the borrower logs in and the data is pulled directly. Tampering risk is low, but credential-sharing raises consent and security concerns.
Account Aggregator data, delivered as digitally signed JSON from the bank (the Financial Information Provider) with the borrower’s consent. This is the most trustworthy source, though bank coverage and borrower drop-off still limit it.

Extraction and Normalisation Indian banks publish statements in hundreds of layouts. Some use separate debit and credit columns; others use a single amount column with Dr/Cr markers. Dates appear in at least four formats, and tables split across pages with carried-forward balances.

Normalisation maps all of this into one schema: date, narration, debit, credit, balance. A reliable engine then checks that each row’s balance equals the previous balance plus credits minus debits. A break in that chain is the first sign of an extraction error or an edited statement.

Transaction Categorisation Narrations carry the meaning. Strings such as NEFT CR, UPI, IMPS, ACH D, NACH and BY CASH tell the engine what kind of transaction occurred. Categorisation tags each line as salary, business receipt, EMI, loan disbursal, cash withdrawal, bounce charge, self-transfer and so on.

The hard part is not the obvious categories. It is recognising transfers between the borrower’s own accounts, recurring payments to individuals that may be informal loans, and credits from related parties that inflate turnover.

Metric Computation
Once transactions are categorised, the engine computes the metrics underwriting rules depend on: average bank balance, monthly income, existing EMI load, bounce counts, cash dependence and credit concentration. These feed FOIR, eligible loan amount and policy knock-out rules.
Integrity and Fraud Checks
The final stage asks whether the statement can be trusted at all. Checks include balance arithmetic, PDF metadata (creation and modification tools and dates), font and layout consistency, duplicate transaction IDs and circular movement of funds. Our guide on how to detect a fake or tampered bank statement covers these signals in detail.

What a Bank Statement Reveals That a Bureau Report Cannot
A bureau report only shows credit that a regulated lender has reported. A bank statement shows how money actually moves. That gap is where many underwriting surprises come from.

Consider a salaried applicant who declares a monthly income of ₹85,000. The statement shows a fixed salary credit of ₹62,000, plus irregular reimbursements that make up the rest. It also shows an ₹18,000 UPI transfer to the same individual on the 5th of every month.

The bureau report is clean. The statement suggests two things it cannot: the usable income is closer to ₹62,000, and there is probably an informal loan being serviced. Both change the FOIR, and both change the decision.

Other signals that only the statement exposes:

Repayments to unregulated lending apps, visible as small, frequent UPI debits to app-linked handles.
Cash dependence, where most income arrives as cash deposits that cannot be traced to a source.
Liquidity stress, shown by month-end balances near zero or repeated low-balance charges.
Turnover inflation, where money cycles between related accounts to make receipts look larger.
Use Cases Across Lending Products
Salaried Personal Loans
The focus is salary consistency, employer name in the narration, and existing EMIs. A salary credit that changes employer name mid-statement, or arrives from an individual rather than a company, warrants a closer look.

MSME and Business Loans
Here the statement is often the primary income document. Lenders assess turnover, ABB, cash share, customer concentration and how receipts compare with GST returns. Our guide to cash flow analysis for MSME lending walks through this in detail.

Loan Against Property and Home Loans for the Self-Employed
Large-ticket loans to self-employed borrowers combine statement analysis with ITR and financial statements. The statement validates whether declared profits are reflected in actual banking.

DSA-Sourced and Co-Lending Files
Files from DSAs and partners carry higher document-fraud risk. A standard automated read gives every partner’s file the same scrutiny, and makes co-lending audits simpler.

Portfolio Monitoring
Some lenders re-analyse statements after disbursal, or through Account Aggregator consents, to spot early warning signs such as falling balances or new loan credits.

Common Misconceptions and Gaps
“Account Aggregator data makes PDF analysis obsolete.” AA coverage and completion rates have grown fast, but many borrowers still drop off at consent or bank many accounts outside the network. Most lenders need both. See Account Aggregator vs PDF bank statements.
“Accurate extraction means the statement is genuine.” A well-edited PDF extracts perfectly. Integrity checks are a separate layer and must be tested separately.
“Higher credits mean higher income.” Circular transfers and loan proceeds inflate credits. Without filtering them, income is overstated.
“One account is enough.” Borrowers often split salary and spending across accounts. Analysing only the account they choose to share can miss obligations.
“Automation replaces credit policy.” A tool computes metrics. Thresholds, exceptions and final decisions remain the lender’s responsibility and must stay explainable.
Key Takeaways
Bank statement analysis answers what a bureau report cannot: real income, undisclosed obligations, liquidity and whether the document is genuine.
Every analysis runs through five stages: ingestion, extraction, categorisation, metric computation and integrity checks. Weakness at any stage flows through to the credit decision.
The metrics that drive decisions are ABB, net income, existing EMIs, bounces, cash share and credit concentration.
Extraction accuracy and fraud detection are different capabilities. Evaluate them separately.
Automation is most valuable when it shifts analysts from data entry to exceptions, while keeping a clear, auditable rule trail.
Conclusion
Bank statement analysis has become the most direct evidence of repayment capacity available to Indian lenders. As more borrowers come from thin-file and MSME segments, its weight in underwriting will only grow.

The lenders who benefit most will not be the ones who simply read statements faster. They will be the ones who read them consistently, catch manipulation before disbursal, and can explain every decision to an auditor or regulator.

That is the standard to hold any process to, manual or automated. FinEye was built to that standard: AI-powered statement analysis with tampering detection and cash flow insights in a single report. Book a demo or request a sample report to see how it reads one of your own files.

Bank Statement to Excel: Why Generic Converters Fail Lenders and What to Use Instead

FinEye — Mon, 05 Oct 2026 11:19:54 +0000

Search for a bank statement converter, and you will find dozens of tools that promise to turn any PDF into a clean spreadsheet in seconds. For an individual reconciling personal expenses, many of them work well enough.

For a lender, “well enough” is the problem. A converter that drops one row in a thousand, swaps a debit for a credit on a page break, or splits a narration across two lines will produce an Excel file that looks correct and leads to the wrong credit decision. Worse, converting the PDF often destroys the evidence that would have shown the statement was edited.

This guide explains how bank statements are usually converted, where generic methods fail on Indian statements, and what a lending-grade approach looks like.

Ways to Convert a Bank Statement to Excel
There are four common routes.

Download directly from net banking. Most Indian banks let account holders download statements as Excel or CSV. This is the cleanest option, but lenders rarely receive statements this way; borrowers send PDFs.
Copy and paste or use spreadsheet import. Works for simple text PDFs, but breaks on multi-page statements and wrapped narrations.
Generic PDF-to-Excel tools. Detect tables and export them. Accuracy depends on how consistently the statement is laid out.
OCR tools. Needed for scanned or photographed statements. They recognise characters from images and then attempt table reconstruction.
All four produce a spreadsheet. None of them, on their own, tells you whether the spreadsheet is complete, accurate, or derived from a genuine document.

Why Indian Bank Statements Are Hard to Convert
India has a very wide variety of statement formats. Large private and public sector banks alone publish several layouts each, differing by account type, channel (branch, net banking, mobile app, email), and period. Add small finance banks, cooperative and regional rural banks, and payments banks, and the number of distinct layouts runs into the hundreds. FinEye’s parsing engine, for example, covers more than 180 statement formats across more than 100 banks.

Format variety is compounded by content. Narrations mix UPI handles, NEFT reference numbers, cheque numbers, and free text, often across two or three lines. Amounts may carry Dr/Cr suffixes instead of separate columns. Dates appear as DD/MM/YY, DD-MMM-YYYY, or with times attached. Cooperative bank statements add their own irregularities.

The one check that catches most of them
A running balance check: for every row, the previous balance plus credits minus debits should equal the stated balance. Any row where it does not is either a conversion error or an edited statement. Generic converters rarely perform this check; lending systems should never skip it.

The Tampering Problem
Fraudulent bank statements are usually edited PDFs: changed amounts, deleted debits, inserted salary credits. A genuine PDF carries evidence of its origin in metadata, fonts, object structure, and layout consistency. Edits leave traces in those same places.

Converting a PDF to Excel throws all of that away. Once the data is in a spreadsheet, there is no way to tell whether the original was genuine. Lenders that convert first and analyse later have, in effect, removed their own fraud check.

The correct order is: validate the original document, then extract. Our guides on fake bank statement detection and financial statement tampering detection cover the checks in detail.

What Lending-Grade Parsing Does Differently
Pre-analysis before extraction. Check that the document is complete, from a supported bank, covers the required period, and shows no signs of tampering. Reject or flag at intake.
Bank-specific parsers. Instead of generic table detection, use templates or models trained on each bank’s layouts, so narrations, columns, and signs are read correctly.
Balance continuity validation. Run the running-balance check on every row and every page.
Narration normalisation. Parse UPI, NEFT, IMPS, NACH and cheque narrations into structured fields: channel, counterparty, reference.
Classification. Tag each transaction as salary, business receipt, EMI, transfer, cash, bounce, charge, and so on.
Structured output. Deliver JSON or Excel with consistent fields across banks, ready for scorecards and credit notes.
FinEye’s Pre-Analysis and Data Parsing follows this sequence. Lenders configure mandatory fields per loan product, and the engine blocks incomplete or tampered statements before processing. Statements that pass are parsed by bank-specific engines and returned as structured data through an API, with the Bank Statement Analyser layered on top for credit metrics. The API integration guide covers the implementation steps.
Key Takeaways
Generic converters produce spreadsheets but not verified data.
Indian statements vary across hundreds of layouts, with wrapped narrations and inconsistent sign conventions.
Column shifts, split narrations, OCR digit errors, and missed rows can materially distort income and obligations.
A running balance check on every row catches most conversion errors and many edits.
Converting before checking authenticity destroys the evidence of tampering.
For lending, validate first, then parse with bank-specific engines, then classify.
Conclusion
Converting a bank statement to Excel is a solved problem for personal finance. For lending, it is the wrong problem. The goal is not a spreadsheet, but a verified, complete, and correctly classified record of what happened in the account.

Lenders that separate authenticity checks from extraction, validate every balance, and parse by bank rather than by guesswork build credit decisions on data they can defend.

To see how FinEye validates and parses statements across 100+ Indian banks, request a demo.

Ocrolus Alternative for India: What Indian Lenders Need From Document AI

FinEye — Mon, 05 Oct 2026 11:09:48 +0000

Ocrolus is one of the best-known names in lending document automation. Founded in 2014 in New York, it reports more than 400 customers, including PayPal, Brex, SoFi, and Enova, and has built a strong position in US small business lending and mortgage underwriting.

Indian lenders researching bank statement analysis often come across it, and the question follows naturally: would it work here? The honest answer depends less on Ocrolus’s quality, which is well regarded, and more on how different Indian lending data is from the documents Ocrolus was built to process.

This guide sets out what Ocrolus does, what Indian lenders specifically need, and how to evaluate any provider, including FinEye, against those needs.

What Ocrolus Does
Ocrolus describes itself as an AI workflow and analytics platform for lenders. Its core capabilities are usually grouped as:

Classify: identify and index document types in a loan package. Ocrolus says it can classify more than 1,600 financial document types.
Capture: extract data from documents, combining AI with human-in-the-loop review. The company cites accuracy above 99 percent.
Detect: identify tampering and fraud on bank statements, pay stubs, and tax documents.
Analyze: produce cash flow and income analytics, including income calculations for salaried and self-employed borrowers.
In mortgage, its Inspect product and automated conditioning target US origination workflows, with integrations into systems such as ICE’s Encompass and features aligned to US agency guidelines.

The human-in-the-loop model is a notable design choice: machine extraction is reviewed by people where confidence is low, which supports high accuracy but affects turnaround and cost structure.

Why Indian Lending Data Is Different
The documents and workflows that define US lending, such as W-2s, 1099s, IRS transcripts, US pay stubs, and mortgage conditions, have few direct equivalents in Indian underwriting. Indian lenders work with a different set of inputs.

Bank statement variety
India has public sector, private, small finance, cooperative, regional rural, and payments banks, each with multiple statement layouts. Coverage of these specific formats, including cooperative and RRB statements, decides extraction accuracy far more than general AI capability.

Payment rails and narrations
UPI, IMPS, NEFT, RTGS, NACH and cheque transactions each produce distinct narration formats. Correctly identifying salary, business receipts, EMIs and transfers depends on parsing these patterns. UPI transaction analysis alone is a specialised task.

India-specific credit metrics
Indian underwriting relies on average bank balance, FOIR, EMI obligation mapping, inward and outward returns, and banking surrogate programmes. These metrics need to be computed the way Indian credit policies define them.

GST and tax data
For MSME lending, GST returns are a core data source, and tax documents such as Form 26AS and AIS support income verification. These are uniquely Indian inputs.

Account Aggregator
The RBI-regulated Account Aggregator framework allows lenders to receive consented financial data directly from banks and other institutions. Integration with the AA ecosystem is increasingly central to Indian digital lending.

Data residency and privacy
RBI’s digital lending guidelines require regulated entities to ensure borrower data is stored on servers located in India, and the Digital Personal Data Protection Act adds consent and processing obligations. Lenders need clarity on where a provider stores and processes data.

Evaluation Criteria for Indian Lenders
Whichever provider you consider, test it against these criteria with your own sample statements:

Format coverage: how many Indian banks and statement layouts are supported, including cooperative banks and scanned documents.
Extraction validation: does every statement pass a running balance check, and what happens when it fails?
Tampering detection: is the original document analysed for edits before extraction?
Indian metrics: ABB (daily and fixed-date), FOIR, EMI mapping, bounce classification, cash deposit analysis.
GST and AA integration: can GST data and AA data be analysed in the same workflow?
Turnaround: time from upload to report, especially if human review is involved.
Data residency and compliance: where data is stored and processed, and how consent is managed.
Integration: API design, LOS compatibility, and support availability in Indian time zones.
The bank statement analysis software buying guide covers these criteria in more depth.
Other India-Focused Options
Indian lenders also evaluate domestic providers. We have published direct comparisons of FinEye with Perfios, FinBox and Precisa. Each has different strengths in breadth, pricing, and platform bundling, and the right choice depends on your loan products, volumes, and existing stack.

Key Takeaways
Ocrolus is a well-established US lending document AI platform with strengths in mortgage and small business lending.
Indian lending depends on inputs Ocrolus was not designed around: Indian bank formats, UPI and NACH narrations, GST returns, and Account Aggregator data.
India-specific metrics such as ABB, FOIR, and banking surrogate eligibility need to be computed the way Indian policies define them.
Data residency under RBI’s digital lending guidelines and consent under the DPDP Act are part of vendor evaluation.
Test any provider on your own sample statements, including cooperative bank and scanned documents.
Compare India-focused providers, including FinEye, Perfios, FinBox, and Precisa, on fit for your products.
Conclusion
Document AI in lending is not a single global category. It is a set of local problems: which banks, which payment rails, which tax documents, which regulator. Ocrolus solved the US version of that problem well.

Indian lenders need the Indian version solved: bank-specific parsing across hundreds of formats, credit metrics defined by Indian policy, GST and Account Aggregator data in the same view, and data that stays in India. That is the standard to evaluate any provider against.

To test FinEye on your own sample statements, request a demo.

Tangible Net Worth and the TOL/TNW Ratio: A Lender’s Guide to Real Equity

FinEye — Fri, 02 Oct 2026 07:55:49 +0000

A balance sheet can show a net worth of ₹5 crore and still leave a lender with far less real equity to fall back on. Goodwill from an acquisition, capitalised preliminary expenses, deferred tax assets and investments in group companies all sit inside net worth, but none of them can absorb a loss when the business runs short of cash.

Tangible net worth (TNW) strips those items out. The TOL/TNW ratio then measures how much the business owes to outsiders for every rupee of that real equity. Together they are the lender’s most direct measure of leverage and loss-absorbing capacity.

This guide explains how both are calculated in Indian credit practice, the adjustments that matter, and the benchmarks banks and NBFCs apply.

Net Worth vs Tangible Net Worth
Net worth, or shareholders’ funds, is paid-up capital plus free reserves and surplus. It is an accounting measure of what the owners have in the business.

Tangible net worth asks a narrower question: if the business had to absorb losses, how much of that equity is backed by assets that have realisable value? Intangible and fictitious assets do not qualify, because they cannot be sold to pay creditors.
How to Calculate Tangible Net Worth
\text{TNW} = \text{Paid-up capital} + \text{Free reserves} – \text{Intangible assets} – \text{Fictitious assets}

Items commonly deducted in Indian credit appraisal:

Intangible assets: goodwill, patents, trademarks, brand value and capitalised software, unless there is a strong case for realisable value.
Fictitious assets: preliminary expenses and miscellaneous expenditure not written off.
Accumulated losses: if shown on the asset side rather than netted against reserves.
Revaluation reserve: usually excluded, since it reflects a book gain rather than capital brought in.
Deferred tax assets: many lenders deduct them because they are only realisable if future profits arise.
Some lenders go further and compute an adjusted TNW that also deducts investments in and loans to group or associate companies. The logic is that capital parked in a sister concern is not available to protect this lender.
Quasi-Equity and Adjusted TNW
MSME promoters frequently fund their businesses through unsecured loans rather than share capital. Banks often treat these as quasi-equity and add them to TNW, provided the promoter signs an undertaking that the loans will stay in the business for the tenure of the bank’s facility and will be subordinated to bank debt.

The undertaking only matters if it is honoured. Promoter loans that are quietly repaid through the bank account, often in round amounts just after a large customer receipt, erode the equity cushion the sanction relied on. Tracking payments to promoters and related parties is how lenders enforce that undertaking in practice.

The TOL/TNW Ratio
\text{TOL/TNW} = \frac{\text{Total outside liabilities}}{\text{Tangible net worth}}

Total outside liabilities include all term loans, working capital borrowing, unsecured loans not treated as quasi-equity, sundry creditors, advances from customers and provisions. In short: everything on the liabilities side except TNW.

TOL/TNW is broader than the debt-equity ratio, which only counts long-term debt. It captures the full burden the business carries, including trade credit, which matters because supplier stretch is often the first place a stressed MSME finds cash.

Verifying the Inputs
TNW and TOL come from audited financials, but three independent checks improve reliability.

Undisclosed borrowings. Repayments to NBFCs, fintech lenders and private financiers visible in bank statements should all appear in TOL. If they do not, the ratio is understated.
Promoter withdrawals. Regular transfers to promoters or their family accounts can mean quasi-equity is leaving the business.
Group company flows. Frequent transfers to associate entities indicate investments or loans that should be deducted from adjusted TNW.
FinEye’s Bank Statement Analyser classifies counterparties and flags loan repayments and related-party transfers, which makes these checks routine. FinEye’s upcoming Credit Report Analyser will extend this to balance sheets and financial ratios directly.

Conclusion
Reported net worth answers an accounting question. Tangible net worth answers a credit question: how much real equity stands between the lender and a loss?

Lenders that compute TNW rigorously, document their adjustments and verify that quasi-equity stays in the business get a leverage measure they can rely on through the loan’s life. Those that accept reported figures tend to discover the difference only when the cushion is needed.

To see how FinEye detects promoter withdrawals and undisclosed borrowing from bank statements, request a demo.

Mule Account Detection: What Lenders Must Check in 2026

FinEye — Fri, 02 Oct 2026 07:38:06 +0000

Mule accounts have moved from a cybercrime problem to a lending problem. The same accounts that receive and pass on the proceeds of digital fraud are now used to inflate borrower turnover, receive loan disbursals that vanish within hours, and route funds through layers that make recovery almost impossible.

Regulators have noticed. RBI’s innovation arm built MuleHunter.AI specifically to detect these accounts, and the government has pushed banks to use AI and network analytics to find mule networks. For lenders, the question is no longer whether mule accounts touch their portfolio, but whether their underwriting can recognise one when it appears in a loan file.

What a Mule Account Is
A mule account is a bank account used to receive and move money on behalf of someone else, usually to disguise the origin of illicit funds. The account holder, the money mule, may be complicit, paid a small fee for lending the account, or entirely unaware that their credentials are being used.

Mules are the layering stage of modern fraud. Money from a phishing scam or fake investment scheme lands in one account, is split and forwarded to several others within minutes, and is finally withdrawn as cash or moved offshore. Each hop makes tracing and clawback harder.

Why Mule Accounts Are a Lending Risk
Most discussion of mule accounts focuses on deposit-taking banks. Lenders face the problem from three directions.

The borrower’s own account is a mule. A statement full of rapid pass-through credits looks like a business with healthy turnover. The inflows are real, but they are not the borrower’s income.
Disbursals land in mule accounts. Organised loan fraud rings apply with synthetic or borrowed identities and route disbursements to accounts they control. The funds leave within hours; the EMI never arrives. This overlaps closely with synthetic identity fraud.
Mule inflows inflate eligibility. Turnover-based and ABB-based programmes reward high credits and balances. Mule activity can push an applicant into a loan size their real business cannot support.
In each case the lender’s loss is not a credit loss in the usual sense. It is fraud, which carries reporting obligations and reputational cost alongside the write-off.
The Regulatory Response in India
The Reserve Bank Innovation Hub developed MuleHunter.AI, a machine learning model that classifies mule accounts from transaction and account data. It is designed to replace static rule-based systems, which RBIH notes produce high false-positive rates and miss evolving patterns.

Adoption has moved quickly. In mid-2025, an RBI official said MuleHunter was live at six banks, with more joining, and that it produced far fewer false positives than existing tools. Industry reports in September 2026 put adoption at 31 banks.

The government has also said banks have been advised to deploy real-time transaction monitoring and AI/ML tools, including network analytics, to identify mule networks. It also noted that the Indian Digital Payment Intelligence Corporation was incorporated in October 2025 to detect and prevent digital payment fraud.

Most of this infrastructure sits with banks. NBFCs and fintech lenders do not operate the accounts, so they cannot see mule behaviour directly. They see it through the bank statements borrowers submit, which makes statement analysis their primary line of defence.

Bank Statement Patterns That Indicate a Mule Account
No single signal proves an account is a mule. Combinations of the following should trigger review.

Pass-through velocity
Credits are followed by debits of similar value within minutes or hours. The end-of-day balance stays close to zero despite high daily throughput. A genuine business retains some float between collections and payments.

Many small credits from unrelated individuals
Dozens of UPI or IMPS credits from personal accounts, often in similar amounts, with no recognisable trade pattern. Legitimate merchant collections usually come through payment aggregators or show repeat customers.

Fan-in, fan-out structure
Many sources pay in, and funds are forwarded to a small set of beneficiaries. Counterparty analysis exposes this shape quickly.

Sudden activation
A dormant or new account moves from minimal activity to high volumes within weeks, often shortly before a loan application.

Inflow and outflow narration mismatch
Credits described as business receipts, debits to individuals or wallets. Or narrations that change pattern abruptly, suggesting a different person is now operating the account.

Cash withdrawal after large credits
Large inward transfers followed quickly by ATM or cash withdrawals across locations. This is the cash-out stage.

Geographic dispersion
Credits from counterparties spread across many states with no business logic, particularly when the applicant describes a local trade.

Separating Mule Behaviour From Legitimate High-Volume Accounts
The hard part is not spotting velocity. It is avoiding false positives on borrowers whose legitimate businesses look similar.

Pattern Mule-like reading Legitimate explanation to test
Many small UPI credits Scam proceeds from victims Kirana, pharmacy or food vendor collections
Near-zero closing balances Pass-through layering Sweep to a linked current or overdraft account
Rapid outward transfers Forwarding to next layer Supplier payments on cash-and-carry terms
Credits from many states Victims spread nationally E-commerce seller receiving marketplace payouts
The test is consistency. A kirana store shows credits clustered in trading hours, supplier payments to known distributors, and GST filings roughly in line with collections. A mule account shows credits with no matching business costs, outflows to unrelated individuals, and no tax footprint. UPI transaction analysis combined with GST data resolves most borderline cases.

Building Mule Checks Into Underwriting
A practical approach for NBFCs and fintech lenders:

Screen every statement for velocity and retention. Compute the ratio of average daily balance to average daily credits. Very low retention with high throughput should route the file to manual review.
Map counterparties. Identify the top inflow sources and outflow beneficiaries by value and frequency. Fan-in, fan-out structures are the strongest single indicator.
Check account age and activation. Flag accounts that went from dormant to active in the 90 days before application.
Verify the disbursal account. Confirm that the account receiving the loan belongs to the borrower and shows ordinary behaviour, not only the account used for eligibility.
Cross-check with GST and bureau data. A high-turnover account with no GST registration and a thin bureau file is a strong combined signal.
Validate the document itself. Mule operators often edit statements to hide outflows. Tampering checks at intake, before analysis, stop edited documents from entering the pipeline.
FinEye’s Pre-Analysis and Data Parsing blocks incomplete or tampered statements before analysis begins. The Bank Statement Analyser then maps counterparties, measures balance retention and flags circular and pass-through flows, so mule patterns surface as part of standard underwriting rather than a separate fraud review.

Key Takeaways
A mule account receives and forwards money for someone else, usually to layer fraud proceeds.
For lenders, mule accounts inflate turnover, receive fraudulent disbursals and distort ABB-based eligibility.
A growing number of banks now uses RBIH’s MuleHunter.AI; NBFCs must rely on statement analysis.
The strongest signals are pass-through velocity, near-zero retention, fan-in fan-out structures, and sudden activation.
Legitimate cash-heavy businesses can look similar; GST, supplier payments and trading-hour patterns separate them.
Check the disbursal account as carefully as the eligibility account.
Conclusion
Mule accounts sit at the intersection of fraud and credit, which is exactly why they slip through. Fraud teams look for identity mismatches; credit teams look for income. A mule account offers a real identity and real inflows, and fails only when someone asks where the money came from and where it went.

Lenders that answer those two questions for every statement, before sanction and again before disbursal, close one of the most active fraud channels in Indian lending today.

To see how FinEye flags pass-through and fan-in, fan-out patterns in bank statements, request a demo.

Drawing Power Calculation: Formula, Margins, Stock Statements, and the RBI Rules Behind Them

FinEye — Mon, 28 Sep 2026 09:29:44 +0000

A cash credit limit is a ceiling, not an entitlement. What a borrower can actually draw on any given day is the drawing power (DP), and DP depends on something the bank cannot see directly: the value of the borrower's eligible stock and receivables.

That gap between the sanctioned limit and verified security is where working capital lending can go wrong. Inflated stock statements, ageing debtors counted as current, and stock funded twice can cause a cash credit account to become irregular and eventually non-performing.

This guide explains how drawing power is calculated, how the margin structure works, how stale stock statements affect account monitoring, and how lenders can test a stock statement against independent bank and GST data.

What Is Drawing Power?

Drawing power is the amount a borrower may draw from a cash credit or overdraft account at a given point in time.

In simple terms, DP is determined by comparing:

The sanctioned credit limit
The value of eligible current assets after applicable deductions and margins

The amount available for drawing is generally the lower of the two.

For example, suppose a borrower has a ₹2 crore cash credit limit, but eligible stock and receivables support only ₹1.4 crore after applying the applicable margins.

The drawing power is ₹1.4 crore.

If the borrower draws ₹1.6 crore, the account is overdrawn against DP even though the outstanding balance is still below the sanctioned ₹2 crore limit.

This distinction matters:

The sanctioned limit defines the facility. Drawing power determines how much can be drawn against the eligible security available at that time.

The sanctioned limit may be based on a working capital assessment such as CMA data. DP is the ongoing control that links actual borrowing to the security available month by month.

Drawing Power Calculation Formula

A simplified drawing power formula is:

DP = (Stock − Sundry Creditors for Goods) × (1 − Stock Margin) + Eligible Debtors × (1 − Debtor Margin)

Where:

Stock is the eligible inventory reported by the borrower.
Sundry creditors for goods are unpaid purchases deducted from eligible stock.
Eligible debtors are receivables that meet the lender's eligibility criteria.
Stock margin is the margin specified in the sanction terms.
Debtor margin is the margin specified in the sanction terms.

The exact calculation can vary depending on the lender's sanction terms, facility structure, and credit policy.

Three adjustments are particularly important when calculating DP.

1. Unpaid Stock Is Deducted

Stock purchased on credit is generally adjusted against the corresponding trade creditors.

This prevents the bank from financing inventory that remains funded by suppliers.

For example:

Gross stock: ₹260 lakh
Sundry creditors for goods: ₹70 lakh
Eligible paid stock: ₹190 lakh

If the applicable stock margin is 25%, the financeable stock value becomes:

₹190 lakh × 75% = ₹142.5 lakh

2. Only Eligible Debtors Count

Not every receivable reported by a borrower contributes to drawing power.

Lenders commonly apply an ageing cut-off. Receivables beyond the permitted period may be excluded from the calculation.

Depending on the sanction terms, lenders may also exclude receivables from:

Related parties
Group companies
Promoters or directors
Other ineligible counterparties

The applicable eligibility rules depend on the lender's policy and sanction conditions.

3. Margins Differ by Asset

Different asset classes can carry different margins.

For example, a sanction may specify:

25% margin on stock
40% margin on eligible debtors

These are illustrative figures. Actual margins are determined by the lender based on the facility and sanction terms.

The purpose of the margin is to provide a buffer between the reported value of the security and the amount financed by the bank.

Worked Drawing Power Calculation

Consider a Ludhiana hosiery manufacturer with a ₹3 crore cash credit limit.

The borrower submits the following month-end stock statement:

Item	Amount (₹ lakh)	Treatment
Raw material, WIP and finished goods	260	Gross stock
Sundry creditors for goods	70	Deducted
Eligible paid stock	190	25% margin = ₹142.5 lakh
Total debtors	180	Reported receivables
Debtors older than 90 days	45	Excluded
Eligible debtors	135	40% margin = ₹81 lakh
Drawing power		₹223.5 lakh

The calculation is:

Eligible stock

₹260 lakh − ₹70 lakh = ₹190 lakh

Financeable stock

₹190 lakh × 75% = ₹142.5 lakh

Eligible debtors

₹180 lakh − ₹45 lakh = ₹135 lakh

Financeable debtors

₹135 lakh × 60% = ₹81 lakh

Drawing Power

₹142.5 lakh + ₹81 lakh = ₹223.5 lakh

Therefore, the drawing power is ₹2.235 crore, compared with the sanctioned limit of ₹3 crore.

If the borrower's outstanding balance is ₹2.6 crore:

₹260 lakh − ₹223.5 lakh = ₹36.5 lakh

The borrower is therefore ₹36.5 lakh above the calculated DP, despite remaining within the sanctioned ₹3 crore limit.

This is why monitoring only the sanctioned limit can miss an important working-capital warning signal.

Why Stock Statements Matter

Drawing power is only as reliable as the stock statement used to calculate it.

Borrowers generally submit periodic statements showing:

Raw materials
Work in progress
Finished goods
Trade receivables
Receivable ageing
Trade creditors

The lender uses this information to calculate eligible security.

The challenge is that much of this information is borrower-reported. Several weaknesses can therefore distort DP.

Stock Valued Above an Appropriate Basis

Inventory valuation needs to follow the applicable accounting and lending requirements.

If finished goods are reported at selling price rather than an appropriate valuation basis, the value of eligible security can be overstated.

Obsolete or Slow-Moving Inventory

Inventory that has not moved for an extended period may continue to appear in the reported stock figure.

Without appropriate ageing or inspection, obsolete inventory can continue contributing to the apparent security value.

Debtor Ageing Problems

Receivable ageing can also be misleading.

Part payments, credit notes, adjustments, or changes in invoice references can make older receivables appear newer unless the underlying transactions are examined.

Double Financing

The same inventory may potentially be:

Pledged to another lender
Covered by supplier credit
Included in another financing arrangement

This can create a risk that the security available to a lender is overstated.

Month-End Timing

The reporting date itself can affect the stock position.

Inventory may temporarily increase around month-end because of delayed dispatches, goods received close to the reporting date, or other timing effects.

For this reason, lenders may use periodic stock audits, inspections, and other verification mechanisms according to their internal policies and exposure levels.

Drawing Power and RBI Asset Classification

Drawing power is not only a credit-control calculation. It can also have implications for asset classification and account monitoring under RBI's income recognition and asset classification framework.

For cash credit and overdraft accounts, an account can be considered "out of order" when the applicable conditions under RBI's IRAC framework are met. These conditions include situations where the outstanding balance remains continuously above the sanctioned limit or drawing power for the prescribed period.

RBI's framework also addresses drawings permitted against stock statements that are more than three months old. Such drawings are treated as irregular under the applicable prudential framework.

This creates three important monitoring questions:

Is the borrower operating within the current drawing power?
Is the DP based on a sufficiently current stock statement?
Does the account meet any applicable "out of order" conditions?

For lenders, DP monitoring is therefore a portfolio-quality issue, not just a documentation exercise.

Stale DP data can create classification risk and may prevent the lender from identifying deterioration in working-capital security in time.

How Lenders Can Validate Drawing Power

A stock statement should not be treated as the only source of truth.

Credit and monitoring teams can compare reported security with independent transaction and tax data.

Three checks are particularly useful.

1. Compare Purchases With GST Inward Supplies

Suppose a borrower reports that inventory increased by ₹60 lakh during a quarter.

The lender can compare the reported movement with GST purchase and inward-supply information for the same period.

A rising stock figure combined with relatively flat purchases does not automatically prove manipulation. Inventory can change because of opening stock, production, valuation, or timing differences.

However, the discrepancy creates an important question:

What explains the increase in reported inventory?

The analyst can then examine purchases, opening stock, production, sales, and valuation changes.

2. Compare Sales With Debtor Build-Up

Trade receivables generally increase when a business makes credit sales that have not yet been collected.

A lender can therefore compare:

GSTR-1 outward supplies
Bank collections
Reported debtor balances

If sales remain broadly flat and collections remain stable while declared debtors suddenly increase, the change deserves investigation.

Possible explanations include:

Longer customer credit periods
Delayed collections
Large invoices near period-end
Customer concentration
Credit notes or adjustments
Timing differences

The objective is to determine whether the reported debtor balance is supported by the underlying business activity.

3. Compare Supplier Payments With Creditors

Trade creditors reported in the stock statement can also be tested against bank transactions.

Bank statements can reveal:

Supplier payments
Payment frequency
Delayed settlements
Large supplier transactions
Changes in supplier concentration

If the borrower reports a particular creditor position but actual supplier-payment behaviour suggests a materially different working-capital cycle, the discrepancy should be investigated.

This helps test whether the creditor deduction used in the DP calculation is reasonable.

A Practical Drawing Power Validation Workflow

A lender can turn DP monitoring into a repeatable process:

Stock Statement

↓

Extract inventory and debtor data

↓

Apply ageing and eligibility rules

↓

Deduct applicable creditors

↓

Apply sanction-specific margins

↓

Calculate drawing power

↓

Compare DP with sanctioned limit

↓

Compare DP with actual outstanding

↓

Compare purchases with GST inward supplies

↓

Compare sales and collections with GST and bank data

↓

Validate creditor payments

↓

Flag exceptions for credit review

This approach shifts DP monitoring from a periodic spreadsheet exercise to a continuous credit-control process.

Using Bank and GST Data for DP Monitoring

Independent data becomes especially valuable when lenders manage multiple accounts, large transaction volumes, or frequent stock statements.

A structured financial-analysis system can help surface information such as:

Month-wise GST inward supplies
Month-wise GST outward supplies
GST filing patterns
Business collections
Supplier payments
Cash-credit utilisation
Loan obligations
Unusual transaction patterns

FinEye's GST Analyser can structure month-wise inward and outward supply information, while its Bank Statement Analyser can help classify collections, supplier payments, and credit utilisation.

Together, these data points can provide a second layer of evidence against which reported stock and receivables can be tested.

The goal is not to replace the borrower's stock statement.

It is to validate the assumptions behind the drawing power calculation using independent data.

Why Monthly DP Monitoring Matters

A sanctioned working-capital limit can remain unchanged while the underlying security changes significantly.

Consider this example:

Period	Sanctioned Limit	Drawing Power	Outstanding
Month 1	₹3 crore	₹2.70 crore	₹2.40 crore
Month 2	₹3 crore	₹2.35 crore	₹2.45 crore
Month 3	₹3 crore	₹2.10 crore	₹2.50 crore

The sanctioned limit remains ₹3 crore throughout.

But the relationship between outstanding borrowing and eligible security deteriorates each month.

That is the signal a monitoring team needs to identify.

Monitoring DP only at renewal or enhancement can miss deterioration that develops between review dates.

Key Takeaways

Drawing power is different from the sanctioned credit limit. It reflects the amount that can be drawn against eligible security under the facility's terms.
Unpaid stock is generally deducted, while receivables outside the permitted eligibility criteria are excluded.
Margins vary by asset and sanction. Stock and debtors can have different margins.
A borrower can be within the sanctioned limit but above its drawing power, creating an important irregularity.
Stock statements can be affected by valuation, ageing, double financing, and reporting-date issues.
GST inward supplies can help validate reported purchases and inventory movement.
GST outward supplies and bank collections can help test debtor build-up.
Bank supplier payments can help validate reported creditor balances.
DP should be monitored continuously, not only during renewal or enhancement.
Stale stock statements and persistent excesses against DP can have implications under RBI's applicable asset-classification framework.

The central principle is simple:

A sanctioned limit tells you how much the bank has agreed to provide. Drawing power tells you how much the borrower can draw against the eligible security available now.

For working-capital lenders, keeping these two numbers separate is the foundation of effective drawing-power monitoring.

CMA Data for Bank Loans: What Lenders Actually Check in a CMA Report

FinEye — Mon, 28 Sep 2026 09:15:09 +0000

CMA Data in MSME Lending: How Banks Assess Working Capital Limits

Almost every MSME working capital or term-loan proposal in India above a few crore arrives with a CMA report attached.

Usually prepared by the borrower’s chartered accountant, the report can run to a dozen pages of tables. It typically presents three years of historical financials alongside two years of projections.

For lenders, however, the CMA is not the answer.

It is the borrower’s financial claim.

The credit team still needs to test whether the assumptions behind those projections are supported by independent data such as bank statements, GST returns, and existing loan obligations.

This guide explains what CMA data contains, how banks use it to assess working capital limits, and where credit teams should challenge the numbers before accepting the conclusions.

What Is CMA Data?

CMA stands for Credit Monitoring Arrangement.

The format was introduced in 1988 as a standard framework for banks to assess and monitor working capital credit. It followed the earlier Credit Authorisation Scheme and provided lenders with a consistent way to present a borrower's financial position.

RBI later gave banks flexibility to adopt their own credit assessment methods, but the CMA format continued to be widely used because it provides a structured view of:

Historical financial performance
Projected sales and profitability
Current assets and liabilities
Working capital requirements
Existing and proposed borrowing
Funds movement
Key financial ratios

Today, banks and many NBFCs may require CMA data for working capital limits, renewals, enhancements, and certain term-loan proposals, depending on their internal credit policies.

The important point for an analyst is that CMA data is a structured financial representation, not independent verification of the underlying numbers.

The Six Forms of a CMA Report

A standard CMA report contains six primary forms.

Form	Contents	Credit question
Form I	Existing and proposed credit limits	What borrowing does the borrower already have and what is being requested?
Form II	Operating statement	How have sales, costs, and profits changed?
Form III	Balance-sheet analysis	How are assets and liabilities structured?
Form IV	Current assets and current liabilities	How much inventory, receivables, and payables does the business carry?
Form V	Computation of MPBF	What level of working capital finance can the bank provide?
Form VI	Funds flow statement	Where did funds come from and where were they deployed?

Most CMA reports also include a ratio analysis covering metrics such as:

Current ratio
TOL/TNW
DSCR
Inventory days
Debtor days
Creditor days
Sales-to-working-capital ratios

These figures give the credit officer a starting point for assessing liquidity, leverage, repayment capacity, and working-capital intensity.

How Banks Size Working Capital Limits From CMA Data

MPBF and the Tandon Committee Methods

Maximum Permissible Bank Finance, or MPBF, originated from the Tandon Committee's recommendations on working capital finance.

The basic concept is straightforward:

Working capital gap = Total current assets − current liabilities other than bank borrowing

The different assessment methods determine how much of this requirement should be funded by the borrower versus the bank.

Method I

Under Method I:

The borrower contributes 25% of the working capital gap.
The bank finances the remaining 75%.

Method II

Under Method II:

The borrower contributes 25% of total current assets.
The bank finances the remaining working-capital gap.

Method II became a commonly used framework for working-capital assessment.

A simplified representation is:

MPBF = 0.75 × Total Current Assets − Other Current Liabilities

The exact assessment, however, depends on the lender's applicable policy and treatment of individual current-asset and current-liability items.

Method III

Method III takes a more conservative approach by requiring the borrower to fund core current assets. The bank then applies the Method II approach to the remaining current-asset requirement.

For a credit analyst, the important point is not simply knowing the formula.

It is understanding whether the current assets used in the formula are realistic.

If inventory or receivables are overstated, the resulting working-capital requirement can also be overstated.

The Turnover Method for Smaller MSME Borrowers

For smaller borrowers, lenders may use the turnover method associated with the Nayak Committee.

The broad framework assumes:

Working-capital requirement = 25% of projected annual turnover
Bank finance = 20% of projected annual turnover
Borrower margin = 5% of projected annual turnover

RBI's MSME lending framework has applied the turnover-based approach to eligible fund-based working-capital limits within specified thresholds.

The key credit risk is the same as with CMA-based projections:

If projected turnover is inflated, the resulting working-capital requirement can also be inflated.

That makes historical sales verification important before relying on projected turnover.

When Banks Use the Cash Budget Method

Some businesses have working-capital requirements that cannot be adequately represented by an annual average.

Seasonal businesses such as:

Sugar manufacturers
Tea businesses
Construction contractors
Certain agricultural businesses

may require a month-wise cash budget.

The CMA can provide the underlying financial assumptions, but actual bank-account flows can reveal when cash requirements increase or fall.

For example, a borrower may show sufficient annual profitability while still experiencing severe liquidity pressure during specific months.

That distinction matters when assessing the appropriate credit structure and limit.

Ratios Credit Officers Commonly Review

Ratio / Metric	What it tests	Indicative consideration
Current ratio	Short-term liquidity	1.33 is associated with the traditional Method II framework
TOL/TNW	Leverage relative to tangible net worth	Often assessed against borrower type and lender policy
DSCR	Debt repayment capacity	Commonly assessed against lender-defined thresholds
Inventory days	Stock build-up	Compare against historical and industry levels
Debtor days	Collection cycle	Rising days can indicate weaker collections
Creditor days	Supplier financing	Sharp increases may indicate payment stress

These are not standalone approval rules.

A ratio should be interpreted in the context of the borrower's industry, business model, historical performance, lender policy, and quality of underlying data.

Why Is the Current Ratio Benchmark 1.33?

The commonly referenced 1.33 current ratio is linked directly to the traditional Method II working-capital framework.

If the borrower is expected to contribute 25% of total current assets, the mathematical relationship produces a current ratio of approximately:

Current Ratio = Current Assets / Current Liabilities
             ≈ 1.33

This is why the figure frequently appears in traditional working-capital analysis.

However, modern credit assessment should not treat 1.33 as a universal pass/fail threshold. The appropriate liquidity level can vary by business model and lender methodology.

Where CMA Projections Commonly Need Validation

The biggest weakness in a CMA report is often not the historical data.

It is the projection logic.

1. Growth That History Does Not Support

Suppose a business has grown at:

Year 1: 9%
Year 2: 10%
Year 3: 11%

and suddenly projects:

Next year: 30%

The projection may be achievable, but the credit team needs to understand what changed.

Possible explanations could include:

A confirmed new customer
Additional production capacity
A new distribution channel
A major contract
Expansion into a new market
Price increases

Without supporting evidence, the projection deserves closer scrutiny.

2. Holding Periods Designed Around the Requested Limit

Inventory and receivable days can have a major impact on the working-capital requirement.

Consider a borrower whose historical debtor days are around 75 days but whose projected CMA assumes 120 days.

The additional 45 days increase the amount of capital tied up in receivables.

That can increase the calculated working-capital gap and support a larger borrowing request.

The question for the credit analyst is therefore:

What operational change justifies the additional 45 days?

The answer should come from business evidence, not only from the CMA table.

3. Stale or Unaudited Base Years

A projection is only as reliable as its starting point.

Risk increases when projections are built on:

Provisional financial statements
Unaudited figures
One-off contracts
Exceptional revenue years
Temporary margin expansion
Unusual working-capital movements

Using the latest reliable audited financial year as a base provides a stronger starting point for the projection analysis.

4. Promoter Contribution That Never Arrives

A CMA may show promoter capital infusion or unsecured loans to satisfy the borrower's expected contribution.

But a projected contribution is not the same as an actual contribution.

The bank statement provides a direct verification point.

If the CMA shows a ₹2 crore promoter infusion, the credit team should be able to identify the corresponding credit in the relevant bank account.

This is particularly important before relying on the projected capital structure for disbursal or enhancement decisions.

Validating CMA Data Against Bank and GST Records

A strong credit process treats the CMA as a hypothesis that needs independent validation.

Three data sources are particularly useful:

CMA financial projections
GST records
Bank-account transactions

The comparison can reveal whether the assumptions are supported by actual business activity.

CMA Sales vs GST Returns

Compare historical turnover in Form II with GST-reported outward supplies for the corresponding period.

A material difference should have a documented explanation.

Possible reasons include:

Exempt supplies
Export transactions
Timing differences
Credit notes
Differences in accounting treatment
Businesses operating across multiple entities

A proper GST reconciliation can determine whether the difference is operational or requires further investigation.

CMA Sales vs Bank Credits

Reported sales should be compared with business-related credits across the borrower's accounts.

The analyst should separate operating receipts from:

Inter-account transfers
Loan disbursals
Capital injections
Refunds
Other non-operating credits

The objective is not to expect sales and bank credits to match line by line.

It is to determine whether the scale and pattern of business inflows are consistent with the reported turnover.

Creditor Days vs Actual Payments

Form IV may show a specific level of trade payables.

Bank transactions can help test whether supplier payments support that assumption.

For example, a significant increase in projected creditor days should have a corresponding business explanation.

Otherwise, the projection may be using supplier credit to reduce the borrower's apparent working-capital requirement.

Promoter Infusion vs Bank Credits

If Form VI shows promoter capital or unsecured loans, the credit team should trace the corresponding transaction.

Look for:

CMA projection
      ↓
Promoter contribution
      ↓
Bank account credit
      ↓
Actual deployment

The existence, timing, and source of the funds can then be assessed independently.

Existing Limits vs Loan Debits

Form I should provide a picture of the borrower's existing borrowing.

Bank statements can provide another verification layer.

Look for:

EMI debits
Interest payments
Cash-credit interest
Loan repayment transactions
Other lender debits

A lender obligation that does not appear in the CMA or borrowing schedule can materially change the assessment of leverage and repayment capacity.

A Practical CMA Validation Workflow

For credit teams, the process can be structured as follows:

CMA Report
    ↓
Extract historical and projected figures
    ↓
Check sales growth against history
    ↓
Compare turnover with GST data
    ↓
Compare business inflows with bank credits
    ↓
Validate inventory and debtor assumptions
    ↓
Check creditor payment patterns
    ↓
Trace promoter contribution
    ↓
Identify existing loan obligations
    ↓
Recalculate working-capital requirement
    ↓
Document exceptions and supporting evidence

This approach shifts CMA analysis from table review to data validation.

Where Financial Data Automation Helps

Manual CMA validation can become difficult when a credit team handles hundreds or thousands of loan files.

The analyst may need to review:

Multiple bank statements
GST returns
Loan transactions
Promoter transfers
Related-party movements
Historical financial statements
Projected financials

A structured financial-analysis system can bring these datasets together and surface discrepancies before the credit officer makes a decision.

For example, FinEye's GST Analyser and Bank Statement Analyser can structure information such as:

Monthly GST turnover
GST filing patterns
Net operating credits
Loan obligations
Transaction classifications

This allows the analyst to spend less time manually searching statements and more time investigating the exceptions that matter.

Key Takeaways

CMA data gives lenders a structured view of a borrower's financial history, projections, working-capital requirement, and funding structure.

But the CMA should be treated as a starting point for credit analysis, not independent proof of the borrower's financial position.

The most important validation checks are:

Projected growth: Does it have operational support?
Inventory and debtor days: Are the holding periods consistent with history?
GST turnover: Does reported business activity support the CMA sales figures?
Bank credits: Do actual operating inflows broadly support reported turnover?
Promoter contribution: Did the projected funds actually enter the business?
Existing borrowing: Do bank debits reveal obligations missing from Form I?
Working-capital requirement: Does the calculated requirement remain reasonable after independent validation?

The strongest CMA review is therefore not about finding the right formula.

It is about testing whether the numbers behind the formula are real.

MSME Underwriting Checklist: A Framework for Modern Credit Teams

FinEye — Fri, 25 Sep 2026 08:12:31 +0000

Ask five underwriters at five different NBFCs what a complete MSME credit review looks like, and you’ll likely get five different answers, not because the underlying principles differ, but because most lenders have never written the process down as a single, consistent framework. That gap shows up as inconsistent decisions, slower training for new analysts, and risk that varies by who happened to review the file.

What is an MSME underwriting checklist?
An MSME underwriting checklist is a structured framework that defines what a credit team reviews, in what order, and against what standard, when assessing an MSME borrower, covering financial documentation, transaction analysis, and the cross-checks needed to reach a consistent, defensible lending decision.

Why a written framework matters more than individual analyst skill
A skilled underwriter can do excellent case-by-case analysis. What a framework adds is consistency across analysts, across time, and across loan volume, so a file reviewed by one analyst on a busy Friday gets the same rigour as one reviewed by another analyst with more time on a quiet Tuesday. It also makes onboarding new credit staff faster and gives risk and compliance teams something concrete to audit against.

A working MSME underwriting checklist:
Income and revenue verification: identify recurring salary or business income from bank statement data, and confirm it’s consistent with the declared figure rather than accepting it at face value
GST-to-banking reconciliation: compare declared turnover against actual bank inflows for the same period, sizing any gap and checking whether it has a reasonable explanation
Existing obligations across all linked accounts: identify recurring debits resembling loan repayments, and cross-check against credit bureau data to catch obligations that may not appear in the account reviewed
Cash-flow stability and seasonality: review average balance trends and bounce frequency over a full cycle, not a single month, and distinguish genuine seasonality from a sustained decline
Related-party and connected-account review: flag transfers to or from connected parties and confirm the business rationale, watching specifically for circular transactions without commercial substance
Connected-account and network mapping: check whether the borrower has meaningful financial ties to other entities already in, or being newly assessed by, the loan book
Loan utilisation planning (for existing borrowers): for repeat borrowers or renewals, review whether prior disbursements were used consistent with their stated purpose
Cross-source consistency check: confirm that bank statement, GST, and bureau data tell a broadly consistent story, and document any unresolved gap rather than letting one source override the others silently
How to use this without turning underwriting into a rigid checklist exercise.
The value of a framework isn’t that every step produces an automatic pass or fail; it’s that every file gets the same questions asked, even if the answers require judgment. A checklist that flags “GST-banking gap of 35%, no clear explanation on file” is more useful to a risk team, a lender’s board, or an auditor than a file that simply says “approved” with no record of what was checked.

Where manual application of this checklist breaks down.
Every item above is doable by hand for a handful of files a week. At the loan volumes most growing NBFCs and digital lenders now target, manually reconciling GST against banking data, tracing related-party transfers, and cross-checking bureau exposure for every file becomes the bottleneck in the lending process not credit policy, but the operational capacity to apply it consistently.

How FinEye helps operationalise this checklist.
FinEye is an MSME financial intelligence platform built around exactly this framework; it can help lenders bring together bank statement data, GST filings, Account Aggregator data, and credit bureau information into one borrower view, surfacing income patterns, obligations, cash-flow stability, related-party transfers, connected accounts, and cross-source inconsistencies without requiring an analyst to manually work through each check file by file. It doesn’t replace underwriting judgment or make credit decisions; it gives credit teams the structured, decision-ready information the checklist above depends on, consistently, across the loan book.

Your credit team already has bank statements, GST filings, and bureau data for every borrower. The question is whether checking all eight items above happens consistently — or depends on which analyst has time this week. See FinEye in action → Book a demo.

Connected Accounts and Borrower Networks: A Blind Spot in Traditional Credit Assessment

FinEye — Fri, 25 Sep 2026 08:08:18 +0000

Underwriting is usually built around a single unit of analysis: one borrower, one loan file, one primary bank account. That’s a reasonable starting point, but it can also be an incomplete one because a borrower’s real financial position often depends on accounts, entities, and counterparties that never appear in the file being reviewed.

What does “connected accounts” mean in credit assessment?
Connected accounts are bank accounts, business entities, or parties that are financially linked to a borrower through ownership, family relationships, frequent transactions, or shared business activity but sit outside the single account or entity being formally underwritten. Evaluating a borrower’s connected accounts means looking at that wider network rather than just the submitted file in isolation.

Why single-account underwriting has a structural blind spot
A borrower’s stated business might run primarily through one account, but many MSMEs, especially family-run or group-owned ones, operate across multiple accounts and legal entities that share cash flow, customers, or obligations. If underwriting only reviews the account the borrower chooses to submit, it can miss obligations sitting with a connected entity, income that’s actually generated by a related business, or risk exposure that only becomes visible when the whole network is considered together.

Where this creates real underwriting risk:
Undisclosed obligations at a connected entity that indirectly reduce the borrower’s true free cash flow, even though they don’t appear on the submitted account
Income attributed to the wrong entity: revenue that’s actually generated by a related business being counted toward the borrower under review
Concentration risk across a lender’s own book, where several “different” borrowers turn out to be connected parties whose combined exposure to one lender is far higher than any single file suggests
Guarantor or informal support relationships that aren’t documented but would meaningfully affect actual repayment capacity if the connected party’s own finances weakened
Why this matters more as digital lending scales.
When a lender processes a handful of loans a month, informal knowledge from an analyst who happens to know a family runs three related businesses can partially cover this gap. That doesn’t scale. A digital or high-volume lender processing hundreds of MSME applications has no realistic way to catch these connections through institutional memory alone; it either has a systematic way to identify related parties across its data, or it doesn’t see the connection until it shows up as a portfolio-level correlation in defaults.

Where the data to do this already exists.
Much of what’s needed to map a borrower’s connected accounts is already present in the sources most lenders already collect: recurring transfers to specific counterparties in bank statement data, shared addresses or ownership details in KYC records, and related-party disclosures in financial or GST data. The gap isn’t usually access to this information; it’s a consistent process for connecting it across a borrower’s file rather than treating each data point independently.

How FinEye helps.
FinEye can help lenders identify connected accounts and related parties within a borrower’s financial profile, surfacing recurring counterparties, shared financial activity, and transfers that suggest a wider network than the single account under review. This gives credit and risk teams visibility into obligations, income sources, and exposure that a single-account, single-borrower review would otherwise miss, without requiring an analyst to manually trace those connections file by file.

Curious what a borrower’s connected-account map actually looks like? See FinEye in action → Book a demo.

If your underwriting process treats every submitted account as a closed, self-contained file, connected-account risk is one of the areas most likely to be under-assessed today.

GST Compliance Calendar 2026: All Due Dates for Returns and Payments

FinEye — Thu, 23 Jul 2026 11:36:10 +0000

A GST Compliance Calendar helps businesses keep track of important filing deadlines, including GST returns, tax payments, and annual compliance requirements. Following a structured compliance schedule helps avoid late fees, penalties, and filing errors while ensuring smooth business operations. Staying updated with key GST due dates is essential for maintaining accurate tax records and regulatory compliance.
To learn more, read Fineye detailed guide provided in link below.

GST Compliance Calendar

GST Reconciliation 2026: GSTR-1, 3B & Books

FinEye — Thu, 23 Jul 2026 11:15:13 +0000

GST reconciliation is the process of matching data in GSTR-1, GSTR-3B, and your books of accounts to ensure accurate tax reporting and compliance. Regular reconciliation helps identify mismatches, avoid GST notices, reduce errors, and ensure the correct payment of taxes and Input Tax Credit (ITC). It is an essential practice for maintaining accurate financial records and smooth GST compliance
To learn more, read Fineye detailed guide provided.

GST Reconciliation: GSTR-1, GSTR-3B & Books Guide