One Blank Column, No Deliberate Default: ITAT Deletes Tax Audit Penalty – Software Error in Form 3CD: ITAT Delhi Deletes Section 271B Penalty | Form 3CD Filing Error

Form 3CD Filing Error – An inadvertent omission in a tax audit report should not automatically be treated as a deliberate failure to comply with the Income-tax Act. The Delhi Bench of the Income Tax Appellate Tribunal has held that leaving Column 40 of Form 3CD blank because of a bona fide software error constituted “reasonable cause” under section 273B of the Income-tax Act, 1961.

Accordingly, the penalty imposed under section 271B for alleged non-compliance with section 44AB was held to be unsustainable.

Case at a Glance

Particular	Details
Case	Partyaksh Sharma v. ITO, Ward-28(1), New Delhi
Appeal	ITA No. 1813/Del/2026
Assessment year	AY 2017-18
Forum	ITAT Delhi
Order date	17 July 2026
Disputed provision	Sections 44AB, 271B and 273B
Reporting error	Column 40 of Form 3CD remained unfilled
Explanation	Inadvertent omission caused by software error
Evidence	Affidavit of the Chartered Accountant
Decision	Penalty deleted; appeal allowed
Additional issue	Delay of 173 days in filing appeal condoned

The appeal and its case details are also reflected in the official ITAT cause list.

What Does Column 40 of Form 3CD Require?

Column 40 of Form 3CD requires comparative financial particulars for the relevant previous year and the immediately preceding previous year, including:

• total turnover;
• gross profit as a percentage of turnover;
• net profit as a percentage of turnover;
• stock-in-trade as a percentage of turnover; and
• material consumed as a percentage of finished goods produced.

The Income Tax Department’s official guidance explains the information required to be reported under Clause 40 of Form 3CD.

Although these particulars are important, the central question before the Tribunal was whether their inadvertent omission should be equated with complete failure to obtain or furnish a tax audit report.

Facts of the Case

The assessee had obtained and furnished the tax audit report as required under section 44AB. During assessment proceedings, however, the Assessing Officer noticed that Column 40 of Form 3CD had been left blank.

The Assessing Officer concluded that material information relating to turnover, profitability, stock-in-trade and other prescribed particulars had not been furnished. The audit report was consequently treated as incomplete and, therefore, as non-compliant with section 44AB.

On that basis, a penalty was imposed under section 271B. The penalty was subsequently confirmed by the CIT(A)/NFAC.

Before the ITAT, the assessee explained that:

• the audit report had actually been obtained and filed;
• only one reporting column had remained unfilled;
• the omission occurred because of a software error;
• there was no intention to conceal information or disregard the law; and
• the Chartered Accountant who prepared the report had furnished an affidavit confirming the circumstances of the omission.

Section 271B: Penalty for Tax Audit Failure

Section 271B provides for penalty where a person fails to get the accounts audited or fails to furnish the audit report required under section 44AB.

The penalty is the lower of:

• 0.5% of the total sales, turnover or gross receipts; or
• ₹1,50,000.

The statutory amount and conditions are explained in the Income Tax Department’s official section 271B guidance.

However, section 271B must be read with section 273B, which protects an assessee who proves that there was reasonable cause for the failure.

Protection Available Under Section 273B

Section 273B provides that no penalty shall be imposed for specified failures, including a failure covered by section 271B, where the assessee proves that there was reasonable cause.

Therefore, a penalty under section 271B is not automatic. The surrounding facts, conduct of the assessee and evidence supporting the explanation must be considered.

The assessee must establish that the default was bona fide and did not arise from deliberate inaction, negligence or lack of good faith.

Arguments Before the ITAT

Assessee’s submission

The assessee contended that the audit report was not deliberately filed with incomplete particulars. Column 40 remained blank because of an inadvertent software error.

The explanation was supported by an affidavit from the Chartered Accountant who had prepared the tax audit report. It was argued that such an unintended technical omission constituted reasonable cause within the meaning of section 273B.

Revenue’s submission

The Revenue argued that an incomplete audit report should be treated as a violation of section 44AB. According to the Department, failure to complete an important reporting column meant that the statutory audit-reporting requirement had not been properly fulfilled.

ITAT Delhi’s Decision

The Tribunal accepted the assessee’s explanation.

It observed that “sufficient cause” ordinarily implies the absence of negligence, deliberate inaction or want of bona fides. After considering the Chartered Accountant’s affidavit, the explanation regarding the software error and the absence of any mala fide intention, the Tribunal found the omission to be bona fide.

On the totality of the facts, the Tribunal held that the assessee’s case fell within the meaning of “reasonable cause” under section 273B. Consequently, the penalty imposed for the alleged section 44AB default was held to be unsustainable.

The appeal was allowed and the penalty was deleted. The full text of the reported ITAT order records the Tribunal’s findings.

Judicial Precedents Considered

The Tribunal referred to the following decisions while considering the meaning of good and sufficient cause:

