Audit · direct tax
Tax audit due date — what actually falls due, and when.
A working reference for practising CAs and articled assistants: how the tax audit report deadline and the ITR deadline for audit cases relate to each other, what Section 271B costs you if you miss it, and the Form 3CD workflow that determines whether you make the date.
- Reviewed July 2026
- 7 min read
- CA Anil Agarwal & the TatvaBooks team
What "tax audit due date" actually refers to
There isn't one date — there are two, and they're linked. The tax audit report (Form 3CA or 3CB, with Form 3CD attached) has to be uploaded electronically and accepted by the assessee before a separate, later date: the income tax return due date for audit cases. Miss the audit-report date and the return itself typically becomes late too, because most audit-case ITRs require the audit report to already be on record before the return can be validly filed as a return within the due date.
Both dates are notified for each assessment year and have been extended by CBDT in several recent years — sometimes by weeks. Treat any specific date you've seen quoted, including in this article, as a working assumption to be confirmed, not a fact to file against.
The two deadlines, and how they relate
The table below sets out the commonly applied structure. It intentionally does not print exact calendar dates for a specific assessment year — those move, and a stale date in a search result is exactly what causes missed deadlines.
| Deadline | Who it applies to | Commonly applied timing |
|---|---|---|
| Tax audit report (Form 3CA/3CB + 3CD) | Every assessee covered by Section 44AB | Roughly one month ahead of the ITR due date for audit cases — commonly around 30 September of the assessment year. |
| ITR for audit cases (non-transfer-pricing) | Assessees requiring audit but not a transfer pricing report | Commonly around 31 October of the assessment year. |
| ITR where a transfer pricing report (Form 3CEB) also applies | Assessees with specified domestic or international transactions under Section 92E | Later still — commonly around 30 November of the assessment year, with the audit report due one month before that. |
| Belated return | Anyone who misses the original due date, including because the audit was late | Later fixed date under Section 139(4) — with loss carry-forward and other restrictions attached. |
These are the commonly applied timings, not this year's notified dates — verify the exact due dates for the relevant assessment year on the Income Tax e-filing portal (and watch for CBDT extension circulars) before you build a filing calendar around them.
Missing the date — what Section 271B actually costs
Section 271B is the penalty provision for failing to get accounts audited under Section 44AB, or for failing to furnish the report by the due date. The penalty is 0.5% of turnover or gross receipts, subject to a fixed rupee cap — but it is not automatic. The assessing officer has to be satisfied there was no reasonable cause for the delay before levying it, and "reasonable cause" has succeeded in practice for things like a documented portal outage close to the deadline, the auditor's own medical emergency, or loss of records in a fire or theft — provided the assessee can show contemporaneous evidence, not an after-the-fact explanation.
Verify the current penalty cap before advising a client — caps under Section 271B, like most fixed rupee figures in the Act, are revised periodically by the Finance Act and a remembered number from a prior year can understate or overstate real exposure.
The bigger practical cost is usually not the 271B penalty itself but the knock-on effect: a return that becomes belated under Section 139(4) because the audit report wasn't ready loses the ability to carry forward business losses (other than unabsorbed depreciation) and may affect certain deduction claims. Clients rarely register this until it costs them a loss set-off two years later.
The Form 3CD workflow — why the due date is won or lost weeks earlier
Practically, the tax audit deadline is rarely missed because the CA hasn't signed — it's missed because the underlying data wasn't reconciled in time to draft Form 3CD. The clauses that eat the most time in the last fortnight are consistently the same ones:
- Turnover reconciliation to GST returns. Form 3CD explicitly calls for books turnover to be reconciled against GSTR-1/3B turnover. Any gap has to be explained, and explaining it requires going back through the year's invoices — not a task to start in the last week of September.
- TDS deducted vs. TDS deposited vs. Form 26Q/24Q filed. Clause-level disallowances under Section 40(a)(ia) hinge on this tie-out. Late or short deposits found at audit time can still be cured before the return is filed, but only if there's runway left.
- Section 43B and cash-payment disallowances (40A(3)). These need a clean expense ledger with payment mode tagged — retrofitting payment-mode tags onto a year of vouchers in the final week is one of the most common sources of audit-season overtime.
- Related-party and loan/deposit clauses (Sections 269SS/269T). These require the client's cooperation to identify related parties and cash-loan movements — start this conversation early; clients are slow to respond to this specific ask.
None of this changes when the due date itself falls. It changes how much of the last month is spent on reconciliation panic versus on the actual audit opinion — and that's the lever a practice actually controls.
Practical notes for a practising CA
- Build your own internal deadline, ahead of the statutory one. Target Form 3CD substantially complete two to three weeks before the notified due date — that buffer is what absorbs late client data, portal slowness in the final days, and any last-minute CBDT extension news that changes nothing about your own workload.
- Track extensions from CBDT directly, not from social media. Extension announcements move fast and unofficial dates circulate faster. Confirm through the Income Tax e-filing portal or a CBDT circular before changing a client communication.
- Separate the audit-report date from the ITR date in client communication. Clients conflate the two and assume "we have until the ITR date." Make clear the audit report itself is due earlier, and that a late audit cascades into a late — and restricted — return.
- Document reasonable cause contemporaneously if a delay is unavoidable. If a 271B exposure looks likely, start the evidence file (portal error timestamps, correspondence with the client) at the time of the delay, not months later when the notice arrives.
- UDIN generation is a separate deadline inside the deadline. The audit report and Form 3CD each require UDIN within the prescribed window after signing — build that into your internal checklist, not as an afterthought once the report is uploaded.
Where clean books buy back the last two weeks
Almost every late-audit story traces back to the same root cause — turnover, TDS and cash-payment data that wasn't reconciled through the year and had to be rebuilt in the final fortnight. TatvaBooks keeps GST-correct invoices, GSTR-2B reconciliation and a full audit trail current all year, so the reconciliation clauses in Form 3CD are a review, not a reconstruction, when audit season starts. See what's built for CA firms specifically on the TatvaBooks for Chartered Accountants page.
Frequently asked questions
What is the due date for tax audit report and ITR filing for an audit case?
What happens if the tax audit report is filed after the due date?
Is the Section 271B penalty automatic once the due date is missed?
What is Form 3CD and why does the due date matter for how it's prepared?
Can the tax audit due date be extended, and how would I know?
Read next
Keep going.
Related audit pages
Compliance & filing
For practising CAs
Built for CA firms · GST-correct books
Books that are already reconciled when the due date hits.
TatvaBooks keeps GST-correct invoices, GSTR-2B reconciliation and an audit trail current all year, so Form 3CD is a review — not a rebuild — every audit season.