GST Portal Says No Records Found: Causes and Fixes

"No records found" on the GST portal's Search Taxpayer page means exactly one thing: the 15-character string you entered does not match any GSTIN ever issued by the GST department. It is not a status like "cancelled" or "suspended" — those still return a full record. In the overwhelming majority of cases the cause is a transcription error, not fraud, but the honest answer is that you cannot tell which from the blank result alone. This post works through the causes in the order you should actually check them.

The most common cause: a transcription error

Before considering anything else, assume you or whoever handed you the number made a typo. A GSTIN is 15 characters, and certain character pairs are visually near-identical depending on the font and the handwriting or printout you copied it from: 0 and O, 1 and I, 5 and S, and 8 and B. Any of these swapped in a scanned invoice, a WhatsApp screenshot, or a hand-filled form is enough to send you searching for a number that was never issued.

This is also the easiest cause to rule out, because the format is not free-form. The 15th character of a GSTIN is a checksum computed over the first 14, using a Luhn mod-36 algorithm, so a single mistyped character almost always fails the check digit — the string is invalid before it even reaches the government's servers. Run the number through an offline validator first. If it fails there, you have your answer and do not need to touch the portal at all; if it passes, the typo (if there is one) is further upstream, in a character that happens to still produce a valid checksum, which does happen but is rarer. See how the GSTIN format and checksum are constructed for the full breakdown of what each position means.

You searched a PAN, TAN, CIN or provisional ID by mistake

The second most common cause is not a typo inside a GSTIN but a different identifier entirely being typed into the GSTIN search box. A PAN is 10 characters, not 15. A TAN is also 10 characters but follows a different pattern. A CIN (Corporate Identity Number, issued by the Ministry of Corporate Affairs) is 21 characters and shares no structure with a GSTIN at all. And a 2017-era provisional ID, issued during the initial migration from the old VAT and service tax regimes, followed its own format and was never meant to be looked up as a permanent GSTIN once final registration was granted.

A fifteen-character string can also fail simply because the first two characters — the state code — do not correspond to any real state, which is a strong signal the string was constructed rather than copied from a genuine document. Rather than repeat the full anatomy here, see how many digits a GST number actually has and the complete format reference if you are unsure whether what you are holding is a GSTIN at all.

A cancelled or surrendered registration

This is the cause people most often assume, and it is usually wrong. A GSTIN whose registration has been cancelled — whether the taxpayer surrendered it voluntarily or the department cancelled it for non-filing — does not disappear from the registry. The Search Taxpayer page still returns a full record for it, with the status field showing "Cancelled" and a cancellation date. If you are seeing an actual populated record with that status, you are not looking at a "no records found" situation at all, and the relevant reading is how GST cancellation and revocation work rather than this post.

"No records found" specifically means there is nothing to return, cancelled or otherwise, which points back towards the number never having existed. The edge case worth naming is very old, pre-GST migration records that were never finalised, which can genuinely fall through a gap in the public search — but this is uncommon enough that it should be your last explanation, not your first.

A brand-new registration that has not indexed yet

If the GSTIN in question was issued very recently — days, not months — there can be a short lag between the Application Reference Number (ARN) being approved and the resulting GSTIN becoming searchable on the public-facing Search Taxpayer page. The backend approval and the public index are not always updated in the same instant. If you know the ARN, check its status directly rather than repeatedly searching a GSTIN that may simply not have propagated yet: see how to check ARN status and, if you only have the ARN and need to get to the resulting number, how to go from ARN to GSTIN. If the ARN shows approved and the GSTIN still will not resolve after a few days, that has moved from "wait" territory into "raise a grievance on the portal" territory.

Portal-side issues: captcha, session and rate limits

Sometimes the GSTIN is entirely genuine and the problem is the search tool itself. The GST portal's captcha occasionally fails silently and returns an empty result rather than an explicit captcha error. A session timeout mid-search can do the same. Searching the same number repeatedly in a short window can trip a rate limit that responds with "no records found" rather than a clear throttling message, which is misleading if you do not know to expect it. Browser cache holding onto a stale page state, or an ad-blocking or privacy extension interfering with the portal's scripts, are the other usual suspects.

The practical fixes, in order: reload and re-enter the captcha carefully rather than resubmitting the same form; clear cookies and cache or try a private window; disable browser extensions for the session; wait a few minutes after searching several numbers back to back; and check whether the portal is in a scheduled maintenance window. None of this diagnoses the GSTIN itself — it only rules out the search mechanism before you draw a conclusion about the number.

