GST e-invoicing and the e-way bill system are often handled by the same finance or ERP team, but they solve different compliance problems. An e-invoice is about authenticating specified invoice data through an Invoice Registration Portal and obtaining an Invoice Reference Number (IRN) and signed QR code. An e-way bill is primarily a document for movement of goods and carries consignment and transport details.
The distinction matters because one does not automatically replace the other. A transaction can require an e-invoice, an e-way bill, both, or neither, depending on the supplier, document, nature and value of the movement, and applicable exemptions.
What is an e-invoice under GST?
Under the e-invoicing model, the supplier first prepares the invoice in its own accounting or ERP system and reports prescribed data to an authorised Invoice Registration Portal (IRP). After validation, the IRP returns an IRN and digitally signed QR code. The GSTN-authorised IRIS IRP explains that e-invoicing currently covers specified documents such as tax invoices, debit notes and credit notes for notified taxpayers, principally for B2B and export transactions. See the official IRP e-invoice FAQ.
E-invoicing is therefore not simply the act of emailing a PDF invoice. The key compliance event is registration of the prescribed invoice data and generation of the IRN and signed QR code.
What is an e-way bill?
An e-way bill is linked to the movement of goods. The official e-way bill FAQ describes it as the document required for movement of a consignment in cases covered by section 68 of the CGST Act read with Rule 138. The general threshold described by the portal is a consignment value exceeding ₹50,000, subject to the rules, specified exceptions and special cases. See the official E-Way Bill System FAQ.
The e-way bill includes transaction and transport information. Depending on the case, it can be generated by the consignor, consignee or transporter. For road movement, vehicle details in Part B are generally important for a complete e-way bill, subject to prescribed exceptions.
E-invoice vs e-way bill: the practical difference
- Primary purpose: e-invoice authenticates prescribed invoice data; e-way bill supports compliance for movement of goods.
- Core output: e-invoicing produces an IRN and signed QR code; the e-way bill system produces an e-way bill number for the consignment.
- Who generates it: an e-invoice is generated through the supplier-side reporting process, while an e-way bill may be generated by the supplier, recipient or transporter as permitted by the rules.
- Trigger: e-invoice applicability depends on the notified e-invoicing framework and the document/transaction involved; e-way bill applicability turns on movement of goods, consignment value and the applicable Rule 138 conditions and exceptions.
- Transport details: vehicle or transporter information is central to e-way bill compliance but is not the basic purpose of invoice authentication.
Can both be required for the same transaction?
Yes. Consider a notified supplier making a taxable B2B sale of goods and dispatching those goods by road. If the invoice is within the e-invoicing mandate and the movement also meets the e-way bill requirements, the business may need both: first a valid e-invoice/IRN for the invoice and an e-way bill for the movement.
The systems are integrated enough to reduce duplicate entry in appropriate workflows, but integration does not erase the legal distinction. The IRP FAQ specifically discusses e-way bill generation in connection with e-invoice data and also explains that if an e-way bill is active, it may have to be cancelled before the related e-invoice can be cancelled.
Examples: when you may need one, both or neither
Example 1: B2B goods dispatch by an e-invoice-covered supplier
Assume a supplier covered by the e-invoicing mandate issues a B2B tax invoice for goods and the consignment is being transported in circumstances requiring an e-way bill. The supplier needs the e-invoice authentication process and the movement needs an e-way bill. This is the common both apply situation.
Example 2: service invoice with no movement of goods
A notified supplier may have an invoice that falls within the e-invoicing framework for a B2B service supply. There is no physical movement of goods merely because a service invoice exists, so the e-way bill question does not arise in the same way. This illustrates why e-invoice applicability should not be used as a proxy for e-way bill applicability.
Example 3: movement under a delivery challan
Goods can move for reasons other than an ordinary sale. The e-way bill FAQ recognises movement for reasons other than supply and refers to documents such as a delivery challan. In such a case, an e-way bill may be relevant even though there is no corresponding B2B tax invoice requiring an IRN for that movement.
What happens when details are wrong?
The correction logic is another area where teams confuse the two systems. The e-way bill FAQ states that a submitted e-way bill cannot simply be edited; if it contains wrong information, it generally has to be cancelled and generated afresh, while Part B can be updated in permitted situations. The portal states that cancellation must generally be done within 24 hours and is subject to conditions, including whether the e-way bill has been verified by a proper officer.
For e-invoices, the IRP FAQ similarly states that an e-invoice cannot be amended on the IRP and may be cancelled within the permitted 24-hour window. Where an active e-way bill is linked to that invoice, the IRP guidance says the e-way bill needs to be cancelled first before e-invoice cancellation can proceed within the allowed window.
A finance-team workflow that avoids confusion
- Classify the document: identify whether it is a tax invoice, debit note, credit note, bill of supply, delivery challan or another document.
- Test e-invoice applicability separately: check whether the supplier and document are covered by the current e-invoicing mandate.
- Test e-way bill applicability separately: determine whether goods are moving, the consignment value, the reason for movement and whether an exemption or special rule applies.
- Generate in the right sequence: where both apply, design the ERP process so validated invoice data can flow into the e-way bill process rather than being re-keyed.
- Validate master data: check GSTIN, document number, place of supply, HSN, taxable value, ship-to/dispatch-from details and transporter data before submission.
- Control cancellations: if an error is found, check both IRN and e-way bill status immediately because the 24-hour cancellation windows and linkage can affect the correction route.
- Retain evidence: preserve the invoice, IRN response, signed QR data, e-way bill number, transport updates and cancellation records as applicable.
Common mistakes
- Assuming that generating an e-invoice automatically means no separate e-way bill compliance is needed.
- Assuming every e-way bill must have an e-invoice behind it.
- Using the ₹50,000 e-way bill threshold as an e-invoice threshold.
- Treating a PDF invoice sent electronically as an e-invoice without checking IRN authentication.
- Ignoring the movement reason and delivery-challan scenarios when testing e-way bill applicability.
- Trying to cancel an IRN without first checking whether a linked e-way bill remains active.
Practical takeaway
Think of e-invoicing as invoice authentication and the e-way bill as goods-movement compliance. Test the two requirements independently for every transaction, then integrate them operationally when both apply. A good ERP control should decide document type, e-invoice applicability and e-way bill applicability separately before dispatch, while using common master data to avoid mismatches.
