Summary: The article discusses the perceived disconnect between the GST portal’s digital records and departmental practices in cases involving NGTP tagging, non-existent suppliers, and retrospective cancellation of GST registrations. It states that despite the GST system being designed as a unified digital compliance framework, buyers are often required to produce old physical records even when portal data such as GSTR-1, GSTR-3B, GSTR-2B, e-way bills, e-invoices, annual returns, and banking records support their transactions. The article contends that retrospective cancellation of a supplier’s registration should not automatically result in denial of input tax credit to a buyer who acted bona fide and maintained documentary evidence. It further discusses the burden of proof, natural justice in portal-based proceedings, field experiences in Karnataka, judicial observations favouring examination of buyer conduct rather than supplier status alone, and the evidentiary value of portal records. The article also outlines documentation that taxpayers should preserve, recommends a transaction-wise response to notices, and suggests a structured adjudication model that begins with portal verification before seeking additional evidence, concluding that digital tax administration should also ensure fair adjudication.
NGTP tags, retrospective cancellation, and the growing disconnect between GST records and departmental disbelief
The GST system was introduced as a digital tax regime. Its promise was simple: less paperwork, more transparency, faster verification, and a compliance trail that could be checked through the portal itself. Tax invoices, GSTR-1, GSTR-3B, GSTR-2B, e-way bills, e-invoices, TDS data, annual returns, and electronic ledgers were all meant to become part of a unified digital record. Yet in practice, especially in cases involving “NGTP”, “non-existent supplier”, or retrospective cancellation of registration, the department often behaves as though the portal is merely a filing utility and not an evidentiary system.
This contradiction has become one of the most painful features of GST litigation. Buyers who have acted bona fide, maintained books, filed returns regularly, and matched transactions with portal data are still asked to produce old physical records from four, five, or even six years ago. If they fail to produce every paper in exact shape, the department often proceeds to deny input tax credit, impose tax, interest, and penalty, and then justifies the action on the ground that the supplier was later tagged NGTP or its registration was cancelled retrospectively. The result is an increasingly familiar pattern: the buyer is asked to prove again what the portal already shows, while the department refuses to trust the very digital architecture it created.
The real issue behind NGTP disputes
At the heart of these disputes lies a simple but uncomfortable question: why does the department distrust portal-based evidence when it helps the taxpayer, but rely on portal intelligence when it helps the revenue?
The answer is not always legal; often, it is administrative. NGTP tags, supplier intelligence inputs, retrospective cancellation orders, and risk-based alerts are treated as convenient shortcuts to suspicion. Once a supplier is marked as non-existent or suspicious, the buyer is often viewed through the same lens. The enquiry then shifts away from the actual conduct of the buyer and towards a broad assumption that the entire chain is tainted. That approach is dangerous because it reverses the burden in a manner that the statute does not always support.
A buyer is not the supplier. A later defect in the supplier’s registration does not automatically prove fraud on the part of the recipient. The buyer may have received goods, made payment through banking channels, recorded the transaction in books, and availed credit only because the supplier appeared active and compliant at the time of supply. If the department wants to deny that credit, it must establish something more than a supplier-side label. It must show recipient-side culpability, collusion, or at least a clear statutory basis for drawing adverse inference.
Why officers still insist on physical records
The most common departmental explanation is that portal data proves filing, not real movement. Officers say that e-filing may show a return, but it does not by itself prove that the goods were actually supplied, transported, and received. On that basis, they ask for invoices, delivery challans, lorry receipts, weighbridge slips, inward registers, stock records, bank statements, and other physical records.
In principle, that demand is not entirely unreasonable. GST is not a system of blind acceptance. The department is entitled to test genuineness. But the demand becomes unfair when it is overbroad, repetitive, and detached from what is already available on the portal. If the taxpayer already has GSTR-1, GSTR-3B, GSTR-2B, e-way bill records, e-invoice data, TDS details, payment trail, and annual return reconciliation, then the department should start with those records and ask only for the specific missing link. It should not require the taxpayer to recreate a transaction file from a period when records may already have been lawfully archived or lost in routine business retention cycles.
This is especially harsh on small and medium businesses. A large corporation may have permanent archival systems. But many traders do not preserve every paper in hard copy for six years. That does not make them guilty. It only means the department must use common sense and evidence already on record rather than demand impossible perfection.
Retrospective cancellation is not proof of buyer fraud
One of the most troubling developments in GST enforcement is the use of retrospective cancellation as a retrospective weapon against the buyer. A supplier may have been registered and active on the date of transaction. The invoice may have been proper. The goods may have been delivered. Payment may have been made through banking channels. The buyer may have filed returns, and the credit may have reflected in GSTR-2B. Then, years later, the supplier’s registration is cancelled retrospectively, and the department attempts to rewrite the past as if the transaction never existed.
That approach is legally fragile. A later administrative action against the supplier does not automatically destroy the genuineness of an earlier bona fide transaction. The law has to be applied to the facts as they existed at the time of supply, not with the benefit of hindsight. If the buyer had no knowledge of any fraud and had acted with due diligence, the mere fact of later cancellation cannot by itself justify denial of credit.
This is where many adjudication orders fail. They rely on the supplier’s later status but do not examine whether the buyer was complicit. They refer to non-traceability, retrospective cancellation, or NGTP tagging, but they do not establish fraud, suppression, or wilful misstatement by the recipient. In such cases, the order becomes vulnerable because it is built on assumption rather than proof.
The legal burden should not be shifted by default
The GST framework does not permit a simple formula of “supplier is bad, therefore buyer must pay.” The department must still show a legal connection between the supplier’s defect and the recipient’s conduct. Where the buyer has a complete documentary trail — invoice, movement proof, payment proof, return reflection, portal validation, and books of account — the burden cannot remain suspended in the air forever. At some stage, the department must point to contrary material.
This is especially true when the portal itself contains much of the evidence that the department later asks the taxpayer to produce again in physical form. GST was designed to reduce informational asymmetry. If GSTR-1 and GSTR-3B were filed, if the supplier was active, if GSTR-2B reflected the credit, and if e-way bills and e-invoices support movement, then that data must carry evidentiary value. It cannot be treated as useful for compliance but useless for defence.
A fair officer should ask five questions before disturbing the buyer’s credit:
- Was the supplier active at the time of supply?
- Is there a valid invoice and payment trail?
- Was the movement of goods supported by e-way bill or transport evidence?
- Did the transaction reflect in GSTR-1, GSTR-3B, and GSTR-2B?
- Is there any direct evidence that the buyer knew of or participated in fraud?
If the first four answers are yes and the fifth is no, then the officer should be slow to deny credit. At the very least, the order must explain why the buyer’s evidence was rejected.
Why natural justice matters more in digital cases
The rise of portal-based notices has created another serious problem: service is being treated as the same thing as hearing. DRC-01A, DRC-01, adjudication orders, cancellation notices, suspension notices, and even coercive recovery notices are uploaded on the portal and then treated as valid communication under section 169. Technically, the department may be right that portal upload is a recognized mode of service. But legally valid service is not always the same as meaningful participation.
In many cases, the taxpayer does not see the notice in time. It may go unnoticed in a portal tab, a login that is not checked daily, or a record that gets buried among multiple GST interactions. The department then says that notices were uploaded, no reply was filed, and recovery under section 79 can begin. This is where justice becomes formal rather than real.
Natural justice demands more than a procedural checkbox. If a taxpayer was genuinely unaware or unable to access the notice in time, and if coercive recovery is then initiated without a fair opportunity to explain the facts, the process becomes vulnerable. The law is not meant to become a trap. It is meant to give a real opportunity to be heard before serious civil consequences are imposed.
Karnataka experience and field realities
In Karnataka, especially in recent years, taxpayers have increasingly complained that field officers are raising large demands in a short span, sometimes covering multiple financial years in one stroke. The pattern is familiar. A supplier is tagged NGTP. The buyer is asked to produce old records. Portal evidence is not fully accepted. The explanation is not discussed transaction-wise. The order is passed. Then recovery begins.
This creates the impression that the department is more interested in generating demand than in determining truth. That may be unfair to the system as a whole, because many officers do act diligently. But from the taxpayer’s standpoint, the experience often feels one-sided. Instead of using portal data as the starting point, some adjudications treat it as irrelevant unless it suits the department’s case.
That approach is especially troubling in bona fide buyer cases. A buyer who has operated transparently, used banking channels, filed returns, matched credits, and preserved evidence should not be condemned simply because a supplier later falls into suspicion. If the law is applied fairly, the focus must remain on the buyer’s conduct, not just the supplier’s later fate.
What the courts have been saying
The judicial trend is more balanced than many field orders suggest. Courts have repeatedly emphasized that a supplier’s retrospective cancellation or later suspicion cannot, by itself, be the sole basis for denying ITC to a genuine purchaser. The stronger line of reasoning is that the department must examine whether the buyer acted bona fide and whether there is evidence of collusion or fraudulent participation.
The Calcutta High Court has taken a notably taxpayer-protective view in cases such as Shyamalmay Paul and Gargo Traders, holding that retrospective cancellation of the supplier’s registration cannot, by itself, destroy a bona fide buyer’s credit where the buyer’s documents and payment trail are intact. The logic is simple and important: a later defect in the supplier’s registration cannot erase an earlier genuine transaction by the buyer.
Several other judgments across High Courts have echoed the same principle in different forms. The common thread is that the department must do more than point to risk flags. It must prove recipient-side wrongdoing or at least articulate a legally sustainable basis for adverse inference. Orders that ignore the taxpayer’s documents or fail to discuss them meaningfully are increasingly vulnerable to challenge.
Why portal evidence should be respected
Portal evidence is not ornamental. It is part of the GST compliance structure. The system itself depends on digital validation. GSTR-1, GSTR-3B, GSTR-2B, e-invoices, e-way bills, TDS data, and electronic ledgers are not casual records; they are the backbone of the tax architecture. If the department uses them to identify discrepancies, it must also accept them as genuine evidence when they support the taxpayer.
A buyer who can show that the supplier was active on the portal at the time of supply, that the invoice matched the portal record, that payment was made, and that the transaction reflected in return data should not be forced into an endless cycle of re-proof. Where 90% of the evidence already exists in the system, the department should ask for the remaining 10%, not insist on the impossible burden of reproducing every old paper trail.
That is the central flaw in many NGTP-based cases. The portal is treated as a surveillance tool when it serves the department, but not as a record of compliance when it serves the taxpayer. Such asymmetry is hard to justify in a digital tax regime.
What taxpayers should preserve
Taxpayers cannot depend only on fairness. They must also prepare for litigation. Every business facing NGTP-related scrutiny should maintain a transaction-wise evidence file with the following:
- Tax invoice.
- E-way bill.
- Transport or delivery proof.
- GRN or inward register.
- Bank payment evidence.
- Ledger extract.
- GSTR-1 and GSTR-3B.
- GSTR-2A and GSTR-2B.
- Annual return reconciliation.
- Supplier GST status snapshot at the time of supply.
Any correspondence with the supplier or transporter.
When a notice comes, the response should be transaction-wise and not generic. It should not merely say “all transactions are genuine.” It should map each disputed invoice to the documentary trail. The reply should also specifically object to any attempt to deny ITC solely on NGTP tagging or retrospective cancellation. If the department passes an adverse order anyway, the appeal should challenge the failure to consider portal evidence, the absence of proof against the buyer, and the denial of effective hearing.
A fairer adjudication model
A fair GST adjudication system in NGTP cases should follow a disciplined sequence. First, it should identify the exact transactions in dispute. Second, it should check whether the supplier was active at the time of supply. Third, it should verify whether the portal records support the transaction. Fourth, it should examine physical evidence only to the extent necessary to fill genuine gaps. Fifth, it should assess whether there is any evidence of collusion by the buyer. Only after doing this should an adverse conclusion be drawn.
This model may take more time, but it produces lawful orders. The current mechanical model may be faster, but it generates appeals, writs, recoveries, and avoidable distrust. In the long run, fair adjudication is more efficient than rushed suspicion.
Conclusion
The GST system was built on digital trust, but many NGTP cases show a stubborn refusal to trust the digital record when it supports the taxpayer. Buyers who have complied with GSTR-1, GSTR-3B, GSTR-2B, e-way bills, e-invoices, banking payments, annual returns, and supplier validation still find themselves forced to defend old transactions with physical papers that may no longer exist. When the supplier later becomes NGTP or faces retrospective cancellation, the department often uses that later event as a shortcut to deny ITC and impose demand.
That approach is not consistent with sound tax administration. A bona fide buyer cannot be condemned merely because the supplier later becomes suspect. The law demands proof of fraud, suppression, or collusion by the taxpayer, not just a supplier-side label. Portal evidence is part of the statutory compliance structure, and when it shows a genuine transaction, it should be treated as evidence, not ignored as inconvenience.
Karnataka’s experience should serve as a reminder that digital tax administration must also be fair tax administration. Notices uploaded on the portal may satisfy service in a technical sense, but if they are not seen in time, or if recovery begins without a meaningful hearing, the process loses legitimacy. The real test is not whether the department can raise a demand quickly. The real test is whether the demand survives scrutiny when the buyer’s portal-based evidence is fairly examined.
