SAP Companion Products for Auto-Component Reconciliation: Why Native SAP Falls Short

A ₹400 crore Indian Tier-1 brake-system supplier in Pune runs SAP S/4HANA, live since 2024, supplying four OEM customers — Maruti, Tata, Mahindra and Bosch. The Tier-1 has built the ZSAR_* family of 11 ABAP Z-reports documented in SAP ABAP custom reports auto component reconciliation — CUM drift, ASN ageing, OEM debit-note decomposition (forked per OEM), RMPV claim, ITC-04 generation, free-issue reconciliation, tonnage billing, Section 393 / 394 split, tooling cap, KLT bin float, supplementary invoice reconciliation. Annual ABAP maintenance run-rate ₹65 lakh. The new ABAP lead’s clean-refactor estimate is 9 months and ₹70 lakh, with no functional gain. The CTO has commissioned a build-vs-buy review evaluating SAP-companion-product options against continuing the Z-report family.

This is the SAP-companion-product decision moment. Every Indian Tier-1 on SAP S/4HANA reaches it within 24-36 months of go-live. The question is not whether SAP S/4HANA is the right transactional ERP — for an Indian auto-component Tier-1 at ₹400 crore and above, SAP S/4HANA is generally the right ERP. The question is whether the auto-component reconciliation streams belong inside SAP or alongside SAP. This is the SAP companion auto component reconciliation India operating reference.

Quick reference

Why native SAP, however excellent, falls short of auto-component reconciliation

SAP S/4HANA is structurally a transactional system. Each transaction (purchase order, delivery, GRN, invoice, payment) is recorded with full audit trail, double-entry posting, and integration across MM / SD / FI / CO. For document mechanics, EDI transmission, three-way match against a purchase reference, AR and AP — SAP is comprehensive. The Indian Tier-1 base on SAP exists because SAP does these things well.

Reconciliation is structurally different from transactions. A reconciliation stream is a continuous matching process across two or more systems, over a window of time, often across currencies and across data formats. The auto-component-specific reconciliation streams cross several system boundaries simultaneously:

• CUM drift crosses the supplier’s SAP (ASN despatch records) and the OEM’s GRN system (visible only through the OEM portal). The supplier’s SAP cannot reconcile its own data against data it does not own.
• OEM debit-note decomposition crosses the bank credit (visible in SAP AR posting), the OEM payment advice (PDF or portal export, OEM-specific format), and the source invoices (in SAP). The decomposition logic is OEM-specific and changes over time.
• RMPV claim crosses an external commodity-index feed (JPC HR / CR coil, LME aluminium / copper / zinc, polymer index), the scheduling-agreement contractual coefficient, and the SAP quantity-supplied register. The index-feed is not an SAP object.
• ITC-04 multi-hop crosses the supplier’s SAP outbound and inbound challan registers and the downstream job-worker’s books, with the chain logic running outside SAP.
• Free-issue Rule 55 supplier-side tracking crosses the OEM’s outbound challan register (visible only as an inbound Rule 55 challan on the supplier’s side) and the supplier’s SAP consumption postings, with the Section 143 12-month / 3-year countdown running on the inbound challan date.
• OEM portal extracts are inherently cross-system — Maruti e-Nagare, Tata SRM, M&M Supplier Portal, SupplyOn — none of which are SAP objects.

Solving these cross-system reconciliation streams inside SAP creates the ZSAR_* Z-report family. The Z-report family forks per OEM customer, compounds in maintenance burden, and has no end-state. The companion product moves the reconciliation streams outside SAP, where they can be solved as cross-system processes natively.

The four-clock three-way match — the canonical companion-product example

Standard SAP three-way match aligns purchase order + GRN + supplier invoice through MM-LIV (Logistics Invoice Verification). For inbound procurement at a Tier-1, this works as designed. For outbound supply to the OEM, the equivalent alignment is a four-clock match — and it is not what SAP’s native three-way match does:

• Clock 1 — supplier ASN despatch (in SAP, IDoc DESADV01 outbound, time-stamped at despatch)
• Clock 2 — OEM GRN receipt (in OEM’s system, visible to supplier only through portal feed, time-stamped at receipt)
• Clock 3 — supplier invoice (in SAP, time-stamped at invoice raise)
• Clock 4 — OEM payment advice (OEM-specific format, time-stamped at remittance)

The reconciliation across the four clocks involves cum-quantity alignment between clocks 1 and 2, invoice-against-confirmed-receipt alignment between clocks 2 and 3, payment-against-invoice alignment between clocks 3 and 4, plus the decomposition of any payment-side shortfall into reason categories (FOMP, JIT shortage, quality reject, line-stop, tooling, technical service, transport). This is the canonical example of cross-system, cross-time reconciliation that SAP’s transactional three-way match does not address.