• CIT v. Mysore Fertiliser Co. — (1984) 145 ITR 91 (Mad.);
• CIT v. Chembara Peak Estates Ltd. — (1990) 183 ITR 471 (Ker.);
• CIT v. Jaipur Electro (P.) Ltd. — (1990) 183 ITR 476 (Raj.); and
• CIT v. Bhikaji Ramchandra — (1990) 183 ITR 478 (Bom.).

These decisions support the broader principle that the existence of sufficient or reasonable cause is a factual determination. A statutory default does not necessarily require imposition of penalty where the taxpayer demonstrates bona fide circumstances through credible evidence.

Is Every Software Error a Reasonable Cause?

No. The decision should not be interpreted as granting automatic immunity whenever a taxpayer or auditor refers to a “software error”.

Relief was granted because the explanation was supported by surrounding facts and, importantly, an affidavit from the Chartered Accountant. There was no material indicating deliberate suppression, dishonest conduct or mala fide intention.

A taxpayer relying on a technical or software-related error should preserve:

• the originally filed audit report;
• screenshots or error messages generated by the software;
• software version and update details;
• email correspondence with the software provider;
• working papers containing the omitted particulars;
• proof that the relevant information was otherwise available in the audited accounts;
• a detailed confirmation or affidavit from the tax auditor; and
• evidence of prompt corrective action after discovery of the mistake.

A bare statement that “the software caused the error”, without supporting material, may not satisfy the burden imposed by section 273B.

Importance of the Chartered Accountant’s Affidavit

The affidavit of the tax auditor played an important role in demonstrating the bona fide nature of the omission.

A properly drafted affidavit in such a case should ordinarily explain:

1. who prepared and uploaded the tax audit report;
2. the software and utility used;
3. the nature of the technical error;
4. how and when the omission was discovered;
5. whether the omitted particulars were available in the audit working papers;
6. that the omission was not deliberate; and
7. the corrective steps taken after discovery.

The affidavit should be consistent with the audit file, financial statements and portal records. Any inconsistency may weaken the reasonable-cause defence.

Condonation of 173-Day Delay

The appeal before the ITAT was delayed by 173 days. The assessee explained that the delay occurred because of a change in tax consultant. The new consultant later reviewed the income-tax portal, discovered the appellate order and found that no further appeal had been filed.

The Tribunal accepted the explanation as bona fide and condoned the delay.

This part of the ruling is also practically important. While a change of consultant may explain a delay in an appropriate case, taxpayers should not depend upon it as a routine defence. Copies of all orders, notices and appeal deadlines should be independently monitored through the income-tax portal.

Position Under the Income-tax Act, 2025

The decision relates to AY 2017-18 and was therefore governed by the Income-tax Act, 1961. For Tax Year 2026-27 onwards, the corresponding provisions are:

Income-tax Act, 1961	Income-tax Act, 2025	Subject
Section 44AB	Section 63	Tax audit requirement
Section 271B	Section 446	Penalty for failure to obtain or furnish tax audit report
Section 273B	Section 470	Protection where reasonable cause is proved
Forms 3CA/3CB/3CD	Form No. 26	Tax audit report and statement of particulars
Rule 6G	Rule 47	Prescribed audit-reporting rule

The official CBDT FAQs confirm that Form No. 26 applies from Tax Year 2026-27. The comparative disclosure relating to turnover, gross profit, net profit, stock and material consumption continues in Part D, item 12(d) of Form No. 26.

Further, section 446 retains the penalty of 0.5% of turnover or gross receipts, subject to the maximum of ₹1,50,000. Section 470 of the Income-tax Act, 2025 continues the reasonable-cause protection.

Readers may use the Income-tax Act 1961–2025 Section Finder for section-wise comparison.

Practical Takeaways

• A minor or technical defect in an otherwise filed tax audit report should not automatically be equated with complete failure to obtain or furnish the report.
• Penalty under section 271B is subject to the reasonable-cause defence under section 273B.
• The burden of proving reasonable cause rests on the assessee.
• Contemporaneous evidence is considerably stronger than an explanation prepared only after penalty proceedings begin.
• An affidavit from the tax auditor can be valuable, but it should be supported by audit working papers and technical records.
• Tax audit reports should be downloaded and reviewed immediately after filing and acceptance by the assessee.
• The ruling is fact-specific and does not excuse careless or repeated omissions.
• For Tax Year 2026-27 onwards, professionals must use section 63, section 446, section 470 and Form No. 26 under the Income-tax Act, 2025.

Conclusion

The ruling in Partyaksh Sharma v. ITO reinforces an important principle: penalty provisions must distinguish between a deliberate statutory violation and a bona fide technical mistake.

Where the tax audit has actually been conducted and furnished, and an isolated reporting omission is credibly shown to have resulted from a software error without mala fide intention, the protection of reasonable cause may be available. Nevertheless, taxpayers and tax auditors should maintain complete evidence because section 273B grants relief only when reasonable cause is proved—not merely asserted.

For notices involving defective tax audit reports, section 271B penalties or appellate proceedings, a fact-based response supported by the audit file, portal records and technical evidence is essential. Professional assistance may be obtained for tax audit compliance and income-tax litigation and appeal representation.