SAP Scheduling Agreement Reconciliation for Auto Component Suppliers: What SAP Doesn't Do

A Tier-1 supplier on SAP S/4HANA with ₹400 crore revenue and four OEM customers (Maruti, Tata Motors, Mahindra, Bosch) commissioned a two-developer custom ABAP team in early 2024 to build CUM drift tracking, RMPV claim computation, and FOMP debit decomposition on top of the standard S/4HANA install. Twenty months later, the codebase has six conditional branches per module to handle OEM-specific variations, the senior developer has left, every Maruti e-Nagare update breaks something, and the new ABAP team’s estimate for a clean rebuild is 9 months at ₹65 lakh. The CFO is reading a fresh proposal to add Section 143 deemed-supply alerting and KLT bin float tracking. The CTO is recommending a halt.

This is the SAP-gap moment that effectively every Indian Tier-1 auto-component supplier on S/4HANA reaches inside 18 months of go-live. The question is not “can SAP do auto-component reconciliation” — SAP does the document mechanics brilliantly. The question is which auto-component reconciliation streams SAP does NOT handle as a standing exception process, and whether a custom-ABAP build is the right answer for them.

This is the SAP scheduling agreement reconciliation auto India operating reference for finance, IT, and procurement teams making the build-vs-buy call.

Quick reference

What does SAP S/4HANA actually do well for scheduling-agreement supply?

SAP’s core MM (Materials Management) and SD (Sales and Distribution) modules handle scheduling-agreement document mechanics with depth that no Indian product can match. Specifically:

• Document types LP and LPA — the standard scheduling-agreement (LP) and the scheduling agreement with delivery schedule (LPA) are well-supported, with target quantity, valid-from / valid-to, release strategy, and conditions structured properly.
• EDI IDoc processing — the IDoc framework handles ORDERS (PO), DELFOR (delivery forecast, used for EDI 830 and 862), DESADV (despatch advice, used for EDI 856), GSVERF (credit memo), and INVOIC (invoice) as standard message types. The mapping from external EDI partner (Maruti e-Nagare, Tata SRM, Bosch SupplyOn) to internal IDoc is configurable in SAP’s standard tooling.
• Delivery creation — VL10A / VL10B can create deliveries against scheduling-agreement schedule lines as standard.
• GRN against scheduling agreement — MIGO posts GRN with SA reference, updating cumulative receipt quantity on the SA item.
• Three-way match — MM-LIV (Logistics Invoice Verification) performs three-way match against scheduling-agreement reference, with tolerance handling.
• AR / AP — FI-AR and FI-AP handle customer/vendor accounting with standard ageing, dunning, and clearing.
• CUM tracking on the SA itself — the scheduling-agreement item record accumulates released quantity, delivered quantity, and invoiced quantity. Standard reports (ME38, MMRV, transaction MMSC) display the position.

If the supplier’s business were a single OEM with no debit notes, no RMPV, no job-work, no free-issue steel, and no returnable packaging, standard SAP would close the loop. None of those conditions hold for an Indian auto-component Tier-1.

What SAP does NOT handle natively — the standing-exception streams

The reconciliation streams below are NOT SAP gaps in the sense of missing transactions. SAP records every individual transaction faithfully. The gap is that SAP does not run a continuous reconciliation between transactions as a standing exception process with ageing, root-cause classification, escalation, and resolution workflow.

CUM drift as a standing exception

The supplier’s CUM-shipped position on a scheduling agreement is in SAP. The OEM’s CUM-received position is also in SAP (from MIGO postings). SAP can show both numbers on a single screen. What SAP does not do is run a continuous reconciliation between the supplier’s CUM-shipped from ASN and the OEM-confirmed CUM-received from GRN, flag the drift as an aged exception, classify the root cause (missed ASN, duplicate ASN, out-of-sequence dispatch, OEM GRN-posting delay), and route to a resolution queue. See OEM delivery schedule and EDI/ASN reconciliation for the underlying CUM mechanics.

The result: Tier-1s with SAP run external Excel workbooks for CUM drift management, manually export ME38/MMRV outputs each fortnight, and chase drift cases through email threads with the OEM’s logistics team. Industry observation: a Tier-1 with four OEMs and 800-1,200 active scheduling agreements typically carries 60-150 open CUM drift cases at any moment.

RMPV recomputation against commodity indices

Raw material price variation clauses re-price already-shipped goods against quarterly index movements (JPC HR/CR steel coil, LME aluminium/copper/zinc, polymer/resin indices). The supplier raises a supplementary debit invoice (price rise) or the OEM issues a credit note (price fall). See Raw material price escalation clause reconciliation for the formula and accounting flow.

SAP records the supplementary invoice once it is generated. SAP does not compute the claim — it does not pull the JPC monthly average, multiply by material weight per part, multiply by quantity supplied in the period, classify the output as a supplementary invoice vs Section 34 GST credit note, or track index-to-settlement lag. RMPV claim generation runs in external Excel at almost every Indian Tier-1, with the SAP entry being a downstream booking.

