E-Invoicing & E-Way Bill Compliance

Effective 1 August 2023 (Notification No. 10/2023–Central Tax), e-invoicing is mandatory for any registered person whose Aggregate Annual Turnover (AATO) has exceeded ₹5 crore in any financial year from 2017-18 onwards. The threshold has been reduced progressively since e-invoicing was first introduced in October 2020 — starting at ₹500 crore and stepping down through ₹100 crore, ₹50 crore, ₹20 crore, and ₹10 crore before reaching the current ₹5 crore level. Businesses should not assume the threshold will stay at this level indefinitely; it has changed roughly every 12–18 months historically.

The AATO threshold is calculated on a consolidated, all-India basis across every GSTIN registered under the same PAN — not separately for each individual GSTIN. A business with three GSTINs in three different states, each individually below ₹5 crore, is still liable for e-invoicing across all three GSTINs if the combined PAN-level turnover exceeds ₹5 crore.

Certain categories are excluded from e-invoicing by specific CBIC notification regardless of turnover: SEZ units (as suppliers), insurance companies, banking companies and financial institutions including NBFCs, goods transport agencies (for GTA road transport services specifically), passenger transportation service providers, and multiplex/cinema exhibitors supplying admission to films. These exclusions are narrow and category-specific — a business in an adjacent sector should not assume the exemption extends to it.

An Invoice Reference Number (IRN) is a unique 64-character hash generated by the Invoice Registration Portal (IRP) when your invoice data is successfully validated and registered. It is derived from your GSTIN, invoice number, financial year, and document type, and it uniquely identifies that specific invoice in the GST system nationally. Your own internal invoice numbering (Series A, INV-2026-001, etc.) continues as before — the IRN is an additional identifier assigned by the government system, not a replacement for your invoice number.

Yes, but only within 24 hours of IRN generation, and only if the underlying goods or services have not yet been supplied and no e-way bill has been generated against it (or the e-way bill is also cancelled). After 24 hours, the IRN cannot be cancelled on the portal — any correction must be made through a credit note, debit note, or amendment reflected in your GSTR-1, following the standard GST amendment process rather than IRP cancellation.

No — e-invoicing under Rule 48(4) currently applies only to B2B supplies, exports, and deemed exports. However, a separate and distinct requirement — the Dynamic QR Code for B2C invoices — applies to notified large taxpayers (presently those with AATO above ₹500 crore) issuing invoices to unregistered (B2C) customers, requiring a QR code that facilitates digital payment, though this does not involve IRN generation through the e-invoicing IRP.

An e-way bill is required under Rule 138 whenever the consignment value of goods being moved exceeds ₹50,000 — whether the movement arises from a sale, a stock transfer, a job-work despatch, a return, or any other reason. This threshold applies broadly across inter-state and intra-state movement, though a small number of States have historically prescribed different (sometimes lower, sometimes higher intra-state) thresholds for specific goods categories, so state-specific rules should always be checked for intra-state movement.

Validity is calculated from the time of e-way bill generation, based on distance: broadly one day of validity for every 200 km (or part thereof) of distance for normal cargo, with a shorter distance-per-day slab applicable for over-dimensional cargo. If the goods have not reached their destination before expiry, the transporter or consignor must extend the validity on the portal before expiry (or within a limited window afterward, in specified circumstances), stating the reason — transhipment, traffic delay, natural calamity, or law-and-order disruption are typical accepted reasons. Goods found moving on an expired e-way bill are treated as though no e-way bill exists at all, exposing them to detention.

Goods (and often the vehicle) can be detained and seized under Section 129 of the CGST Act. Release is generally conditional on payment of the applicable tax and a penalty — commonly cited as equal to 200% of the tax payable for taxable goods where the owner comes forward (or a different computation for exempt goods), or a bank guarantee for an equivalent amount, before goods and vehicle are released. Prolonged non-payment or repeated violation can escalate towards confiscation proceedings under Section 130 in more serious cases.

