Facts of the Case
The present matter arose from two appeals
preferred by the Revenue challenging the order dated 12.04.2017 passed by the
Income Tax Appellate Tribunal (ITAT) concerning the block period from
01.04.1996 to 09.05.2002. The dispute centered on the validity of penalty
proceedings initiated by the Assessing Officer under Section 158BFA(3)(c) of
the Income Tax Act, 1961.
The ITAT held that the penalty order was barred by
limitation as it was passed beyond six months from the end of the month in
which the appellate order of the Tribunal was first received by the
Commissioner of Income Tax (Judicial).
Issues Involved
- Whether
limitation under Section 158BFA(3)(c) commences from the date the ITAT
order is received by the Commissioner of Income Tax (Judicial) or by the
concerned Commissioner?
- Whether
the interpretation laid down in earlier judicial precedent regarding
receipt of appellate orders applies equally to penalty proceedings under
Section 158BFA(3)(c)?
- Whether
such judicial interpretation would apply retrospectively or prospectively?
Petitioner’s Arguments (Revenue’s Contentions)
The Revenue contended that:
- The
earlier decision in Odeon Builders Pvt. Ltd. vs Principal Commissioner
of Income Tax was rendered in the context of Section 260A and
therefore could not automatically govern Section 158BFA(3)(c).
- Although
the wording in both provisions was similar, the legal context differed.
- At
the time the Assessing Officer initiated penalty proceedings, the judgment
in Odeon Builders had not yet been pronounced. Therefore, that decision
should apply only prospectively and not affect already initiated
proceedings.
Respondent’s Arguments (Assessee’s Contentions)
The respondent supported the ITAT’s findings and
argued that:
- The
statutory language under Section 158BFA(3)(c) is materially identical to
Section 260A.
- Once
the Tribunal’s order is received by any competent Commissioner, including
the Commissioner (Judicial), the statutory limitation begins to run.
- The
penalty order having been passed beyond the prescribed period was legally
unsustainable.
Court Findings / Order
The Delhi High Court dismissed the Revenue’s
appeals and upheld the ITAT’s order. The Court held that:
- The
expression used in Section 158BFA(3)(c), namely receipt by the Principal
Chief Commissioner, Chief Commissioner, Principal Commissioner, or
Commissioner, is identical to Section 260A.
- The
receipt of the ITAT order by the Commissioner (Judicial) constitutes valid
receipt for computing limitation.
- The
limitation period of six months starts from such receipt and not from the
date of receipt by the “concerned” Commissioner.
- Judicial
interpretation in Odeon Builders declared the law as it always existed;
therefore, the principle applies retrospectively to pending matters.
- No
substantial question of law arose for consideration.
Important Clarification
This judgment clarifies that for the purpose of
limitation under Section 158BFA(3)(c), the relevant trigger point is the first
official receipt of the ITAT order by any authorized Commissioner, including
the Commissioner (Judicial), and not necessarily the jurisdictional or
concerned Commissioner.
Further, judicial interpretation of statutory
provisions is declaratory in nature and ordinarily retrospective unless
specifically stated otherwise.
Sections Involved
- Section
158BFA(3)(c), Income Tax Act, 1961 –
Time limit for passing penalty order in block assessment proceedings
- Section 260A, Income Tax Act, 1961 – Appeal to High Court (interpretative relevance)
Link to download the order -
https://delhihighcourt.nic.in/app/case_number_pdf/2017:DHC:8948-DB/SMD20092017ITA8222017_101618.pdf
Disclaimer
This content is shared strictly for general information and knowledge purposes only. Readers should independently verify the information from reliable sources. It is not intended to provide legal, professional, or advisory guidance. The author and the organisation disclaim all liability arising from the use of this content. The material has been prepared with the assistance of AI tools.
0 Comments
Leave a Comment