Developer Overheads Deductible Without Project Revenue: Delhi HC Upholds ₹8.73 Crore Relief
The Delhi High Court has held that a real estate developer's overheads do not become non-deductible merely because no project revenue was recognised in the year. In ITA 319/2026, Pr. Commissioner of Income Tax, Central, Gurugram v. M/s Experion Developers Pvt. Ltd., decided on 18 November 2026, a Division Bench of Justice Subramonium Prasad and Justice Renu Bhatnagar dismissed the Revenue's appeal for Assessment Year 2012-13 and left intact the ITAT's deletion of an ad hoc disallowance of ₹8,73,10,314.
The question of developer overheads deductible without project revenue comes up in almost every scrutiny of a group in the early years of a township or housing project, when the percentage of completion method (POCM) has not yet been triggered and the profit and loss account shows nil revenue from operations. The ruling does not settle that question for every developer, but it does tell assessing officers that a flat percentage disallowance, made without rejecting the books, will struggle to survive appeal.
How the ₹9.70 crore claim reached the High Court
Experion Developers is engaged in developing townships, housing and commercial premises. For AY 2012-13 it filed its return on 29 September 2012 declaring a loss of ₹7,82,95,075. The return was picked for scrutiny, and the assessment under section 143(3) of the Income-tax Act, 1961 was completed on 19 March 2015 at a total income of ₹90,15,239.
The gap between the two figures is the disallowance. The company had claimed ₹9,70,11,460 as revenue expenditure. The Assessing Officer allowed 10% and disallowed the remaining 90%, holding that the costs were directly or indirectly connected with projects under development and should have been carried as project cost or work-in-progress, since no project revenue had been recognised that year. The arithmetic runs as follows: returned loss of ₹7,82,95,075 plus the disallowance of ₹8,73,10,314 gives the assessed income of ₹90,15,239.
The CIT(A) confirmed the addition on 2 January 2017. The ITAT reversed it on 31 July 2025 in ITA No. 1367/Del/2017, and the Revenue then appealed under section 260A.
What the ITAT found on the developer's accounting
The Tribunal recorded that the company had allocated costs attributable to its projects to inventory, following AS-7 and the ICAI Guidance Note on real estate transactions, and had claimed only the balance as revenue expenditure. The Assessing Officer had not rejected the books of account under section 145(3).
Relying on the Supreme Court's decision in Virtual Soft Systems Ltd. v. ACIT (404 ITR 409), the ITAT held that earning revenue is not a condition precedent for a deduction under section 37 once the business is set up and the expense is incurred for business. It also followed the Delhi Bench decision in AB Multiplex Pvt. Ltd. (ITA 739/Del/2014), where administrative expenses not attributable to a project were allowed.
Two further findings carried weight. First, the AO's own allowance of 10% showed that he accepted the expenses were incurred for business, which made the 90% cut, in the Tribunal's words, "totally arbitrary in nature". Second, the company had followed the same method from AY 2011-12. The Revenue had accepted that method for AY 2011-12 (except finance cost) and from AY 2016-17 onwards, disputing only the non-project costs for AY 2012-13 to 2015-16. Counsel also placed on record how project income had been offered to tax under POCM up to AY 2022-23, with some of those years assessed under section 143(3) accepting the claim.
The Revenue's case: no POCM revenue, so capitalise
Before the High Court, the Revenue argued that the AS-7 threshold for recognising revenue had not been crossed and the company showed nil revenue from operations, so no activity in the year could yield receipts. On that footing, costs linked to projects had to sit in work-in-progress. It also said the company had not proved the revenue character of the expenses or substantiated its split between project and non-project costs, and that the 10% allowance merely reflected the difficulty of verifying the split and covered statutory costs.
Citing Tuticorin Alkali Chemicals v. CIT, the Revenue stressed that genuineness of an expense and the year of its deduction are separate questions, and that unallocated expenses are not automatically allowable. It framed six proposed questions of law, including whether a developer can defer income under POCM while deducting overheads in the same period.
The company's answer was that the expenses had been classified under 27 heads, the AO had not pointed to a single head as wrongly claimed, general administrative and selling costs are excluded from project cost under AS-7 and the Guidance Note, and no law requires them to be pushed into work-in-progress. It added that the disallowed amount had never been allowed in any later year, so restoring the addition would deny a genuine business expense permanently rather than merely shift its timing.
Why the High Court refused to frame a question of law
The Bench treated the case as one about the reach of section 260A. Relying on CIT v. Hamdard National Foundation and the tests in Chunilal V. Mehta and Santosh Hazari, it held that an appeal lies only on a substantial question of law, that such a question must be debatable and material to the result, and that the ITAT's findings of fact cannot be reopened because another view of the evidence is possible.
On the core issue, the court said allowability depends on the nature of each expense: whether it is attributable to a project or incurred wholly and exclusively for the business generally. The ITAT had examined the accounting method, the work-in-progress allocation, the business purpose of the expenses and the accounting guidance, and its conclusion rested on the record. The Revenue had not shown any misreading of the Act or of accounting principles. On the POCM question, the court noted that the Guidance Note itself separates costs tied to specific projects from costs attributable to project activity in general, and the department had not demonstrated an error in that distinction. The appeal was dismissed in paragraph 28.
Two limits the court placed on the ruling
The judgment is not an unqualified win for the argument that consistency and a partial allowance settle the matter. In paragraph 24 the court agreed with the Revenue that an AO's partial allowance cannot constitute a conclusive admission that the whole expenditure is deductible. It also held that the rule of consistency in the method of accounting cannot override the provisions of the Act.
The relief survived because the ITAT had gone further and recorded factual findings on what the expenses were and how they had been allocated. A developer that relies only on past acceptance of its method, or on the AO's own token allowance, without a documented head-wise split, would not get the same protection from this decision.
What developers and tax auditors should keep on file
For developers still in the pre-revenue phase of a project, the ruling points to the records that decided this case. The allocation between project cost and period cost should follow AS-7 and the Guidance Note and be documented head by head, so that any disallowance has to engage with specific items. The method should be applied the same way every year. Where an AO proposes to recast costs into work-in-progress, the first point to test is whether the books have been rejected under section 145(3) at all; in Experion they had not.
For departmental appeals on similar facts, the decision also shows how hard it is to bring a POCM timing dispute to the High Court once the Tribunal has examined the allocation: the court treated it as a question of fact, not of law. The question of developer overheads deductible without project revenue will now turn largely on the quality of the cost allocation placed before the ITAT.
Official source: View the official source document
