How to Prepare Bank Statement Working Papers for a Section 44AB Tax Audit (2026)

Start with who is in the net. A tax audit under Section 44AB is triggered where business turnover exceeds Rs 1 crore (raised to Rs 10 crore where both cash receipts and cash payments are 5% or less of the respective totals), where professional gross receipts exceed Rs 50 lakh, or in the presumptive-scheme opt-out cases under 44AD, 44ADA and 44AE. Notice that the 5% test itself cannot be computed without splitting receipts and payments into cash and banking channels. Before you have even accepted the engagement, the bank statement is load-bearing.

Once inside the audit, the statement earns its place for a simple reason: it is external evidence. Under the auditor's evidence framework, a record generated by a third party (the bank) outside the assessee's control carries more weight than the assessee's own books. Almost every figure in the financials touches the bank at some point, so the statement corroborates income, expenses, loans, capital and tax payments in one place.

That is also why it is dangerous to treat casually. A statement dumped into the file as a PDF printout, un-reconciled and un-analysed, is not a working paper. A working paper is the statement reorganised into the shape the audit questions actually take, tied to the books, and annotated so that a reviewer (or an assessing officer years later) can retrace every conclusion. The rest of this guide is about building that.

A bank-statement working-paper file is not one document. It is a small set of schedules, each answering a different question and each feeding a different part of the audit. At minimum it should contain the following.

The completeness schedule deserves a line of its own because it is the one people skip. You audit the accounts you were given, but the assessee may have an account you were not told about. AIS and Form 26AS often reveal interest credited by a bank whose statement is not in your file. Reconciling the bank interest in AIS against the accounts you hold is the cheapest way to catch an undisclosed account before the department does. If a client is sending statements as PDFs, ask them to re-export in Excel from netbanking instead; our bank-wise export guides show the exact steps you can forward to them, and clean Excel inputs remove an entire class of transcription error from the file.

The bank hands you the year date-wise. Every question an auditor has is party-wise. Reorganising the statement so that each counterparty is rolled up, with its transaction count, total debits, total credits and net position, is the analytical move that turns raw rows into evidence. This is the same discipline as classical ledger scrutiny, applied to the bank rather than to a nominal ledger, and it is the backbone everything else hangs on.

Why it matters for a 44AB file specifically:

Alongside the rollup sits categorisation: every transaction assigned an accounting head, from supplier payment to salary to bank charges to EMI to cash deposit. Categorisation is what feeds the disallowance and TDS clauses later, so it has to be honest. The failure mode to avoid is a sheet that forces every row into a confident head with no unknowns; a real statement always contains rows no one can classify from the narration alone, and those belong in a visible suspense bucket, not smoothed over. Our guide to categorising bank transactions sets out a defensible head list, and the party ledger guide covers the merge-and-rollup mechanics in detail.

Clause 31 of Form 3CD is where cash-mode loans, repayments and receipts get reported, and it is the clause most often understated because the trail sits inside the bank statement and the cash book together, not in the ledger summary. The party ledger is what makes it testable. Three sections drive it:

The bank statement matters here in two ways. First, it evidences the mode of payment. A loan received by NEFT satisfies 269SS on its face; the same amount appearing as a cash deposit into the account on the day a loan was recorded is a flag that needs documenting either way. Second, cash deposits and withdrawals in the statement are the starting point for the mirror-image test: a large cash withdrawal by the assessee may be someone else's cash receipt, and a cash deposit into the account may be a cash receipt that trips 269ST at the assessee's end.

Work the cash-transaction register against the party ledger, tag every line with the section it could attract and the mode actually used, and carry the residue into clause 31 with the mode-of-payment particulars the form demands. Our guide to cash transactions under 269SS, 269T and 269ST walks each sub-clause with worked examples.

If the party ledger is the backbone, the categorised transaction sheet is what feeds the disallowance clauses. Clause 21 collects amounts debited to the profit and loss account that are inadmissible, and several of its heads are discoverable only by reading the payment side of the bank statement:

The same categorised payments feed clause 34, the TDS and TCS compliance clause. A payment head that attracts deduction becomes a line item to trace against the TDS returns and the 26AS. Building this once, off the categorised sheet, means the clause 21(b) inadmissibility and the clause 34 compliance testing draw on the same evidence rather than two separate passes over the statement.

The Annual Information Statement has changed what a defensible file looks like. The department now sees a large slice of the assessee's banking activity independently, reported by banks and other filers under the Statement of Financial Transactions regime (Rule 114E). If your working papers do not reconcile to it, you are leaving the mismatch for an assessing officer to find first.

The high-value bank reporting that lands in AIS includes items such as cash deposits aggregating Rs 10 lakh or more in a year across savings accounts, cash deposits or withdrawals aggregating Rs 50 lakh or more in current accounts, time deposits of Rs 10 lakh or more, and credit-card bill payments above the prescribed cash and non-cash limits. Each of these is, at root, a bank-statement figure. That makes the statement the primary record and AIS the third-party corroboration, which is exactly the direction of reliance an auditor wants.

The working paper is a three-way reconciliation: books, bank statement, and AIS or SFT. Where they agree, tick and move on. Where they differ, the reconciling item and its reason go into the file (a deposit reported gross of a same-day reversal, a joint-account figure attributed in full, a timing difference across the year end). Do not force the numbers to match; document why they do not. This schedule then rolls straight into the ITR summary with the AIS and SFT flags attached, and our AIS and SFT reconciliation guide sets out the line-by-line method.

Working papers exist to be re-performed. The governing test, drawn straight from the auditing standards on documentation, is whether an experienced auditor with no prior connection to the engagement could pick up your file and understand the nature, timing and extent of the work, the evidence examined, and the conclusions reached. A bank-statement file that only you can navigate is not documented; it is remembered.

What that means in practice for this file:

Retain the file for the full statutory period and keep it consistent with the ICAI guidance for tax audits. The reader you are really writing for is not this year's reviewer; it is an assessing officer opening the file three years from now with a specific clause in mind. Much of the assembly, the party rollup, the categorisation and the AIS-ready summary, is mechanical rather than judgemental, which is where a tool like Greenote earns its place: it produces the party-wise ledger, the categorised sheet and the summary from an Excel or CSV statement, so the auditor's time goes to the judgement calls rather than the transcription.

Put together, the file assembles in a sequence, each step building on the last:

1. Confirm completeness. List every bank account and reconcile bank interest in AIS and 26AS against the accounts you hold. Chase any account you cannot see. 2. Get clean inputs. Obtain Excel or CSV exports from netbanking rather than PDFs, to keep amounts as numbers. 3. Tie out balances. Agree opening and closing balances to the books and prepare the reconciliation. 4. Build the party ledger. Roll up every counterparty across narration variants. This is the backbone. 5. Categorise every row. Assign an honest accounting head, with a visible suspense bucket for the unclassifiable. 6. Run the cash-transaction register. Isolate cash deposits, withdrawals and cash-mode payments; test 269SS, 269T, 269ST and 40A(3). 7. Trace the TDS-attracting heads. Feed clause 21(b) and clause 34 off the categorised sheet. 8. Reconcile to AIS and SFT. Three-way tie-out, with reasons for every difference. 9. Document and cross-reference. Legend, sign-off, clause-to-schedule links, exception register closed.

If you want the honest comparison of doing steps 4 to 8 by hand versus automating them, our note on manual Excel versus automated bank-statement analysis walks through where each approach holds up under audit conditions.