Legal Name vs Trade Name on a GSTIN

Every GST registration carries two names. The legal name is who the registration belongs to in law. The trade name is what the business calls itself on the signboard. Most of the time nobody cares about the difference, until an invoice is rejected by a customer's AP team, a vendor record fails to match, or a payment goes out to a bank account whose holder is neither. This post explains where each name comes from, which one belongs on an invoice, and how to match names in vendor data without drowning in false alarms.

What the two names actually are

A GSTIN is built on a PAN. Characters 3 to 12 of the fifteen-character number are the holder's PAN, as the GSTIN format guide walks through position by position. The legal name is the name that PAN is issued in. When you apply for registration, the portal validates the PAN and the name against the income tax database, so the legal name is not something you type freely and hope for the best. If the two do not agree, the application does not go through.

The trade name is a separate field in the same application. It is the name the business operates under: the shop board, the brand on the packaging, the name on the website. You declare it yourself, it is not validated against anything, and you can leave it the same as the legal name. Nothing in GST makes the trade name a registered trade mark, and registering it under GST gives you no rights to it as a brand.

The practical consequence: the legal name tells you who is liable, the trade name tells you who you think you are dealing with. Tax, credit and legal notices all attach to the legal person behind the PAN.

Legal name and trade name by type of business

Where the legal name comes from depends on the constitution of the business, because that decides whose PAN the registration sits on.

The proprietorship row causes most confusion. A proprietorship is not a separate legal person, so there is no business PAN: the registration is on the owner's own PAN and the legal name field shows a person's name. That also means the record contains personal data, a point covered in whether a GST number is public information.

What a GSTIN search shows

A search on the GST portal's Search Taxpayer page shows both names, along with the constitution of business, registration status, taxpayer type, principal place of business and return filing history. So does our free GST number search, which allows five lookups a day without signing up.

Going the other way is harder. There is no public tool that finds regular taxpayers by business name, so if all you have is a trade name you are usually stuck asking the counterparty for their GSTIN. The guide to searching a GST number by name covers what is and is not possible.

Through the API, a single verification call returns the government record with both names: taxpayer_data.name is the legal name and taxpayer_data.tradename the trade name, next to the registration details and GSTR filing history from the same call. Bulk verification results normalise them to legal_name and trade_name, and there one behaviour needs designing around: where a business has declared no separate trade name, trade_name falls back to the legal name rather than returning empty. Identical values in the two fields are normal, not a data error.

Which name goes on a tax invoice

Rule 46 of the CGST Rules requires a tax invoice to carry the name, address and GSTIN of the supplier, and the name, address and GSTIN of the recipient where the recipient is registered. The rule says "name". It does not say legal name or trade name, and in practice you will see both on invoices that nobody has challenged.

The safe practice is to print the legal name as the supplier's name and show the trade name alongside it, for example "Rakesh Kumar, trading as Sharma Electricals". The legal name ties unambiguously to the PAN and GSTIN, so there is no argument about whose invoice it is. The trade name keeps the invoice recognisable to the customer. The full list of particulars is in the GST invoice format guide.

Why names do not match in your vendor master

If you verify supplier GSTINs in bulk and compare the result with your vendor master, expect a large share of rows to "mismatch" on a naive string comparison. Almost all of those are formatting, not fraud. The usual causes:

• Proprietor name versus shop name. Your master says "Sharma Electricals"; the legal name is the proprietor's personal name. Compare against the trade name instead, and the row matches.
• Suffix spelling. "Pvt Ltd", "Pvt. Ltd.", "Private Limited" and "(P) Ltd" are the same thing.
• Abbreviations and initials. "ABC Traders" versus "A B C Traders", "M/s" prefixes, "&" versus "and".
• Case, punctuation and spacing. The public record is typically upper case; your ERP may not be.
• Amended names. The supplier renamed itself, the GST record was amended, and your master still holds the old name.
• Wrong GSTIN in the master. The name is right but someone keyed a different entity's GSTIN, often a group company.

A workable matching approach normalises both sides before comparing, then scores what is left:

1. Upper-case, strip punctuation, collapse whitespace, and drop prefixes such as "M/S".
2. Map legal suffixes to one canonical token with a small dictionary: PRIVATE LIMITED, PVT LTD and P LTD all become PVT LTD; LIMITED and LTD become LTD.
3. Compare token sets rather than raw strings, so word order and single missing words do not sink a match.
4. Compare the vendor's name against both legal_name and trade_name, and keep the better score.
5. Auto-accept above a high threshold, send the middle band to a person, and treat a low score as a probable wrong GSTIN.

import re

SUFFIXES = {
    "PRIVATE LIMITED": "PVT LTD", "PVT LIMITED": "PVT LTD", "P LTD": "PVT LTD",
    "LIMITED": "LTD", "AND": "&",
}

def normalise(name: str) -> set[str]:
    s = re.sub(r"[^A-Z0-9& ]", " ", name.upper())
    s = re.sub(r"^M S\b", "", s)
    s = re.sub(r"\s+", " ", s).strip()
    for long, short in SUFFIXES.items():
        s = re.sub(rf"\b{long}\b", short, s)
    return set(s.split())

def score(a: str, b: str) -> float:
    x, y = normalise(a), normalise(b)
    return len(x & y) / max(len(x | y), 1)   # Jaccard on tokens

def best_match(vendor_name: str, response: dict) -> float:
    # response is the JSON from GET /api/get-taxpayer-info/{gstin}
    record = response["taxpayer_data"]
    return max(score(vendor_name, record.get("name") or ""),
               score(vendor_name, record.get("tradename") or ""))

Token overlap is crude but explainable, which matters when an auditor asks why a vendor was approved. If you need tolerance for typos, swap the scoring function for an edit-distance measure; the normalisation step does most of the work either way. The wider workflow around it is in the accounts payable verification guide.

When a name mismatch is a red flag

Trade name mismatches are rarely interesting. The trade name is self-declared and unvalidated, so it tells you little either way. The legal name is different: it is anchored to a PAN, and a mismatch there is worth stopping for.

For a proprietorship, the bank account is often in the proprietor's personal name, which will match the legal name even though it does not match the shop name. That is expected. What should worry you is an account in the name of an unrelated third party. The vendor onboarding checklist puts this cross-check in context with the other documents you collect.

If you want to run the check at scale, verification costs ₹0.50 a GSTIN pay-as-you-go, and the 20 free credits you get on email verification are enough to test the matching logic on a sample of your own vendor master first.

Changing either name

The two names sit on opposite sides of the core and non-core split in Rule 19 of the CGST Rules.

• Trade name is a non-core field. The amendment takes effect when you submit it, with no officer approval.
• Legal name is a core field. Because it follows the PAN, the PAN record has to carry the new name first, and the amendment then goes to the proper officer for approval. An approved change produces a fresh registration certificate.

The portal has moved fields between amendment screens over the years, so confirm on gst.gov.in which tab currently carries each one. The registration amendment guide has the step-by-step process.

One boundary matters. A name change on the same PAN is an amendment. A change of constitution, such as a proprietorship becoming a private limited company, creates a new legal person with a new PAN, and that needs a new GSTIN rather than an amendment; see when a business needs a new GSTIN. For your vendor master, the difference is important: an amended legal name keeps the same GSTIN, while a new constitution means the old GSTIN should eventually show as cancelled and the supplier has to give you a new one.

Frequently asked questions