₹23.33 Crore Addition Deleted: ITAT Says Wrong ITR Column Is Not Undisclosed Income




Loading

₹23.33 Crore Addition Deleted: ITAT Says Wrong ITR Column Is Not Undisclosed Income

 

 

A clerical mistake in the ITR cannot become taxable income when the amount was already disclosed and the error had no impact on the final computation

How much can a wrong column in an Income-tax Return cost a taxpayer?
Apparently, 23.33 crore – at least until the Tribunal looked at what had actually happened.

A recent ruling of the Bangalore Bench of the Income Tax Appellate Tribunal provides an important lesson in return filing: a mistake in reporting an amount in one column instead of another does not automatically convert that amount into taxable income.
In Castles Vista (P.) Ltd. v. Assistant Commissioner of Income-tax, Central, IT Appeal No. 1621 (Bang.) of 2025, for AY 2022-23, the Tribunal dealt with an addition of 23,33,32,982 arising from an incorrect entry in the Income-tax Return.
The Tribunal ultimately held that the mistake was merely clerical and directed deletion of the entire addition.

The 23.33 crore mystery

The assessee had computed an adjustment under the Income Computation and Disclosure Standards (ICDS).
The net adjustment amounted to approximately:
23.33 crore.
While filing the return, however, the assessee entered this amount in Column 4(e) of Part A-OI instead of the appropriate Column 3B of Part A-OI.
That may sound like a small data-entry error.
But because the amount was substantial, it caught the attention of the Assessing Officer.
The return was scrutinised and the Department examined the substantial reduction in profit attributed to the ICDS adjustment.
The AO ultimately treated the amount as an addition.
The result was extraordinary:
A figure of 23.33 crore, which the assessee said had merely been placed in the wrong reporting column, was converted into an addition to taxable income.

What was the taxpayer’s explanation?

The assessee did not dispute that the figure had been entered in the wrong column.
Instead, it explained exactly what had happened.
The amount represented a decrease in profit/increase in loss arising from the ICDS adjustment.
According to the assessee, it ought to have been reported in Column 3B, dealing with the relevant ICDS adjustment.
Instead, through inadvertence, it was entered in Column 4(e), which related to deviation from the method of valuation prescribed under Section 145A.
In other words:
The number was there.
The disclosure was there.
The mistake was in where the number was placed.
The assessee argued that there was no concealment of the amount and no change in the ultimate computation of taxable income.

The Revenue’s own admission became important

There was an interesting moment before the Tribunal.
The Department’s representative supported the orders of the lower authorities but fairly confirmed that the addition had been made only because the amount was disclosed in Column 4(e) instead of Column 3B.
More importantly, it was accepted that:
Had the amount been reported in Column 3B, no further income would have been required to be offered.
That admission went to the heart of the controversy.
If the correct entry would not have resulted in any additional income, how could the incorrect column placement itself create taxable income of ₹23.33 crore?

The Tribunal looked beyond the column

The Bangalore ITAT examined the actual computation.
It found that the assessee had in fact computed the ICDS adjustment and that the amount represented the relevant decrease in profit.
The only error was the column in which the figure was entered.
The Tribunal therefore concluded:
This was only a clerical error.
There was no increase in income merely because the amount appeared in a different column.
The Tribunal further observed that even if the Assessing Officer corrected the entry, he would also have to remove the amount from the column in which it had been wrongly reported.
Otherwise, the same amount would effectively get counted twice.
And that would lead to an absurd result.

A return form is a reporting mechanism — not a tax-generating machine

This is perhaps the broader lesson.
An Income-tax Return contains numerous schedules, columns and sub-columns.
Some are meant for:

•  reporting accounting figures;

•  making tax adjustments;

•  providing additional information;

•  reporting ICDS adjustments;

•  reporting statutory deviations; and

•  arriving at taxable income.
A mistake in one reporting field should certainly be corrected.
But the mere location of a number cannot change the underlying economics of the transaction.
If an amount has already been disclosed and properly accounted for in determining taxable income, shifting it from one column to another cannot by itself create a second taxable amount.
The tax liability arises from the law and the computation — not from the coordinates of a spreadsheet cell.

23.33 crore makes the lesson even more important

A taxpayer may reasonably wonder:
“If the mistake was clerical, why did it reach the Tribunal?”
Because the number was enormous.
A ₹23.33 crore entry in an unexpected column naturally attracts attention.
And rightly so.
The Department should investigate such a discrepancy.
The important point is what happens after the discrepancy is identified.
The investigation should answer:

1.  What does the amount actually represent?

2.  Where else has it been disclosed?

3.  What is its impact on taxable income?

4.  Is there any actual understatement of income?

5.  Has the taxpayer received any unintended tax benefit?

6.  Is there any evidence of concealment?
In the present case, the answers did not support the addition.

A mismatch is a starting point, not the conclusion

Modern tax administration increasingly relies on automated checks.
Returns are processed electronically.
Large figures trigger alerts.
Mismatches between schedules can be identified automatically.
This is useful for detecting genuine errors and possible tax evasion.
But there is a danger:
A mismatch can become the conclusion instead of the starting point of an enquiry.
The Castles Vista decision is a reminder that an apparent mismatch must be understood in context.
A return can contain a genuine human error without containing concealed income.

What distinguishes an error from concealment?

This is where the case becomes particularly useful.
Suppose a taxpayer receives ₹10 crore but deliberately omits it from the return.
That is obviously very different from reporting ₹10 crore in the wrong column while fully disclosing the underlying transaction and correctly computing the taxable income.
The first situation raises a substantive tax issue.
The second may be a reporting error.
The Tribunal’s decision reinforces the need to distinguish between the two.