The companion product runs the four-clock match as a continuous process — pulling clock 1 from SAP IDoc / OData, clock 2 from OEM portal feed, clock 3 from SAP invoice register, clock 4 from OEM payment advice parser, aligning across the four time-stamps and producing exception lines.

How the companion product connects without disrupting SAP

The companion-product architecture is intentionally non-invasive to SAP’s core:

• IDoc outbound — message types DELFOR01 (inbound forecast acknowledgement), DESADV01 (outbound ASN), INVOIC02 (outbound invoice) routed to a port that drops to SFTP or to a third-party EDI middleware. The companion product consumes from the drop location.
• OData services on NetWeaver Gateway — exposed for on-demand object queries: scheduling agreement header / item / release, GRN, supplementary invoice, withholding tax register. Standard SAP services, no Z-code.
• Scheduled standard report exports — ME38 (scheduling agreement releases), MIGO (goods movements), J_1IG family (India Localisation registers), withholding tax register output, scheduled nightly to SFTP. No Z-code.
• Optional write-back — limited to user-defined fields carrying exception state (e.g., a Z-field on the scheduling-agreement line carrying the CUM-drift exception flag from the companion). Configuration-only, no Z-code.

This pattern keeps SAP’s core untouched, leverages SAP’s standard extract interfaces, and lets the companion product run the standing-exception streams as a separate concern. SAP support-pack cycles, Note applications, and S/4HANA upgrades do not break the companion’s interfaces — the standard IDoc message types and OData services are stable across SAP releases.

See ERP data extracts for auto-component reconciliation for the broader extract-layer architecture.

The 11-Z-report family versus a unified companion product

A ₹400 crore Tier-1 with four OEM customers typically carries an 11-Z-report ZSAR_* family. The maintenance run-rate, the fork-per-OEM pattern and the build-vs-buy economics are detailed in SAP ABAP custom reports auto component reconciliation. The decision input for the build-vs-buy review:

Build path — continue the Z-report family

• Annual ABAP maintenance run-rate: ₹65 lakh (at the 4-OEM Tier-1 scale)
• Rebuild investment in the near term: ₹70 lakh, 9 months
• OEM customer number five: ₹15-20 lakh incremental build effort + ongoing maintenance increment
• Five-year cumulative cost: roughly ₹400 lakh
• End-state: unchanged; still 8-12 Z-reports requiring continuous maintenance

Buy path — companion product

• Implementation: 2-4 weeks on AWS Mumbai (ISO 27001:2022)
• Auto-component industry preset configured for the four OEM customers
• Standard SAP extract connectors out of the box
• ABAP team (3 developers) redirected to core SAP roadmap: Tax migration (Income Tax Act 2025 codes), S/4HANA upgrade preparation, EWM evaluation, or simply absorbed into the OEM number five onboarding without the historical Z-report drag
• Z-report family decommissioned in tranches over 12 months as the companion takes over each stream

The build-vs-buy boundary tends to favour buy beyond OEM customer number three. A single-OEM Tier-1 might keep custom ABAP; a four-OEM Tier-1 reaches break-even on the companion product comfortably inside 18 months.

Worked example — ₹400 crore SAP-shop Tier-1 evaluating companion options

The Pune brake-system supplier introduced earlier:

Current state

• SAP S/4HANA live since 2024
• 11 ZSAR_* Z-reports in production, including 4 OEM-forked debit decomposition codebases and 3 OEM-forked RMPV codebases
• Annual ABAP maintenance run-rate: ₹65 lakh
• 18-feature open backlog: Section 143 standing alert engine, Section 34 GST credit-note calendar, Rule 37 ITC reversal ageing, KLT bin float Section 143 exposure refinements, Form 168 reconciliation against books
• Rebuild backlog estimate: ₹70 lakh, 9 months

Companion product evaluation criteria

• Standard SAP extract connectors (IDoc DELFOR01 / DESADV01 / INVOIC02 + OData on NetWeaver Gateway + scheduled report SFTP) — no Z-code required in SAP
• Auto-component industry preset covering the seven reconciliation streams
• Per-OEM payment-advice parser for Maruti e-Nagare, Tata SRM, M&M Supplier Portal, SupplyOn
• Commodity-index feed integration for JPC HR / CR steel, LME aluminium / copper / zinc, polymer / resin
• Income Tax Act 2025 codes 1001-1092 overlay in the companion’s tax overlay
• Implementation on AWS Mumbai with ISO 27001:2022, data residency in India
• Customer outcome reference: match-rate improvement from 51% to 88%

