Sections10
Reading time10 min
EvidenceDocument workflow

Answer in 30 seconds

Extract supplier and buyer GSTINs from Indian invoices with AI in Dynamite Docs. Keep party roles clear and check identifiers against the source.

Dynamite Docs logoDynamite Docs
The handoff
PARTY IDENTIFIERS: Supplier and buyer stay distinctUpload documents. Structural format check. Export for your books. Illustrative example, not extracted customer data.FROM SOURCE FILE TO A RESULT YOU CAN USEPARTYIDENTIFIERSReview workspaceSupplierand buyerstay…1Upload documents2Structural formatcheck3Export for yourbooks
  1. 01Upload documents
  2. 02Structural format check
  3. 03Export for your books
Check all 15 characters Illustrative example.

Supplier and buyer GSTIN checks

  • Matching purchase bills against portal records requires exact GSTINs. A typo in either the supplier or buyer GSTIN prevents automatic matching.
  • Standard OCR software often confuses similar characters in 15-digit strings, such as swapping "8" with "B", "0" with "O", or "1" with "I".
  • In "Bill To / Ship To" transactions, the billing customer GSTIN determines the tax regime while the consignee GSTIN marks physical delivery.
  • Some e-invoices display a signed QR code as well as printed identifiers, creating two visible sources that may need separate review.

How GSTINs are extracted and checked

01

Upload documents

Add digital PDFs, scanned purchase bills, e-invoices, or e-way bills. Digital files use embedded text directly when present, without OCR on those pages.

02

Extract role-tagged GSTINs

The system identifies supplier, customer (billed-to), and consignee (shipped-to) GSTINs as distinct fields rather than merging them into one column.

03

Structural format check

Each proposed GSTIN is checked for the expected length and character positions. Values that do not fit the pattern are flagged for source review.

04

Export for your books

Export reviewed GSTIN fields to Excel, CSV or JSON, or push them to Google Sheets for purchase-register matching and master-data review.

Document types this workflow handles

B2B GST invoicessupplier and buyer GSTINs with state codes
E-invoices (IRP signed)printed GSTINs captured for source review
E-way bills (NIC)consignor, consignee, and transporter GSTIN records
Bill To / Ship To invoicesseparate billing buyer and shipping consignee GSTINs

What gets extracted from the GSTIN block

Dynamite Docs logoDynamite Docs
Inside the output
PARTY IDENTIFIERS: Supplier and buyer stay distinctSupplier GSTIN: 27AABCS1429B1ZP. Customer (Billed-to) GSTIN: 27BAAFG2874Q1ZX. Format review status: Pattern pass; source review required. Illustrative example, not extracted customer data.Source-linked field inspectorPARTY IDENTIFIERS27AABCS1429B1ZP27BAAFG2874Q1ZXPattern pass; source revie…Supplier GSTIN27AABCS1429B1ZPCustomer (Billed-to) GSTIN27BAAFG2874Q1ZXFormat review statusPattern pass; source reviewrequired
Supplier GSTIN
27AABCS1429B1ZP
Customer (Billed-to) GSTIN
27BAAFG2874Q1ZX
Format review status
Pattern pass; source review required
Check all 15 characters Illustrative example.

Each GSTIN is organized into components and checked against structural rules:

Supplier GSTIN27AABCS1429B1ZP
Customer (Billed-to) GSTIN27BAAFG2874Q1ZX
Consignee (Shipped-to) GSTIN07AAECU4471L1ZF
State code (digits 1-2)27 (Maharashtra) / 07 (Delhi)
PAN component (digits 3-12)AABCS1429B (5 letters, 4 numbers, 1 letter)
Entity & check characters (13-15)1ZP (Entity 1, default Z, check P)
Trade / legal registered nameShri Balaji Traders
Format review statusPattern pass; source review required

Understanding the 15-character GSTIN structure

Dynamite Docs logoDynamite Docs
The review
PARTY IDENTIFIERS: Supplier and buyer stay distinctKeep party roles separate. Check all 15 characters. Verify registration separately. Illustrative example, not extracted customer data.SOURCE DOCUMENTPARTYIDENTIFIERSSupplier GSTIN27AABCS1429B1ZPCustomer (Billed-to) GSTIN27BAAFG2874Q1ZXFormat review statusPattern pass; source…Review before exportSupplier GSTIN27AABCS1429B1ZPCompare with the source on the leftAccept after reviewCheck all 15 charactersOriginal stays…
Supplier GSTIN
27AABCS1429B1ZP
Customer (Billed-to) GSTIN
27BAAFG2874Q1ZX
Format review status
Pattern pass; source review required
Check all 15 characters Illustrative example.

A GSTIN follows a strict 15-character structure: digits 1 and 2 indicate the state code (such as 27 for Maharashtra or 07 for Delhi); characters 3 to 12 represent the 10-character PAN of the business; character 13 indicates the entity registration number; character 14 is default "Z"; and character 15 is a checksum digit.

A structural check can catch the wrong length or a letter in a numeric position, but it has limits. A different 15-character value may still fit the pattern. If glare turns "8" into "B," or a blurred "0" into "O," use the confidence signal to find the field and then compare it with the source document. For supplier onboarding or filing, use the organization's approved registry or portal-check process as well.

Role tagging matters as much as character recognition. The GSTIN closest to a "Bill To" block should not automatically become the supplier value, and a delivery address may carry a consignee identifier that differs from the billed-to party. Keep the printed label, nearby name and address with each extracted value so the reviewer can resolve the role from context.

Build duplicate and mismatch checks around the reviewed export. Compare the supplier GSTIN with the vendor master, compare the buyer GSTIN with the entity receiving the invoice, and flag unexpected state-code changes. Preserve the raw extracted value separately from a corrected value, along with the reviewer and reason, so a later reconciliation can explain what changed.

GSTIN capture with model choice

Reading alphanumeric identifiers from mobile photos and scanned bills requires careful visual extraction. Every signed-in tier can connect a supported provider key, subject to the provider's own terms and limits.

Digital PDFs may expose embedded text, while scans need visual extraction backed by structural checks. Neither method proves that a GST registration is active or belongs to the printed name.

Reviewed GSTIN records can be exported to Excel, CSV or JSON, or pushed to Google Sheets when connected. Free and Starter own-key pages use monthly PE; Pro and Scale own-key runs do not consume PE.

Paid invoice intake · PRO and Scale

Stop downloading invoices from email.

Forward invoice attachments to your private Dynamite Docs address. They are stored in your account, extracted automatically, and placed in the dashboard for review and export.

  1. 01Invoice arrives
  2. 02Forward attachment
  3. 03Extract and review
  4. 04Export to your workflow
Automate invoice intakeIncluded from $59/month. Storage and processing limits apply.

Questions, answered

Extraction guides

Related document workflows

From the blog

Extract and verify your GSTINs

Upload an invoice or e-way bill, review the role-tagged GSTINs, and export the checked values for matching. Connect your own provider key on any signed-in plan; monthly PE rules still apply on Free and Starter.

Can we save optional cookies?

Essential cookies keep you signed in. With your permission, optional analytics cookies and masked session replays help us understand usage and diagnose errors. Privacy policy. Change your choice anytime in Cookie settings.