Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Tier-1 auto-component suppliers shipping against rolling schedule agreements run an ASN-GRN-invoice three-way match across four clocks (dispatch, transit, GRN, e-invoice IRN) with cum-quantity drift, lost-in-transit ASNs, ad-hoc PI receipts, and partial rejections. Generic PO-anchored AP three-way matching cannot model this — exception rates above 10% per cycle, recovery losses on lost ASNs, and analyst hours lost to manual cum-quantity reconciliation are the consequences.
Anchor the match on the ASN (EDI 856), not the PO. Walk forward to the OEM dock-receipt timestamp to form the GRN match. Reconcile the supplier's tax invoice (with IRN from the GST e-Invoice portal) against the matched ASN-GRN pair. Maintain a cum-quantity ledger per schedule agreement reconciling running totals on both sides; flag drift events for joint sign-off. Classify exceptions into four buckets (no-GRN, no-ASN, cum-drift, partial-rejection) and route each to its own resolution path. Split the matched invoice into goods value and conversion value at payment release for Section 393(1)(k) TDS routing under code 1012.
Schedule-agreement master with cum-quantity counter per OEM per part. ASN feed (EDI 856) by dispatch event. GRN feed by OEM dock-receipt timestamp. Tax invoice feed with IRN reference. Cum-quantity reconciliation ledger with reset-event support. Exception classifier with four-bucket taxonomy. TDS split routing for Section 393(1)(k) code 1012. OEM-portal handshake (Bosch SupplyOn, Maruti e-Nagare, Tata iFM, M&M Source One) for ASN acknowledgement and GRN pull.
Per-cycle three-way match worksheet showing matched ASN-GRN-invoice triplets, exception lines classified into the four buckets with rupee exposure and aging, the cum-quantity ledger with drift events flagged, the TDS split per matched invoice (goods portion, conversion portion, 1012 code TDS payable), and a recovery-action queue (chase missing GRNs, lift ad-hoc PI receipts into the schedule, negotiate cum-quantity resets, process partial-rejection debit notes within Section 34 cutoff).
Generic AP three-way matching — purchase order, goods receipt note, supplier invoice — is the textbook procurement control. Every finance manual covers it. Every ERP ships it out of the box. It does not work in Tier-1 auto-component supply.
The auto-component three-way match starts in a different place, runs across four clocks instead of two, and has to absorb four exception classes the generic flow does not contemplate. The result is that AP teams running auto-component supply on a generic three-way match see exception rates above 10% per cycle, lose recovery on lost-in-transit shipments, and burn analyst hours reconciling cum-quantity drift the textbook does not even mention. This piece walks the ASN GRN invoice three-way match auto component India in the form it actually takes, including a 30-day worked example for a clutch-disc supplier into Bosch.
Quick reference
| Element | Generic AP three-way match | Auto-component three-way match |
|---|---|---|
| Anchor document | Purchase order | ASN (EDI 856) |
| Governance | Transactional PO | Rolling schedule agreement with cum-quantity counter |
| Clocks reconciled | 2 (PO → GRN → invoice) | 4 (dispatch, transit, GRN, e-invoice IRN) |
| Quantity reconciliation | Per-PO quantity | Per-ASN quantity walked against cum-quantity ledger |
| Exception classes | Quantity / price / tax mismatch | No-GRN, no-ASN, cum-drift, partial-rejection |
| GST anchor | Tax invoice | Tax invoice with IRN from GST e-Invoice portal |
| TDS overlay | One TDS event at payment | Section 393(1)(k) at 2% (code 1012) on conversion value only |
Why the ASN, not the PO
Tier-1 auto programmes do not run on POs. The contractual instrument is a multi-year schedule agreement that locks programme award, base price, RMPV mechanics, quality and PPM targets, payment terms, and the cum-quantity counter. Against that agreement, the OEM issues a rolling delivery schedule — weekly at minimum, daily for high-cadence programmes — that calls a new cum-quantity target by a delivery date. The supplier dispatches the delta.
The handshake that actually triggers receivables is the ASN: the EDI 856 advance shipping notice the supplier transmits the moment a truck is loaded for dispatch. The ASN carries the schedule reference, the lot, the new cum-quantity, the delivery destination, the carrier and vehicle, and the expected dock-arrival window. The OEM’s inward-goods system pre-stages the GRN against the ASN before the truck arrives. When the truck rolls onto the dock, a barcode scan against the ASN materialises the GRN with the dock-receipt timestamp.
Anchoring an AP match on a PO that does not exist in this flow is the original sin. Every downstream control fails because the anchor is wrong.
The four clocks
Generic AP runs on two clocks — the PO clock and the invoice clock. Auto-component supply runs on four:
- Dispatch clock — when the supplier physically ships and the ASN is transmitted. Often Friday evening for a Monday-morning OEM dock arrival.
- Transit clock — the in-transit period. Lane-dependent: Pune → Chennai is typically 36 hours, Pithampur → Manesar 24 hours, Chennai → Pune 30 hours by surface.
- GRN clock — the OEM dock-receipt timestamp at inward goods inspection. The GRN is materialised only when the barcode is scanned against the ASN.
- E-invoice IRN clock — when the supplier raises the tax invoice and the IRN is minted by the Invoice Registration Portal. This typically lags the GRN by 24–72 hours because the supplier’s billing run is batched.
The four clocks routinely span five calendar days for one ASN-GRN-invoice triplet. A generic AP three-way match interprets every gap as a mismatch. A correctly architected auto match tolerates the gap window while still catching real drift — quantity mismatches between ASN and GRN, IRN mismatches between invoice and e-invoice portal, late dock-receipts that fall outside the schedule window.
Cum-quantity drift
The schedule agreement carries a running cum-quantity counter — cumulative parts shipped since agreement opening. Every ASN advances the counter. Every accepted GRN confirms the advance on the OEM ledger. The two counters must stay in lockstep.
When they drift, every downstream triplet appears mismatched even though the underlying records are correct. The mechanics: ASN #847 of 1,200 parts is lost in transit (truck breakdown, paperwork misfile, OEM dock missed the scan). The supplier ledger reads cum-quantity = 1,02,400 after the dispatch. The OEM ledger reads cum-quantity = 1,01,200 because the lost ASN never materialised a GRN. Every subsequent ASN — #848, #849, #850 — carries a cum-quantity 1,200 ahead of the OEM ledger. Every GRN booked against those ASNs flags as a quantity mismatch.
The exception queue floods. The analyst burns hours walking the trail back to ASN #847. The remediation is a cum-quantity reset event — a joint reconciliation that confirms the lost ASN, processes the partial rejection or write-off, and resets both counters to a common baseline. Without that mid-window reset, the cum-quantity exception count compounds across every subsequent schedule release.
The four exception classes
Generic AP three-way match catalogs quantity-, price-, and tax-mismatch. Auto-component three-way match needs four orthogonal classes:
Class 1: ASN sent but no GRN. The supplier transmitted the ASN and dispatched the truck. The OEM dock never registered a receipt. Causes: truck lost in transit, dock-scan missed, supplier ASN transmitted but truck never actually left, paperwork rerouted to the wrong dock. Resolution: 24-hour escalation window, OEM logistics confirmation, write-off or recovery via insurance.
Class 2: GRN created but no ASN. An ad-hoc emergency dispatch — the OEM’s plant manager called for parts outside the schedule, the supplier shipped on a courier without raising an EDI 856. The OEM dock booked the GRN against a manual PI (perpetual inventory) receipt. The downstream tax invoice has no ASN anchor. Resolution: retrofit the dispatch into the schedule agreement, raise a retro-ASN, normalise the cum-quantity ledger.
Class 3: Cum-quantity drift. Covered above. Resolution: joint cum-quantity reset event.
Class 4: Partial rejection at incoming inspection. ASN dispatched 1,500 parts. Dock-scan confirmed 1,500. Inward inspection rejected 60 for surface defects. GRN booked at 1,500, but the rejection means the goods-acceptable value is 1,440. The supplier must process a Section 34 credit note for the 60 rejected parts, the OEM raises a debit note for the inspection cost, and the cum-quantity must be reduced by 60. The Section 34 credit note must be issued within the cutoff — by 30 November of the following financial year, or the annual return filing date, whichever is earlier.
Worked example — 30-day window for a Bosch clutch-disc supplier
A Tier-1 stamping-and-friction supplier ships clutch discs to Bosch’s Bidadi plant against a schedule agreement opened in April. The programme has been running 14 months; cum-quantity at the start of the 30-day window is 18,45,600 parts.
Window: 1 to 30 June. ASN volume: 1,400 ASNs across the month — roughly 47 per day across 30 days; an average ASN carries 280 parts. Total dispatched: 3,92,000 parts. Expected cum-quantity at month-end: 22,37,600.
OEM-portal handshake: Bosch SupplyOn for ASN transmission; SupplyOn GRN feed pulled into the supplier’s ledger nightly.
E-invoice flow: supplier’s billing run is batched twice a week — Wednesday and Saturday. IRN is generated on raise; IRP echo is captured.
End-of-window reconciliation produces the following exception profile:
| Class | Count | Quantity exposed | Rupee exposure |
|---|---|---|---|
| Class 1 — ASN sent, no GRN | 8 ASNs | 2,240 parts | ₹19.6 lakh |
| Class 2 — GRN created, no ASN (manual PI) | 11 GRNs | 1,860 parts | ₹16.3 lakh |
| Class 3 — Cum-quantity drift events | 3 resets | n/a | analyst hours only |
| Class 4 — Partial rejection at inspection | 19 GRNs | 412 parts | ₹3.6 lakh debit + Section 34 credit |
| Total exception lines | 41 of 1,400 | 2.93% | ₹39.5 lakh under reconciliation |
Recovery action queue:
- Class 1: 8 ASNs traced. 5 confirmed delivered with dock-scan missed (Bosch SupplyOn issued retro-GRNs within the 24-hour window). 2 truly lost-in-transit, processed via transit insurance claim. 1 confirmed never dispatched (supplier error, ASN cancelled, cum-quantity rolled back).
- Class 2: 11 ad-hoc PI receipts. All 11 lifted into the schedule agreement via retro-ASNs. Cum-quantity normalised. The supplier’s tax invoice was raised correctly against each — the IRN flow worked even though the ASN flow was retrofitted.
- Class 3: 3 cum-quantity reset events processed jointly. Drift was traced to the 2 lost-in-transit ASNs from Class 1 plus one earlier-month rejection that had not been propagated to the cum-quantity counter.
- Class 4: 19 partial rejections aggregated. Supplier issued one Section 34 credit note for ₹3.6 lakh covering all 19 events; the credit note was raised on 12 July, well within the Section 34 cutoff. Bosch issued a corresponding inspection-cost debit note.
Analyst hours saved by the structured exception taxonomy versus a generic PO-anchored match: estimated 18–24 hours over the month, with the rupee recovery on the 5 retro-GRNs (₹12.3 lakh) entirely dependent on the 24-hour escalation window the four-clock model enables.
TDS overlay at payment release (under the Income Tax Act 2025, in force from 1 April 2026):
- Total month invoice value matched: ₹3,42,80,000
- Goods value (raw material + steel + friction materials): ₹2,89,20,000 — no TDS
- Conversion value (labour, tooling amortisation, overheads): ₹53,60,000
- Section 393(1)(k) TDS at 2% (payment code 1012): ₹1,07,200 routed to TRACES under code 1012, not the retired 194Q.
For the underlying TDS payment code framework see the TDS payment codes 1001–1092 reference and the Section 393 master guide.
Cost out the four-class exception profile across your OEM book
A 2.93% exception rate on one OEM rarely stays there. Estimate the working-capital cost of no-GRN, no-ASN, cum-quantity drift and partial-rejection exceptions across every schedule agreement in your book.
Open the Exception Cost Calculator →OEM-portal mechanics
The OEM-side handshake is portal-mediated. Each major OEM runs its own:
- Bosch — SupplyOn. EDI 856 ASN transmission, SupplyOn-issued GRN feed, 24-hour escalation queue for class-1 exceptions, retro-GRN window of 24 hours for missed dock-scans.
- Maruti — e-Nagare. ASN transmission, dock-scan GRN, supplementary-invoice flow for RMPV claims, partial-rejection workflow via portal-issued debit advice.
- Tata Motors — iFM (integrated Fleet Management) for inbound + supplier portal. EDI 856 transmission, GRN auto-populated from inward inspection, cum-quantity reset events require joint sign-off in portal.
- Mahindra & Mahindra — Source One. ASN-to-GRN-to-invoice triplets fully tracked; partial-rejection raises auto-debit notes the supplier must offset via Section 34 credit.
The auto reconciliation engine has to ingest from whichever portals the supplier is connected to and present a unified four-clock view across OEMs. A supplier shipping to Bosch + Maruti + Tata + M&M runs four different portal handshakes and four different exception escalation windows.
GST under the Income Tax Act 2025 — unchanged
The Income Tax Act 2025 modernises the TDS framework — Sections 393/394/413 replace the legacy 194-series, and payment codes 1001–1092 replace the old TAN-section codes. GST law itself is unchanged. Every B2B auto-component tax invoice continues to require an IRN from the GST e-Invoice portal, and Section 34 credit notes for partial rejections continue to follow the same 30 November cutoff rule.
The three-way match must therefore handle both regimes in parallel: the GST/IRN flow on the invoice side, and the Income Tax Act 2025 TDS split on the payment side. The TDS split is where the largest carry-forward exposure sits — wrongly applied 194Q (retired) instead of 1012 (live) on conversion value reconciles in Form 26AS only at year-end, by which time the cash has moved and Form 168/131/141 mismatches accumulate.
What automated reconciliation changes
A spreadsheet-driven ASN-GRN-invoice match cannot carry the cum-quantity ledger reliably, cannot reconcile four clocks per triplet, and cannot route exception lines to the right escalation queue within the 24-hour window. Purpose-built auto-component reconciliation software India carries the schedule-agreement structure with cum-quantity counters per OEM-part, ingests ASN feeds from each OEM portal (Bosch SupplyOn, Maruti e-Nagare, Tata iFM, M&M Source One), reconciles against GRN feeds and IRN-bearing tax invoices, classifies exceptions into the four-bucket taxonomy, processes Section 34 partial-rejection credit notes within the cutoff, and routes Section 393(1)(k) TDS at code 1012 on conversion value. TransactIG ships 24+ industry presets including the auto-component ASN-GRN-invoice preset. Customer outcomes include match-rate improvement from 51% to 88%. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the Tier-2 procurement equivalent see three-way matching software India.
Continue reading in the automotive-components cluster
- Automotive component manufacturing reconciliation in India — sub-pillar
- RMPV calculation formula for auto-component suppliers — operator-level RMPV claim walkthrough
- Line rejection PPM and quality debit reconciliation — partial-rejection downstream