Global organizations rarely manufacture, warehouse, and sell goods out of a single legal entity. A product might be produced by a manufacturing subsidiary in one country, transferred to a distribution subsidiary in another, and finally sold to an external customer by a third entity, each one a separate company code within the same SAP S/4HANA client. Moving physical stock between plants that belong to different company codes, while keeping financial books, taxes, and inventory valuation clean on both sides, is the job of Intercompany Stock Transfer.
For decades, SAP handled this with the Classic Intercompany Stock Transport Order (STO). It works, but it was designed in the R/3 era and has real limitations when measured against today’s requirements for auditability, real-time financial visibility, and compliance with standards such as IFRS 15. To close these gaps, SAP introduced the Advanced Intercompany Stock Transfer process, first for SAP S/4HANA Cloud, private edition and on-premise (from release 2022), and later as a dedicated scope item (5HP) for SAP S/4HANA Cloud Public Edition, followed by multistage/multi-level support in the SAP S/4HANA 2025 release wave.
This article explains what Advanced Intercompany Stock Transfer is, how it differs from the classic process, the technical architecture behind it, the end-to-end document and goods-movement flow, configuration essentials, and the practical benefits and considerations for an implementation team.
1. What Problem Is Being Solved?
In a classic intercompany STO, physical stock moves from Plant A (Company Code 1) to Plant B (Company Code 2) using a purchase order at the receiving company and an outbound delivery at the supplying company. It is lean, few documents, quick to configure, but it has three structural weaknesses:
- No sales order in the delivering company. Because there is no sales order, the delivering company code cannot run standard sales-order-based KPI reporting (order-to-cash pipeline, backlog, sales performance) for intercompany volumes.
- Weak matching of revenue and cost. Billing and cost-of-goods-sold postings are not tightly synchronized with the point at which control of the goods actually transfers, which creates friction with IFRS 15 / ASC 606 revenue-recognition rules that require revenue and the related COGS to be recognized at the same time, when control passes to the buyer.
- Limited real-time visibility and orchestration. The classic process is essentially a chain of manually or batch-triggered documents with no built-in end-to-end monitoring layer.
Advanced Intercompany Stock Transfer (sometimes abbreviated AIC, or referred to by its Cloud scope item 5HP versus classic scope item 1P9) was built specifically to close these three gaps.
2. Classic vs. Advanced Intercompany STO
| Aspect | Classic Intercompany STO | Advanced Intercompany Stock Transfer |
|---|---|---|
| Sales order in delivering company | Not created | Automatically created (document type such as CBIC) |
| Orchestration | Manual / batch job chaining | Value Chain Monitoring (VCM) framework |
| Stock in transit | Often unvaluated or plant-to-plant in one step | Valuated Stock in Transit (VSiT), tracked with dedicated movement types |
| Revenue/COGS matching | Not tightly synchronized | Designed to support simultaneous recognition (IFRS 15 aligned) |
| Reporting on intercompany volume | Difficult, no sales order KPIs on delivering side | Full sales-order-based reporting available |
| Monitoring | No dedicated app | Monitor Value Chains Fiori app, Manage Financial Chain app |
| Multi-level (3+ company code) flows | Not supported | Supported from S/4HANA 2025 FPS01 (multistage AIC) |
| Availability | All S/4HANA releases | S/4HANA on-premise/private cloud from 2022 (OP2022/OP2023); S/4HANA Cloud Public Edition from scope item 5HP |
3. Core Concepts Behind the Advanced Process
3.1 Value Chain Monitoring (VCM) Framework
VCM is the orchestration engine underneath Advanced Intercompany Stock Transfer (and its sibling process, Advanced Intercompany Sales). Rather than relying on ad hoc batch jobs or manual follow-on document creation, VCM:
- Defines the sequence of documents that make up an end-to-end process (purchase order → sales order → outbound delivery → inbound delivery → goods movements → billing/invoice).
- Triggers follow-on documents automatically, either immediately or against a scheduled job, based on predefined “process templates.”
- Provides a single Fiori app, Monitor Value Chains, where a consultant or business user can select the leading document (the purchase order) and see the complete downstream chain, including any documents still pending or in error.
- For multistage/multi-plant chains (introduced with S/4HANA 2025 FPS01), VCM tracks a Financial Chain ID that links every leg of a multi-company-code transfer together, viewable in the Manage Financial Chain app.
3.2 Valuated Stock in Transit (VSiT)
Instead of goods simply disappearing from the sending plant and reappearing at the receiving plant, Advanced Intercompany Stock Transfer routes the movement through a valuated stock-in-transit bucket. This means the inventory has a financial value while it is “on the road,” and the system can post the transfer of economic control precisely, supporting accurate balance sheet reporting and clean audit trails while goods are physically in movement between company codes (including third-party logistics, EWM, or TM-managed transportation).
3.3 Matching Principle / IFRS 15 Alignment
Because the process creates a genuine sales order and delivery chain in the supplying company code, and because valuated stock-in-transit lets the system post goods movements at the moment control actually transfers, revenue and cost-of-goods-sold can be recognized together, directly supporting the IFRS 15 (and US GAAP ASC 606) matching principle. This is one of the primary business drivers cited by SAP for the redesign.
3.4 Document Types
- NBIC – Purchase Order / Stock Transport Order type used to trigger the Advanced Intercompany process. The “supplier” on this purchase order is a business partner that represents a plant belonging to a different company code.
- CBIC – The automatically generated Intercompany Sales Order type created in the supplying (delivering) company code once the purchase order is processed.
Exact document type keys can be relabeled during configuration, but NBIC/CBIC are the SAP standard defaults referenced in SAP’s own documentation and community content.
4. End-to-End Process Flow
A typical single-level Advanced Intercompany Stock Transfer, executed within one S/4HANA system across two company codes, runs as follows:
- Create the Purchase Order (Stock Transport Order). The receiving company code creates a purchase order using document type NBIC. The “vendor” is the business partner representing the supplying plant. This PO can be created manually or triggered by an upstream business process (e.g., MRP).
- VCM auto-creates the Sales Order. The Value Chain Monitoring framework automatically generates a sales order (document type CBIC) in the delivering company code, carrying over quantities, dates, and pricing-relevant data from the purchase order. An (advanced) ATP check can be used at this stage.
- Outbound Delivery. The delivering plant creates an outbound delivery against the sales order (e.g., via transaction VL10B or the corresponding Fiori delivery-creation app).
- Post Goods Issue (PGI). When PGI is posted (e.g., via VL02N), the system generates valuated stock-in-transit postings. Typical movement types include 681 (stock transfer to issuing valuated cross-company-code stock in transit, CST) and 685 (stock transfer from issuing valuated CST). Depending on release and scenario, including EWM-managed warehouses, movement types 683 and 685T are also used for goods issue into valuated stock in transit.
- Goods Receipt in Blocked Stock. Simultaneously, a material document posts the goods receipt at the receiving plant into valuated goods-receipt blocked stock, typically using movement type 107.
- Transfer of Control / Proof of Delivery. A transfer-of-control date (often linked to proof of delivery, POD) determines when ownership/control formally passes from the delivering to the receiving company. This date triggers the next wave of postings.
- Post Stock Transfer into Physical, Unrestricted Stock. Once the transfer-of-control date is reached, VCM automatically (or via a scheduled job) posts the receiving stock-in-transit into normal physical/unrestricted stock, typically using movement type 109, completing the physical receipt. The inbound delivery can also be posted manually through the Inbound Deliveries for Purchase Orders Fiori app or transaction VL32N.
- Billing. The delivering company issues an intercompany invoice to the receiving company code, based on the sales order/delivery. The receiving company processes this as a supplier invoice, matched against the original purchase order (logistics invoice verification), with the possibility to also route relevant tax codes for the transfer.
- Monitoring throughout. At every stage, the Monitor Value Chains app shows the full document chain (purchase order → sales order → outbound delivery → material documents → inbound delivery → billing/invoice → supplier invoice) so that exceptions and delays are visible in real time, rather than requiring users to trace documents manually across transactions.
4.1 Multistage (Multi-Company-Code) Extension
Starting with SAP S/4HANA 2025 FPS01, Advanced Intercompany processing extends beyond a simple two-company scenario to multistage chains, e.g., a manufacturing company code, a transit/central-distribution company code, and a final selling company code strung together (for example, DE → transit plant → SE). Each leg of the chain still uses valuated stock-in-transit, and the entire multi-leg flow is tracked under a single Financial Chain ID in the Manage Financial Chain app, so finance and supply-chain teams can see the full path a shipment (and its associated financial postings) takes across three or more legal entities.
5. Availability by SAP S/4HANA Edition
| Edition | Availability |
|---|---|
| SAP S/4HANA on-premise | From release 2022 (OP2022), further enhanced in 2023 (OP2023) and 2025 |
| SAP S/4HANA Cloud, private edition | Same functional scope as on-premise, from the 2022 release wave |
| SAP S/4HANA Cloud, Public Edition | Delivered as scope item 5HP, Advanced Intercompany Stock Transfer, layered on top of scope item 1P9, Intercompany Stock Transfer (Classic); the two scope items can technically coexist |
Note that if scope item 5W2 – Group Valuation is active in the Public Cloud edition, the system will not allow classic intercompany processes to be activated in parallel, an important design decision to keep in mind for edition and scope-item planning.
Group Valuation (5W2) and end-to-end Value Chain Analysis are explicitly called out by SAP as scenarios where Advanced Intercompany processing is effectively a must-have, since both depend on the more granular, valuated stock-in-transit postings the advanced process provides.
6. Key Configuration Steps (SPRO)
Implementation teams generally work through configuration nodes under Materials Management and Sales and Distribution, including:
- Materials Management → Purchasing → Purchase Order → Advanced Intercompany Processes → Enable Value Chain Monitoring for Purchase Orders — activates VCM-based orchestration for the relevant purchase order document type(s), such as NBIC.
- Materials Management → Logistics Invoice Verification → Advanced Intercompany Processes → Assign Tax Codes for the Transfer of Supplier Invoices — maps tax codes so intercompany supplier invoices post with the correct tax treatment.
- Materials Management → Logistics Invoice Verification → Advanced Intercompany Processes → Configure Program Parameters — sets program-level parameters controlling how the advanced process behaves during invoice verification and related background processing.
- Corresponding SSCUI-based configuration exists for the Public Cloud edition (e.g., “Enable Value Chain Monitoring for Purchase Orders” SSCUI), alongside pricing setup that must be maintained independently for the purchase order and the auto-generated sales order.
Key SAP Notes referenced in SAP’s own guidance for this process include:
- 3233845 – Configuration steps for Advanced Intercompany Stock Transfer in SAP S/4HANA
- 3283316 – Scope activation of technical job definitions in VCM processes
- 3366080 – SAP S/4HANA 2023 restrictions relevant to Advanced Intercompany Stock Transfer
As with any SAP Note reference, teams should verify current content and applicability against their exact release/support package in the SAP Support Portal, since notes are periodically updated.
Prerequisites commonly called out by SAP and implementation practitioners:
- SAP S/4HANA on-premise 2022 FPS00 or higher (for the on-premise/private-cloud variant).
- SAP Fiori front-end server must be installed, since monitoring and several process steps are Fiori-app-driven.
- Classic ATP (or Advanced ATP, depending on scenario) is used for availability checks during purchase order creation.
- Business partner master data correctly set up so that the “vendor” on the NBIC purchase order maps to the correct supplying plant/company code combination.
7. Relevant Fiori Apps
| App | Purpose |
|---|---|
| Monitor Value Chains | End-to-end visibility of the document chain from purchase order through invoice; primary troubleshooting and process-monitoring tool |
| Manage Financial Chain | Visualizes multistage/multi-company-code chains under a single Financial Chain ID (from S/4HANA 2025 FPS01) |
| Inbound Deliveries for Purchase Orders | Manual processing of inbound deliveries / goods receipt where automatic posting via VCM is not used |
| Set Material Prices | Maintaining intercompany pricing conditions (e.g., condition type such as PPR0) independently for purchase order and sales order pricing |
8. Benefits Summary
- True sales-order visibility in the delivering company code, enabling standard SD reporting (pipeline, backlog, order-to-cash KPIs) for what were previously “invisible” intercompany moves.
- IFRS 15 / matching-principle alignment, with revenue and COGS recognized together at the point control actually transfers.
- Valuated stock-in-transit for more accurate, auditable inventory valuation while goods are physically moving, including scenarios with EWM- or TM-managed warehouses and third-party logistics providers.
- Built-in orchestration and monitoring through the Value Chain Monitoring framework, replacing manual document chaining with a governed, trackable process.
- Support for complex, multi-entity supply chains, including multistage flows spanning three or more company codes, tracked end-to-end via a single financial chain identifier.
- Coexistence with classic processes in many scenarios, allowing phased rollout rather than a forced big-bang cutover (subject to the Group Valuation/5W2 restriction noted above).
9. Considerations Before Implementing
- Not a drop-in replacement. Advanced Intercompany Stock Transfer is functionally richer but also introduces more moving parts (VCM jobs, additional document types, additional movement types); implementation and testing effort is higher than for the classic STO.
- Release dependency. The functionality is only available from specific releases/support package levels (2022 FPS00+ on-premise/private cloud; scope item 5HP for Public Cloud); older systems require an upgrade before adoption.
- Group Valuation interaction. In the Public Cloud edition, activating Group Valuation (5W2) forecloses parallel use of the classic process, which should factor into scope-item planning during a Public Cloud implementation.
- Master data and pricing discipline. Because purchase order pricing and sales order pricing are maintained independently, teams need clear governance to keep intercompany pricing consistent and avoid margin/valuation discrepancies.
- Change management for finance and logistics teams. The additional sales order, valuated stock-in-transit postings, and new monitoring apps represent a process change for both supply chain and finance/controlling teams who are used to the leaner classic flow.
10. Conclusion
Advanced Intercompany Stock Transfer represents SAP’s response to a long-standing gap in intercompany logistics: the lack of a genuine sales-side document and tightly synchronized financial postings when stock moves between company codes. By introducing an automatically generated intercompany sales order, valuated stock-in-transit, and the Value Chain Monitoring framework for orchestration and visibility, SAP S/4HANA now offers a process that is not only more transparent operationally but also better aligned with modern revenue-recognition standards like IFRS 15. With the 2025 release wave extending the model to multistage, multi-company-code chains, the functionality is increasingly relevant for larger, more complex group structures, while the classic STO remains available for organizations whose intercompany flows are simple enough not to need the additional sophistication.
