Bulk E-Way Bill Generation: Complete Guide

Quick answer: Bulk e-way bills are generated by filling the official Excel-based Bulk Generation Tool, converting it to a JSON file and uploading it on the portal, or through an authorised API/GSP integration. Valid records are generated and failed ones reported for fixing and re-upload. Bulk generation is not a claimed feature of the E-Way Easy app.

If your dispatch desk makes 40 e-way bills a day, typing each one into the portal is slow and error-prone. Bulk generation lets you prepare the data once in a structured sheet and upload it together. It also lets one bad row turn into one failed e-way bill rather than a delayed truck — if you know how to read the results and retry safely.

This guide explains the official bulk route in general terms, how to prepare and check data, and how to deal with errors. It also makes clear what E-Way Easy does and does not do.

Three different things

People use "bulk e-way bill" to mean three separate things. Keep them apart.

If someone offers you bulk generation, ask which of these three they mean. Only the second actually produces e-way bills in bulk.

What bulk generation means on the official portal

The official e-way bill system provides a bulk generation facility:

1. Download the official Bulk Generation Tool (an Excel-based utility) from the portal.
2. Fill one row per e-way bill (with item rows as the tool requires) in the tool's format.
3. Use the tool to validate the sheet and convert it to a JSON file.
4. Log in to the portal, choose the bulk generation option, and upload the JSON file.
5. The portal processes each record and shows which e-way bills were generated and which records failed, with reasons.
6. Download or print the generated e-way bills and share each e-way bill number with the transporter or driver.

The portal also offers bulk options for some other functions, such as updating Part B or generating consolidated e-way bills. Which bulk operations are available at any time is listed in the user documentation.

The tool's exact layout, sheet names and field formats are set by the portal and can change. Always download the latest version from the official portal and follow the user documentation. Do not reuse an old copy of the tool indefinitely.

Large taxpayers usually connect their ERP to the e-way bill system via API, either directly (where eligible) or through a GST Suvidha Provider (GSP). That is system-to-system integration with its own registration, credentials and security requirements. The ERP sends e-way bill data when the invoice is finalised and receives the e-way bill number back, so there is no manual upload at all. In return it needs:

• API access registration on the e-way bill portal,
• a compatible ERP or GSP solution,
• IT effort to map fields and handle errors.

For most small and mid-sized businesses, the portal's bulk tool is the more practical route.

The e-invoice route

If your business must issue e-invoices, the e-way bill can be generated using the IRN. Part A is auto-populated from the e-invoice data, so you mostly add transport details. When your ERP produces e-invoices in bulk, e-way bills can often follow in the same process — another way of getting volume without a separate JSON upload.

Who benefits

• Manufacturers and distributors dispatching many invoices daily from one location.
• Traders who make invoices in accounting software and want to avoid re-typing.
• Transporters' clients who send many small consignments to different buyers.
• Businesses that dispatch in a batch at fixed times (morning loading, evening loading).

When it is useful — and when it is not

Example (illustrative): a Nagpur FMCG distributor has 48 invoices to dispatch by 10 am. At around 4 minutes to key in and check each bill, single entry takes over 3 hours. Exporting the invoices from billing software into the bulk tool, validating, converting, uploading and reviewing results might take around 30 minutes. Actual timings depend on your data quality and connection, but the gap widens as volume grows.

Preparing structured data

Good bulk generation is 80% data preparation. Every row needs the same fields you would type manually (see Documents and Data Required).

Fix your masters first

Most failed rows trace back to the customer and item masters in your billing software, not to the upload itself. Before your first upload:

• Standardise and verify GSTINs in the customer master. One wrong character fails the record.
• Fix HSN codes at item master level, at the digit length that applies to your turnover.
• Use actual dispatch and delivery PIN codes, not billing addresses.
• Keep date formats consistent with what the tool expects.

Our article on preparing invoice data for bulk processing goes into this in more detail.

Common fields

