# How to Read and Validate the Structure of a GSTIN

## Structure checking is the first check

A GSTIN is a fifteen-character identifier assigned under the GST registration framework. Rule 10 describes its components: two State-code characters, ten characters for PAN or TAN as applicable, two entity-code characters and one checksum character. For an ordinary PAN-based business registration, the embedded PAN is particularly useful when checking that the number belongs to the intended legal person.

A plausible format does not establish that the registration exists or is active. Separate three questions: does the text fit the expected structure, does official search return the intended taxpayer, and does that taxpayer's registration status support the transaction being reviewed? Each check provides different evidence.

## Break the identifier into the statutory positions

| Positions | Component | Practical check |
|---|---|---|
| 1–2 | State code | Compare with the intended State registration |
| 3–12 | PAN or TAN as applicable | Match the relevant identity record |
| 13–14 | Entity-code positions | Preserve the issued characters exactly |
| 15 | Checksum character | Use a reliable validation process |

This grouping avoids treating the whole identifier as an unreadable block. Count characters after removing accidental surrounding spaces, but do not delete or substitute a character within the number. A spreadsheet imported from a PDF can introduce hidden spaces, while manual typing can confuse similar-looking letters and numerals.

For a business using several GST registrations, the State component and entity positions help distinguish records that share the same PAN. Do not assume the familiar PAN substring means every registration in the list is interchangeable for invoices. The specific State registration and actual supplier establishment still matter.

## Compare the embedded identity with the legal person

Use the PAN belonging to the registrant, not automatically the owner's personal PAN. A proprietorship normally uses the proprietor's identity, while a company or partnership uses its own PAN. An invoice carrying a company's brand beside a proprietor's unrelated GSTIN should prompt a factual review of who actually made the supply.

Read the middle ten-character segment carefully and compare it with reliable records. Do not accept a number merely because its last few characters resemble a familiar vendor code. Where the registration category uses TAN under the statutory framework, apply the appropriate identity check rather than forcing a PAN-only assumption onto every special registration.

Illustratively, a buyer is onboarding a supplier for a ₹75,000 equipment purchase. The supplier has sent GST details for two group companies. Both names contain the same brand word, but the PAN segments differ. The buyer should establish the contracting and invoicing company before selecting a GSTIN; choosing whichever number passes a basic format test would not resolve the identity question.

## Use checksum validation within its limits

The final character helps detect input errors through the applicable validation method. If accounting software reports a checksum error, compare the number with the original supplier document and official source before changing it. Do not calculate a replacement final character for an otherwise guessed number and treat that as the supplier's genuine registration.

A passed checksum means the character sequence meets that check. It does not prove that goods were delivered, the supplier filed returns or the buyer is entitled to input tax credit. Likewise, a failed import may be caused by formatting or transcription rather than misconduct by the supplier. Investigate the source record before reaching a conclusion.

Keep a control that separates an invalid input from an identity mismatch. The first may be corrected by retyping one verified character. The second can require a revised invoice, different supplier master or explanation of the contracting entity. Staff should not be trained to overwrite errors until the software accepts a number without recording why it changed.

## Verify using official taxpayer search

GSTN provides Search Taxpayer using GSTIN or UIN before and after login. Enter the exact identifier through the official portal and inspect the legal name, trade name, effective registration date, constitution, principal location and status information available. Record the check date because status can change after an old certificate was issued.

Compare the result with the invoice and purchase order. A legitimate trade name can differ from the legal name, so do not reject it solely for that reason. However, a different legal person or State registration needs explanation. Confirm the supplier used the GSTIN relevant to the actual supply rather than a nearby branch's number copied from old stationery.

If search returns no record, recheck the text and the type of identifier. A TRN or ARN belongs to the application process and is not a substitute for a GSTIN on a supplier master. If the input is verified but the issue persists, retain the result and use appropriate official support rather than inventing a replacement number.

## Store and maintain the verified identifier

Store GSTINs as text in business systems so leading characters, fixed length and exact spelling are preserved. Link each number to the legal name, State, relevant supplier branch and date of verification. Do not maintain one unlabelled list of several registrations and let billing staff choose at random.

When a supplier changes name, location or constitution, review whether the same registration continues or a new legal person is involved. A changed PAN-based identity cannot be explained as a harmless typo in the GSTIN. Preserve the old and new records with their effective history.

A useful GSTIN check ends with a verified identifier attached to the correct legal person and transaction context. Structure makes errors easier to find; official search and document matching make the result useful for real purchasing and billing decisions.

## Sources and references

- [CBIC: CGST Rules, official compilation including registration amendment rules](https://cbic-gst.gov.in/pdf/10112020_CGST-Rules-2017_Part-A_Rules.pdf)
- [GSTN: Searching taxpayers using GSTIN or UIN](https://tutorial.gst.gov.in/userguide/taxpayersdashboard/Search_Taxpayer_manual.htm)
- [GSTN: Applying for normal taxpayer registration](https://tutorial.gst.gov.in/userguide/registration/Apply_for_Registration_Normal_Taxpayer.htm)