Effective 1 April 2025, taxpayers with AATO of ₹10 crore or more must report their e-invoices (invoices, credit notes, debit notes) to the IRP within 30 days of the document date. Any attempt to report a document older than 30 days is rejected by the portal, and the taxpayer must instead issue a fresh document. This requirement does not currently apply to taxpayers below the ₹10 crore AATO threshold, though — consistent with the pattern of past threshold reductions — it may be extended to lower-turnover taxpayers in future.

Yes. For taxpayers who are e-invoice-liable, credit notes and debit notes issued in relation to a B2B supply above the notified threshold also require IRN generation on the IRP, on the same basis as the original tax invoice. This is a frequently missed requirement because businesses associate e-invoicing primarily with sales invoices and treat credit/debit notes as an internal accounting adjustment rather than a document requiring separate IRP reporting.

Yes. Export invoices — whether under LUT/Bond (without payment of IGST) or with payment of IGST — require IRN generation for taxpayers who are e-invoice-liable, in the same way as domestic B2B invoices. The export invoice details reported to the IRP should align with the shipping bill and other customs documentation to avoid discrepancies that can delay export benefit processing, including GST refund claims on export supplies.

The QR code embedded on an e-invoice by the IRP encodes key invoice parameters — supplier GSTIN, buyer GSTIN, invoice number and date, invoice value, number of line items, HSN code of the main item, and the IRN itself — in a machine-readable format. It allows any party (the buyer, a GST officer, or an auditor) to verify the invoice's authenticity by scanning it, without needing to separately query the IRP database. The QR code must be printed on the invoice copy provided to the buyer.

Yes, for notified taxpayers, Part A of the e-way bill (invoice details, goods description, value) can be auto-populated directly from the e-invoice/IRN data at the time of IRN generation, if the supplier opts for this integrated flow. However, Part B — the vehicle number and transporter details — still needs to be entered separately once the mode of transport and vehicle are finalised, typically at the point of dispatch. Since March 2024, for notified categories, the e-way bill document details must correspond to the linked e-invoice IRN, closing an earlier gap where the two records could diverge.

Under Rule 138, the e-way bill can be generated by the consignor (seller), the consignee (buyer), or the transporter, depending on who causes the movement of goods and who is registered on the e-way bill portal to do so. If neither the consignor nor consignee generates it and the value exceeds ₹50,000, the transporter is required to generate the e-way bill for road transport, based on the invoice or other document provided to them. Contractual clarity — recorded in the purchase order or transport agreement — on who is responsible avoids a gap where each party assumes the other will generate it.

For a stock transfer or any movement 'for reasons other than supply' — such as moving goods between your own branches, sending goods for job work, or moving goods to an exhibition — a Delivery Challan is used instead of a tax invoice as the supporting document, and the e-way bill is generated referencing that challan, with the appropriate 'reason for transportation' selected on the portal (e.g., 'Own use', 'Job work', 'Exhibition or fairs'). GST implications differ from a sale, and the underlying transaction type must be correctly classified before the e-way bill is generated.

2FA requires users to confirm login with a one-time password sent to a registered mobile number, in addition to the standard username and password, when accessing the e-way bill or e-invoice systems. It has been progressively rolled out as mandatory, starting with larger AATO taxpayers and extended over successive phases to a wider set of taxpayers. Businesses should check their current applicability status directly on the e-way bill portal, since the rollout has continued in phases and the exact taxpayer segment covered has expanded over time.

The IRP validates the invoice against the schema fields you submit, including HSN/SAC codes, but it does not independently verify whether the HSN code you have used is the objectively correct classification for your goods or services — that classification responsibility remains with the taxpayer. An incorrect HSN code that nonetheless passes IRP validation can still result in a GST demand later if the tax authority reclassifies the goods and finds a different (often higher) rate applicable, along with interest and possible penalty.

Software (whether an ERP module, GSP-provided API, or standalone e-invoicing tool) handles the mechanical generation of IRNs and e-way bills reliably once correctly configured — but it does not determine whether your business is presently liable, correctly classify your exemption status, catch a credit-note gap, or advise on the tax consequence of a misclassified stock transfer. Software executes the transaction; it does not make the judgment calls around applicability, exemption, and process design that determine whether the transactions it is executing are actually correct.