FOMP back-charge reason-coded decomposition

When the OEM payment advice arrives 8% short, the supplier needs to decompose the short-pay into FOMP / JIT shortage / quality / line-stop / tooling / technical service / transport categories, tie each debit to its source invoice via claim ID, decide accept vs contest, and trigger Section 34 GST credit notes on accepted debits. See OEM-Tier 1 settlement and debit-note reconciliation and How Indian auto-component suppliers handle OEM short-pays for the full workflow.

SAP records the bank credit and the eventual GL postings. It does not parse the OEM payment advice, classify by reason, or maintain the FOMP running account per OEM per programme. This is the highest-frequency, highest-value reconciliation stream at any Tier-1, and SAP’s absence here is the single biggest driver of custom-ABAP investment.

Section 143 deemed-supply alerting

A Tier-1 sending semi-finished parts to platers, heat-treaters, and machinists under Section 143 of the CGST Act on Rule 55 delivery challans must return the goods within 12 months for inputs or 3 years for capital goods. Failure triggers deemed supply with 18% interest. See Tier-2 sub-vendor job-work reconciliation under Section 143 for the underlying mechanics.

SAP records outbound and inbound challans. It does not run a continuous countdown clock per challan with escalation alerts at day 270 / 330 / 360 of the 365-day window. ITC-04 quarterly filing data is reportable from SAP but the early-warning that prevents deemed-supply exposure runs externally.

Tooling amortisation cap monitoring

A supplier recovers tooling investment per-part over a committed volume. Cumulative parts shipped exceeding the contractual cap triggers a clawback. SAP records the parts shipped and the cumulative quantity, but it does not monitor cumulative recovery against the contractual cap per programme, generate alerts at 80% / 95% / 100% of cap, or compute the over-recovery liability automatically.

KLT bin float with GST exposure

Returnable KLT bins move on Rule 55 delivery challans (no GST). If bins are not returned within the contractual window, the movement can become a deemed supply attracting GST. SAP records bin gate-passes, but does not run net bin-position tracking per OEM per plant per bin type, deemed-supply alerting against the return window, or deposit-vs-float reconciliation. See Returnable packaging and KLT bin reconciliation for the underlying mechanics.

Rule 37 ITC reversal ageing

Every OEM short-pay residual that sits unpaid past 180 days from invoice date triggers Rule 37 ITC reversal at the OEM end, who then forces resolution on the supplier. SAP records the unpaid residual but does not bucket it into 60 / 90 / 150 / 180-day ageing with escalation triggers per bucket. See Rule 37 / 37A ITC reversal on supplier default for the underlying compliance flow.

Section 34 GST credit-note calendar trigger

Every accepted OEM debit triggers a supplier-issued GST credit note under Section 34 with a hard 30-November-of-next-FY cutoff. SAP records the credit note once it is issued, but does not run a per-source-invoice calendar trigger that flags approaching cutoffs. Lapsed Section 34 windows on accepted debits become unrecoverable GST liability — a real annual loss at Tier-1 scale.

The custom-ABAP trap — pattern of failure

The pattern repeats across Tier-1s on SAP S/4HANA, year after year:

Phase 1 (year 1): Tier-1 goes live on S/4HANA. Finance discovers CUM drift, FOMP decomposition, and RMPV gaps. Hires a 2-3 person ABAP team. Builds custom modules for the first OEM customer (typically Maruti or Tata). Works.

Phase 2 (year 2): Second OEM customer (different scheduling-agreement variant, different debit-note format, different RMPV index basis). ABAP team forks the modules. Conditional branches multiply.

Phase 3 (year 2-3): Third and fourth OEMs added. Codebase carries six conditional branches per module. Maruti e-Nagare portal update breaks the Maruti branch. Tata SRM portal change breaks the Tata branch. Bug-fix backlog grows.

Phase 4 (year 3-4): Senior developer leaves. New developer estimates 9-month rebuild for clean architecture. Backlog of new features (Section 143 alerting, KLT bins, tooling cap) keeps growing. Annual cost ₹40-60 lakh, with no end-state.

Phase 5: CFO halts new feature spend, freezes ABAP team, and starts the build-vs-buy conversation.

The structural issue is that the auto-component reconciliation streams are not really SAP customisations — they are independent reconciliation processes that happen to need SAP data as input. Forcing them into custom ABAP creates a maintenance burden disproportionate to the value.

The TransactIG-as-SAP-companion positioning

The companion-product thesis is straightforward: SAP retains transactional system-of-record status; the companion runs the standing-exception streams externally, connecting through standard SAP data extracts (scheduled IDoc exports, custom report exports, file drops via SFTP). Write-back to SAP is limited to user-defined fields carrying exception status, so SAP’s core configuration is not touched.

This works because:

