Quick Answer
A vendor master health score measures whether data fields are populated, not whether the GSTINs in those fields are valid, active, or correctly assigned. Across eight diagnostic runs on Indian mid-market companies, every vendor master had missing or invalid GSTINs despite raw scores between 90 and 97 out of 100. The financial consequence splits into two distinct risks depending on the supplier’s actual tax status, and the vendor master entry alone cannot tell you which one you are facing.
A diagnostic run on a vendor master with 875 records returned a raw health score of 97 out of 100. The same run flagged 72 vendors with entirely blank GSTIN fields, all active in the AP system and capable of receiving payments. The score and the finding are not contradictory. The score reflects the checks that ran cleanly. The GSTIN gaps are what the score could not see.
This pattern appeared in every diagnostic we have run on Indian mid-market vendor masters: across 8 runs, 38,935 vendor records, raw scores ranging from 90 to 97. Missing or invalid GSTINs are not an outlier finding. They are the most consistent one.
What the GSTIN Validation Check Actually Tests
A GSTIN validation check has three layers, and most vendor master audits stop at the first.
Format validation checks whether the 15-character alphanumeric value conforms to the GST registration pattern. This check runs offline against the data in the ERP. It catches blank fields and values that do not match the format. It will not catch a GSTIN that is correctly formatted but cancelled, suspended, or assigned to a different entity.
Status validation checks whether the GSTIN is currently active at the GST portal. This requires an API call against the GST registry. Without it, a vendor whose registration was cancelled six months ago looks identical to one whose GSTIN is current. For a deeper look at what cancelled GSTIN status costs an AP function, see Cancelled GSTIN in Your Vendor Master: The ITC Risk Your AP Team Is Not Tracking.
Assignment validation checks whether the GSTIN corresponds to the legal entity named in the vendor master. A GSTIN that is active and correctly formatted but registered to a different company is a mismatch that format checks cannot detect.
Most ERP vendor master audits run the first layer only. A structured diagnostic runs all three. The gap between what the first layer finds and what the second and third find is where the risk lives. Vendor Master Data Quality in India: What Good Looks Like When You Measure It covers the broader framework across all four data dimensions.
What Does GSTIN Validation Actually Find in Indian Vendor Masters?
Across eight runs on Indian mid-market companies, the missing and invalid GSTIN check flagged records in every vendor master reviewed. The count ranged from 55 flagged vendors in a 585-record master to 15,479 in a 19,423-record master. The common thread was not scale. It was the coexistence of high raw scores and persistent gaps.
Two profiles illustrate how the same failure takes different forms.
A small engineering company with 875 active vendors scored 97 out of 100. The diagnostic found 72 vendors with entirely blank GSTIN fields, no format errors, no placeholder values, just empty cells attached to live payment accounts. The score was high because the checks that ran on the remaining 803 vendors came back clean. The 72 blanks were an absolute gap, not a statistical anomaly.
A large manufacturing company with 5,434 vendors scored 93 out of 100. The diagnostic flagged 3,198 vendors with GSTIN issues, of which 1,682 had placeholder values rather than blank fields. These strings (“URPAASV0408” and similar) passed the ERP’s own format validation at entry, inflated the health score, and sat undetected until a structured check ran pattern matching against the GST registration format.
Placeholder values are harder to find than blank fields. A blank is visible in a filter. A placeholder that passes format validation is not.
Blank fields cluster in smaller, older vendors onboarded before GSTIN was mandatory. Placeholder strings cluster around ERP migration periods, where data was carried forward without re-validation. Neither category is an isolated data entry error. Both reflect a structural gap in the onboarding or migration process. The Duplicate GSTIN check in the same diagnostic series covers a related pattern: the same GSTIN assigned to multiple vendor records, which format checks also cannot detect.
What Does a Blank GSTIN Actually Cost the Finance Team?
The consequence of a missing GSTIN depends on the supplier’s actual tax status, which the vendor master entry alone cannot confirm.
If the supplier is registered but the GSTIN was not captured at onboarding or was lost during an ERP migration, the missing field creates a reconciliation gap. The supplier files their returns correctly and charges GST on the invoice, but the buyer cannot map that invoice to their GSTR-2B without a GSTIN in the master record. ITC on that invoice is blocked until the record is corrected, not through a statutory disallowance, but because the matching cannot run.
If the supplier is genuinely unregistered, an unregistered supplier charges no GST, which means there is no ITC to claim and no GSTR-2B entry will exist for that vendor. The blank GSTIN reflects the supplier’s actual status. The cost to the buyer is the full invoice value without any tax offset, and the absence of a GSTR-2B entry means the gap will surface during reconciliation without an obvious explanation.
The vendor master does not tell you which scenario you are in. A blank field could be a clerical omission on a registered vendor, an intentional “URD” placeholder for an unregistered dealer, or a random string left over from a data migration. Each requires a different remediation, and an ERP format check cannot distinguish between them.
Once GSTIN gaps are identified, verify whether the supplier is registered at the GST portal, correct the master record if a valid GSTIN exists, and assess the procurement basis for vendors who are genuinely unregistered. The diagnostic surfaces the list and the failure type. The verification and remediation work follows from it.
If your vendor master has not been validated against the GST portal, a Vendor Master Diagnostic will show you the actual count, the split between blank and placeholder, and which records require immediate attention.
Key observations
- Every vendor master in eight Indian mid-market diagnostic runs had missing or invalid GSTINs, regardless of raw health scores between 90 and 97 out of 100
- Placeholder values such as “URD” or random alphanumeric strings pass ERP format checks and inflate health scores; they are harder to detect than blank fields
- The financial consequence of a missing GSTIN depends on the supplier’s actual tax registration status, which the vendor master entry alone cannot confirm
- A blank GSTIN on a registered supplier creates a practical ITC block via GSTR-2B mismatch; a blank GSTIN on a genuinely unregistered supplier means no ITC is available and no GSTR-2B entry will exist
- Remediation requires GST portal verification for each flagged vendor — the failure type determines the remediation path