Summary: The article examines the growing tendency of GST authorities to invoke Section 74 of the CGST Act as a default provision for turnover mismatches, Input Tax Credit disputes, and procedural irregularities, often without establishing fraud, wilful misstatement, or suppression with intent to evade tax. Drawing on a series of Madras High Court decisions, it highlights that mere discrepancies between GST returns, Income-tax records, or portal data cannot automatically justify proceedings under Section 74. The Court has consistently emphasized that authorities must conduct proper verification of books, bank records, and supporting documents, provide adequate notice and personal hearing, consider taxpayers’ replies—including manually filed submissions—and pass reasoned orders. The article also underscores that Section 74 cannot be used to overcome limitation under Section 73 or based solely on generic allegations. It concludes that genuine turnover disputes and threshold-related issues require fact-based adjudication, strict compliance with natural justice, and clear evidence before imposing fraud-based demands and penalties.
Section 74 Is Not a Default Weapon: Madras High Court’s Message on Turnover, Threshold and Natural Justice in GST”
Why we need to talk about Section 74 misuse
Anyone handling GST disputes in all states now knows one common pattern: whenever the department finds some discrepancy – turnover mismatch, ITC issue, cancellation of registration, even small procedural lapses – the default section in the order is Section 74. Fraud, wilful misstatement and suppression with intent to evade have become standard phrases, copied and pasted, whether the facts justify them or not.
At the same time, in several recent matters, the Madras High Court has quietly but firmly pushed back. It has said, in plain language, that:
You cannot treat every shortfall or mismatch as “suppression”.
You cannot pass heavy demand orders under Section 74 without clear notice, proper opportunity of hearing, and application of mind.
You cannot base GST liability only on figures appearing on another portal when the basic records show something else.
This is directly relevant for cases where the taxpayer’s actual turnover appears prima facie below the GST registration threshold, but the department has still invoked Section 74 and created huge demands, often ex prate and without proper hearing.
The Madras HC strand: turnover mismatch and natural justice
Let me first pick up the turnover mismatch line, because it is the closest to your “below threshold” fact situation.
K.N. Raj Constructions – mismatch is a red flag, not proof
In M/s K.N. Raj Constructions vs State Tax Officer, the Madras High Court dealt with a very large mismatch between GST turnover and Income‑tax portal figures. In GST returns, turnover was around ₹29.69 crore. On the Income‑tax side, the figure was about ₹166.93 crore.
The department took the easy route: treat the differential as suppressed turnover, use Section 74, and pass heavy orders. The assessee said something quite interesting – that the Income‑tax turnover was inflated only to qualify for government tenders, and that the bank receipts and books did not support such high turnover.
The Court’s reaction is important for us:
A huge disparity between portals and bank records requires deeper scrutiny; it cannot be brushed aside or blindly adopted for GST liability.
Figures on the Income‑tax portal are not conclusive for GST; they may be inflated or reported for different purposes.
Section 74 demands proof of suppression or fraud in taxable supplies, not just reliance on figures taken from another statutory regime.
So, the Court set aside the Section 74 assessments and ordered a forensic audit by the GST Audit Wing, with directions to examine books, bank accounts and electronic data.
You can see the principle: where prima facie evidence (bank statements, books, registration profile) suggests that actual business activity is lower than what is shown in some other portal, the department cannot jump straight to Section 74 with assumptions. It must first examine facts in depth.
Kathiravan – serious Section 74 demands need serious natural justice
The next relevant Madras HC case is Kathiravan vs Commissioner of State Tax, decided in February 2026. Here, Section 74 assessments for 2017–18 and 2018–19 raised demands of about ₹18.74 lakh and ₹9.40 lakh.
The facts show exactly the “portal‑centric” problem you mentioned:
Show cause notices were uploaded on the GST portal.
The assessee stated that replies were given manually at the office, but the officer proceeded only on the record that nothing was filed online.
No personal hearing was granted before passing orders, despite the sizeable demands.
The High Court’s ratio is blunt and useful:
Orders under Section 74 involving serious tax consequences must strictly comply with principles of natural justice.
Denial of personal hearing in such cases, especially when demands are significant, renders the orders unsustainable.
Manual replies cannot be treated as non‑existent merely because they were not loaded on the portal; once received, they must be considered.
The Court therefore set aside the assessment orders and remanded the matter with clear directions:
Assessee to file replies with documents within two weeks.
Authority to give a clear 14‑day notice of personal hearing.
Fresh order to be passed on merits after hearing.
For your “below threshold” case, Kathiravan gives you the natural‑justice backbone: if Section 74 is invoked and serious demand is raised, hearing is not a formality. It is compulsory, and ignoring manual replies is not permitted.
Bold Rocchi, Crystal Granites and others – when hearing is denied or reply is ignored
There is a line of Madras HC decisions reinforcing this theme:
In Boldrocchi India Pvt. Ltd., the department ignored manually filed replies and proceeded on the ground that there was no portal reply; the Court quashed Section 74 orders and rectification orders, holding that once a reply is acknowledged, it must be considered and personal hearing granted with sufficient notice.
In Crystal Granites vs Assistant Commissioner (ST), a Section 74 order was quashed primarily on the ground that the assessee was not properly informed of the SCN and subsequent proceedings; the Court insisted on proper information and natural‑justice compliance.
In earlier cases like Engineering Aids, Madras HC declared that a Section 74 order passed without considering the assessee’s reply is invalid and must be remanded for fresh consideration with mandatory personal hearing.
In Anantham Silks (Madurai Bench), the Court refused an assessment order issued without giving a proper chance for personal hearing under Section 74(1); it directed the department to issue a fresh SCN, invite objections and then pass orders after giving hearing.
Across these cases, one message is constant: Section 74 orders are not routine; they sit at the heavy end of the GST enforcement spectrum and therefore require strict natural‑justice discipline.
Neeyamo – Section 74 needs jurisdictional facts, not just missed deadlines
Neeyamo Enterprise Solutions (Madurai Bench) is slightly different in focus but very relevant to your concern about Section 74 being used in every case.
There, notices arising out of a Section 67 inspection listed discrepancies but did not contain allegations of fraud, wilful misstatement or suppression with intent to evade. Despite this, the department proceeded under Section 74, imposed tax, interest and equal penalty, and treated Section 74 like a default provision.
The Court struck down the proceedings on the simple ground that:
Section 74 cannot be invoked unless the SCN itself clearly sets out the jurisdictional facts for extended limitation – fraud, wilful misstatement or suppression with intent to evade.
These elements cannot be assumed or implied; they must be stated and supported.
A tax shortfall does not automatically translate into suppression; the law demands a direct link between discrepancy and intent.
When jurisdiction to invoke Section 74 is missing, proceedings are void ab initio and cannot be salvaged by remand under the same provision.
This judgment directly attacks the “Section 74 in every case” culture. It reminds officers that Section 73 exists for normal cases without fraud or suppression, and that the extended period in Section 74 is not a fallback tool just because they missed the limitation bus.
How department officers are reading facts and stretching Section 74
From these cases, we can reconstruct how officers are currently reading facts to drag everything under Section 74.
1. Treating any mismatch as suppression
If GST returns show one figure, Income‑tax portal shows another, or bank receipts differ from declared turnover, the immediate assumption is: “difference = suppression” and “suppression = Section 74”.
There is no patient step of asking:
Why is the portal showing higher turnover?
Are there actual bank receipts supporting the higher figure?
Is it a matter of classification, timing, or mere estimation?
Instead, portal print‑outs are treated as gospel, and Section 74 orders are prepared on that basis. The K.N. Raj ruling shows that this is legally unsound.
2. Using inflated figures without looking at threshold
In small cases, especially works contractors and petty traders, officers are lifting figures from Income‑tax filings or tender documents and applying them directly to GST, without checking whether the core bank turnover and books actually cross the GST registration threshold.
In a “prima facie below threshold” situation, this is dangerous:
Threshold exists precisely to avoid burdening micro entities with full GST machinery.
When bank turnover is below threshold, jumping straight to Section 74, on the basis of untested, higher figures from another portal, is not just harsh – it is jurisdictionally weak.
Madras HC has not yet said in one line “Section 74 cannot be used when turnover appears below threshold”, but if you combine K.N. Raj’s caution on portal mismatch with Neeyamo’s insistence on clear ingredients, the logic flows naturally.
3. Over‑reliance on portal and under‑reliance on hearing
Officers have become comfortable with a “portal‑only” workflow:
SCN uploaded.
Reminder uploaded.
Hearing date uploaded.
Order uploaded.
Whether the assessee actually saw any of this, whether he is capable of operating the portal, and whether any genuine hearing took place, is pushed into the background.
Kathiravan and other Madras HC cases have directly criticised this habit. Uploading is not communication by itself, and hearing is not a checkbox event; it must be effective.
4. Copy‑paste reasoning and lack of application of mind
In some Section 74 orders, the officer simply reproduces the SCN or even reproduces the assessee’s reply without analysis and then confirms the demand. Madras HC has treated such orders as legally unsustainable:
A Section 74 order that merely copies the assessee’s reply without examination is invalid.
Section 74(9) requires a reasoned order after considering the representation.
Lack of reasoning is itself a natural‑justice violation.
In “below threshold” cases, this becomes worse: a cut‑paste order that does not even discuss threshold turnover, business profile and bank records has no credibility.
5. Using Section 74 as default when Section 73 is time‑barred
The Neeyamo commentary points out that some officers invoke Section 74 mechanically whenever they have missed the normal limitation under Section 73, especially for one year out of an audit period. They treat “extended period” as a back door.
Madras HC has clearly said this is not permissible: extended period is not a cure for poor departmental discipline; it is only available if statutory ingredients are actually present.
How to build a “below threshold + no hearing” case using these strands
Even if we don’t have one Madras HC case with your exact fact matrix, we can confidently use these lines by analogy.
A. Start with the threshold facts
Put your turnover on the table:
Bank statements and books show turnover below threshold.
GST registration may have been obtained later, but for the relevant period, there is prima facie non‑taxability.
Any higher figure appearing on Income‑tax portal or tender database is projected/estimated, not supported by bank receipts.
This aligns with the K.N. Raj logic: figures on another portal are not conclusive and must be tested against primary financial records.
B. Show how Section 74 was invoked mechanically
Next, show how the department jumped straight to Section 74:
SCN under Section 74 alleging “suppression” solely on the basis of higher portal figures.
No specific allegations of fraud, wilful misstatement or suppression with intent to evade – only generic wording.
No attempt at reconciliation or verification of bank accounts and books before issuing SCN.
This is squarely hit by Neeyamo and the later analysis reported on Section 74: jurisdictional facts must be spelt out and proved, not assumed.
C. Emphasize denial of hearing and ignoring replies
Then you bring in the natural‑justice line:
SCN and hearing intimation only on portal; no effective communication to the assessee.
Manual reply, if any, filed and acknowledged, but not considered, with the order simply saying “no reply on portal”.
No personal hearing with reasonable notice; either no hearing date at all or a portal‑only date which never translated into an actual interaction.
Here, Kathiravan, Boldrocchi, Crystal Granites, Anantham Silks and Evershine Industries all help:
Serious Section 74 demands must strictly comply with natural justice and hearing requirements.
Ignoring manual replies is clearly wrong.
Passing orders without hearing in person has been repeatedly quashed and remanded.
D. Attack the order as non‑speaking and arbitrary
Finally, show that the order is mechanical:
It reproduces portal data but does not analyse threshold turnover.
It fails to discuss bank statements and books.
It does not explain why Section 73 could not be used and why extended period under Section 74 is justified.
It contains no reasoning on intent to evade, despite the heavy penalty.
Madras HC has already said that Section 74 orders without proper reasoning, or orders that merely repeat the assessee’s reply without analysis, are invalid. In a below‑threshold case, this non‑speaking nature becomes even more glaring.
Concluding thoughts
At the end of the day, Section 74 is meant for serious cases – fraud, wilful misstatement, suppression with intent to evade. It is not meant to be a routine tool for every mismatch, every small discrepancy, or every delayed assessment. When officers start treating Section 74 as the default section, three things happen:
The statutory scheme separating normal cases (Section 73) from exceptional ones (Section 74) collapses.
Small and marginal taxpayers – including those whose turnover is actually below threshold – are dragged into heavy litigation, bank attachments and penalties based more on portal figures than on real activity.
Natural justice becomes a casualty: no proper notice, no hearing, and orders which are more template than judgment.
The Madras High Court, through these recent decisions, is quietly restoring balance. It is saying:
Look at the facts, not just the portal screenshots.
Prove suppression if you want Section 74; don’t just recite the words.
Give real notice, real hearing, and real reasons.
For practitioners, especially in below‑threshold and turnover‑mismatch cases, this line of case law is a powerful tool. It allows you to challenge not just the quantum but the very foundation of Section 74 proceedings, and it reminds everyone – department and taxpayers alike – that GST is still supposed to operate under the Constitution, under natural justice, and under common sense.
Author Bio