• The standing-exception streams (CUM drift, RMPV, FOMP, Section 143, tooling, bins, Rule 37, Section 34) are reconciliation processes, not transactional postings. Keeping them external avoids burdening SAP’s transactional layer.
• SAP extracts are stable interfaces — scheduling-agreement extract, GRN extract, MIRO extract, IDoc DELFOR/DESADV/INVOIC. Portal-specific OEM variations get handled in the companion’s connector layer, not in SAP custom ABAP.
• Income Tax Act 2025 codes (Section 393(1)(a) code 1002, 393(1)(k) code 1012, 394 code 1071) and GST overlays (Section 34 calendar, Rule 37 ageing) get encoded once in the companion’s tax overlay, not per-OEM in custom ABAP.

Worked example — Tier-1 on SAP S/4HANA, ₹400 crore revenue, 4 OEM customers

A Tier-1 brake-system supplier in Pune:

• Revenue ₹400 crore, four OEMs (Maruti ₹150 crore, Tata ₹110 crore, Mahindra ₹80 crore, Bosch ₹60 crore)
• SAP S/4HANA live since 2024, custom ABAP team of 2 developers
• Annual ABAP fully-loaded cost: ₹50 lakh (salaries + overhead)
• Open backlog: 18 features across CUM drift completeness, RMPV claim automation, Section 143 alerting, KLT bin float, tooling cap monitoring

The build path:

• Year 1-3 sunk cost: ₹150 lakh
• Year 4 estimated rebuild: ₹65 lakh + 9 months
• Year 4-onward run-rate: ₹50 lakh annually
• 5-year total cost: roughly ₹400 lakh
• End-state: covers maybe 60-70% of the standing-exception streams; never closes RMPV recomputation against external indices; KLT bin GST exposure remains in Excel

The buy path:

• Implementation: 2-4 weeks on AWS Mumbai (ISO 27001:2022)
• Configuration of the 24+ industry presets including auto-component, with the four-OEM customer master and the per-programme tooling and RMPV configuration
• SAP integration via standard extract endpoints — scheduling-agreement export, GRN export, MIRO export, IDoc DELFOR/DESADV
• ABAP team redirected to core SAP roadmap (Tax / S/4HANA upgrades / EWM if applicable)

The buy economics tend to favour buy by OEM number three. A single-OEM Tier-1 might keep custom ABAP; a four-plus-OEM Tier-1 reaches break-even on the companion product comfortably inside 18 months.

Tax overlay — Section 393, 394 and the SAP configuration burden

The Income Tax Act 2025 framework effective from 1 April 2026 changes TDS code mapping across every Tier-2 vendor payment in SAP. Specifically:

• Section 393(1)(a) code 1002 — contractor TDS at 1% / 2% on Tier-2 job-work (heat treatment, plating, machining, painting, sub-assembly). Replaces legacy Section 194C. See TDS payment code 1002 — Section 393(1)(a) contractor and the full Section 393 TDS new Income Tax Act reconciliation.
• Section 393(1)(k) code 1012 — purchase TDS at 0.1% on aggregate raw-material purchase above ₹50 lakh per supplier per FY. Replaces legacy Section 194Q. See TDS payment code 1012 — Section 393(1)(k) purchase goods.
• Section 394 code 1071 — scrap TCS at 1% on skeleton scrap and other auto-component process-loss sales. Replaces legacy Section 206C(1).
• Section 413 code 1062 — TDS on foreign-agent commission for export programmes. Relevant to suppliers with export incentive flows.

SAP’s withholding-tax configuration handles code-based deduction natively, but the migration from legacy 194x codes to the new 1001-1092 framework typically requires a configuration project of 4-8 weeks at a Tier-1 — separate from the standing-exception streams above. The Income Tax Department of India publishes the framework reference at the Income Tax Department of India website.

GST law (Section 17(5), Section 34, Section 143, Rule 36(4), Rule 37, Rule 43, Rule 55) remains unchanged by the Income Tax Act 2025. The GST overlay in SAP and the companion product follows the pre-existing CGST configuration.

What automated reconciliation changes for a SAP Tier-1

Purpose-built reconciliation software India treats each standing-exception stream as a structured variance process and surfaces only the lines that fail to match. TransactIG carries 24+ industry presets including an auto-component configuration that handles CUM drift, RMPV recomputation against commodity indices, FOMP reason-coded decomposition, Section 143 deemed-supply alerting, tooling cap monitoring, KLT bin float, Rule 37 ageing, Section 34 GST credit-note calendar, and Section 393 / 394 code overlay — all sitting outside SAP’s core, connected via standard data extracts. Customer outcomes include match-rate improvement from 51% to 88% and exception rates moving into the sub-15% band post-implementation. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound procurement side see three-way matching software India.

Continue reading

Sibling articles in the auto-component cluster:

• OEM delivery schedule and EDI/ASN reconciliation
• Raw material price escalation clause reconciliation
• Tier-2 sub-vendor job-work reconciliation under Section 143

Up the chain:

• Sub-pillar: Automotive component manufacturing reconciliation in India
• Pillar: Manufacturing reconciliation in India
• Money pages: three-way matching software India · reconciliation software India