A GST Suvidha Provider (GSP) is a GSTN-authorised third-party technology provider offering an API layer between a business's ERP/accounting software and the GST/e-invoice/e-way bill systems, so invoices and e-way bills can be generated programmatically rather than through manual portal data entry. A GSP is not mandatory — you can enter invoices manually on the government portals — but for any business generating more than a handful of invoices a day, manual entry does not scale and a GSP integration (or a billing software with native GSP connectivity) becomes operationally necessary.

No government fee is charged for generating an IRN on the e-invoice portal or an e-way bill on the NIC e-way bill portal — both are free government services. Costs arise instead from GSP subscription fees (if you use a third-party API layer), ERP/software licensing or customisation costs to integrate with the IRP and e-way bill systems, and professional fees for the CA-led applicability assessment, process design, and ongoing compliance support.

We coordinate an immediate response: reviewing the specific defect alleged (expired validity, mismatched vehicle number, missing Part B, or a genuinely missing e-way bill), preparing the explanation and supporting documentation (IRN, e-way bill copy, invoice, transport documents), and representing the business's position to the detaining officer or in the subsequent proceedings under Section 129, aiming for the fastest possible release of goods and vehicle while managing the underlying tax and penalty exposure correctly.

No. E-invoicing does not replace GSTR-1 — it feeds into it. Once an invoice is registered on the IRP, its key details are auto-populated into the corresponding GSTR-1 return, reducing manual re-entry and the associated risk of transcription error. GSTR-1 must still be reviewed and filed by the due date; auto-population is a data-entry convenience, not a substitute for the taxpayer's filing obligation or for reviewing that the auto-populated data is complete and correctly reflects all outward supplies, including any not captured by e-invoicing (such as B2C supplies).

A B2B customer of an e-invoice-liable supplier is entitled to expect a properly IRN-validated invoice with the QR code, because without it, the invoice may not be treated as a valid tax invoice for the customer's own input tax credit claim. If your business is e-invoice-liable and an invoice is issued without the IRN due to a system failure or oversight, the correct fix is to generate the IRN retrospectively where the reporting window still permits it, or issue a corrected/replacement invoice — not to argue the point with the customer, since their concern about ITC eligibility is well-founded.

Yes. A business below the current ₹5 crore AATO threshold can voluntarily register for and use the e-invoicing system ahead of any mandatory requirement, though this is uncommon in practice given the additional process discipline required. More commonly, businesses approaching the threshold from below choose to build the process and software integration in advance of crossing it, so the transition happens smoothly rather than under time pressure once the obligation becomes mandatory.

Yes. Any movement of goods where the consignment value exceeds ₹50,000 requires an e-way bill regardless of the underlying reason — this includes goods sent for repair, goods returned to a supplier, goods sent on approval basis, or goods moved for any purpose other than a sale. The 'reason for transportation' field on the e-way bill captures the specific nature of the movement (repair, return, sales return, etc.), and the supporting document is typically a delivery challan rather than a tax invoice for non-sale movements.

An e-way bill with a genuine, minor error (such as a small mismatch in the vehicle number due to a last-minute vehicle change that was not updated) is treated differently under departmental practice and case law from a wholly missing e-way bill, and several minor-discrepancy circulars and rulings have provided for a reduced penalty (commonly cited around a fixed amount rather than the full detention penalty) in specific minor-error scenarios. However, this is fact-specific and depends on the nature of the error, whether it appears to be a genuine clerical mistake versus an attempt at tax evasion, and the specific facts presented to the officer — it should never be assumed as a safe fallback.

GST rate changes affect the tax computation shown on the invoice and reported to the IRP, but they do not change the mechanics of e-invoicing or e-way bill generation themselves — the invoice must simply reflect whatever the correct rate is for the goods or services in question at the time of supply. Rate changes are periodically notified by the GST Council, and a business should ensure its billing software's rate master is updated promptly whenever a rate change is notified, since an e-invoice generated with a stale rate is still incorrect even if it passes IRP validation (the IRP checks schema, not rate correctness).