You searched the wrong facility, or it is a UIN

The GST portal exposes more than one search tool, and typing a correct number into the wrong one returns nothing. "Search Taxpayer by GSTIN/UIN" is for a GSTIN or UIN string specifically. "Search Taxpayer by PAN" expects a 10-character PAN and returns every GSTIN registered against it, not a single record. "Search Composition Taxpayer" is a narrower list restricted to businesses registered under the composition scheme, and a regular taxpayer's GSTIN will not show up there even though it is entirely valid. If you have been pasting the same string into one box and it keeps failing, confirm you have the right box before concluding anything about the number. If you have a PAN rather than a GSTIN in hand, searching by PAN is the correct starting point, not a GSTIN search.

It may be a UIN, not a GSTIN

A UIN — Unique Identification Number — is issued to foreign diplomatic missions, embassies, and certain UN bodies and international organisations for the specific purpose of claiming a GST refund on their purchases, rather than for ordinary business registration. It follows the same 15-character shape as a GSTIN but sits in a separate, much smaller registry and can behave differently depending on which search facility you use. If the document you are working from names an embassy or a UN agency, you are very likely holding a UIN, and the standard GSTIN search box is the wrong tool for it.

The systematic diagnosis order

Once you have ruled out the mechanical causes above, work through them in this order rather than guessing, because each step is cheaper than the next:

1. Validate the format offline first. A failed checksum ends the investigation immediately — the string is malformed and no portal search will ever return it.
2. Re-key the number from the original source rather than copying your own previous entry. If you keep re-searching a string you typed once, you are re-testing your own typo, not the GSTIN. Go back to the invoice, the letterhead, or wherever the number originated and type it fresh.
3. Check the ARN if the registration is new. This rules out an indexing lag before you treat a genuine registration as non-existent.
4. Search by PAN if you know it. This cross-checks the number independently of whatever character may have been mistyped in the GSTIN itself.
5. Contact the supplier or counterparty directly. Ask them to confirm the exact GSTIN printed on their registration certificate, not from memory.
6. If none of the above resolves it, treat the number as a red flag. At that point you are no longer debugging a typo — you are looking at a number that may never have been issued, and how to check for a fake GST number is the next read.

It is also worth checking your assumptions about status in passing: a GSTIN that returns a record but with a status you do not recognise, such as suspended pending cancellation, is a different problem from no record at all — see what a suspended GST status means if that is what you are actually looking at.

What "no record" means for the invoice in front of you

If a supplier has issued you an invoice charging GST under a number that returns no record, the practical consequence is immediate: do not pay the tax component of that invoice until the GSTIN is confirmed. Input tax credit can only be claimed against a valid, active registration, and a number that does not exist in the registry cannot support a credit claim no matter how correctly the invoice is otherwise formatted. If the number later turns out to be fabricated, you have no recourse to recover the tax you paid to that party — the loss sits with you, not the tax department.

If it is your own GSTIN that returns no record, treat it with equal urgency rather than assuming a display glitch. Confirm your registration certificate and ARN independently, check the ARN status, and if everything on your end shows approved but the public search still returns nothing after a reasonable wait, raise a grievance through the portal's helpdesk. A business that cannot be found in the GST registry cannot be paid against with GST applied, which stalls invoicing on both sides of the relationship until it is fixed.

Where a programmatic lookup helps

Everything described above under portal-side issues — captcha failures, session timeouts, rate limiting — is specific to the human-facing website, not to the underlying data. A programmatic GSTIN verification call removes the captcha and session layer entirely and returns a structured, machine-readable response you can branch on in code: a clear "not found" versus a populated record versus a rate-limit error are distinct, parseable outcomes rather than the same blank page. That distinction is what makes checking GSTINs in bulk — hundreds or thousands from a vendor master, rather than one at a time by hand — workable at all. See how these error codes are structured for what a failed lookup actually looks like over an API.

Being precise about what such an API does matters here too. A verification call looks up one GSTIN and returns the taxpayer's registered details, current status, filing history, e-invoicing applicability and jurisdiction for that number. It does not resolve a PAN into the list of GSTINs registered against it — that is a separate lookup, and on the portal it is a genuinely different search facility, as covered above. If your workflow needs to go from a PAN to its GSTINs, that is a distinct capability, not something a standard GSTIN verification call does on the side.

Frequently asked questions