the essay of 9 October 2024 · the untouched capture
Rendered as it looked. Links and images are disabled in this view; the file itself is untouched.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <title>Untitled Document</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> </head> <body> <p align="left"><strong><font color="#663399" size="2" face="Verdana, Arial, Helvetica, sans-serif">OCTOBER 09, 2024</font></strong></p> <p align="center"><font color="#FF6633" size="2" face="Verdana, Arial, Helvetica, sans-serif"><strong>Read <em>"AND" </em>as<em> "OR" </em>or<em> "OR" </em>as <em>"AND"</em></strong></font></p> <p align="center"><strong><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><u>Vijay Kumar</u></font></strong></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><strong>IS </strong>the Supreme Court right? Many people asked me immediately after the recent judgement of the top court in the famous <em>SAFARI RETREATS case -<strong> <a href="https://taxindiaonline.com/RC2/caseLawDet.php?QoPmnXyZ=MTgzNDE4" target="_blank">2024-TIOL-101-SC-GST</a></strong></em>, which set the tax net on fire with almost everybody expressing an opinion immediately after the judgement was made public and some even before. There is no question of the Supreme Court being wrong; it is always right, because it is final - of course subject to acceptance by the government. This eminence is shared by the GST officers also - they are always right. If you dare to think they are not right, you can start from the Inspector and go up to the Supreme Court and get a judgement that they were not right and then they will make a retrospective law that they were always deemed to be right. I am not discussing the complex judgement, but I am fascinated by a question that the Supreme Court had to deal with in this case. </font></p> <blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"style="background-color:#F3DBCF">Whether the definition of "<font color="#FF0000"><em>plant and machinery</em></font><em>"</em> in the explanation to Section 17 of the CGST Act applies to the expression <em>"<font color="#FF0000">plant or machinery</font>"</em> used in clause (d) of sub-section (5) of Section 17? </font></p> </blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">At the outset, the Supreme Court made an interesting observation: </font></p> <blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"style="background-color:#F3DBCF">Very detailed submissions have been made by the parties. We find that the submissions made by the learned counsel for the assessees and the intervenors are repetitive. There are a large number of decisions relied upon, whether relevant or irrelevant. <font color="#FF0000">Brevity is the hallmark of good advocacy</font>. It would be ideal if parties on one side file joint written submissions. The Judges and lawyers are humans. Sometimes, bulky compilations and submissions can be counterproductive. </font></p> </blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Assessees submitted that: </font></p> <blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">a) Clause (d) exempts <em>"plant or machinery"</em> from blocked credit, which is distinct from the expression <em>"plant and machinery"</em> used in Clause (c). </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">b) The expression <em>"plant and machinery"</em> has been used at least ten times in Chapters V and VI of the CGST Act, and the expression <em>"plant or machinery" </em>occurs only once in Section 17(5)(d). Therefore, the intention of the legislature to treat the expression <em>"plant or machinery"</em> differently from the expression<em> "plant and machinery" </em>is apparent. </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">c) In the model GST law, which the GST Council Secretariat circulated in November 2016 for inviting suggestions and comments, the expression <em>"plant and machinery"</em> was used both in clauses (c) and (d) of Section 17(5). However, while enacting the law, the legislature has used the expression <em>"plant and machinery" </em>in clause (c) and <em>"plant or machinery"</em> in clause (d) of Section 17(5). Therefore, the intention of the legislature cannot be brushed aside by contending that the use of the word <em>"or"</em> in Section 17(5)(d) is a mistake of the legislature. </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">d) The expression<em> "plant or machinery"</em> has not been defined under the CGST Act. The definition of <em>"plant and machinery"</em> provided in the explanation to Section 17 will not apply to the expression <em>"plant or machinery"</em>. Since the legislature has intentionally used two different expressions in clauses (c) and (d) of Section 17(5), different meanings will have to be assigned to these expressions. </font></p> </blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Revenue opposed this contention by submitting that <font color="#FF0000">'or'</font> must be read as<font color="#FF0000"> 'and'</font> stating it to be the <font color="#FF0000">mistake of the legislature</font>. </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The Additional Solicitor General submitted: </font></p> <blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">a) The expression <em>"plant or machinery" </em>must be read as <em>"plant and machinery"</em>. It is not uncommon to read <em>"and" </em>as<em> "or" </em>or<em> "or" </em>as<em> "and"</em>. </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">b) He accepted that the expression<em> "plant and machinery" </em>occurs ten times in Chapter V and Chapter VI and the expression <em>"plant or machinery"</em> occurs only once in Section 17(5)(d). </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">c) For identifying what would constitute plant and machinery/plant or machinery, it is not necessary to refer to decisions under the Income Tax Act as the same have no relevance. There is no concept of ITC in the Income Tax Act. The scheme of the Act is completely different. </font></p> </blockquote> <p align="justify"><font color="#009900" size="2" face="Verdana, Arial, Helvetica, sans-serif">Supreme Court considered the issue </font></p> <blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"style="background-color:#F3DBCF">Whether the definition of "<em>plant and machinery" </em>in the explanation appended to Section 17 of the CGST Act applies to the expression <em>"plant or machinery"</em> used in clause (d) of sub-section (5) of Section 17? </font></p> </blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The Court observed: </font></p> <blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">- The explanation defines the meaning of the expression <em>"plant and machinery"</em>. However, the expression <em>"plant or machinery"</em> has not been defined under the CGST Act </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">- The question is whether the explanation that lays down the meaning of the expression<em> "plant and machinery"</em> in Section 17 will apply to the expression<em> "plant or machinery" </em>used in Section 17 (5)(d). </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">- Learned ASG himself accepted that the expression<em> "plant and machinery" </em>appears at ten different places in Chapters V (Input Tax Credit) and VI (Tax Invoice, Credit and Debit Notes) of the CGST Act. According to him, the expression <em>"plant or machinery"</em> appears only in clause (d) of Section 17(5). </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">- His submission is that the use of the word "or" in clause (d) is a <font color="#FF0000">mistake of the legislature</font>. </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">- To counter this, it was submitted that in the Model GST Law, which the GST Council Secretariat circulated in November 2016 to invite suggestions and comments from the public, the expression 'plant and machinery' was used in clauses (c) and (d). However, while enacting the CGST Act, the legislature has consciously chosen to use the expression <em>"plant or machinery"</em> only in clause (d). </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">- The impugned judgment in the main Civil Appeal is more than five years old. The writ petition in which the impugned decision was rendered is a six-year-old writ petition. If it was a drafting mistake, as suggested by learned ASG, the legislature could have stepped in to correct it. However, that was not done. In such circumstances, it must be inferred that the legislature has intentionally used the expression<em> "plant or machinery"</em> in clause (d) as distinguished from the expression <em>"plant and machinery"</em>, which has been used in several places. </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">- As the expression <em>"plant or machinery"</em> appears to be intentionally incorporated, it is not possible to accept the contention of the learned ASG that the word "or" in clause (d) should be read as "and". </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">- If the legislature intended to give the expression <em>"plant or machinery" </em>the same meaning as "plant and machinery" as defined in the explanation, the legislature would not have specifically used the expression "plant or machinery" in Section 17(5)(d). The legislature has made this distinction consciously. Therefore, the expression "plant and machinery" and "plant or machinery" cannot be given the same meaning. </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">- Therefore, if the expression "plant or machinery" is given the same meaning as the expression<em> "plant and machinery" </em>as per the definition contained in the explanation to Section 17, we will be doing violence to the words used in the statute. </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">- While interpreting taxing statutes, it is not a function of the Court to supply the deficiencies. </font></p> </blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The Supreme Court <font color="#FF0000">summarised the principles governing the interpretation of the taxation statutes:</font> </font></p> <blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">a) A taxing statute must be read as it is with no additions and no subtractions on the grounds of legislative intendment or otherwise; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">b) If the language of a taxing provision is plain, the consequence of giving effect to it may lead to some absurd result is not a factor to be considered when interpreting the provisions. It is for the legislature to step in and remove the absurdity; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">c) While dealing with a taxing provision, the principle of strict interpretation should be applied; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">d) If two interpretations of a statutory provision are possible, the Court ordinarily would interpret the provision in favour of a taxpayer and against the revenue; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">e) In interpreting a taxing statute, equitable considerations are entirely out of place; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">f) A taxing provision cannot be interpreted on any presumption or assumption; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">g) A taxing statute has to be interpreted in the light of what is clearly expressed. The Court cannot imply anything which is not expressed. The Court cannot import provisions in the statute to supply any deficiency; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">h) </font><font size="2" face="Verdana, Arial, Helvetica, sans-serif"style="background-color:#F3DBCF">There is nothing unjust in the taxpayer escaping if the letter of the law fails to catch him on account of the legislature's failure to express itself clearly; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">i) If literal interpretation is manifestly unjust, which produces a result not intended by the legislature, only in such a case can the Court modify the language; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">j) Equity and taxation are strangers. But if construction results in equity rather than injustice, such construction should be preferred; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">k) It is not a function of the Court in the fiscal arena to compel the Parliament to go further and do more; </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">l) When a word used in a taxing statute is to be construed and has not been specifically defined, it should not be interpreted in accordance with its definition in another statute that does not deal with a cognate subject. It should be understood in its commercial sense. Unless defined in the statute itself, the words and expressions in a taxing statute have to be construed in the sense in which the persons dealing with them understand, that is, as per the trade understanding, commercial and technical practice and usage. </font></p> </blockquote> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">What is the <font color="#FF0000">mistake of the legislature?</font> </font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The other day, I heard a very senior Revenue Officer telling a very senior Law Officer that he had drafted some provisions of the GST Act and rather very well. This is how laws are made. Some officers in the Revenue Department draft the laws and they get passed in Parliament with or without discussions and become laws of the land and for every error, we have to look at the intent of the legislature. Can you imagine both houses of Parliament detecting the error of "or" instead of "and"? But Parliament has to own up as it has passed the law. It becomes the <font color="#FF0000">mistake of the legislature. </font></font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Whenever there is a doubt on what the intent of the legislature was, can't we just call the officer who drafted the law and ask him what his intent was? Let him give a clarification and let that be made part of the law with prospective effect. We can spare the Supreme Court the agony of deciding what the bureaucrat meant by "or" and call it a <font color="#FF0000">mistake of the legislature. </font></font></p> <p align="justify"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The Supreme Court says, "If it was a drafting mistake, as suggested by learned ASG, the legislature could have stepped in to correct it". They will - now. Maybe the mistake was detected only now. </font></p> <p align="justify"><font color="#009900" size="2" face="Verdana, Arial, Helvetica, sans-serif">To err is human, but can you collect tax on that error? </font></p> <p align="justify"><font color="#FF0000" size="2" face="Verdana, Arial, Helvetica, sans-serif">Until next week </font></p> </body> </html>