Both, depending on what the business needs. We offer a one-time applicability assessment and process/software setup for businesses that want to build internal capability, and an ongoing retainer-based service for businesses that want continuous monitoring, reconciliation, staff support, and query/detention handling. Most clients start with the setup engagement and move to an ongoing retainer once the process is live, since operational questions (extensions, corrections, threshold re-checks) tend to arise continuously rather than at a single point in time.

Part A of the e-way bill (Form EWB-01) captures the transaction details — GSTIN of supplier and recipient, place of dispatch and delivery, document number and date, value of goods, HSN code, and reason for transportation. Part B captures the transport details — vehicle number (for road transport) or transport document number (for rail, air, or vessel). An e-way bill is only fully valid for movement once both Part A and Part B are complete; Part A alone (sometimes generated automatically from an e-invoice) does not permit lawful movement of goods until Part B is also filled in.

The core ₹50,000 consignment value threshold and validity-period rules under Rule 138 apply uniformly for inter-state movement across India. For intra-state (within one state) movement, most States have adopted the same threshold and rules, but a small number of States have historically notified different thresholds, exemptions, or additional requirements for specific goods categories moving intra-state. A business moving goods primarily within one state should confirm the specific State's e-way bill notification rather than assuming the central rule is the complete picture.

Yes. The e-way bill system covers goods movement by any mode of transport — road, rail, air, or vessel (ship) — with Part B capturing the relevant transport document number for the mode used (for example, the railway receipt number for rail transport, or the airway bill number for air transport) instead of a vehicle registration number.

Immediate priorities are: (1) confirm the exact date turnover crossed the threshold and the applicable go-live date under the relevant notification; (2) register the GSTIN on the e-invoice system without delay; (3) obtain, at minimum, manual portal access to begin IRN generation on outstanding invoices even before a full ERP/API integration is complete; (4) review recent invoices issued without an IRN to determine any corrective action needed; and (5) begin ERP/GSP integration work in parallel so manual entry is a short-term bridge, not a permanent process.

Supplies to an SEZ unit or developer are generally treated as zero-rated supplies under GST and, for an e-invoice-liable supplier (the domestic supplier, not the SEZ recipient), such invoices typically fall within the e-invoicing requirement in the same way as other B2B supplies, since the exclusion under the e-invoicing notification applies to SEZ units as suppliers, not to suppliers making outward supplies to an SEZ. This distinction — SEZ as supplier (excluded) versus SEZ as recipient of a domestic supplier's outward supply (not excluded for the domestic supplier) — is frequently misunderstood.

The e-invoice schema (the technical specification for what data fields must be submitted and in what format) has been updated periodically by GSTN since the system's introduction, generally with advance notice and a transition window during which both old and new schema versions may be accepted. Businesses using GSP-integrated or actively maintained ERP software typically have schema updates applied by their vendor; businesses on older or custom-built systems bear the responsibility of tracking and implementing schema changes themselves.

Businesses should retain IRN registration records (including the signed QR code data), the complete e-way bill register (including Part A and Part B history and any extensions), and the underlying invoices, credit notes, and delivery challans, generally for the same retention period applicable to GST records overall — a minimum of 72 months (6 years) from the due date of filing the annual return for the relevant financial year, under the record-retention requirement of the CGST Act, or longer if litigation or an ongoing proceeding is pending.

Yes. For a UAE-headquartered business setting up Indian operations — whether a subsidiary, branch, or liaison arrangement — we coordinate the GST registration, e-invoicing and e-way bill system enrolment, and ERP/billing software setup for the Indian entity from our Chennai, Bangalore, or Hyderabad offices, while our Dubai office manages the UAE-side coordination, so the business deals with one team across both jurisdictions rather than separately briefing an India-based vendor.

PNPC charges a fixed, agreed professional fee for the applicability assessment, process design, and software integration support, confirmed in writing before work begins, with ongoing retainer options for continuous monitoring and support. The fee depends on the complexity of your existing billing software, the number of GSTINs and dispatch locations involved, and whether ongoing retainer support is included. We are not the lowest-cost option in the market — software-only vendors can generate an IRN or e-way bill for a lower fee — but a software vendor does not advise on applicability, exemption correctness, or process gaps the way a practising CA firm does.