Scheduling Agreement vs Purchase Order: Financial Implications for Indian Auto Component Suppliers

A Tier-1 forging supplier in Pune wins a brake-line programme with Hyundai Motor India after years of supplying aftermarket parts through discrete purchase orders to multi-brand distributors. The commercial team negotiates the supply agreement; production scales up; the first deliveries land at Sriperumbudur in May. In November the controller closes Q2 and notices that AR aging shows ₹4.2 crore of “overdue” receivables that the cash-application team insists are not actually overdue. The auditor flags revenue-recognition timing on dispatch quantity that exceeded confirmed-received quantity by 1.8% — inside delivery tolerance but recognised as full sales. The finance team has run an SA-based OEM account through PO-based finance logic for six months, and the cleanup will take two quarters. This is the scheduling agreement vs purchase order auto component India transition pain — and it is preventable.

Quick reference

Why OEMs run scheduling agreements

A passenger-car final assembly line runs at roughly one vehicle per minute. A Tier-1 brake-system supplier ships dozens of part numbers into that line every day, sometimes sequenced to the chassis number (JIS). Issuing a discrete purchase order per truck would consume hours of procurement and supplier operational time per day per part, would introduce closure events that do not exist in continuous production, and would create reconciliation noise the OEM does not want. The scheduling agreement solves four operational problems:

• Capacity reservation. The agreement contractually ties the supplier to maintain capacity for the programme life. The supplier books press, forge, machining or assembly time and raw material inventory against the forecast.
• Predictable supply. Daily firm call-offs (the EDI 862 or portal equivalent) give the supplier a few-days-to-two-weeks visible firm window with the longer 830 forecast horizon behind it.
• Transactional overhead reduction. One agreement plus a release stream replaces hundreds of POs per year per part.
• Sequencing for JIS. Where the line consumes parts in chassis-number sequence, the agreement supports the SDQ or FST segments and portal-equivalent payloads that carry sequence data per ASN.

Every major Indian OEM running series production — Maruti Suzuki, Tata Motors, Mahindra & Mahindra, Hyundai Motor India, Bajaj Auto, TVS Motor, Ashok Leyland — operates on SA-based supply for the Tier-1 base. Discrete POs survive in aftermarket, spare-parts distribution, tooling and capex, and one-off engineering changes.

What an SA contract actually carries

A typical Indian auto-component scheduling agreement carries the contract framework, not per-shipment quantities. Inside the agreement document or master record:

• Agreement number — the persistent identifier the supplier and OEM both use in every release and invoice.
• Part code and ship-to plant — one agreement may cover multiple parts and multiple OEM plants, but each part-plant combination has its own line.
• Pricing — per-part rate, escalation/de-escalation clauses (often steel-index linked to JPC HR coil, LME aluminium, polymer-resin index), tooling amortisation per part.
• Delivery tolerance band — typically 2–5% over/under allowed per call-off without triggering a back-order or short-pay.
• Reset marker — almost always 1 April for Indian fiscal alignment, but model-start dates apply where a programme launches mid-year.
• Payment terms — typically T+45 to T+60 days from GRN at the OEM plant, not from invoice date.
• Quality thresholds — rolling-12-month PPM bands per part with contractual penalty consequences for breach.
• Programme attribution — which vehicle programme(s) the agreement supports, which determines FOMP and tooling-cap accounting.

The agreement does not say “ship 3,000 units this week.” That number comes from the release stream — daily 862 call-offs or daily portal updates (Maruti e-Nagare, Tata SRM, Hyundai HMI Vaatika, Bajaj BAL Connect, Bosch SupplyOn). See the EDI 830/862/856 finance primer for the release-stream mechanics in detail.

Financial implications — where SA breaks PO finance logic

Revenue forecasting basis: forecast vs firm

In the PO model, the receivables forecast is the open-PO book — committed value at agreed dates. In the SA model, there is no open-PO book. The forecast must be assembled from two streams:

• The 830 forecast horizon (12 to 26 weeks of planning quantities) gives a cash-flow band, but it is non-binding and should never be treated as committed.
• The 862 firm window (next few days to two weeks of authorised dispatch) is the contractually committed near-term position.

A controller forecasting receivables off 830 forecast quantity is over-committing capacity and over-stating expected receipts. A controller forecasting off 862 firm only is short-sighted beyond two weeks. The discipline is to forecast firm-as-firm and forecast-as-probability-weighted, against historical firm-vs-forecast hit rate per OEM programme.

Receivable risk profile

Under PO, receivable risk is per-PO — each PO is an independent obligation. Under SA, receivable risk is concentrated to the OEM relationship for the programme life. The single contract carries all the receivable exposure. This concentration is why Indian auto-component working-capital strategy increasingly uses TReDS receivable financing on confirmed-received quantity rather than per-PO discounting.

Ind AS 115 — performance obligations recognised at control transfer

Under Ind AS 115 the performance obligation is satisfied at control transfer. For SA-based supply:

• The agreement itself is the contract.
• The performance obligation is delivery of each unit at agreed specifications to the agreed ship-to point.
• Control transfers at OEM-confirmed GRN — not at dispatch, not at the firm call-off, not at the periodic invoice.
• Revenue is recognised at GRN-confirmed quantity at the contracted price.

The common error is to recognise revenue on dispatch (ASN) quantity. Inside the 2–5% delivery tolerance band, dispatched quantity routinely runs above confirmed-received quantity (rejections at receipt, sequencing failures, packaging damage), so revenue recognised on ASN over-states sales. Year-end auditors invariably catch this and force a restatement against confirmed-received.

GST e-invoice trigger: periodic, not per-call-off

