What the department sees in your client's bank statement (and what you should see first)

Banks report to the Income-Tax department. GST returns cross-match against bank flows. Company secretaries are required to flag related-party transactions. Increasingly, the data that clients assumed was private is flowing into government systems — and CAs are the ones who need to make sense of it before a notice does.

Bank statement analysis used to mean a junior sitting with a printout and a calculator. For a 12-month statement with 1,500 transactions, that's two days of work and a meaningful error rate. The value is high; the process has been manually painful.

What the department's algorithm is looking for

When the Income-Tax department's system runs a bank statement match against a filed ITR, the primary checks are:

• Total credit entries vs declared turnover — a business with ₹40 lakh in bank credits but ₹25 lakh in declared revenue needs to explain the gap (could be loan repayments, inter-account transfers, personal deposits, GST collected — or it could be suppressed income).
• Large round-number credits — especially recurring ones that could suggest undeclared income.
• Cash deposits above the reporting threshold — especially in irregular patterns post-demonetisation.
• Large outflows to unregistered entities — potential bogus expense claims.
• Patterns that suggest structured transactions designed to stay below reporting thresholds.

What a CA needs to see before the department does

The purpose of bank statement analysis for CA practice is different from the department's adversarial check — but it uses the same data. Before filing a return or preparing for an assessment, you want to:

• Reconcile total bank credits to GST turnover and ITR revenue — identify and explain every gap.
• Categorise all credits: customer receipts, inter-account transfers, loans received, investments liquidated, personal deposits. Every credit needs a category.
• Flag any significant debit that isn't in the books — either it's a payment not recorded (accounting gap) or it's a personal expense run through the business account.
• Identify the top ten counterparties by volume and cross-check them against your client's disclosed customer and vendor list.

How Statements works

Statements in DribbleAudit takes a bank statement PDF (from any major Indian bank format) and extracts the full transaction list, categorised and summarised. The reconciliation view shows the credit-debit summary, the categorised inflow breakdown, and any transactions that were flagged as requiring explanation.

The cash-flow view shows the monthly pattern of business receipts against the declared turnover, so you can see where the gaps are and prepare your explanation before any notice arrives.

For clients under scrutiny or in the process of assessment, Statements gives you the same view of the data that the AO will eventually see — which means you can prepare a reconciliation statement in advance rather than scrambling when the department asks for one.

The inter-account transfer problem

The most common reason for a bank-to-ITR gap in a small business is inter-account transfers that get double-counted. If a client has two accounts and regularly transfers funds between them, both the credit in one account and the debit in the other appear in each statement. Naive analysis counts the credit twice.

Statements automatically identifies likely inter-account transfers — same-day credits and debits of the same amount across accounts when multiple statements are uploaded — and nets them out of the turnover reconciliation. The remaining unexplained gap is smaller and more precisely the thing you need to explain.