Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Auto-component Tier-1 suppliers run high-frequency JIT despatch to OEMs — dozens of part-specific consignments per day matched to the OEM line schedule under EDI 862 / 866 calls — and every single despatch crosses two parallel statutory gates: the e-invoice IRN under the IRP for any taxable supply by a registered person above the ₹5 crore turnover threshold, and the e-way bill under Rule 138 for any consignment whose value (single or aggregated by conveyance) exceeds ₹50,000; the two systems run independent 24-hour cancellation clocks, demand IRN-to-invoice-to-ASN-to-e-way-bill quantity tie-out, distinguish taxable supply from returnable-bin gate-pass movement under Rule 55, and apply different threshold logic when cross-state movements aggregate multiple sub-₹50,000 ASNs onto one truck.
Generate IRN on the IRP before truck departure; classify the despatch as taxable supply or returnable-bin Rule 55 movement; for taxable supply, generate single e-way bill if consignment value exceeds ₹50,000 or queue for consolidated e-way bill if multiple sub-threshold ASNs aggregate onto the same conveyance; tie IRN to ASN (EDI 856) on quantity and PO release; track the 24-hour cancellation clocks per IRN and per e-way bill independently; for returnable bin movement, issue Rule 55 delivery challan and e-way bill if value exceeds ₹50,000, no IRN; reconcile end-of-day to ASN dispatched, IRN generated, e-way bill issued and consolidated bills referenced; surface gaps to the OEM gate pass before the truck rolls.
Tier-1 GSTIN per plant; OEM GSTIN per ship-to; transporter master with GSTIN, transporter ID and conveyance plate; PO and PO-release master from EDI 830/862/866; ASN template (EDI 856) per OEM; IRN generation route per OEM and per invoice type; e-way bill template with Part-A (consignor/consignee/HSN/value) and Part-B (vehicle); consolidated e-way bill rule per conveyance; Rule 55 delivery challan series for returnable bins; cancellation watch on the 24-hour clock per IRN and per e-way bill.
An end-of-day despatch register tying every ASN to its IRN, e-way bill (single or consolidated), Rule 55 challan (if applicable), OEM gate-pass acknowledgement and EDI 856 transmit log; a 24-hour cancellation tracker for any IRN or e-way bill not yet matched to a moved truck; a returnable-bin float register integrated with the same conveyance reconciliation; and a pre-GSTR-1 register of IRNs that ties back to the same despatch volumes by the 10th of the following month.
A Tier-1 sheet-metal supplier at Manesar starts its dispatch day at 06:00 IST. By 06:00 the next morning 84 ASNs have left the gate to four OEM plants, 79 of them carrying e-invoice IRNs, five of them gate-pass-only returnable bin movements under Rule 55, 22 carrying single-consignment e-way bills, the remaining 57 stitched into 18 consolidated e-way bills at the conveyance level. Two IRNs are sitting in the 24-hour cancellation window because the trucks blew through their scheduled despatch slot and rolled back. One e-way bill was generated for the wrong vehicle plate and re-issued. This is e-invoice e-way bill auto component JIT India at production cadence — and the two statutory systems do not forgive a single broken link in the chain.
Quick reference
| Concept | Provision | Regulator | Threshold / clock |
|---|---|---|---|
| E-invoice mandate | Notification 13/2020-CT + amendments | CBIC / GSTN | Turnover above ₹5 crore in any FY from 2017-18 |
| IRN generation | Rule 48(4) + IRP/NIC | CBIC / GSTN | Before or at time of invoice |
| IRN cancellation window | IRP procedure | CBIC / GSTN | 24 hours, before GSTR-1 reporting |
| E-way bill threshold | Rule 138(1) | CBIC | Consignment value above ₹50,000 |
| Consolidated e-way bill | Rule 138(7) | CBIC | Multiple consignments on one conveyance |
| E-way bill cancellation | Rule 138(9) | CBIC | 24 hours of generation |
| E-way bill validity | Rule 138(10) | CBIC | 1 day per 200 km (regular cargo) |
| Rule 55 challan movement | Rule 55 CGST Rules | CBIC | No GST, no IRN, e-way bill if value above ₹50,000 |
| Detention for missing documents | Section 129 CGST Act | CBIC | Goods detained; tax + penalty |
Why JIT despatch is a fundamentally different e-invoice problem
Most B2B suppliers raise a few invoices per day, each well above the ₹50,000 e-way bill threshold. Auto-component JIT is the opposite. A Tier-1 supplying Maruti Manesar against an EDI 862 despatch instruction may break a single shift’s release into 10–15 part-specific ASNs sequenced to the OEM line, each carrying 2–4 hours of OEM consumption, each typically in the ₹15,000–₹45,000 range. The EDI 830/862/856 mechanics are dissected in the EDI 830/862/856 finance primer; the e-invoice and e-way bill mechanics layered on top are dissected here.
This breaks two assumptions of the standard e-invoice / e-way bill workflow:
- Single-consignment e-way bill is the exception, not the rule. Most ASN-level invoices sit below the ₹50,000 single-consignment line. The consolidated e-way bill under Rule 138(7) is the workhorse.
- The IRN cadence is hourly, not daily. A despatch team at a JIT supplier is generating IRNs continuously through the shift, not in a daily batch. Any IRP-side latency directly translates into truck-at-gate delay, which translates into OEM short-pay handling downstream via line-stop debit notes.
This article is the operational walkthrough of how the two compliance gates work in JIT auto, and where the failure modes hide.
What the e-invoice IRN actually is
The e-invoice IRN — Invoice Reference Number — is a 64-character hash generated by the Invoice Registration Portal (operated by NIC for GSTN) under Rule 48(4) of the CGST Rules. The supplier sends invoice JSON to the IRP; the IRP validates schema, runs duplicate checks against the supplier GSTIN and document number, and returns the IRN, an IRP-signed QR code and an Acknowledgement Reference Number. The invoice carrying the IRN and signed QR is then the legally valid tax invoice for the supply — an invoice without an IRN, when an IRN is mandated, is treated as not having been issued at all for the purposes of Section 31 and Section 129.
For an auto-component Tier-1 the gating threshold is aggregate turnover above ₹5 crore in any preceding financial year from 2017-18 onward — a threshold that virtually every Tier-1 and most Tier-2s have crossed. From the date the supplier crosses the threshold, e-invoicing is mandatory for every B2B taxable supply (B2C is outside the IRN system; exports and SEZ supplies are inside it). For an auto-component despatch to an OEM (B2B by definition), the IRN is a hard precondition of legal despatch.
The IRP also pushes the validated invoice data into the supplier’s GSTR-1 auto-population stream and triggers the e-way bill workflow if the consignment value crosses ₹50,000.
When does the ₹50,000 e-way bill threshold actually trigger?
Rule 138(1) of the CGST Rules requires an e-way bill before movement of goods of consignment value exceeding ₹50,000 — either in pursuance of a supply, or for reasons other than supply, or for inward supplies from an unregistered person. The key construct is consignment value, defined in Rule 138 Explanation 2 as the value declared in the invoice, bill of supply or delivery challan, including CGST/SGST/IGST and cess.
For JIT despatch, three sub-rules drive the operational reality:
- Rule 138(1) — single consignment above ₹50,000: generate a single e-way bill with Part A (consignor, consignee, HSN, value) and Part B (transporter, vehicle).
- Rule 138(7) — multiple consignments on one conveyance: when several consignments (each potentially below ₹50,000) are loaded onto one vehicle and the aggregate exceeds ₹50,000, the transporter must generate a consolidated e-way bill at the conveyance level before the vehicle moves. The individual e-way bills (if any) are linked.
- Rule 138(3) — voluntary generation: the supplier may generate an e-way bill even below ₹50,000.
For a JIT Tier-1 the practical workflow is: at IRN generation time, classify the ASN as single-consignment (value above ₹50,000 — generate single e-way bill alongside IRN) or as queue-for-consolidated (value below ₹50,000 — register intent, wait for the loading manifest to crystallise, then generate the consolidated bill before despatch).
How do the 24-hour cancellation windows work?
Two clocks run, and they run independently.
IRN cancellation. The IRP allows the supplier to cancel an IRN within 24 hours of generation, provided the underlying invoice has not yet been reported in GSTR-1. After 24 hours the IRN is locked; any commercial reversal must run through a credit note under Section 34. Common JIT triggers for IRN cancellation: the truck blew its loading slot and was rolled back, the part-specific despatch was reassigned to another supplier under an OEM expedite call, or the despatch quantity was found short of the EDI 856 commitment after IRN was generated.
E-way bill cancellation. Rule 138(9) allows cancellation of the e-way bill within 24 hours of generation if the goods are not transported or are transported but not as per the e-way bill. After 24 hours the e-way bill is locked and stays in the system.
For a JIT supplier, the two clocks need independent monitoring. A common JIT failure is to cancel the IRN within the 24-hour window after a despatch reversal but forget the linked e-way bill — the e-way bill stays open in the NIC system, surfaces at month-end as an “e-way bill without matching GSTR-1 invoice” in the e-way bill / GSTR-1 cross-check, and triggers a Section 65 audit query.
The reverse failure also happens: cancel the e-way bill within 24 hours but forget the IRN — the IRN locks at the 24-hour mark and now requires a credit note even though the underlying despatch never happened.
Cost the exception load on a quarter of broken IRN-to-ASN matches
Plug in your IRN-without-ASN orphans, ASN-without-IRN gaps and stale 24-hour cancellations and see the audit and operational hit.
Open the three-way match exception calculator →Cross-state JIT: what changes when the supplier and OEM are in different states
The IRN is GSTIN-agnostic on tax type — the IRP generates an IRN regardless of whether the underlying invoice is CGST+SGST or IGST. Tax type is decided by the place-of-supply rule in Section 10 of the IGST Act. For movement supplies, place of supply is the location where the movement terminates — the OEM plant. So an Aurangabad Tier-1 despatching to Maruti Manesar (Haryana) is an inter-state supply — IGST; an Aurangabad supplier to Tata Motors Pune (Maharashtra) is intra-state — CGST + SGST.
The e-way bill mechanics are identical for inter-state and intra-state movements at the centre level, but state-level thresholds and intra-state exemption notifications under Section 138(14) can vary. The default to assume in a JIT auto context is that the central ₹50,000 threshold applies and no state has carved out an exemption that would help — auto-component movements are squarely inside the regime.
Cross-state JIT also exposes a quietly painful workflow gap: the vehicle (Part B) update. A truck that crosses state lines may be reloaded onto a different vehicle at a transhipment hub. Rule 138(5) requires that the e-way bill be updated with the new vehicle number on the same e-way bill — not a new one — within the validity window. Failure to update is a Section 129 trigger.
Returnable KLT bins, trolleys and dunnage: outside the IRN, inside the e-way bill
The single most misunderstood JIT compliance edge is the returnable packaging dispatch. A Tier-1 routinely sends KLT bins, metal stillages, trolleys, blue-bin small-part containers and dunnage out with a finished-part despatch and gets them back empty on the return run. The bin float is the operational reality dissected in returnable packaging and KLT bin reconciliation.
For GST purposes the returnable bin movement is ‘otherwise than for supply’ under Rule 55 of the CGST Rules. The supplier issues a delivery challan, not a tax invoice. No GST is charged; no IRN is generated because IRN attaches to a tax invoice. So far so straightforward.
The trap is the e-way bill. Rule 138 applies to any movement of goods above ₹50,000 in consignment value — whether or not the movement is a taxable supply. A truckload of metal stillages going from a Tier-1 to Maruti easily crosses ₹50,000 in declared value. The supplier must therefore generate an e-way bill on the basis of the Rule 55 delivery challan, with Part A drawing values from the challan and Part B carrying the vehicle. The e-way bill is generated in the NIC system as document type “Delivery Challan” rather than “Tax Invoice.”
A Tier-1 that confuses “no IRN” with “no e-way bill” on returnable bins exposes the truck to Section 129 detention at the inter-state check post. The same logic applies to free-issue (FI) material being returned from the Tier-1 back to the OEM, and to job-work delivery challans — the wider Rule 55 frame is set out in Rule 55 delivery challans for auto components.
Worked example — Tier-1 despatching 80 ASNs/day to Maruti Manesar
A Manesar-based stamping Tier-1 supplying Maruti Manesar runs a 3-shift, 24×7 despatch operation. A representative 24-hour cycle:
- Total ASNs: 84 (76 outbound taxable supplies, 8 returnable-bin Rule 55 movements).
- Despatch value: 76 × average ₹38,000 = ₹28.88 lakh taxable; 8 returnable-bin Rule 55 challans at average declared value ₹62,000 each = ₹4.96 lakh of bin float in motion.
- IRNs generated: 76 (one per taxable ASN; zero on bin dispatches).
- Single-consignment e-way bills: 14 (taxable ASNs above ₹50,000 individually).
- Consolidated e-way bills: 18 (covering the remaining 62 sub-threshold taxable ASNs aggregated onto 18 truck loads, plus the 8 bin movements absorbed into the same conveyances).
- Stand-alone bin e-way bills: 0 (all bin movements aggregated into the consolidated bills of the conveyance carrying them).
- 24-hour cancellation cohort: 2 IRNs and 2 e-way bills cancelled within the window — the truck blew its 14:00 slot at Maruti gate and was rolled back; cancellations completed within 18:00 the same day.
Tax type: Manesar-to-Manesar is intra-state Haryana — CGST + SGST 9% + 9% = 18%. Maruti’s GSTIN at Manesar plant is a Haryana registration; the place-of-supply is the Manesar plant.
EDI cross-reconciliation: 76 ASNs (EDI 856) transmitted, 76 IRNs generated, 76 e-way bills covered (32 documents counting consolidated + single). At end-of-day, the despatch reconciliation matrix shows: ASN-to-IRN 1:1 clean; IRN-to-ASN quantity tie-out within ±0.4% on container counts; e-way bill conveyance plate matches gate-pass plate on 31 of 32 (one mismatch on a substituted truck — the e-way bill Part B was updated within 30 minutes of the substitution under Rule 138(5)).
Pre-GSTR-1 cross-check: the 76 IRNs generated today will auto-populate September 2026 GSTR-1 by the 10th of October. Returnable-bin movements have no GSTR-1 line — they are Rule 55 challans only. Sub-threshold (below ₹5 crore turnover scenario) suppliers are exempt from the IRN — not applicable here.
The despatch team and the GST analyst together touch 32 documents to clear 84 ASNs. Without a consolidated bill discipline the supplier would generate 76 single e-way bills (more than double the workload) and still have 8 separate bin-bill documents.
Tax overlay — Section 393(1)(a) on the freight invoice
The e-invoice and e-way bill compliance closes the outbound goods leg. The freight invoice from the transporter carries its own TDS leg under the Income Tax Act 2025:
- Section 393(1)(a), payment code 1002 — replacing legacy Section 194C from 1 April 2026. 1% for individual/HUF transporters, 2% for company/firm transporters, applied on the freight charge. Threshold ₹30,000 per single contract or ₹1,00,000 aggregate per transporter per FY. The freight exemption under Section 194C(6) — declaration-based exemption for goods carriers owning 10 or fewer vehicles — carries forward in spirit under Section 393 with the new declaration form (Form 168). The full code framework sits in TDS payment codes 1001–1092.
- Cross-era handling. Freight invoices for despatches before 1 April 2026 and Form 26AS entries thereafter carry the legacy 194C reference; the reconciliation must keep the cross-reference live across Form 26AS reconciliation for auto-component suppliers.
If the goods transport agency (GTA) operates under reverse charge under Notification 13/2017 (services other than to specified registered persons), the principal pays GST under RCM on a self-invoice — outside the IRN system. The principal’s RCM ITC is claimed in GSTR-3B Table 4(A)(3) and reconciled to the self-invoice register.
How does this all tie back to OEM gate pass and short-pay?
The OEM gate at Maruti Manesar checks three documents at the in-gate: the e-invoice (with IRN and QR), the e-way bill (single or consolidated), and the ASN that the Tier-1 transmitted electronically before despatch. Any one of the three missing, mismatched on quantity, or mismatched on PO release reference will trigger one of three OEM responses:
- In-gate detention until the supplier resolves — the worst case, because the OEM’s line is now starving and the line-stop clock starts.
- Acceptance with a quality / receipt note flag — the goods are unloaded against a partial GR, the missing reconciliation legs are flagged and the OEM pays against the lower of invoice and GR, with the rest staged as a short-pay for resolution.
- Rejection at gate — the goods are turned back; the supplier eats the freight and the line-stop debit note risk.
A clean e-invoice / e-way bill / ASN reconciliation is the operational pre-condition for the OEM goods-receipt and settlement cycle that the rest of the auto-component cluster covers. The downstream three-way match across PO, ASN/GR and invoice is the focus of ASN, GRN and invoice three-way match for auto components (where it exists in the build), and the wider settlement reconciliation flows through why the OEM pays less than the invoice.
Continue reading — the auto-component reconciliation cluster
- Sub-pillar: Automotive component manufacturing reconciliation in India — the full surface from gate to settlement.
- EDI mechanics: EDI 830/862/856 for auto-component finance teams — what each EDI transaction carries and how it cross-ties to the e-invoice.
- Returnable carriers: Returnable packaging and KLT bin reconciliation — the bin float ledger that runs alongside the despatch.
- Rule 55 frame: Rule 55 delivery challans for auto components — when the movement is not a supply.
- Settlement consequence: OEM short-pay handling — what happens at month-end when any of the despatch documents do not reconcile.
- External authority: the GST portal for the e-invoice notification, IRP schema and Rule 138 e-way bill specifications.
What automated reconciliation changes
Manual orchestration of 80+ ASNs per day, 76+ IRNs, 32+ e-way bills (mixed single and consolidated), 8+ Rule 55 bin movements, two independent 24-hour cancellation clocks and the ASN-IRN-e-way-bill-gate-pass tie-out is where compliance fails quietly until a Section 129 detention at a state border or a Section 65 audit query in month four. Purpose-built auto component reconciliation software India ties every ASN to its IRN, classifies the despatch as taxable or Rule 55, drives single vs consolidated e-way bill choice from the conveyance manifest, watches the two 24-hour cancellation clocks per document, reconciles end-of-day to a tight despatch register, and stages the IRN data for clean GSTR-1 auto-population by the 10th of the next month. TransactIG carries 24+ industry presets including configurations for JIT despatch and consolidated e-way bill workflow. Customer outcomes include match-rate improvement from 51% to 88% on inbound reconciliation. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound three-way match discipline see three-way matching software India.