Figment Global Solutions
API

E-Way Bill Number Changes to 14 Digits from 1 January 2027: What ERP, API and Transport Teams Must Update

E-way bill numbers move to 14 digits and consolidated EWB numbers to 11 from 1 Jan 2027. What ERP, API and transport teams must update, with a checklist.

Figment Global Solutions logoFigment Global Solutions 7 min read
Illustration showing a 12-digit e-way bill number changing to a 14-digit e-way bill number from 1 January 2027

The e-way bill number moves to 14 digits from 1 January 2027. In an advisory dated 4 November 2026, GSTN announced that e-way bill (EWB) numbers will grow from 12 digits to 14 digits, and consolidated e-way bill (CEWB) numbers from 10 digits to 11 digits. GSTN says the reason is volume: at the current rate of generation, the existing numbering range is expected to run out.

The tax rules do not change. Section 68 of the CGST Act and Rules 138 to 138D still decide when an e-way bill is needed, how long it is valid and how Part A and Part B work. What changes is the number itself, and that affects every system that stores, validates, prints or passes it on: ERPs, transport management systems, warehouse apps, GSP connections, reports and Excel templates.

What GSTN has announced

ItemUp to 31 Dec 2026From 1 Jan 2027
E-way bill number (EWB-01) 12 digits 14 digits
Consolidated e-way bill number (EWB-02) 10 digits 11 digits
Who should act Taxpayers, GSPs, ERP and software vendors, API integrators Same
Testing GSTN says the change will be released in the e-way bill sandbox "shortly" Details to be published on the e-way bill portal

The advisory asks stakeholders to update applications, APIs, database schemas and validation rules, and to be ready well before 1 January 2027. It describes the new formats as "proposed" and says sandbox details will follow on the e-way bill portal. As of 16 November 2026, no detailed technical specification or sandbox release had been published, so details such as whether the extra digits carry any meaning are still awaited. Plan on the stated lengths and watch the portal for the final specification.

What does not change

  • The e-way bill threshold (consignment value above ₹50,000, with some States using a different limit for intra-State movement).
  • Validity rules: one day per 200 km for regular cargo, one day per 20 km for over-dimensional cargo.
  • Part A / Part B structure, vehicle updates, extension, cancellation within 24 hours and rejection within 72 hours.
  • The advisory does not ask anyone to renumber existing e-way bills.

One point is still open: the advisory does not say how e-way bills generated in late December 2026 will be handled after the switch, for example when a Part-B update or validity extension is needed in January. Until GSTN publishes migration instructions, plan for both formats to exist side by side, and avoid generating long-haul e-way bills at the last minute on 31 December if you can.

Why a longer number can break working systems

Generating the e-way bill on the portal will work on 1 January 2027. The problems start when the number comes back to your systems. A few common failure points:

  • Fixed-length database columns. A field defined as CHAR(12) or VARCHAR(12) will reject or cut a 14-digit number. The e-way bill is valid on the portal, but your dispatch record holds a wrong number.
  • Validation rules. Screens and bulk-upload templates that check "exactly 12 digits" will stop users entering a valid new number, for example when a transporter shares a 14-digit EWB for an inward consignment.
  • Numeric fields. Some systems store the EWB number as a number, not text. A 14-digit value can overflow a 32-bit integer field, and Excel may show it in scientific notation if the column is not formatted as text.
  • API mapping. Request and response mappings between your ERP, middleware and GSP may assume the old length. This includes the e-way bill number returned when you generate an e-way bill from an IRN.
  • Print layouts. Invoice, delivery challan and gate pass templates may have a fixed-width box for the EWB number.
  • Downstream reports. Dispatch registers, logistics MIS, reconciliation tools and audit exports may join tables on the EWB number. A truncated number breaks the match.
  • Consolidated EWBs. Transporters and trip-sheet software must handle 11-digit CEWB numbers as well.

Mixed data is the other risk. From January, your systems will hold old 12-digit and new 14-digit numbers side by side, at least in historical records. Any logic that infers something from the length of the number needs to handle both.

Who needs to do what

TeamWhat to check and update
IT / ERP team Field lengths in SAP, Oracle, Tally customisations and in-house systems; validation rules; middleware mappings
GSP / API integrator Confirm the GSP's January release supports 14-digit EWB and 11-digit CEWB numbers in every API: generation, Part-B update, extension, cancellation, consolidated EWB and lookup
Logistics and transport TMS, trip sheets, driver apps and gate entry systems; consolidated EWB handling
Tax team E-way bill vs GSTR-1 / e-invoice reconciliation logic; reports used for audit and notices
Warehouse / stores Inward consignment entry screens where supplier or transporter EWB numbers are keyed in
Finance / MIS Excel templates, Power BI or other dashboards that store or join on EWB numbers

Readiness checklist before 1 January 2027

  • List every system that creates, stores, receives, prints or reports an EWB or CEWB number.
  • Widen database fields. A text field of 15 or more characters gives headroom for future changes.
  • Store EWB numbers as text, not numbers, in databases and spreadsheets.
  • Update validation rules to accept both 12-digit and 14-digit EWB numbers, and both 10-digit and 11-digit CEWB numbers.
  • Check API request and response mappings, including e-way bill details returned with e-invoice (IRN) generation.
  • Update print layouts for invoices, delivery challans and gate passes.
  • Get written confirmation from your GSP and ERP vendor that their release supports the new formats, and when it goes live.
  • Test in the e-way bill sandbox once GSTN releases the change: generate, update Part B, extend, cancel, consolidate and fetch.
  • Run a test with a dummy 14-digit value through every report and reconciliation.
  • Plan a support desk for the first week of January for dispatch and gate teams.
  • Brief transporters and key customers that new e-way bills will carry longer numbers.

Practical example

A manufacturer generates around 2,000 e-way bills a month from SAP through a GSP. Its custom dispatch table stores the EWB number in a 12-character field, and its gate pass print has a 12-character box. If nothing changes, on 2 January 2027 the GSP returns a 14-digit number, the custom table saves only the first 12 characters, and the gate pass prints the wrong number. If the vehicle is stopped for checking, the number on the paper does not match the portal. Fixing the field length and the print layout in December avoids both problems.

How Figment's e-way bill API handles it

Figment's e-Way Bill API runs through Figment's GSTN-authorised GSP. It covers e-way bill generation, generation from an IRN, Part-B and vehicle updates, multi-vehicle movement, validity extension, transporter updates, cancellation, consolidated e-way bills and lookup. A sandbox is available for testing, and requests can switch to NIC backup portals if the primary portal is unavailable.

For tax teams, GSTCPC fetches e-way bill and e-invoice data for all GSTINs through Figment's GSP, alongside GSTR-2A, GSTR-2B and IMS data. Companies connecting several GST systems can see Figment's GST API integration options for SAP, Oracle and Tally.

Key takeaways

  • From 1 January 2027, e-way bill numbers have 14 digits and consolidated e-way bill numbers have 11 digits.
  • The e-way bill rules, thresholds and validity do not change. Only the number format does.
  • The risk is in your own systems: field lengths, validations, API mappings, print layouts and reports.
  • Systems must accept both old and new formats, because 2026 e-way bills keep their 12-digit numbers.
  • Test in the sandbox as soon as GSTN releases it, and get your GSP and ERP vendor to confirm readiness in writing.

Frequently Asked Questions

From 1 January 2027, as per GSTN's advisory dated 4 November 2026. Consolidated e-way bill numbers will move from 10 to 11 digits on the same date.

Share this article

Compliance support

Need Help with Compliance?

Tell us which returns are hurting.

Our team will walk through it with you...