7 Days Money Back Guarantee - Limited Time Offer before 31 October, 2026

How to fix GSTIN/party-detail mismatch errors during Tally import?

A GSTIN/party-detail mismatch in Tally usually comes from one of a few sources: the GSTIN was entered incorrectly on the party ledger in the first place, it carries extra spaces or special characters, the party's address doesn't match the state the GSTIN's first two digits point to, or the supplier changed their registration without telling you. Fix it by cross-checking the GSTIN on the GST portal's Search Taxpayer, then correcting the party master so the state name/code and GSTIN agree.

Common causes

A GSTIN is a fixed 15-character structure — the first two digits are the state code, the next ten characters are the party's PAN, the 13th character is the entity/registration number, the 14th is a default "Z", and the 15th is a check code — so a mismatch is usually a data problem, not a Tally bug. The recurring causes: an incorrect GSTIN entered while creating the party ledger, extra spaces or special characters carried over from a copy-paste, the party's address not matching the state the GSTIN's opening two digits indicate, and a supplier who has since changed their registration without telling you.

How to fix it

Verify against the portal before changing anything in Tally, then correct the party master:

  1. Search the GSTIN on the GST portal's Search Taxpayer tool and confirm the trade name and state code against what's in Tally.
  2. Update the party ledger in Tally with the verified GSTIN, and make sure the state name/code on the ledger matches the GSTIN's opening two digits.
  3. Re-select the corrected party ledger in any existing vouchers that used the wrong one.
  4. Use Tally's Error or Exception Reports to confirm the correction cleared the mismatch.
How Charter AI does this

Charter AI runs a GSTIN's format and check digit against the party record before a voucher is marked ready to post — a mismatch is flagged in the review queue, deterministically, rather than surfacing later as a Tally rejection. The GSTIN/PAN checksum logic is code, not something asked of a model.

Start free 7-day trial

FAQs

What are the parts of a GSTIN, in order?

State code (first 2 characters), the party's PAN (next 10 characters), an entity/registration number (13th character), a default "Z" (14th character), and a check code (15th character) — per Tally's own glossary.

The GSTIN is right but the state doesn't match — what does that mean?

The GSTIN's first two digits are tied to the state it was registered in, so if the party master's address is in a different state, either the address or the GSTIN is wrong for this party and needs checking against the portal.

Can a supplier's GSTIN change over time?

Yes — a supplier can change or update their registration; tallyatcloud's guidance lists an outdated GSTIN (the supplier changed registration without updating you) as one of the recurring mismatch causes.

Related guides

Sources checked

Last reviewed 2026-09-23

Tally, Vyapar and other product names are trademarks of their respective owners. Charter AI is not affiliated with them.