Document intelligence · Documents

Invoice OCR India

An Indian invoice and tax-document dataset concept with layout regions, field transcription and structured line-item tables.

Catalogue statusIllustrative custom specification

Reference volumeIllustrative 32K-page specification

Delivery modelScoped pilot → versioned production

Designed for

Document-AI teams building invoice extraction, accounts-payable automation and OCR evaluation systems.

Every specification is adapted to the buyer's model, production environment, data rights and measurable acceptance criteria.

Primary use cases

Invoice field extraction
GSTIN and tax-value recognition
Line-item table understanding
OCR correction and benchmarking

Annotation schema

Labels tied to model behaviour.

vendor name and address
GSTIN
invoice number and date
subtotal and tax fields
line-item rows and columns
currency and totals
document quality attributes

Coverage design

Variation before volume.

GST and non-GST invoice layouts
Scans, mobile photos and native PDFs
Printed, stamped and handwritten additions
English and selected Indian-language text
Skew, blur, shadows and damaged documents

Quality target

Target: ≥99% character accuracy on audited priority fields

Targets are agreed during scoping and reported only after measurement on the applicable delivery.

Quality controls

Double-entry transcription for critical fields
Field-level exact-match audit
Table-structure validation
Arithmetic consistency checks
Template and vendor distribution analysis

Delivery format

JSONL, CSV, PDF/JPEG and optional layout JSON

Buyer-specific schema and storage requirements can be incorporated before production.

Example file package

01documents/

02records.jsonl

03line_items.csv

04schema.json

05dataset_card.md

06field_quality_report.csv

Documentation included

Evidence travels with the files.

Field dictionary and normalization rules
Source, consent and confidentiality context
PII and sensitive-field treatment
Per-field quality metrics
Template coverage and known failure modes

Known limitations

What buyers should understand.

Illustrative specification with no claim of pre-cleared document rights
Sensitive business data requires a project-specific handling plan
Tax and accounting rules must be confirmed by the buyer

Build from this pattern

Turn your requirement into a pilot.

Share the model objective, target environment, approximate volume and delivery constraints. We will respond with the questions needed to scope a credible dataset.

Request this dataset pattern ↗