A vendor’s GSTIN can be cancelled by the GST authority at any point after onboarding. When that happens, every invoice your AP team processes against that vendor after the cancellation date creates an ITC reversal risk under Section 16(2)(c) of the CGST Act, as typically interpreted. Most vendor masters are not validated against the GST portal after onboarding, which means cancelled GSTINs stay active in the system for months. The fix is not complex, but it requires a check that most AP teams have not built.
The problem is not that finance teams ignore GSTIN compliance. Most onboarding checklists include a GSTIN verification step. Verification happens once, at the point of onboarding, and is never repeated. A GSTIN that was active in January can be cancelled by April for non-filing, and your vendor master will still show it as valid. Your AP team will continue raising purchase orders, processing invoices, and claiming ITC against that vendor through the rest of the year. By the time a GST notice arrives, the exposure has compounded across multiple tax periods.
How Does a Cancelled GSTIN Create an ITC Reversal Risk?
GSTIN cancellation is not a rare event. The GST authority cancels registrations for several reasons: a supplier voluntarily surrenders registration, the authority cancels for sustained non-filing, or cancellation follows a fraud finding. In each case, the supplier’s GSTIN moves from Active to Cancelled on the GST portal. Invoices raised after that date carry a GSTIN that is no longer valid.
Under Section 16(2)(c) of the CGST Act, as typically interpreted, ITC eligibility requires that the supplier has filed their returns and paid the tax to the government. Post-cancellation invoices are not automatically treated as void for ITC purposes — the reversal risk operates independently through these return-filing and tax-payment conditions. A cancelled GSTIN generally means the supplier has ceased filing. If the supplier has not filed the returns against which your ITC claim sits, the credit is at risk of reversal on assessment.
The financial consequence, if the reversal is assessed, is the ITC amount plus interest under Section 50 of the CGST Act. Where ITC has been wrongly availed but not yet used, interest applies at 18% per annum under Section 50(1). Where ITC has been wrongly availed and used, the rate rises to 24% per annum under Section 50(3). Both rates apply from the date of the original claim.
The chain runs as follows: a vendor’s GSTIN is cancelled, your vendor master is not updated, your AP team processes invoices and claims ITC, a GST audit surfaces the discrepancy, and a reversal notice follows. The gap between the cancellation date and the notice date is typically six months to a year, long enough for the exposure to span multiple quarters.
Why Your ERP Does Not Catch This Automatically
ERPs store GSTIN as a static field in the vendor master. The value entered at onboarding stays in the record unless someone manually updates it. No standard ERP configuration polls the GST portal for status changes between payment runs. SAP, Oracle, and Tally have the same structural gap: GSTIN validation is a one-time input check, not a live compliance control.
The GST portal does not push cancellation notices to buyers. When a supplier’s registration is cancelled, the authority notifies the supplier. The buyer receives no alert. If your AP team is not actively checking portal status, they will not know.
In a vendor master diagnostic we ran for a mid-market manufacturer with 875 active vendors, 72 records — 8.2% of the population — failed GSTIN validation checks. These included blank GSTINs, format-invalid GSTINs, and address-state mismatches. Within this set, live portal reconciliation is required to identify which registrations have lapsed or been cancelled, a step the client’s ERP had not been configured to run.
The table below shows what the gap looks like in practice:
| GSTIN Status in ERP | Actual GST Portal Status | ITC Consequence |
|---|---|---|
| Active (onboarded) | Still active | No issue |
| Active (onboarded) | Cancelled — non-filing | ITC reversal risk per Section 16(2)(c) |
| Active (onboarded) | Cancelled — surrendered | ITC reversal risk per Section 16(2)(c) |
The ERP reflects the first column. What matters for ITC eligibility is the second.
What Does a GSTIN Status Check Actually Look For — and How Often Should It Run?
There are two distinct checks, and most teams only run one of them.
Format validation confirms that a GSTIN is structurally correct: 15 characters, the first two digits matching the supplier’s state code, the next ten matching the supplier’s PAN, and the last three following the prescribed suffix format. This check can be run offline against the vendor master without portal access. It catches blank GSTINs, typographical errors, and state-code mismatches.
Live portal validation confirms that the GSTIN is currently active on the GST portal. This requires querying the portal’s taxpayer search against each GSTIN in the vendor master. It is the only check that catches a cancellation that occurred after onboarding. The portal returns a current status — Active or Cancelled — for any GSTIN in seconds.
Most AP teams run format validation at onboarding and stop there. Live portal validation, if it runs at all, is done manually for high-value vendors before large payments. For the rest of the vendor master, it does not run.
The appropriate frequency depends on vendor activity and payment volume. For vendors with active purchase orders, quarterly portal reconciliation of the full vendor master is a defensible baseline. For vendors processing above a payment threshold you define, at-point-of-payment validation is worth the effort. The GST portal’s taxpayer search is not rate-limited for individual lookups, and a bulk reconciliation across several hundred vendors takes less than a day with a structured extract.
If you have not run a live portal reconciliation of your vendor master in the last twelve months, the starting point is to understand what is actually in there. That is what the IQSS Finance Operations Diagnostic covers in five days — GSTIN status, PAN validity, duplicate records, and shared bank accounts — before any of it becomes a notice on your desk.
Key observations
- A GSTIN validated at vendor onboarding is not a control. It is a point-in-time check that expires the moment the supplier’s registration status changes.
- Under Section 16(2)(c) of the CGST Act as typically interpreted, ITC claimed against invoices from a cancelled-GSTIN supplier is reversible on assessment.
- Most Indian mid-market ERPs store GSTIN as a static vendor master field and do not poll the GST portal for status changes after onboarding.
- A vendor master of 875 vendors can contain 72 GSTIN validation failures of varying severity — format errors, blank fields, and status drift — without any ERP alert firing.
- The remediation is a structured portal reconciliation, not an ERP upgrade: the GST portal’s taxpayer search returns current GSTIN status in seconds.
Internal Links
- Vendor Master Data Quality in India: What Good Looks Like When You Measure It — this article extends the GSTIN validity dimension covered there
- MSME 43B(h): Calculating Your Company’s Actual Payment Exposure — a parallel compliance exposure in the same vendor data