Extract supplier and buyer GSTINs from invoices using AI
Dynamite Docs- Supplier GSTIN
- 27AABCS1429B1ZP
- Customer (Billed-to) GSTIN
- 27BAAFG2874Q1ZX
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- 01Upload documents
- 02Structural format check
- 03Export for your books
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
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.
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.
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.
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
What gets extracted from the GSTIN block
Dynamite Docs- Supplier GSTIN
- 27AABCS1429B1ZP
- Customer (Billed-to) GSTIN
- 27BAAFG2874Q1ZX
- Format review status
- Pattern pass; source review required
Each GSTIN is organized into components and checked against structural rules:
Understanding the 15-character GSTIN structure
Dynamite Docs- Supplier GSTIN
- 27AABCS1429B1ZP
- Customer (Billed-to) GSTIN
- 27BAAFG2874Q1ZX
- Format review status
- Pattern pass; source review required
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.
- 01Invoice arrives
- 02Forward attachment
- 03Extract and review
- 04Export to your workflow
Questions, answered
The system checks length and expected character positions, which can flag some OCR mistakes. A pattern pass is not the same as portal validation or proof of ownership, so compare the value with the document and your approved party master.
In "Bill To / Ship To" transactions, the buyer billing GSTIN and shipping consignee GSTIN are extracted into distinct, role-tagged columns so they do not get mixed up.
No. This workflow extracts visible document fields and checks the GSTIN structure. Cryptographic QR validation and portal verification are separate controls.
GSTIN is a key match field between a purchase record and supplier-reported data. Accurate capture reduces avoidable mismatches, but input tax credit eligibility depends on additional document, transaction and compliance conditions reviewed by your tax team.
Extraction guides
Related document workflows
Extract HSN and SAC codes beside their item descriptions with AI
Extract HSN and SAC codes with AI in Dynamite Docs. Review printed codes beside item descriptions, taxable values, and rates on Indian GST invoices.
Extract CGST, SGST, IGST, and cess into separate columns with AI
Extract CGST, SGST, IGST, and cess with AI in Dynamite Docs. Review separate tax columns against taxable values and totals on Indian GST invoices.
Extract GST invoice fields using AI for Rule 46 review
Extract Indian GST invoice fields with AI in Dynamite Docs for Rule 46 review. Check GSTINs, invoice dates, taxable values, and tax against the source.
Extract IRN, QR fields, and tax amounts from e-invoices using AI
Extract IRN, QR fields, GSTINs, and tax from Indian e-invoices with AI in Dynamite Docs. Review captured values against the source before export.
From the blog
Build a Tally invoice import workflow using AI-extracted data
Build a Tally import workflow with AI-extracted GST invoices from Dynamite Docs. Map reviewed rows to masters and voucher fields, then test and reconcile.
How to extract document data with LLM models and your own keys
Learn document extraction with your own LLM API keys in Dynamite Docs. Connect a provider, choose a model, check policies and PE rules, and review a test run.
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.