Automotive supply is collaboration-intensive. A supplier exchanges forecasts, call-offs, order confirmations, shipping notifications, goods receipts, and invoices with customers above it and sub-tier suppliers below it, often many times a day, and frequently settles through models that reduce manual invoicing. SAP S/4HANA Cloud Public Edition supports this electronic collaboration through standard scope, chiefly by connecting to SAP Business Network and by offering settlement models such as evaluated receipt settlement and self-billing that automotive relationships commonly use.
This article describes those collaboration and settlement capabilities as they exist in the public cloud edition: electronic collaboration through SAP Business Network, self-billing, evaluated receipt settlement, subcontracting, and consignment, and the way electronic data interchange actually works in a multi-tenant SaaS system. The related modeling of call-offs through scheduling agreements is covered in the scheduling-agreements article, and the boundary on just-in-time and just-in-sequence is covered in its own article; this one concentrates on the collaboration and billing layer.
The standard route for electronic supplier collaboration in SAP S/4HANA Cloud Public Edition is SAP Business Network. The automation of source-to-pay with SAP Business Network connects the system to suppliers through SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network, and covers the electronic exchange of purchase orders, order confirmations, advanced shipping notifications, goods receipts, invoices, and payment advices.
For automotive, an important detail is that this integration supports not only purchase orders but also scheduling agreements and scheduling-agreement releases. That means the call-off model described in the scheduling-agreements article can be operated electronically with sub-tier suppliers: a release generated against a procurement scheduling agreement is transmitted through SAP Business Network, the supplier confirms and ships against it, and the advanced shipping notification allows goods receipt to be posted efficiently against the expected quantities. This gives an automotive supplier the same continuous, document-light collaboration upstream that its own customers expect from it downstream.
Self-billing is a settlement model in which the customer, rather than the supplier, creates the billing document based on the goods actually received, and the supplier reconciles against it. SAP explicitly identifies self-billing as a common billing process in the automotive industry, where high-volume, schedule-driven deliveries make supplier-issued invoicing for every shipment impractical.
SAP S/4HANA Cloud Public Edition supports self-billing through integration with the SAP Self-Billing Cockpit. The cockpit processes the self-billing documents a customer sends, matches them against the supplier's deliveries and expected values, and manages discrepancies so that differences between the customer's self-billing and the supplier's own records are identified and resolved. For an automotive supplier whose customers settle by self-billing, this capability allows the incoming settlement to be handled systematically rather than reconciled by hand.
Evaluated receipt settlement is the complementary model on the buying side. Under evaluated receipt settlement, the supplier does not send an invoice for a purchase; instead, the buyer settles automatically based on the purchase order or scheduling agreement conditions and the goods receipt. SAP S/4HANA Cloud Public Edition supports evaluated receipt settlement as standard: a supplier is flagged as relevant for the process in its business-partner data, and the settlement runs generate the supplier invoices from the receipts.
For an automotive supplier procuring direct materials on a call-off basis, evaluated receipt settlement removes a large volume of incoming invoices from sub-tier suppliers, settling instead from the agreed conditions and the confirmed goods movements. Combined with scheduling-agreement releases through SAP Business Network, it supports a lean upstream process where physical receipts, not paper invoices, drive settlement.
Automotive supply frequently involves parts that are finished, processed, or held under specific ownership arrangements, and the public cloud edition supports the two most common patterns as standard.
Subcontracting is available as a standard scope item. In a subcontracting process, the supplier provides components to a sub-tier supplier who performs an operation and returns the processed material; the system tracks the components provided, the expected finished material, and the consumption at the subcontractor. This is common where an automotive supplier outsources a specific process step while retaining ownership of the material.
Consignment is also supported. On the sales side, the consignment fill-up and pickup process lets a supplier place stock at a customer location while retaining ownership until the customer consumes it, at which point consignment issue triggers billing; consignment issue can be driven from a sales scheduling agreement in a business-to-business relationship, aligning consignment with the call-off model. Consignment is widely used in automotive to hold line-side stock at a customer without transferring ownership until consumption.
A critical point for anyone coming from an on-premise automotive background is that SAP S/4HANA Cloud Public Edition does not use the classic on-premise electronic-data-interchange model. On-premise automotive EDI relies on IDocs and ALE, delivery-forecast and just-in-time-call and shipping-notification message types exchanged through ports with message control. The public cloud edition, as a multi-tenant SaaS system, does not expose that toolset.
Instead, the equivalent message content, delivery forecasts, call-offs, order confirmations, and shipping notifications, is exchanged as application-programming-interface and business-to-business payloads routed through SAP Integration Suite and SAP Business Network, or through a certified partner EDI provider that connects to the public cloud edition. Output such as order confirmations can be issued on an EDI channel, and standard best-practice content includes an EDI variant of the sell-from-stock process. SAP-certified partner EDI integrations exist specifically for the public cloud edition for organizations that need direct trading-partner connectivity.
The functional outcomes an automotive supplier needs, exchanging forecasts and call-offs, confirming orders, sending and receiving shipping notifications, and settling electronically, are achievable. The design point is that they are achieved through cloud integration, and a project should plan the integration approach, whether SAP Business Network, SAP Integration Suite, or a certified partner EDI provider, rather than assume IDoc and ALE parity with an on-premise system.
Bringing the collaboration and billing layer together, an automotive project on SAP S/4HANA Cloud Public Edition should decide:
Handled this way, the collaboration and settlement processes that define automotive supply can be operated within standard SAP S/4HANA Cloud Public Edition scope, with the integration approach designed for the cloud rather than carried over from on-premise.