Bank reconciliation for NBFCs has to run account by account, not as one blended cash number, because an NBFC typically holds separate current accounts, cash-credit or overdraft accounts against sanctioned limits, and dedicated collection accounts per lending product — each with its own transaction pattern and its own risk of a stale reconciling item hiding inside it. The volume is also the real constraint: a mid-size NBFC disbursing retail loans can post several thousand bank lines a month across these accounts, which makes full-population matching the only realistic way to actually look at everything.
Why NBFCs have more bank accounts than most companies their size
A trading or manufacturing company of comparable turnover might run two or three bank accounts. An NBFC commonly runs more, because the accounts aren't interchangeable — each serves a distinct function that the business or the lender mandates separately. A collection account exists because EMI collections (via NACH, UPI autopay, or direct debit) are swept there before being transferred to the main operating account, often on a lag of one to three days. A cash-credit or working-capital demand loan account exists against a specific sanctioned limit from a bank or NBFC lender, with its own interest and drawing-power mechanics. And escrow or designated accounts exist where a co-lending or securitisation arrangement requires collections to be ring-fenced.
- A primary current account for disbursements and operating expenses
- One or more collection/escrow accounts per lending product or co-lending partner
- A cash-credit or overdraft account against a working-capital facility
- A fixed-deposit-linked account where FDs are pledged as collateral against borrowings
- A nodal or pool account where a securitisation or assignment transaction requires segregated receipts
The volume problem is real, and sampling makes it worse
A collection account alone can have hundreds of inbound lines a day during a busy EMI cycle. Sampling twenty-five transactions from that account and extrapolating tells you almost nothing about whether collections are being swept and recorded correctly, because the failure mode you're actually looking for — a batch of collections that sat in the account for six days before being recorded, or a reversal that was never traced back to the right loan account — is exactly the kind of low-frequency event a sample is built to miss. Matching every line against the ledger, for every account, across the full period, is the only version of this test that has a chance of catching it.
Common practice, not a requirement
Treat each bank account as a separate reconciliation unit with its own exception register. A firm that nets exceptions across accounts to get to a tidier combined number has stopped testing cash and started managing optics.
What the date window should look like per account type
| Account type | Typical clearing lag | Why the window matters here |
|---|---|---|
| Current/operating account | 1–3 days | Standard cheque and NEFT clearing; a wide window here just invites false matches |
| Collection account | 1–5 days | NACH bounces and re-presentations create legitimate multi-day gaps between the debit date and the credit landing in the ledger |
| Cash credit / overdraft | Up to a full interest cycle | Interest debits and limit-linked sweeps can post with a lag tied to the bank's own interest calculation date, not the transaction date |
| Escrow / nodal account | Varies by trust & retention agreement | Movements are often governed by a contractual waterfall, not ordinary banking timelines — treat a wide gap here as a reason to read the agreement, not widen the window further |
A single firm-wide date window applied blindly across all of a client's accounts will either be too tight for the collection account (generating a flood of false exceptions that don't mean anything) or too loose for the current account (letting unrelated transactions pair up). Set the window per account, not per engagement.
What persistent exceptions in a collection account usually mean
An outstanding item in a current account is usually a cheque in transit. An outstanding item in a collection account that keeps recurring is different — it often means the client's sweep-and-record process has a genuine gap: collections landing in the bank before the loan management system posts them, or a reconciliation break between the payment aggregator's settlement file and what actually hits the account. That's not a cash-testing footnote; for an NBFC it's a control observation worth raising separately, because it bears on whether collection income and loan-level receivables are being recorded on time.
How we think about this
Lekhya reconciles each bank account on its own exception register, matching ledger entries to statement lines by amount and a date window set per engagement, across the full statement period for every account — not a blended cash position. A recurring break in one collection account should be visible as exactly that, not diluted into a firm-wide cash number that nets out fine.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Bank, cash & treasuryBank reconciliation audit procedure for statutory auditWhat a BRS must reconcile, the red flags that separate a timing difference from a cover-up, and how many months you actually need to review.
- Audit documentationHow to test bank overdraft classification between cash equivalents and borrowingsThe same overdraft facility can be a cash equivalent in the cash flow statement and a borrowing on the balance sheet. Testing it means checking both treatments separately, against different rules.
- Related parties & disclosuresBank branch statutory audit checklist: LFAR, advances and revenueA branch audit runs on a compressed timeline against a fixed RBI format. The work that has to happen regardless of time pressure: advances classification, LFAR, revenue audit.
- Bank, cash & treasuryA bank reconciliation workflow for audit firms, not just a procedureMatching the ledger against the bank statement is mechanical. Doing it the same way across every client file, with every unmatched item actually explained, is the part firms get wrong.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.