Under PO, the supplier typically raises one GST e-invoice per PO at dispatch or per agreed milestone. Under SA, the GST e-invoice is periodic — typically weekly or fortnightly per OEM plant — consolidating many ASNs into one IRN against confirmed-received quantity for the billing window. The IRP issues an IRN against the consolidated invoice; the e-way bill links to the underlying ASNs. GST law itself is unchanged by the Income Tax Act 2025 — Section 17(5), Section 34 credit notes, Rule 36(4), Rule 37, Rule 43 and Rule 55 still govern.

Critically, the GSTR-2A / 2B reconciliation at the OEM end works only if the supplier’s periodic invoice ties to OEM-confirmed received quantity. Billing on raw ASN quantity inherits delivery-tolerance noise directly into output GST, and the OEM sees an ITC shortfall in GSTR-2B that triggers a debit-note cycle.

The missing PO number — why generic ERP reconciliation breaks

Off-the-shelf three-way matching modules in SAP, Oracle, D365 and Tally are configured for PO-to-GRN-to-invoice. SA-based supply has no per-shipment PO number, so the match logic must be reconfigured to:

• Use the scheduling-agreement number plus release ID as the contract anchor
• Match per ASN to GRN with delivery-tolerance band applied
• Roll many GRN-matched ASNs into one periodic invoice
• Tie the periodic invoice to confirmed-received quantity for the billing window

Most ERPs require customisation or a dedicated auto-component reconciliation software India layer that understands SA semantics. Generic three-way matching software India without SA awareness will throw exceptions on every match.

Tax overlay — Section 393, periodic invoicing, and Form 26AS

Under the Income Tax Act 2025, the OEM deducts TDS on the conversion-charge portion of an auto-component supply at Section 393(1)(k) — 2%, payment code 1012. Where the supply is structured as a works-contract or pure job-work flow, Section 393(1)(a) — payment code 1002 applies on the labour component. The legacy Section 194C reference is retained only for cross-era reconciliation of Form 168, Form 131 and Form 141 transitional cases.

The TDS deduction base is the conversion portion of the periodic invoice value. For Form 26AS to reconcile cleanly, the periodic invoice must tie to OEM-confirmed received quantity — not to raw ASN quantity. Where the supplier has billed against ASN quantity inside the delivery-tolerance band, the TDS deducted at the OEM end runs slightly below what the supplier expects against its invoice register, and the Form 26AS mismatch surfaces three to six months later as an unreconciled TDS receivable.

For the receivable-financing overlay, lenders evaluating SA-based supply look at confirmed-received quantity rolling-12-month rather than open-PO book — meaning the TReDS or invoice-discounting facility is sized to a flow figure, not a balance figure.

Worked example — a Tier-1 transitioning from PO-based to SA-based with Hyundai

A Pune-based forging Tier-1 wins a brake-line programme with Hyundai Motor India for the Sriperumbudur plant. Annual programme value ₹120 crore. The agreement covers two part codes, ship-to-store dock at Sriperumbudur, ₹61,400/MT JPC HR coil index escalation, 3% delivery tolerance, 1 April CUM reset, T+50 from GRN.

Pre-transition (PO-based aftermarket supply):

• AR aging anchored to invoice date plus 30 days
• Revenue recognised at invoice
• One GST e-invoice per PO
• ERP three-way match: PO + GRN + invoice
• Receivables forecasting from open-PO book

Post-transition (SA-based OE supply with Hyundai):

First three months under the new model — what actually happened:

• Months 1–2: ERP three-way match threw 100% exception rate because there was no PO number on dispatch records. Finance team manually reconciled every line.
• Month 3: ERP was customised with the SA-Release-ASN-GRN logic, exception rate dropped to roughly 12%.
• Month 4: First periodic GST e-invoice raised against confirmed-received quantity. The remaining 12% exceptions were primarily delivery-tolerance band ASNs (dispatched 3,060 against firm 3,000 — inside tolerance, but the match needed explicit tolerance acceptance).
• Month 5: AR aging clock re-anchored to GRN date plus 50, which removed the phantom-overdue noise that had built up during months 1–4.
• Month 6: First quarter close. Revenue was restated for months 1–3 to recognise on GRN-confirmed quantity, not invoice quantity. Output GST adjusted via Section 34 credit notes for the over-billed delivery-tolerance differences. Section 393(1)(k) TDS receivable register tied to Form 26AS for the first time in six months.

The Tier-1 carried roughly ₹1.4 crore of one-time reconciliation cleanup cost — auditor hours, ERP customisation, internal effort — before the model stabilised. Almost all of it was preventable with an upfront SA-aware finance design.

For deeper OEM-specific operational discipline, see the Tata Motors Tier-1 supplier reconciliation guide and the automotive component manufacturing reconciliation sub-pillar. The broader pillar is manufacturing reconciliation in India. For SA adoption guidance across the Indian Tier-1 base see the Automotive Component Manufacturers Association of India (ACMA).

What automated reconciliation changes

A purpose-built reconciliation engine that understands SA semantics — agreement-plus-release as the contract anchor, ASN-to-GRN with delivery-tolerance applied, many-ASN-to-one-periodic-invoice consolidation, GRN-anchored AR aging — removes the friction that breaks generic ERP three-way matching on auto-component accounts. TransactIG ships 24+ industry presets including the auto-component SA-aware 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 broader sub-tier supply layer, see auto-component reconciliation software India and three-way matching software India.

Continue reading

• Automotive component manufacturing reconciliation in India (sub-pillar)
• EDI 830, 862 and 856 finance primer
• CUM quantity drift: the auto-component reconciliation problem nobody talks about
• Manufacturing reconciliation in India (pillar)