Clause 34 of Tax Audit Report: TDS/TCS Reconciliation Guide for AY 2026-27
Updated: Sep 5
Clause 34 of tax audit report is the Form 3CD TDS/TCS control point. For FY 2025-26 / AY 2026-27, it asks the tax auditor to examine three connected areas: whether tax was required to be deducted or collected and the amounts involved under Clause 34(a); whether required TDS/TCS statements were furnished and whether they contained the required information under Clause 34(b); and whether interest under section 201(1A) or section 206C(7) was payable and paid under Clause 34(c). A reliable Clause 34 review therefore starts from the books and statutory ledgers, not only from filed quarterly returns.
Freshness check — 3 September 2026: Income Tax Department guidance for FY 2025-26 / AY 2026-27 continues to place the tax audit under the Income-tax Act, 1961 framework using Form 3CA/3CB with Form 3CD. The Department’s current tax-audit reporting material also describes Clause 34(a), 34(b) and 34(c) as the TDS/TCS deduction-or-collection, statement-filing and interest-reporting components respectively.
Clause 34 of Tax Audit Report: What 34(a), 34(b) and 34(c) Require
Clause 34 should be treated as one reconciliation chain rather than three isolated boxes. A transaction may first create a TDS or TCS obligation, then flow into a quarterly statement, and later create interest if deduction, collection or payment was delayed. If the population used for these three stages does not reconcile, the tax-audit file can contain internal contradictions even where each individual return was filed.
Clause 34(a): TDS/TCS amount reconciliation
Clause 34(a) begins with the fundamental question: was the assessee required to deduct or collect tax at source? Where the answer is yes, the auditor has to report the prescribed TDS/TCS particulars. The practical risk is incompleteness. A quarterly statement can only show transactions that were identified and processed through the TDS/TCS system; it does not prove that every payment or receipt in the general ledger was correctly screened.
The stronger audit approach is to build a books-first population. Scan expense ledgers, capital expenditure, provisions, year-end accruals, professional and contractual payments, rent, commission, interest, non-resident payments and other relevant transaction classes. Then map the population to the applicable withholding or collection provision, exclusions, certificates or lower-rate positions, tax actually deducted or collected, and tax deposited. The objective is a defensible bridge from financial records to the TDS/TCS compliance trail.
For the transaction-level fields and reconciliation workflow, use PGT’s detailed Clause 34(a) guide. That page remains the deeper sub-clause resource; this page is the umbrella decision and control guide.
Clause 34(b): TDS/TCS statement filing
Clause 34(b) moves from transaction identification to statement compliance. The audit file should establish which TDS/TCS statements were required, whether they were furnished, and whether the information that was required to be reported was in fact included. A filing acknowledgement is useful evidence, but it is not enough by itself if the return population is incomplete, a correction statement remains pending, or book transactions were omitted from the statement.
A practical reconciliation should connect the TAN-wise liability, challans, statement acknowledgements, correction statements, defaults and unmatched items. Particular attention is warranted where payroll and non-payroll TDS are maintained in different systems, where multiple branches operate under one or more TANs, or where ERP vendor masters do not reliably capture withholding attributes.
For the statement-filing side, see the dedicated Clause 34(b) TDS/TCS statement guide.
Clause 34(c): interest under sections 201(1A) and 206C(7)
Clause 34(c) closes the loop by asking whether the assessee is liable to pay interest under section 201(1A) or section 206C(7), and, where relevant, requiring the prescribed payment details. This makes unresolved timing differences important. A tax amount may ultimately have been deposited, yet a delay in deduction, collection or payment can still create a separate interest exposure that needs to be identified and reconciled.
The working papers should therefore compare due events, actual deduction or collection dates, deposit dates, demands or defaults reflected on the compliance system, interest workings and challans. Old defaults that were corrected during the year should not disappear from the audit trail merely because the principal TDS/TCS amount now matches.
For the interest-specific audit trail, use the Clause 34(c) interest reporting guide.
A practical Clause 34 reconciliation workflow
Extract the full payment and receipt population from the books, including year-end provisions and manual journal entries that may not pass through the normal vendor workflow.
Classify transactions by the relevant TDS/TCS provision and document exclusions, thresholds, declarations, certificates and lower-rate positions where applicable.
Reconcile tax required to be deducted or collected with tax actually deducted or collected and deposited.
Match challans to quarterly statements and identify challans used across multiple statements or correction cycles.
Compare statement data with the books and quantify transactions that should have appeared but did not.
Review defaults, notices, correction statements and interest computations for delayed deduction, collection or remittance.
Resolve TAN-wise and branch-wise differences before finalising Form 3CD, and retain an exception log for items requiring judgement.
Mini-case: why a filed TDS return may still leave a Clause 34 issue
Assume a company’s quarterly statement contains all invoices processed through its accounts-payable workflow. During year-end closing, however, finance books a manual professional-fee provision that is not routed through the vendor master. If the TDS review begins only from the filed statement, the provision may never enter the population. A books-first Clause 34 review instead flags the manual entry, tests the withholding requirement, checks whether it was captured in a later deduction or correction cycle, and separately considers any resulting interest.
The lesson is broader than this example: Clause 34 is a completeness test as much as a return-filing test. The most useful working paper is a single control schedule that connects the general ledger, tax determination, challans, statements, corrections and interest.
Common Clause 34 red flags
Quarterly statements are treated as the starting population instead of being reconciled back to the books.
Year-end provisions, reversals and manual journals are not separately screened for withholding consequences.
A lower or nil deduction position is used without retaining the supporting basis in the audit file.
The amount deposited agrees with challans, but the underlying statement contains missing or incorrect transaction data.
Correction statements filed after an error are not linked to the original exception and supporting working paper.
Interest is checked only against outstanding portal demands rather than independently considering delayed events.
Different TANs or branches are aggregated without a clear reconciliation to the audited financial statements.
How Clause 34 fits into the wider Form 3CD file
Clause 34 should not be reviewed in isolation from the rest of Form 3CD. Related expense disallowance, statutory liability, related-party, non-resident payment and reconciliation issues can interact with the same underlying transactions. For the broader reporting structure, use PGT’s Tax Audit Clauses for AY 2026-27 guide as the pillar page and then move into the relevant clause-specific working paper.
FAQ: Clause 34 of tax audit report
What is Clause 34 of the tax audit report?
Clause 34 of Form 3CD is the TDS/TCS reporting clause. In practical terms, it covers the assessee’s obligation to deduct or collect tax and the prescribed amounts under 34(a), required TDS/TCS statements under 34(b), and interest liability under section 201(1A) or 206C(7) under 34(c).
Is Clause 34 only a check of TDS returns?
No. Filed statements are important evidence, but the auditor should reconcile them to the underlying books and transaction population. Otherwise, a transaction omitted from the statement may never be identified.
Should Clause 34(a), 34(b) and 34(c) be reconciled together?
Yes. They represent connected stages of the same TDS/TCS compliance chain: the underlying obligation and amounts, statement reporting, and interest consequences. A combined schedule makes inconsistencies easier to identify.
What records should finance teams prepare for Clause 34?
At minimum, prepare the relevant general-ledger extracts, TDS/TCS workings, challans, quarterly statements and acknowledgements, correction statements, certificates or lower-rate support, defaults or notices, interest workings, and a reconciliation of these records to the audited financial statements.
Practical takeaway
For AY 2026-27, the strongest Clause 34 file is not a collection of portal downloads. It is an auditable reconciliation from books to tax obligation to deposit to statement to interest. Finance teams that complete this bridge before the tax-audit close are better placed to identify omissions early, explain exceptions and avoid inconsistent Form 3CD reporting.
PGT & Associates can assist businesses and finance teams with tax-audit reconciliations and review of complex Form 3CD reporting positions. The appropriate treatment depends on the facts and supporting records; this guide is for general professional information and does not guarantee a particular tax outcome.
Primary sources checked
📥 Free Download: AY 2026-27 Form 3CD Working Paper & Tax Audit Checklist (Excel)
Preparing for Section 44AB tax audits? Ensure seamless clause-by-clause verification, Section 43B(h) MSME compliance, and Clause 44 GST reconciliations with our complete working paper.
Comments