Just a moment...
Convert scanned orders, printed notices, PDFs and images into clean, searchable, editable text within seconds. Starting at 2 Credits/page
Try Now →Press 'Enter' to add multiple search terms. Rules for Better Search
Use comma for multiple locations.
---------------- For section wise search only -----------------
Accuracy Level ~ 90%
Press 'Enter' after typing page number.
Press 'Enter' after typing page number.
No Folders have been created
Are you sure you want to delete "My most important" ?
NOTE:
Press 'Enter' after typing page number.
Press 'Enter' after typing page number.
Don't have an account? Register Here
Press 'Enter' after typing page number.
ISSUES PRESENTED AND CONSIDERED
1. Whether the relevant date for computing limitation under Section 275(1)(c) for imposition of penalty under Section 271D is the date on which the Assessing Officer (AO) records satisfaction/findings of violation (e.g., in the assessment order) or the date on which the competent authority (Joint/Addl. Commissioner) issues a show-cause notice.
2. Whether an assessment order recording AO's satisfaction concerning contravention of Section 269SS (after prior approval under the statute where required) constitutes initiation of "action for imposition of penalty" for the purposes of Section 275(1)(c).
3. Whether approval of a draft assessment order by the competent supervisory authority under the statutory provision (e.g., section requiring prior approval for certain assessment orders) is merely administrative/directory or has legal/mandatory effect binding on limitation computation and the validity of subsequent penalty proceedings.
4. Whether delay in inter-office communication (from AO to competent authority) can be relied upon by Revenue to extend limitation under Section 275(1)(c) in respect of penalties under Sections 271D/271E.
ISSUE-WISE DETAILED ANALYSIS
Issue 1 - Date for computing limitation under Section 275(1)(c): AO satisfaction vs. notice by competent authority
Legal framework: Section 275(1)(c) prescribes limitation for penalty orders in "other cases" as the expiry of the financial year in which the proceedings in the course of which action for imposition of penalty has been initiated are completed, or six months from the end of the month in which action for imposition of penalty is initiated, whichever is later. CBDT Circular No.10/2016 applies Section 275(1)(c) to penalties under Sections 271D/271E.
Precedent treatment: The Court relied on a consistent line of authorities (including the Supreme Court and several High Courts and Tribunals) holding that recording of satisfaction by the AO is a mandatory, condition-precedent step to initiate penalty proceedings under Sections 271D/271E and that limitation runs from that initiation. Decisions treated as followed include jurisprudence holding the AO's satisfaction/assessment order as the triggering event for limitation, and cases holding penalty orders invalid where passed after expiry of limitation measured from AO's recorded satisfaction.
Interpretation and reasoning: The Court reasoned that "action for imposition of penalty" is a sequence of steps whose decisive stage is the AO's recording of satisfaction/finding of fact regarding contravention. Since recording satisfaction is mandatory before penalty proceedings can validly commence, that recording date must be the date of initiation for Section 275(1)(c) calculation. Reliance on the competent authority's later issuance of notice would permit the executive to manipulate limitation by delaying notice issuance and thereby frustrate statutory limits.
Ratio vs. Obiter: Ratio - limitation under Section 275(1)(c) is to be reckoned from the date of the AO's recorded satisfaction forming the basis of penalty initiation; Obiter - policy observations on Article 14 and consequences of allowing discretionary delay by supervisory officers.
Conclusion: The date of AO's recorded satisfaction (here, the assessment order date) is the date on which "action for imposition of penalty is considered as initiated" for Section 275(1)(c).
Issue 2 - Effect of AO recording satisfaction in an assessment order approved by competent authority
Legal framework: Statutory provision requiring prior approval for certain assessment orders (e.g., where prior approval of Additional Commissioner/Joint Commissioner is mandatory) and statutory scheme for initiation and imposition of penalty (Sections 269SS, 271D, 274, 275).
Precedent treatment: Courts have held that satisfaction recorded by the AO in the course of assessment is a pre-requisite for valid penalty proceedings (cited authorities). The Court also relied on precedents recognizing that initiation by AO is permissible even where imposition is vested in a higher authority.
Interpretation and reasoning: Where the AO's assessment order containing satisfaction is issued after obtaining the requisite statutory prior approval, that satisfaction cannot be treated as merely administrative or non-binding. The statutory approval transforms the assessment order (including the satisfaction) into a valid, binding exercise triggering limitation. Disregarding an AO's recorded satisfaction in such context would render many penalty proceedings vulnerable and allow supervisory authorities to defeat statutory limitation.
Ratio vs. Obiter: Ratio - an AO's satisfaction recorded in an assessment order which has been approved as statutorily required constitutes initiation of penalty proceedings; Obiter - discussion on the interplay between administrative directions and quasi-judicial functions where approval is statutorily mandated.
Conclusion: The AO's satisfaction recorded in an assessment order, when issued with required statutory approval, constitutes initiation of penalty proceedings for limitation purposes and is binding for that purpose.
Issue 3 - Whether delay in AO's communication to competent authority or timing of show-cause notice can extend limitation
Legal framework: Absence of any statutory prescription tying limitation to the date of internal communication; established principles of Article 14 and rule-of-law considerations against arbitrary extension of statutory time limits.
Precedent treatment: Decisions cited demonstrate judicial reluctance to permit internal administrative timing or supervisory discretion to determine statutory limitation, and support measuring limitation from AO's recorded satisfaction.
Interpretation and reasoning: Allowing the date of internal communication or the date when the competent authority first issues a show-cause notice to determine limitation would confer unbounded discretion on Revenue and permit arbitrary extension of limitation periods. The assessment order publicly puts the assessee on notice; internal communications are often informal and not accessible to assessee, and hence cannot be operative to extend limitation.
Ratio vs. Obiter: Ratio - internal delay or discretionary timing of issuance of notice by competent authority cannot validly extend limitation under Section 275(1)(c); Obiter - examples illustrating anomalous outcomes if Revenue's argument were accepted.
Conclusion: Delay in internal communication or timing of the competent authority's notice does not extend limitation; limitation is computed from the date of AO's recorded satisfaction.
Final Conclusion and Disposition
Because the AO recorded satisfaction in the assessment order on the earlier date, and that order had the requisite statutory approval, the initiation date for penalty proceedings under Section 271D was that assessment-order date. Limitation under Section 275(1)(c) therefore expired prior to the date on which the competent authority passed the penalty order. The impugned penalty order was held time-barred and quashed. The Court followed controlling precedents to reach this conclusion and dismissed Revenue's appeal as academic after allowing the assessee's cross-objection on limitation grounds.