Section 68 addition deleted where software error caused false cash difference, regular books accepted as accurate

The ITAT Bangalore allowed the assessee's appeal and deleted the addition made u/s 68 for unexplained cash credit. The AO had treated the difference between cash on hand as on 8.11.2016 and opening cash balance on 9.11.2016, as reflected in two cash statements generated from custom-made software, as unexplained. The Tribunal noted that the assessee's regular books of account, produced before both lower authorities, showed no such discrepancy and were not found faulty. It held that an error in software-generated statements alone could not justify addition u/s 68.

---

---

ISSUES PRESENTED AND CONSIDERED

1. Whether an addition under section 68 as "unexplained cash credit" based on a difference between closing cash on one day and opening cash on the next day shown in a software-generated cash statement is sustainable where the regular books of account produced before the assessing officer show no such discrepancy.

2. Whether discrepancies arising from printouts or extracts of a custom-made accounting software, when reconciled by production of complete regular books of account, can justify treating the unexplained amount as income.

ISSUE-WISE DETAILED ANALYSIS

Issue 1 - Legal framework

Section 68 principles: additions as unexplained cash credits require that the assessee fails to satisfactorily account for the source of an amount claimed as cash balance/receipt. Assessment must be founded on irregularity or inadequacy of regular books or failure to explain the entry.

Issue 1 - Precedent Treatment

No prior judicial authorities or statutory interpretations were cited or relied upon by the authorities or the Tribunal in the judgment; therefore no precedent was followed, distinguished, or overruled in this decision.

Issue 1 - Interpretation and reasoning

The Tribunal examined the material before the assessing officer and the appellate authority: (a) initial software-generated cash statements produced during assessment showing a mismatch between closing cash as on 8 November 2016 and opening cash as on 9 November 2016; (b) the assessee's explanation that the mismatch arose from printouts/extracts from a custom-made accounting software affected by option-selection and inherent software issues; and (c) the production, subsequently, of complete regular books of account (cashbook and other books) before the assessing officer and the CIT(A) which did not exhibit any discrepancy in cash balances.

The Tribunal accepted that the assessing officer noted the absence of discrepancy in the regular cashbook produced but nonetheless made the addition relying upon the earlier software-produced statement. The Tribunal held that assessment in income tax is to be made on the basis of regular books of account; an erroneous or inconsistent printout from custom software, by itself, does not convert a properly recorded balance into an unexplained credit.

Issue 1 - Ratio vs. Obiter

Ratio: Where regular books of account, maintained in the ordinary course and produced before the revenue authorities, show no discrepancy in cash balances, an addition under section 68 predicated solely on an inconsistent software-generated printout is not sustainable.

Obiter: Observations about the practical causes of software inconsistency (option-selection errors, inherent difficulties in a custom-built package) are explanatory and non-binding on other facts; the Tribunal did not lay down a general rule on the evidentiary weight of software printouts beyond the facts of this case.

Issue 1 - Conclusion

The addition of Rs. 811,250 as unexplained cash credit under section 68, founded on the discrepancy between two software-generated cash statements but contradicted by the regular books of account produced before the authorities, was held to be not sustainable and was deleted. The Tribunal directed the assessing officer to delete the addition.

Issue 2 - Legal framework

Evidence and burden: The assessing officer must examine books and materials on record; where assessee produces books properly maintained that satisfactorily explain entries, the revenue cannot treat an isolated inconsistent extract as establishing unexplained income without further contrary proof.

Issue 2 - Precedent Treatment

None applied; the Tribunal relied on principles of accounting evidence and the primacy of regular books rather than judicial precedents.

Issue 2 - Interpretation and reasoning

The Tribunal emphasised that the existence of two different statements emanating from the same custom software - one showing a discrepancy and another (the regular cashbook) showing no discrepancy - warranted acceptance of the regular books when produced in full. The Tribunal found no material to impugn the regular books and accepted the assessee's explanation regarding the cause of the inconsistent printouts. The Tribunal rejected the revenue's reliance on the earlier inconsistent statement absent additional material demonstrating that the regular books were false, fabricated, or unreliable.

Issue 2 - Ratio vs. Obiter

Ratio: Production of complete regular books of account that reconcile and explain the relevant balances rebuts additions based solely on inconsistent software extracts; such extracts cannot, without more, form the basis for invoking section 68.

Obiter: The Tribunal's acceptance of software-origin explanations (option-selection errors, inherent software defects) is fact-specific and not a general endorsement of all software outputs as unreliable; revenue may still investigate where independent corroboration or suspicion of manipulation exists.

Issue 2 - Conclusion

Discrepancies caused by software-generated statements, when contradicted by regular books of account duly produced and unexplained otherwise, do not justify treating amounts as unexplained cash credits. The Tribunal allowed the appeal on this ground and set aside the addition.

Cross-reference

Issues 1 and 2 are interrelated: the core legal outcome derives from the evidentiary primacy of regular books over inconsistent software extracts and the requirement that the revenue prove that sums are unexplained despite production of regular books before making additions under section 68.

---