Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian OEMs run JIT/JIS supply through rolling scheduling agreements transmitted by EDI — 830 planning schedules, 862 firm call-offs, 856 ASNs — or via portals (Maruti e-Nagare, Tata Motors supplier portal, Bosch SupplyOn). Quantities are cumulative (CUM), not discrete, so a single dropped ASN permanently drifts the supplier CUM-shipped from the OEM CUM-received, while GST e-invoice and e-way bill ride alongside the ASN and a supplier may invoice many ASNs as one periodic tax invoice.
Reconcile four-way on a cumulative basis per part and ship-to: 830 scheduled forecast (planning only) is excluded from invoiceable quantity; 862 firm call-off sets the authorised dispatch; 856 ASN CUM-shipped is matched against OEM GRN CUM-received within the part-level delivery tolerance; periodic GST tax invoice quantity is reconciled to confirmed received quantity for the billing window; CUM drift between supplier-shipped and OEM-received is surfaced as a standing exception until both sides agree the cumulative.
Part master keyed by OEM plant code, ship-to point (line vs store) and scheduling-agreement number, with over/under delivery tolerance band per part; EDI map for 830 (forecast horizon), 862 (firm-from date, CUM-required), 856 (ASN, CUM-shipped, pack/SNP structure); GRN feed carrying OEM CUM-received; e-invoice IRN and e-way bill number linked to each consolidated tax invoice; CUM reset markers (year-start / model-start) per agreement.
A per-part cumulative reconciliation showing 862 CUM-required vs 856 CUM-shipped vs GRN CUM-received with open-requirement and CUM-drift flags, ASN-to-GRN match status inside tolerance, a many-ASN-to-one-invoice quantity reconciliation per billing window with e-invoice and e-way bill linkage, and an exception queue for forecast-vs-firm gaps, over/under-delivery beyond tolerance, missing-ASN cascades, and CUM drift awaiting joint correction.
A Tier 1 stamping supplier in Manesar pulls its Maruti Suzuki delivery position on a Monday morning and finds a 1,800-unit gap between what its own dispatch records say it has shipped and what the OEM’s portal shows as received — cumulative since the April year-start reset. Nothing was lost on a truck. One ASN three weeks earlier was transmitted twice during a portal timeout, and from that day every call-off has been computed against a CUM-received figure that is permanently 600 units behind the supplier’s CUM-shipped. This is the defining failure mode of OEM delivery schedule EDI ASN reconciliation India work: in a cumulative-quantity world, a single ASN error does not net out next week — it drifts forever until both sides reconcile the CUM.
Quick reference
| Concept | Standard / document | GST treatment | Reconciliation trigger |
|---|---|---|---|
| Planning schedule (forecast) | ANSI X12 830 / portal forecast | None — not a supply | Not invoiceable; capacity/RM planning only |
| Firm shipping schedule (call-off) | ANSI X12 862 / portal call-off | None until dispatch | Authorised dispatch quantity, CUM-required |
| Advance Shipping Notice | ANSI X12 856 (ASN) | Not a tax document | CUM-shipped; match to GRN within tolerance |
| Goods receipt at OEM | OEM GRN / line confirmation | Recipient ITC on tax invoice | CUM-received; CUM-drift detection |
| Tax invoice | GST e-invoice (IRN) + e-way bill | Output GST; periodic consolidation common | Invoiced qty = confirmed received qty |
| Delivery tolerance | Scheduling-agreement clause | n/a | Over/under-delivery beyond band |
Why Indian OEMs replaced POs with scheduling agreements
A discrete purchase order is a one-shot instruction: buy 5,000 units, deliver by a date. That model collapses under JIT, where an OEM assembling several hundred thousand vehicles a year needs a continuous, daily-adjusting supply against a moving production plan. So Indian OEMs — Maruti Suzuki, Tata Motors, Mahindra & Mahindra, Hyundai, Bajaj Auto, and Tier 1 system suppliers such as Bosch acting as their own OEM to a Tier 2 base — run scheduling agreements instead. In SAP terms these are the LP (scheduling agreement without release documentation) and LPA (with release documentation) agreement types: a single long-lived agreement against which the OEM transmits a stream of releases rather than fresh POs.
Each release is an electronic delivery schedule. The supplier never sees a “PO number per shipment” — it sees a rolling schedule line that updates, sometimes daily, against the same agreement. That is why reconciliation cannot be built on PO-to-invoice matching: there is no per-shipment PO. The match has to be schedule-to-ASN-to-receipt on a cumulative basis.
The EDI document chain — 830, 862, 856
Indian OEMs transmit schedules either through classic EDI (ANSI X12 in most global-OEM environments, EDIFACT DELFOR/DELJIT in some European-lineage plants) or through web portals that emit the same logical documents. The three documents that matter:
- 830 — Planning Schedule. A rolling forecast over a long horizon (commonly 12 to 26 weeks). It tells the supplier roughly how much will be needed so steel can be booked and capacity reserved. It is not a firm order and nothing on an 830 is invoiceable.
- 862 — Shipping Schedule. The firm, near-term call-off (the next few days to about two weeks). This is the document the supplier actually ships against. It carries the firm quantity-by-date and, critically, the CUM-required.
- 856 — Advance Shipping Notice (ASN). Transmitted by the supplier when goods are dispatched. It tells the OEM what is on the truck, in what pack/handling-unit structure (the SNP — standard pack quantity), and carries the supplier’s CUM-shipped. The ASN drives the OEM’s receiving and, in ship-to-line cases, the line feed.
Many Indian OEMs front these documents with a portal rather than raw EDI: Maruti’s e-Nagare supplier portal, the Tata Motors supplier portal, Bosch’s SupplyOn platform, and the EDI gateways used by Hyundai and Ford-lineage operations. The portal screens differ but the logical chain — forecast, firm call-off, ASN, receipt — is the same, and the reconciliation discipline is identical.
The four-way (really five-way) reconciliation
The match an auto supplier must run, per part and per ship-to point:
- 830 scheduled forecast — used only for planning; carried in the reconciliation as context, never as invoiceable quantity.
- 862 firm called-off quantity — the authorised dispatch and the CUM-required.
- 856 ASN dispatched quantity — the CUM-shipped, matched against the firm call-off inside the delivery tolerance.
- OEM GRN / line confirmation — the CUM-received, which must agree with the supplier’s CUM-shipped.
- GST tax invoice — the billed quantity, reconciled to the confirmed received quantity for the billing window.
This is the auto-industry cousin of PO-GRN-invoice three-way matching in India — except the “PO” is a rolling schedule and every quantity is a cumulative, not a discrete order.
CUM accounting — the mechanic that breaks everything
The single hardest thing about auto delivery reconciliation is that quantities are cumulative. The 862 does not say “ship 3,000 this week”; it says “CUM-required is 84,000 as of this date.” The supplier’s open requirement is CUM-required minus its own CUM-received-confirmed. The ASN carries CUM-shipped. At a reset point (year-start, typically 1 April for Indian fiscal alignment, or model-start) both sides zero the CUM and start again.
The consequence: if one ASN is dropped, duplicated, or transmitted with a wrong quantity, the supplier’s CUM-shipped and the OEM’s CUM-received diverge by that amount permanently — every later call-off is computed off a wrong base. Netting does not heal it; only a joint CUM reconciliation does. A reconciliation system therefore cannot just compare last-shipment-to-last-receipt — it must compare CUM-shipped against CUM-received continuously and raise a standing CUM-drift exception the moment they part company.
Ship-to-line vs ship-to-store
The same part can be on two clocks. Ship-to-line (dock-to-line, or JIS — Just-in-Sequence — where parts arrive in build order) means delivery feeds the assembly line directly inside a 2 to 4 hour window with little or no OEM buffer; ASN and sequence confirmations arrive near real-time and any shortage triggers an immediate line-stop risk and a fast short-pay. Ship-to-store means the supplier delivers into an OEM warehouse, a store GRN is booked, and consumption is decoupled — reconciliation runs against a periodic store GRN, so quantity disputes surface more slowly. The ship-to point must be stored per part so the reconciliation applies the right matching cadence.
Delivery tolerance
Scheduling agreements allow an over-delivery and under-delivery tolerance — commonly a small percentage band, sometimes a fixed quantity — so standard-pack rounding does not flag a false exception. Reconciliation applies the band per part before deciding match-or-exception: an ASN inside the band is matched; outside it is a genuine over-delivery (which the OEM may refuse or return) or under-delivery (which can trigger a premium-freight expedite or a line-stop charge).
Worked example — 12,000 units/month to Maruti on a rolling 862
A Tier 1 supplying a stamped bracket to Maruti Suzuki at Manesar, ship-to-line, on a rolling 862:
- Monthly firm requirement: 12,000 units (~600/working day across ~20 days).
- April year-start CUM reset to 0 on 1 April.
- 830 forecast horizon: 16 weeks; used to book HR coil and reserve press capacity.
- 862 firm window: 10 working days, refreshed daily; standard pack (SNP) = 200 units/bin.
- Delivery tolerance: a small over/under band per the agreement, applied per call-off.
- GST: weekly consolidated e-invoice with IRN; e-way bill per truck.
By 21 April the OEM 862 shows CUM-required = 12,600. The supplier’s dispatch log shows CUM-shipped = 12,600 across 63 bins. But the Maruti portal GRN shows CUM-received = 12,000 — a 600-unit (3-bin) gap. Tracing it: ASN #41 on 9 April was transmitted twice during a portal timeout and the OEM de-duplicated the receipt, but the supplier’s CUM-shipped counted both. Every call-off since 9 April has been computed against a CUM that is 600 ahead on the supplier side.
The fix is not a credit note and not a fresh dispatch — the goods physically arrived correctly. It is a CUM correction: both sides agree the duplicate ASN, the supplier reverses 600 from its CUM-shipped, and the open requirement realigns. A reconciliation control that compares CUM-shipped to CUM-received would have flagged this on 9 April as a standing CUM-drift exception instead of letting it compound for two weeks and threaten a false over-delivery dispute. Separately, the weekly e-invoice for the period must bill received-confirmed quantity, not raw ASN quantity, or the GST output will overstate.
GST e-invoice and e-way bill alongside the ASN
The ASN is not a tax document, so GST compliance runs in parallel. Each taxable movement above the e-way bill threshold needs an e-way bill; each invoice above the e-invoice turnover threshold needs an IRN. Because JIT suppliers commonly bill periodically (weekly or fortnightly) against cumulative received quantity rather than per truck, reconciliation must map many ASNs to one tax invoice and assert that invoiced quantity equals OEM-confirmed received quantity for that window — otherwise output GST drifts away from physical supply and the OEM’s ITC will not match the supplier’s GSTR-1.
Put a number on every CUM-drift and short-pay exception
A single mishandled ASN can cascade into weeks of cumulative drift, premium freight and disputed short-pays. Estimate what each unresolved schedule exception is costing across your OEM accounts.
Open the Exception Cost Calculator →Where this sits in the auto-component reconciliation stack
EDI/ASN reconciliation is the inbound-quantity rail; the OEM-Tier 1 settlement and debit note reconciliation sits downstream where short-pays and debit notes land, and line rejection and PPM quality debit reconciliation handles parts rejected after receipt. The full picture is in the automotive component manufacturing reconciliation sub-pillar and the broader manufacturing reconciliation pillar. For EDI-adoption and supplier-portal standardisation guidance across the Indian base, see the Automotive Component Manufacturers Association of India (ACMA).
What automated reconciliation changes
Hand-reconciling cumulative EDI schedules across multiple OEM portals is where suppliers lose days each month and let CUM drift compound into false over-delivery disputes. Purpose-built reconciliation software India treats the 830/862/856/GRN/invoice chain as a structured cumulative stream — it carries CUM-shipped against CUM-received per part, applies the delivery tolerance from the part master, maps many ASNs to one periodic e-invoice, and surfaces only the lines that fail. TransactIG ships 24+ industry presets, including a configuration for OEM schedule-to-ASN-to-GRN cumulative matching with e-invoice/e-way bill linkage. Customer outcomes include match-rate improvement from 51% to 88%. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound procurement equivalent at the Tier 2 interface, see three-way matching software India.