Updated 11 November 2026. A practical guide for businesses and software teams, not legal advice. Technical specifications will be published on the e-way bill portal; follow them over any summary.
Short answer: according to a GSTN advisory dated 4 November 2026, from 1 January 2027 new e-way bill (EWB) numbers will have 14 digits instead of 12, and consolidated e-way bill (CEWB) numbers will have 11 digits instead of 10. The tax rules do not change. What changes is the number your software stores, validates, prints and sends through APIs. If your billing, ERP, transport or warehouse system assumes 12 digits anywhere, it may reject or cut off the new numbers.
Why the number is getting longer
GSTN says the current numbering capacity is close to running out because of the volume of e-way bills. CAalley reports that e-way bills grew from about 773.9 million in FY 2021-22 to about 1,419 million in FY 2025-26, and that September 2026 set a monthly record. Longer numbers add capacity without changing how the system works.
What changes and what does not
| Item | Before | From 1 January 2027 |
|---|---|---|
| E-way bill number | 12 digits | 14 digits |
| Consolidated e-way bill number | 10 digits | 11 digits |
| ₹50,000 threshold, validity, documents, tax rates | No change reported | |
Reports from StudyCafe and others say the new formats will first be released in the GSTN sandbox for testing, with technical details on the e-way bill portal. The advisory, as reported, does not describe how numbers already generated before 1 January 2027 will be handled, so plan for both lengths to exist in your data at the same time.
Who needs to act
- Businesses that generate e-way bills from their own billing or ERP software, directly or through a GSP.
- Software vendors and in-house teams that integrate with the e-way bill API or e-invoice API (where the EWB is generated with the IRN).
- Transporters and logistics apps that store EWB numbers, print them on LRs or update Part-B.
- Businesses using Excel templates, scanners or barcode labels that carry the EWB number.
If you only use the portal by hand, there is little to do beyond making sure your own records and spreadsheets do not cut off the longer number.
Software checklist
1. Database and data types
- Find every column that stores an EWB or CEWB number (invoices, dispatch, trips, LRs, audit logs, reports).
- If it is a
CHAR(12)/VARCHAR(12)or a fixed-width field, widen it. AVARCHAR(20)gives room for the future. - If it is stored as a number, check the type. 14 digits fit in a 64-bit integer (
BIGINT) but not in a 32-bit one. Storing it as text is usually safer, because it is an identifier, not a quantity. - Check Excel exports: long numbers can show in scientific notation. Format the column as text.
2. Validation rules
- Search the code for checks like
length == 12, regex^\d{12}$or^\d{10}$, and input masks on forms. - Change them to accept both the old and new lengths during the transition (12 or 14 for EWB, 10 or 11 for CEWB).
- Check mobile apps and driver apps too, not only the web backend.
3. API integration
- Read the updated API documentation once GSTN publishes it, and test in the sandbox.
- Check how your code parses the generate-EWB, update Part-B, extend validity, cancel and consolidate responses.
- If you use a GSP or an e-invoice vendor, ask them in writing when their update will be live and whether you need to change anything.
4. Printing and documents
- Check invoice, delivery challan and LR templates. A fixed-width field may wrap or cut off two digits.
- Check barcodes and QR codes that encode the EWB number.
5. Reports and reconciliations
- Matching logic between invoices, EWBs and GSTR-1 should not depend on number length.
- Search and filter fields in your software should accept 14 digits.
6. Test before 1 January 2027
- Create test records with 14- and 11-digit numbers in a staging system.
- Run a full cycle: generate, print, update Part-B, consolidate, cancel, report.
- Plan a freeze window over the year-end so no other release lands at the same time.
A simple timeline
| When | What to do |
|---|---|
| November 2026 | Find every place your systems store, check or print EWB and CEWB numbers. Ask your GSP or software vendor for their plan. |
| When the sandbox opens | Test generation, Part-B updates, consolidation and cancellation with the new lengths. |
| December 2026 | Release the change to production early in the month, train dispatch staff and transporters, and keep a rollback plan. |
| 1 January 2027 onwards | Check the first few 14-digit numbers end to end: invoice print, LR, reports and reconciliation. |
Common mistakes to avoid
- Fixing only the screen: widening the input box but leaving a 12-character database column or API model behind it.
- Dropping leading zeros: treating the number as an integer in one place and as text in another, which breaks matching.
- Forgetting third parties: transporters, warehouse partners and customers' portals may also read your EWB numbers.
- Assuming only new code is affected: old reports, scheduled exports and scripts written years ago often contain hard-coded lengths.
Other e-way bill changes to track
This is separate from the proposed Ship-to GSTIN and closure changes, which we covered in our post on e-way bill Ship-to GSTIN and closure rules. If you generate e-invoices too, our post on e-invoicing for reverse charge and import of services from 2027 lists another change landing on the same date. For a wider view, see our GST billing software checklist.
Need help updating your system?
Nextinera builds and maintains ERP, billing and GST API integrations. We can audit your code and database for 12-digit assumptions and test the change in sandbox before January. Book a free call.