Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Auto-component job-work chains rarely sit at a single vendor — a forging routes through forge to CNC to heat-treat to zinc-nickel plate to return-leg, typically three to four hops, each with its own Rule 55 inter-job-worker challan and its own ITC-04 Table 5C disclosure; the Section 143 one-year input clock and three-year capital-goods clock run from the original principal-dispatch date and do NOT restart at any hop, so a forging that has spent eight months across three job-workers has only four months of window remaining regardless of how recently it arrived at the current vendor; a Tier-1 with disciplined single-hop tracking but no multi-hop visibility carries the entire Table 5C surface as an audit-time blind spot; on a typical engine-block cohort of 2,400 castings dispatched annually to a 3-hop chain even a 2% inter-hop documentation gap can crystallise ₹8-12 lakh of deemed-supply liability at Section 65 audit.
Stamp every Rule 55 principal-dispatch challan with original-dispatch date, statutory clock (1 year inputs, 3 years capital), part programme code and job-worker GSTIN; for every inter-job-worker movement issue a Rule 55 inter-vendor challan that references the original-dispatch challan number as the linked reference and is keyed to ITC-04 Table 5C; track the single original clock across all hops without resetting; surface the days-to-deemed-supply countdown per part-cohort per current-vendor; alert 60 and 30 days before the original clock expires regardless of how many hops the goods have travelled; reconcile the principal's Rule 55 register to the ITC-04 Table 5C disclosure to the receiving job-workers' inward records at every quarter-end.
Job-worker master with GSTIN, PAN, process type (forge, machine, heat-treat, plate, paint, assembly), registration status; Rule 55 challan series per principal plant per movement type (principal-to-JW, JW-to-JW, JW-to-principal); part-programme master with intended routing graph (forge → machine → heat-treat → plate → principal); original-dispatch clock policy (1 year inputs, 3 years capital goods, no clock for jigs/fixtures/moulds/dies); Table 5C inter-vendor challan template with linked reference field; quarterly ITC-04 build with Tables 4, 5A, 5B and 5C reconciled to register.
An open-balance position per original-dispatch challan tracked through every hop with current-vendor, days-since-original-dispatch and days-to-deemed-supply countdown; the Table 5C inter-vendor challan register tying each hop to the original dispatch; the ITC-04 pre-filing pack with the original-dispatch clock intact and a Table 5C trail that matches the principal's Rule 55 register; the multi-hop deemed-supply provisional accrual at the 30-day band; and a board-visible Section 143 multi-hop dashboard.
A Tata Motors Tier-1 engine-component supplier in Sanand opens the Q2 ITC-04 review on a Thursday morning. The job-work register shows 4,860 open original-dispatch challans across nineteen vendors. The headline number looks comfortable — weighted-average age 138 days against the 365-day clock. But the multi-hop view tells a different story. Of those 4,860 open challans, 1,180 are currently sitting at a second-hop vendor (not the first job-worker dispatched to) and 290 are at a third-hop vendor. The third-hop cohort weighted-average age from original-principal-dispatch is 261 days. Two challans in that cohort are at 348 and 351 days respectively — and the receiving plater has not yet started the operation. Nobody on the operations floor at the plater knows the original-dispatch clock; their view starts from the day the parts hit their inward gate.
This is the multi-hop job work challan tracking auto component India corner of the Section 143 surface, and it is where deemed-supply liability builds most quietly. Most Tier-1 challan-tracking systems were built when the typical job-work pattern was single-hop — dispatch to plater, plater returns. The multi-hop pattern, structurally common in forging-to-machining-to-heat-treat-to-plate chains, exposes a different surface that the original tooling does not see.
Quick reference
| Concept | Provision | Regulator | Rate / clock |
|---|---|---|---|
| Original-dispatch clock — inputs | Section 143(1) CGST Act | CBIC | 1 year from original principal dispatch |
| Original-dispatch clock — capital goods | Section 143(1) | CBIC | 3 years from original principal dispatch |
| Clock at inter-vendor hop | Section 143(1) read with ITC-04 schema | CBIC | Does NOT restart |
| Jigs / fixtures / moulds / dies | First proviso to Section 143 | CBIC | No return clock |
| Inter-vendor challan requirement | Rule 45 read with Rule 55 | CBIC | Principal-authorised Rule 55 challan |
| ITC-04 multi-hop disclosure | Rule 45(3) — ITC-04 Table 5C | CBIC | Original-dispatch challan number referenced |
| Deemed supply on lapse | Section 143(3) inputs / 143(4) capital | CBIC | GST payable on original dispatch date |
| Interest on tax | Section 50(1) | CBIC | 18% per annum from original dispatch |
| ITC-04 due date (turnover above ₹5 crore) | Rule 45(3) | CBIC | 25th of month following quarter |
Why multi-hop chains are structural in auto components
A typical engine-block casting routes as follows. The principal foundry produces the rough casting in-house or buys it from a specialist foundry. From the principal’s plant the casting dispatches to:
- A CNC machining vendor — fine machining of bores, faces and threads. 12–18 days at the vendor.
- A heat-treatment vendor — controlled hardening and tempering. 6–9 days.
- A plating or coating vendor — corrosion-resistant treatment. 3–5 days.
- Return to the principal’s plant for assembly.
Single-hop alternatives exist but are operationally expensive. Bringing the casting back to the principal between every hop requires four return trips and four onward dispatches, four GRN cycles, four logistics moves and four ITC-04 entries per casting. The multi-hop alternative — vendor-to-vendor handoff on a Rule 55 inter-vendor challan — collapses three return trips into one and is the industry-standard pattern for most three-stage chains. Section 143(1) explicitly permits the multi-hop pattern; the cost is a Table 5C disclosure obligation on each inter-vendor move.
A cell-housing or transmission-component chain may extend to four hops. A complex forging for a steering-knuckle may go through five. The pattern is structural, not exceptional.
The single original-dispatch clock — what it actually means
Section 143(1) ties the return clock to the original dispatch by the principal. The text does not contemplate a hop-by-hop restart and the ITC-04 schema does not provide a mechanism for one. The original-dispatch clock runs through every Table 5C movement and only stops when the goods either return to the principal under a Rule 55 return challan (Table 5A) or are supplied from the final job-worker’s premises (Table 5B) within the original window.
A worked-through view of a single engine-block casting:
- 1 April — principal dispatches to CNC machinist. Original-dispatch clock starts. Day 0 of 365.
- 15 April — CNC machinist completes. Inter-vendor Rule 55 challan to heat-treater. Day 14.
- 24 April — casting arrives at heat-treater. Day 23.
- 3 May — heat-treater completes. Inter-vendor Rule 55 challan to plater. Day 32.
- 8 May — casting arrives at plater. Day 37.
- 12 May — plater completes. Return Rule 55 challan to principal. Day 41.
- 14 May — casting returns to principal plant. Day 43.
A 43-day cycle inside a 365-day window. No risk. But change one variable — say the plater is overloaded and the casting sits for 280 days waiting for treatment. The clock has been running the whole time. By the time the casting returns to the principal at day 323, the open-balance position has eaten 88% of the window. A 60-day expedite delay at any hop now puts the casting past the deemed-supply line.
The operational reality is that no individual vendor in the chain has visibility into the original-dispatch clock. The CNC machinist knows when it received and when it shipped to the heat-treater. The heat-treater knows when it received from the machinist and when it shipped to the plater. The plater knows when it received from the heat-treater and when it shipped back to the principal. None of them knows the original principal-dispatch date. The principal is the only party with the full picture, and the principal is the only party who carries the deemed-supply liability.
The Rule 55 inter-vendor challan — what it must carry
Every inter-vendor movement requires a Rule 55 delivery challan. The Rule 55 form is the same as for a principal-to-job-worker dispatch but with three additional fields populated:
- Linked reference — the original principal-dispatch challan number and date. This is the field that carries the Section 143 clock forward.
- Sending job-worker GSTIN — the vendor physically dispatching the goods to the next hop.
- Receiving job-worker GSTIN — the vendor receiving the goods.
The principal authorises the movement and the principal’s challan series is the FY-unique reference. In practice many Tier-1s issue a standing authorisation to the sending job-worker to generate the inter-vendor challan against the principal’s challan series — operationally efficient but it requires controlled access to the challan series at the vendor end and a daily upload of the issued challans back to the principal. The wider Rule 55 instrument detail is in Rule 55 delivery challans for auto components.
Where the linked-reference field is blank or carries the previous inter-vendor challan number instead of the original principal-dispatch number, the Table 5C disclosure breaks. The auditor cannot tie the goods at the third-hop vendor back to the original dispatch by the principal, and the deemed-supply position becomes indefensible.
Plan and reconcile a multi-hop ITC-04 cohort
Lay out Tables 4, 5A, 5B and 5C for a multi-hop part programme with original-dispatch clocks intact and the inter-vendor reference fields populated.
Open the ITC-04 tracker template →The five multi-hop failure patterns
Five operational patterns account for the overwhelming majority of multi-hop deemed-supply exposure.
1. Missing Table 5C entry. The principal’s ITC-04 Table 4 shows the dispatch to vendor 1. Vendor 1’s records show the dispatch out to vendor 2. The principal has no Table 5C entry tying the goods to vendor 2. The audit asks: where are the parts? The principal cannot evidence. Deemed supply fires.
2. Broken linked reference. The inter-vendor challan references the previous inter-vendor challan number rather than the original principal-dispatch number. The Table 5C entry carries the wrong reference and the chain cannot be traced back to the principal’s Rule 55 register. The audit treats it as an unrelated movement.
3. Hop-clock-reset assumption in the tracking system. The system shows the casting at vendor 3 with “30 days at vendor 3 of 365 allowed” — the system has reset the clock at the inter-vendor receipt. The reality is “315 days from original dispatch of 365 allowed”. The system under-reports risk by 285 days.
4. Goods physically returned but documentation does not close the chain. The casting returns to the principal but the return Rule 55 challan references only the most recent inter-vendor dispatch, not the original principal-dispatch. The Table 5A return entry cannot be matched against the Table 4 original dispatch. The original-dispatch challan stays open in the register even though the goods have come home.
5. Vendor 2 in the chain shuts down or migrates GSTIN. The casting is at vendor 2 when the vendor shuts. The goods may be retrievable through commercial channels; the documentation chain breaks because the inter-vendor onward challan that would have moved the casting to vendor 3 was never issued. The principal’s books carry an open balance at a non-functioning vendor.
A disciplined Tier-1 holds the multi-hop documentation breakage rate to under 0.5%. A Tier-1 without dedicated multi-hop discipline runs at 2–4%, which translates into substantial deemed-supply exposure over a five-year audit window.
Worked example — engine-block 3-hop chain for a Tata Motors Tier-1
A Sanand Tier-1 supplying engine blocks to Tata Motors dispatches 2,400 castings annually through a forge → machine → heat-treat → return chain. Each casting carries a stamped input value of ₹1,840 at original principal-dispatch (rough-casting cost). The intended cycle time is 28 days end-to-end across three hops.
Annual cohort: 2,400 castings dispatched, 2,376 returned on time, 24 castings stranded at one of the three vendors past the 12-month window — a 1.0% non-return rate, which is below the disciplined-Tier-1 benchmark of 0.5% but typical of a Tier-1 in transition to dedicated multi-hop tracking.
Exposure construction on the stranded cohort:
- Open-input value at risk: 24 castings × ₹1,840 = ₹44,160.
- GST rate: 28% (HSN 8409 — engine parts).
- Deemed-supply GST: ₹44,160 × 28% = ₹12,365.
- Interest exposure at average age 15 months from original dispatch: ₹12,365 × (15/12) × 18% = ₹2,782.
- Aggregate current-year exposure: ~₹15,147.
But this is the headline-clean exposure. The multi-hop blind spots layer on top:
- Missing Table 5C entries: 36 castings appear on the principal’s Table 4 dispatch to vendor 1 but vendor 1’s records show outward to vendor 2 with no corresponding Table 5C entry. At audit the 36 castings cannot be tied to vendor 2. Exposure: 36 × ₹1,840 × 28% × (1 + 15/12 × 18%) ≈ ₹22,706. ₹18,547 GST plus ₹4,159 interest.
- Hop-clock-reset assumption errors: 18 castings flagged by tracking system as inside window but in fact past it because the clock was reset on receipt at vendor 2. Exposure: 18 × ₹1,840 × 28% × (1 + 18/12 × 18%) ≈ ₹11,761.
- Return-challan reference break: 22 castings physically returned but the Table 5A return entry referenced only the last inter-vendor challan, not the original. At audit the Table 4 entries appear open. Defendable with operational evidence but the cleanup cost — joint reconciliation across vendor 1, vendor 2 and the principal’s gate-pass records — runs 2–3 weeks.
Aggregate across the cohort: roughly ₹50,000 of clean current-year deemed-supply exposure on the 24 truly-stranded castings, plus a further ₹35,000-40,000 of documentation-break exposure that surfaces only on Table 5C audit. On a 5-year cumulative view the multi-hop trail adds approximately ₹8-12 lakh of exposure to the headline Section 143 number for the Tier-1 — almost entirely avoidable with disciplined inter-vendor challan and Table 5C tracking.
Tax overlay — TDS at the inter-vendor moves
The inter-vendor movements themselves do not trigger TDS — the casting moves under Rule 55 challan, not under a fresh service contract. The TDS attaches to the conversion-charge invoice that each job-worker raises on the principal at the close of its operation. Each conversion-charge invoice carries:
- Section 393(1)(a), payment code 1002 — replacing legacy Section 194C from 1 April 2026. 1% individual/HUF, 2% company/firm. Threshold ₹30,000 per single contract, ₹1,00,000 aggregate per FY. The wider Section 393 frame is in Section 393 TDS under the new Income Tax Act.
- Form 26AS / TDS reconciliation carries the cross-era reference for FY 2025-26 dispatches that closed in FY 2026-27 — see Form 26AS reconciliation for auto-component suppliers.
Scrap generated at a hop and sold from the vendor’s premises sits on the vendor’s TCS register, not the principal’s. Section 394, payment code 1071 at 1% applies. Scrap returned to the principal and sold from the principal’s plant carries the principal’s TCS obligation. The detail is in TCS on scrap sale under Section 394.
How does the multi-hop disclosure cross-check at audit?
A Section 65 audit asks the principal to produce, for a sample of open original-dispatch challans:
- The original Rule 55 dispatch challan (Table 4 entry).
- The inter-vendor Rule 55 challans tying the goods through each hop (Table 5C entries).
- The return Rule 55 challan from the final hop to the principal (Table 5A entry).
- Or the supply-from-job-worker invoice if supplied from the final vendor’s premises (Table 5B entry).
- The principal’s challan register reconciled to all four.
- The job-workers’ inward and outward records at each hop.
A clean four-document chain with original-dispatch reference carried through every hop closes the position immediately. A break in any of the four — a missing inter-vendor challan, a wrong reference, a return that does not match the original — opens the position to deemed-supply. The detailed Table-by-Table walkthrough is in ITC-04 filing for auto-component manufacturers.
Continue reading — the auto-component reconciliation cluster
- Sub-pillar: Automotive component manufacturing reconciliation in India.
- Statutory frame: Section 143 deemed supply for auto components — the underlying provision the multi-hop discipline defends against.
- Quarterly disclosure: ITC-04 filing for auto-component manufacturers — Tables 4, 5A, 5B and 5C in operational detail.
- Documentation instrument: Rule 55 delivery challans for auto components — the challan form that runs the chain.
- External authority: the GST Portal — Central Board of Indirect Taxes and Customs for Section 143, Rule 45 and the ITC-04 schema.
What automated reconciliation changes
Manual tracking of a 4,860-challan multi-hop register across nineteen vendors, with original-dispatch clocks intact through every Table 5C inter-vendor movement, with 60-day and 30-day alert bands surfaced regardless of the current-hop vendor, and with a quarterly ITC-04 pack that ties every Table 5C entry back to a Table 4 original dispatch, is where the multi-hop blind spot quietly builds. Purpose-built auto component reconciliation software India stamps every original-dispatch challan with the statutory clock, generates inter-vendor Rule 55 challans with the linked reference field auto-populated from the original, tracks the single original clock across all hops without resetting, surfaces the days-to-deemed-supply countdown per challan regardless of current vendor, fires alert bands on the original clock, and produces an ITC-04 Table 5C pre-filing pack that reconciles to the principal’s register and to the job-workers’ records. TransactIG carries 24+ industry presets including configurations for multi-hop Section 143 chains and the Table 5C disclosure. Customer outcomes include match-rate improvement from 51% to 88% on multi-hop challan ledgers. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound match discipline see three-way matching software India.