Filtering GST Registration Data by State, District and PIN

Every GSTIN begins with a two-digit state code, so state-level filtering on GST data is exact in a way that almost no other B2B geographic filter is. Below the state level, precision falls away quickly: district and PIN come from the declared principal place of business, and that address is frequently not where the business operates, not where its decision-maker sits, and occasionally not a business premises at all.

This guide covers what each level of geographic filtering actually guarantees, and how to build territory lists that survive contact with a field sales team.

The state code is structural, not declared

The first two digits of a GSTIN encode the state or union territory of registration. They are not a free-text field a business fills in — they are assigned by the registration itself, which makes state-level segmentation reliable in a way the rest of the address is not.

A working subset of the codes:

The full list is published on the GST portal and is stable. Two consequences follow directly:

• You can validate any state filter yourself. Take a delivered file, read the first two digits, cross-tabulate against the state column. Mismatches mean the file was assembled carelessly.
• A multi-state business appears multiple times. A company registered in Maharashtra, Gujarat and Karnataka has three GSTINs. State filtering returns three records for one commercial prospect. Whether that is what you want depends on whether your territories are geographic — see the deduplication discussion in what "daily" and "fresh" mean.

Below state level, precision degrades

District and PIN come from the principal place of business declared at registration. Four things routinely make that address a poor proxy for where the business actually is:

1. Residential registration. A large share of new small businesses register at the proprietor's home. The PIN is real; the "business location" implied by it is a flat.
2. Professional and virtual addresses. Registration at a CA's office or a virtual office provider clusters hundreds of unrelated businesses at one address, in one PIN, often in a commercial district the businesses have never visited.
3. Registered versus operating address. A business may register at a head office and operate from a warehouse in another district. Additional places of business exist as a field, but are not always present in extracts.
4. PIN boundaries are postal, not commercial. A PIN can straddle the kind of boundary a sales territory is drawn along.

Building a territory list that holds up

A sequence that works, in order:

1. Start with the state code. It is the only geographic field that is structurally guaranteed.
2. Add district, and treat it as a strong hint rather than a fact. Good enough for allocating between regional teams, not for routing a field visit.
3. Use PIN for clustering, not for precision. PIN-level counts tell you where density is; they do not tell you a specific record is at that location.
4. Run the cluster test above and flag high-count addresses before distributing the list.
5. Layer non-geographic filters early. Constitution of business and nature of business activity narrow a list far more usefully than tightening the radius. A list of 400 service providers across a state usually outperforms 4,000 mixed records in one district.
6. Verify locally before field deployment. For anything requiring physical travel, confirm by phone first. The cost of a wasted visit dwarfs the cost of a call.

Why counts differ between sources

If you compare "new registrations in Karnataka last month" across two providers, expect disagreement. The reasons are methodological, not necessarily errors:

• Definition of new — registration date versus first-observed date, as covered here.
• Deduplication key — GSTIN-level counts exceed PAN-level counts, sometimes substantially.
• Status handling — whether cancelled or suspended registrations from the period are included.
• Taxpayer type inclusion — whether TDS deductors, ISDs, casual and non-resident taxpayers are counted alongside regular registrants. They are registrations, but most are not sales prospects.
• Amendment handling — whether a change of address emits a new row.

Ask for the definition alongside the number. A count without a methodology is not comparable to anything.

For official aggregate statistics rather than vendor counts, GST collection and registration data is published periodically through government channels including data.gov.in and GST Council releases. Use those for market sizing and cite the period; use vendor data for prospecting.

Geographic filtering at this level is offered by most GST-based providers, including FinScreener — built by the team that publishes this site, see our disclosure — and approached differently by directory-derived sources such as Fundoodata and JustDial, whose coverage biases differ by category. Compare them on your specific districts rather than in general.

Filters that outperform geography

In practice, three filters do more work than tightening a radius:

Constitution of business. Proprietorship, partnership, private limited and LLP are different buyers with different budgets, different decision speeds and different needs. A proprietorship decides in one conversation; a private limited company has a process. Segmenting on this before geography usually improves conversion more than any location refinement.

Nature of business activity. Retail, wholesale, manufacture, service provision, export. This is the field that determines whether your product is relevant at all.

Taxpayer type. Composition-scheme taxpayers are small by definition and have restricted input credit — which makes them the right target for some products and the wrong one for others. Excluding TDS/TCS deductors and ISD registrations from a prospecting list removes records that were never going to convert.

Registration age cohort. Days since registration is often more predictive than location. Businesses at day 15 and day 150 want different things — the cohort structure is in the outreach playbook.

Common questions

Can I get GST data for one district only? Most providers support district filtering, but the underlying limitation is the address, not the filter. Ask what proportion of records in the district are residential or shared addresses before assuming the count represents commercial premises.

Does the state code tell me where the business operates? It tells you where it registered. For single-state businesses these coincide almost always. For multi-state businesses, each GSTIN indicates a genuine place of business in that state — which is more informative than it first appears.

Is PIN-level targeting worth paying extra for? For density analysis and territory planning, yes. For "these 50 businesses are within 3km of my store", no — not without verification. The address quality does not support that claim.

How do I check whether a specific address is a virtual office? Count how many distinct GSTINs share the exact address string in your own file. It is the fastest signal available and needs no external data.

Where does the geographic data ultimately come from? The declared principal place of business in the registration record. Its provenance and limits are covered in what new GST registration leads actually are, and how to verify an individual record is in looking up a company from its GST number.