Consistent accounting treatment for project liabilities, revenue recognition, and software maintenance expenses was upheld as deductible and revenue in nature.

A consistent and duly supported accounting method was accepted for project-related liabilities and contract revenue recognition. Provision for costs incurred on completed contracts was allowed as a business deduction because it reflected identified liabilities, was based on project-wise technical estimates, and conformed to accounting standards. Provision for expected cost overruns on incomplete contracts was also allowed as a reasonably estimated probable loss. Additions linked only to higher progress billings were vacated because the percentage completion method had been consistently applied and accepted in earlier years. Software maintenance expenses were held revenue in nature, as they represented recurring upkeep and did not create an enduring capital asset.

---

---

Issues: (i) Whether provision for costs incurred on completed contracts was allowable as a business deduction; (ii) whether provision for cost overruns on incomplete contracts, being expected project loss, was allowable; (iii) whether addition of amounts linked to percentage completion accounting and progress billings was sustainable; and (iv) whether software maintenance expenses were revenue expenditure or capital expenditure.

Issue (i): Whether provision for costs incurred on completed contracts was allowable as a business deduction.

Analysis: The provision related to identified project liabilities arising in the course of execution of complex engineering contracts, where revenue was recognized before final acceptance of the plant and further expenditure was still required to be incurred. The assessee had followed a consistent method of accounting and supported the estimate by project-wise technical evaluation. The provision was also consistent with the recognition of known liabilities on a best-estimate basis and with the applicable accounting standards. The recurring nature of the issue and the prior order of the Tribunal in the assessee's own case for the immediately preceding year supported allowance of the claim.

Conclusion: The disallowance was deleted and the claim was allowed in favour of the assessee.

Issue (ii): Whether provision for cost overruns on incomplete contracts, being expected project loss, was allowable.

Analysis: The provision represented an anticipated loss on contracts where projected cost was expected to exceed contract revenue. The assessee had made project-wise estimations on the basis of expected future costs and had maintained the same accounting method in earlier years. The Tribunal treated the claim as falling within the settled principle that probable and reasonably estimated losses arising from ongoing contracts may be recognized when supported by material and consistent accounting treatment. The issue was also covered by the Tribunal's decision in the assessee's own case for the immediately preceding year.

Conclusion: The disallowance was deleted and the claim was allowed in favour of the assessee.

Issue (iii): Whether addition of amounts linked to percentage completion accounting and progress billings was sustainable.

Analysis: The assessee followed a consistent percentage of completion method under which revenue was recognized by reference to stage of completion rather than mere progress billings. The difference between billing and recognized revenue was treated appropriately as advance received or amount receivable depending on the position of the contract. No revenue leakage or change in accounting method was established, and the method had been accepted in earlier years. The Tribunal found that the addition was made only because billings exceeded revenue recognized, which by itself was insufficient to disturb the consistent method of accounting.

Conclusion: The addition was vacated and the issue was decided in favour of the assessee.

Issue (iv): Whether software maintenance expenses were revenue expenditure or capital expenditure.

Analysis: The expenditure was in the nature of annual maintenance, rectification, modification, and upgrading of software and did not result in acquisition of an enduring capital asset. The issue was already covered by the Tribunal's earlier decision in the assessee's own case, and the assessee was entitled to claim the expenditure as a recurring business outlay.

Conclusion: The disallowance was deleted and the expenditure was held to be revenue in nature in favour of the assessee.

Final Conclusion: The additions and disallowances made in assessment were substantially reversed, and the assessee succeeded on all substantive issues decided in the appeal.

Ratio Decidendi: A consistent and duly supported method of accounting that recognizes probable project-related liabilities and revenue on a reasonable estimate cannot be displaced merely because the amounts are contingent or because progress billings differ from revenue recognized.

---