What this checker looks at
Bulk generation on the portal works through a JSON file prepared with the official Excel-based bulk generation tool, or through an API connection via a GSP or ERP. When a few rows in a large file are wrong, you lose time fixing and re-uploading. This checker runs common checks on each row first:
- GSTINs: format and check digit for From and To GSTIN; URP is accepted for an unregistered recipient.
- State codes and PINs: state code against the first two digits of the GSTIN; PIN must be 6 digits and not start with 0.
- Document: valid date, not in the future and not older than 180 days from the generation date; no duplicate of the same document type, number and supplier GSTIN.
- Goods and values: HSN of 4–8 digits, quantity and taxable value above zero, IGST for inter-state and CGST + SGST for intra-state, CGST equal to SGST, and total value within ₹1 of taxable value plus tax.
- Transport: distance from 1 to 4,000 km, vehicle number or transporter ID for road movement (Part B), vehicle number pattern, and a 15-character transporter ID.
Example (illustrative)
A Rajkot pipe manufacturer prepares 120 invoices for the month-end dispatch. The checker shows that one invoice was dated 200 days earlier (cannot be used), two rows repeat the same invoice number, and a Gujarat-to-Gujarat row carries IGST. Fixing these in the sheet before preparing the JSON avoids rejected rows on the portal.
Common mistakes
- One row per item instead of one row per invoice, which shows up as duplicate documents.
- Excel dropping the leading zero from state codes such as 07 or turning PINs and HSN codes into numbers.
- Leaving the vehicle number blank and forgetting to update Part B later — the e-way bill cannot be used for movement without it, except within the state up to 50 km to or from the transporter.
For one-off invoices, the E-Way Easy app takes you from invoice to e-way bill on your phone. Learn more in the bulk e-way bill generation guide and common e-way bill errors.