Indicators of a genuine clerical error

A taxpayer’s case becomes stronger where:

•  The amount is actually disclosed in the return;

•  The underlying transaction is recorded in the books;

•  The computation supports the taxpayer’s explanation;

•  There is no corresponding understatement of taxable income;

•  Other schedules corroborate the amount;

•  The mistake is capable of being corrected without changing the substantive tax position; and

•  There is no evidence of an intention to conceal income.

Indicators requiring greater scrutiny

The position would be entirely different where:

•  The amount is not disclosed anywhere;

•  Books do not support the transaction;

•  The taxpayer obtains a tax benefit because of the error;

•  The explanation is an afterthought;

•  Supporting records contradict the return; or

•  There is evidence suggesting deliberate misreporting.
Therefore, the ruling should not be read as saying:
“Any wrong column is harmless.”
The correct principle is:
A genuine clerical error having no substantive impact should not be converted into taxable income merely because the wrong column was selected.

CBDT Circular No. 14 of 1955 also came into the picture

The assessee relied upon CBDT Circular No. 14 (XL-35) of 1955 dated 11 April 1955.
The circular has long embodied the principle that tax authorities should assist taxpayers in obtaining relief legitimately available under the law and should not take advantage of an innocent mistake or omission.
The assessee relied upon this principle to argue that the Department should not exploit an inadvertent reporting error when the underlying computation was correct.
The Tribunal’s reasoning is consistent with that broader philosophy.

The danger of “form over substance”

Imagine two taxpayers.
Taxpayer A correctly enters ₹23.33 crore in Column 3B.
No addition is made.
Taxpayer B enters the exact same ₹23.33 crore in Column 4(e), but the Department adds the entire amount as income.
The economic transaction is identical.
The difference is only the column selected.
If the underlying computation remains unchanged, treating Taxpayer B as having ₹23.33 crore additional income would create an outcome based entirely on form rather than substance.
The Tribunal refused to endorse such an approach.

What should return preparers learn?

The judgment does not mean that column-level accuracy is unimportant.
Quite the opposite.
It demonstrates how expensive a simple data-entry error can become.
A return preparer should therefore perform a final review not merely of:
“What is the taxable income?”
but also:
“Does every figure appear in the correct schedule and column?”
A useful pre-filing review can include:

•  Schedule BP reconciliation;

•  ICDS adjustments;

•  Form 3CD reconciliation;

•  Tax audit report versus ITR;

•  Profit and loss account versus computation;

•  Part A-OI cross-check;

•  Carry-forward losses;

•  MAT/AMT schedules, wherever applicable;

•  Major additions and deductions; and

•  Significant year-on-year movements.
The objective is simple:
Catch the clerical error before the Department does.

Why this matters especially for large businesses

For companies with complex tax computations, one figure can appear in several places:

•  Financial statements;

•  Tax audit report;

•  ICDS workings;

•  Tax computation;

•  ITR schedules;

•  Supporting annexures.
A mismatch between any two of these can trigger scrutiny.
The larger the number, the greater the likelihood that the mismatch will attract attention.
Therefore, a return reconciliation sheet prepared before filing can be extremely valuable.

The Tribunal did not give a licence to make mistakes

This is an important caution.
The decision should not be interpreted as:
“Don’t worry about ITR columns; ITAT will fix everything.”
That would be a dangerous lesson.
The taxpayer had to go through assessment, first appeal and Tribunal proceedings to establish what should have been obvious from the computation.
Litigation itself has a cost – professional time, management time and uncertainty.
The best tax litigation is often the litigation that never becomes necessary.

The larger lesson

Tax administration is increasingly becoming data-driven.
That makes accurate return preparation more important than ever.
But data-driven assessment must also remain context-driven.
An incorrect column entry may be a red flag.
It is not automatically evidence of hidden income.
The Department must examine whether the mistake has actually resulted in:
under-reporting of income, tax evasion or an unintended tax benefit.
If the amount is already disclosed and the error has no impact on taxable income, an addition of the entire amount can produce an artificial tax liability.
That is precisely what the Bangalore ITAT found in this case.

The message is simple

A wrong column is an error. It does not become income merely because the number is large.
The ₹23.33 crore figure was not discovered as hidden cash.
It was not an undisclosed transaction.
It was not an unexplained credit.
It was already present in the return – only in the wrong place.
The Tribunal therefore treated the mistake for what it was:
a clerical error, not concealed income.
For taxpayers, the message is reassuring.
For return preparers, the message is cautionary:
check every column.
Because while a genuine clerical error should not become taxable income, explaining a ₹23.33 crore clerical error before the tax authorities is certainly more stressful than correcting it before pressing “Submit Return.”

Case: Castles Vista (P.) Ltd. v. Assistant Commissioner of Income-tax, Central
ITAT: Bangalore Bench
ITA No.: 1621 (Bang.) of 2025
Assessment Year: 2022-23

Key issue: ₹23,33,32,982 ICDS adjustment entered in the wrong ITR column

Decision: Addition deleted; Tribunal held the error to be clerical and found no impact on taxable income.

Disclaimer: This article is for general information and educational purposes. Whether an incorrect entry constitutes a mere clerical error or has substantive tax consequences depends upon the complete facts, computation and supporting records of the particular case.

 

The copy of the order is as under:

ITA No. 1621-Bang-2025