Bank Statement Red Flags: 12 Patterns Every CA Should Catch in Ledger Scrutiny (2026)

1. Party concentration. A single counterparty accounts for the bulk of the year's credits.

• Date-wise: receipts are spread across dozens of dates, so nothing looks unusual on any one day.
• Party-wise: one name sits at the top of the credit side by a wide margin. That is a revenue-concentration and going-concern signal, and sometimes the sign that the client's many customers are really one.
• What to do: confirm the party is genuinely third-party and at arm's length, corroborate with invoices and agreements, and consider whether concentration disclosure is warranted.

2. Undisclosed related-party flows. Money moving to or from directors, partners, relatives, or sister concerns that never made the related-party list.

• Date-wise: a transfer to a plausible-looking trading name reads as an ordinary vendor payment.
• Party-wise: the aggregate to a party whose name, address, or UPI handle ties back to a director or a group entity rises to the surface, as do directors' current-account swings.
• What to do: test the rollup against the related-party list you were given, and the one you were not. Keep 40A(2)(b), deemed dividend under 2(22)(e) for closely held companies, and AS 18 / Ind AS 24 disclosure in view.

3. Out-and-back loans. Money leaves to a party and a near-equal amount returns from the same party months later.

• Date-wise: the outflow in April and the inflow in November are hundreds of rows apart and never connected.
• Party-wise: the same counterparty carries both a large debit and a matching later credit, the signature of a loan given and repaid, or an advance that round-tripped.
• What to do: obtain confirmation, check whether any leg touched cash against the 269SS and 269T limit of Rs 20,000, and verify whether interest and TDS were handled.

4. Round-tripping. Funds go out and come back, often to inflate turnover or dress up a year-end balance.

• Date-wise: a debit and a similar-sized credit a few days apart look like two unrelated transactions.
• Party-wise: money that leaves to one party and returns from the same or a linked party, with no goods or service in between, forms a visible there-and-back.
• What to do: trace both legs, test the cut-off around year-end, and ask what underlying transaction the movement supposedly represents.

5. Circular transfers. A loop across group or associated accounts, A to B to C and back to A.

• Date-wise: each leg sits in a different account and a different week, so the loop is invisible.
• Party-wise, read across the group: funds that return to their origin with no economic substance close the circle.
• What to do: map the full loop, question the substance of every leg, and consider disclosure and disallowance.

6. Round-sum transfers. Exact round figures, Rs 5,00,000 or Rs 2,00,000, with none of the odd-rupee texture of real invoices.

• Date-wise: a clean round amount looks tidier than a messy one, not more suspicious.
• Party-wise: a counterparty whose entire relationship is round numbers is almost never a trade debtor or creditor. It is financing, a loan, or capital, frequently misfiled as sales or an expense.
• What to do: reclassify to loan or capital, and check documentation, interest, and TDS accordingly.

7. Large cash deposits and withdrawals. Aggregate cash movement that the client's books may not fully explain.

• Date-wise: CDM and branch cash entries are scattered through the year, individually unremarkable.
• Party-wise, treating cash as its own bucket: the yearly cash-in and cash-out totals stand on their own. Watch the reporting triggers: aggregate cash deposits of Rs 10,00,000 in savings or Rs 50,00,000 in a current account are SFT-reportable, and any single cash receipt of Rs 2,00,000 or more engages 269ST.
• What to do: reconcile the bank cash to the cash book, establish the source, and tie the totals to AIS and SFT.

8. Structuring and splitting below thresholds. Amounts parked deliberately just under a statutory line.

• Date-wise: Rs 19,000 on Monday and Rs 19,500 on Wednesday read as two small deposits.
• Party-wise, clustered by amount: repeated receipts just under Rs 20,000, or under the Rs 2,00,000 of 269ST, or under the Rs 10,000 of 40A(3), point to splitting rather than coincidence.
• What to do: this is a hard flag. Document the pattern, put the question to the client in writing, and weigh reporting and disallowance. The cash-transaction guide sets out the sections in full.

9. Dormant-then-active spikes. A quiet account that erupts near year-end.

• Date-wise: months of small activity, then a burst in February and March that you only notice if you happen to scroll there.
• Party-wise with a timeline: a sudden concentration of large flows, often from a new party, clustered in the closing weeks.
• What to do: raise the intensity of your cut-off testing on those weeks and confirm the closing transactions directly.

10. Reference-number-as-party junk. Narrations that are all machine reference and no name.

• Date-wise: rows read as `UPI/2247xxxx` or `NEFT-SBINxxxx` with nothing human in them, by the hundred.
• Party-wise: these refuse to resolve to a counterparty and collect in Suspense or Unknown, taking real parties down with them.
• What to do: do not wave the bucket through. For every material row in it, chase the underlying party from the client or the bank. Clean categorisation is what keeps this bucket small.

11. Suspense-heavy narrations. The size of the unattributable pile is itself a finding.

• Date-wise: you cannot even measure it without reading every row.
• Party-wise: the share of total value sitting in Suspense is a number you can quote. A statement where a large slice of value is unattributed has been skimmed, not scrutinised. An honest suspense bucket is a feature: it tells you precisely what still needs answers.
• What to do: work the suspense by value, not by row count, and resolve the largest items first.

12. Mismatched interest versus AIS. Bank interest that does not agree with what the department already knows.

• Date-wise: interest credits land quarterly and blend into the noise.
• Party-wise: the year's total bank interest, rolled up as one figure, sits next to the AIS interest entry and the Form 26AS TDS. A gap means under-reported income or mis-deducted tax.
• What to do: reconcile bank interest to AIS and carry the reconciled figure through to the ITR summary.

• Rollup first, read second. Convert the date-wise export to a party-wise ledger before you form any view. Judge parties, not rows.
• Sort by value. Scrutiny time is finite. Rank counterparties and the suspense bucket by rupee value and start at the top.
• Run the threshold sweep. Pass the whole statement against the Rs 20,000, Rs 2,00,000, Rs 10,000, and SFT lines in one go, rather than spotting them by eye.
• Reconcile outward. Tie interest, TDS, and cash totals to AIS, 26AS, and the books, then carry the numbers into the ITR summary.
• Write the suspense down. Whatever will not resolve stays in an honest Unknown bucket with a note, so next year's file, or a reviewer, can see exactly what was open.