• Supply type and sub-type
• Document type, number and date
• Supplier GSTIN, name, dispatch-from address, PIN, state
• Recipient GSTIN (or URP), name, ship-to address, PIN, state
• Item lines: product name, description, HSN, quantity, unit, taxable value, tax rates and amounts
• Total invoice value and consignment value
• Transport mode, approximate distance, Transporter ID, transport document number and date, vehicle number

Validations to run before upload

Run these checks in your sheet before converting to JSON. Each one prevents a failed record.

Example (illustrative): a morning batch

A Morbi tile distributor (GSTIN 24ABCDE1234F1Z5) has 22 invoices for the morning loading. Before upload, the sheet checks find:

• 1 duplicate row (invoice MT/0912 entered twice) — removed.
• 1 recipient with state code 27 but an address in Gujarat — buyer called, correct GSTIN obtained.
• 2 rows with IGST for intra-state buyers — corrected to CGST + SGST.

The cleaned 21 rows are converted to JSON and uploaded. The portal generates 20 e-way bills; 1 fails because the distance entered was above the allowed margin. The team corrects that one row, saves it in a new file, and uploads only that record. Result: 21 e-way bills, no duplicates.

Common upload and validation errors (in plain words)

These describe situations, not specific error codes. Read the actual message the portal shows.

Reviewing results and failed records

After each upload:

1. Download or note the results: EWB numbers for successful records, error reasons for failures.
2. Match each EWB number back to its invoice in your register.
3. Separate failed records into a new sheet.
4. Do not share any e-way bill with a driver until its own record shows success.

Correcting and retrying safely

The goal is to retry only what failed and never create a second e-way bill for the same consignment.

• Remove successful rows before re-uploading. Upload a fresh file containing only the corrected failures.
• Never change the document number just to get past a "duplicate" message. That creates a second e-way bill for the same goods.
• If a record shows as failed but you suspect it was actually generated (for example, the session dropped mid-upload), search the portal for that document before retrying.
• If a wrong e-way bill was generated, cancel it within 24 hours and generate the correct one — see Cancellation.
• Keep the original and corrected files for your records.

Common mistakes

• Editing the JSON file by hand. Fix the sheet and regenerate the JSON with the tool instead.
• Re-uploading the whole file after partial errors, which invites duplicates for records already generated.
• Using an old version of the bulk tool after the portal has changed its format.
• Not reconciling. Match every e-way bill number generated back to your invoice list the same day.
• Leaving Part B blank in bulk and forgetting it. If vehicle details were not in the file, update Part B for each bill before the truck leaves; the e-way bill is not valid for movement without it (except the short-distance case allowed by the rules).

Security and privacy

Bulk files contain your buyers' GSTINs, addresses and sales values.

• Store files on business devices, not personal chat apps.
• Do not email JSON files to unknown "service providers".
• Limit portal logins to people who need them; use sub-users with limited roles where available.
• Keep the OTP device with a responsible person; multi-factor authentication now applies to all taxpayers.
• Delete old working files on a schedule your business follows.

Never bypass authentication or use unauthorised automation

Do not use scripts, browser bots or third-party tools that log in to the portal for you by capturing passwords, OTPs or captchas. This can breach the portal's terms, risk your credentials, and expose your data. If you need automated generation, use the official bulk upload or an authorised API/GSP integration with its own credentials.

Where E-Way Easy fits

E-Way Easy is a mobile app for creating one invoice and its e-way bill details at a time, with saved buyers and products, automatic HSN and distance, and a review step before completion. It does not claim bulk generation. For a business raising a handful of invoices a day, that single-invoice flow can be quicker than preparing upload files. For high-volume batches, use the official bulk tool or an authorised integration. The free quantity and tax calculator and HSN code lookup can help when checking rows in your sheet.

Official sources

Download the current Bulk Generation Tool and read the instructions on the official e-way bill portal and in the user documentation. For API access, follow the procedures published on the official portals.