Transition plan

• Month 1-2: companion product implementation, SAP extract connectors configured, auto-component industry preset configured for 4 OEM customers
• Month 3-6: parallel run of Z-report family and companion product, reconciliation between the two for validation
• Month 7-12: tranche-wise decommissioning of Z-reports as the companion takes over each stream
• Month 13 onwards: ABAP team redirected to Income Tax Act 2025 code migration, S/4HANA upgrade preparation, OEM number five onboarding without the historical Z-report drag

Expected outcomes

• Annual run-rate reduction on the auto-component reconciliation surface
• ABAP team opportunity-cost recovery into core SAP roadmap value
• Faster cycle time on OEM-specific reconciliation refinements (companion product configuration changes versus ABAP development)
• Closed-loop visibility on the standing-exception streams with ageing and root-cause classification — currently fragmented across Z-reports

The CTO’s recommendation to the CFO: proceed with the companion-product evaluation; halt new Z-report development; cap the existing Z-report family at current scope; commission the rebuild only if the companion-product evaluation does not proceed.

Tax overlay — Income Tax Act 2025 in the companion-product architecture

The Income Tax Act 2025 framework effective from 1 April 2026 introduces the payment code framework 1001-1092 that the SAP withholding tax configuration carries through configuration. The companion product overlays the same code framework in its tax overlay so that the reconciliation streams (Form 168 reconciliation, withholding tax register reconciliation against books, cross-era 194x-to-1001-1092 reconciliation) run with the codes embedded:

• Section 393(1)(a) code 1002 — contractor TDS on Tier-2 job-work. See TDS payment code 1002 — Section 393(1)(a) contractor.
• Section 393(1)(k) code 1012 — purchase TDS on aggregate raw-material purchase above ₹50 lakh per supplier per FY. See TDS payment code 1012 — Section 393(1)(k) purchase goods.
• Section 394 code 1071 — TCS on scrap sales.
• Section 413 code 1062 — TDS on foreign-agent commission for export programmes.

The cross-era reconciliation between legacy 194C / 194Q / 206C(1) (before 1 April 2026) and the new codes (after) is handled in the companion product’s tax overlay through the effective-date logic on transactions, without requiring a Z-report extension in SAP.

GST law (Section 17(5), Section 34, Section 143, Rule 37, Rule 43, Rule 55) remains unchanged. The companion product handles the standing exception streams — Section 143 12-month / 3-year deemed-supply countdown, Section 34 30-November-of-next-FY credit-note cutoff calendar, Rule 37 180-day ITC reversal ageing — as continuous processes, not as Z-report periodic outputs.

Where this leaves a Tier-1 on SAP S/4HANA

SAP S/4HANA is the right transactional ERP for an Indian auto-component Tier-1 at ₹400 crore and above. SAP’s strength on document mechanics, EDI transmission, three-way match, AR / AP and GST returns is genuine. The auto-component reconciliation streams that SAP does not handle natively are not SAP defects — they are cross-system reconciliation processes that no transactional ERP handles natively. The companion-product category exists to fill this gap as an architecturally clean alternative to the ZSAR_* Z-report family. The build-vs-buy boundary tends to favour buy beyond OEM customer number three.

What automated reconciliation changes for an SAP Tier-1

Purpose-built auto-component reconciliation software India is designed as an SAP companion product for Indian auto-component Tier-1s. TransactIG consumes SAP standard extracts (IDoc DELFOR01 / DESADV01 / INVOIC02, OData on NetWeaver Gateway, scheduled standard report exports) plus OEM portal exports (e-Nagare, TML SRM, M&M Supplier Portal, SupplyOn) plus commodity-index feeds (JPC steel, LME metals, polymer indices) and runs the auto-component reconciliation streams (four-clock three-way match, cum-drift, OEM debit decomposition, RMPV claim, ITC-04 multi-hop, free-issue Rule 55, Section 143 alerting, Section 34 credit-note calendar, Rule 37 ITC reversal, Form 168 reconciliation) as continuous exception management. Customer outcomes include match-rate improvement from 51% to 88% and exception rates moving into the sub-15% band. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the procurement-side three-way match see three-way matching software India.

Continue reading

Sibling articles in the auto-component cluster:

• SAP scheduling agreement reconciliation auto India
• SAP ABAP custom reports auto component reconciliation
• ERP data extracts for auto-component reconciliation

Up the chain:

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