# SAP S/4HANA Intercompany Process Setup Guide: STO, Pricing, Billing and Reconciliation > Source: https://netray.co/erp-help/sap-s4hana-intercompany-stock-transfer-billing-setup-guide > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer The intercompany stock transfer flow in S/4HANA runs from a stock transport order (ME21N) in the receiving company, through a delivery (VL10B) and goods issue from the supplying plant, to goods receipt, intercompany billing (VF01 with billing type IV), and an incoming invoice in the receiving company. Setup needs plants, customer and vendor assignments, delivery type, intercompany pricing and account determination. ## Kind how-to ## System sap ## Erp SAP S/4HANA ## Module MM / SD Intercompany ## Query sap s4hana intercompany process set up guide ## Alternate Queries - intercompany stock transfer order S/4HANA - sap intercompany billing setup - intercompany STO configuration - sap intercompany reconciliation ## Applies To SAP S/4HANA on-premise (1909 and later); steps for ECC are similar, with Business Partner replacing separate customer and vendor masters in S/4HANA ## Steps ### How to set up the intercompany process **Items:** - Create the plants, and assign each to its own company code (OX18). The supplying and receiving plants belong to different company codes. - Maintain the receiving plant as a customer and the supplying plant as a vendor via Business Partner (BP), and enter these numbers in the plant details so SAP finds them. - Assign a delivery type and checking rule to the document type and supplying plant (OMGN), typically delivery type NL for intercompany STO. - Define a supplying plant for the receiving plant in the purchasing info or the material's procurement settings, so STO and MRP can find the source. - Set the intercompany billing: billing type IV, copy control from the delivery, and an intercompany price condition (commonly PI01 for the price per item or IV01 for a percentage). - Create account determination for the intercompany billing and for the inventory transfer, so the sales and COGS-type postings are separated correctly. - Test the whole cycle: ME21N > VL10B > VL02N (goods issue) > MIGO (goods receipt) > VF01 (IV) > MIRO, then compare balances in both company codes. ## Sections ### Stock transfer versus intercompany sales **Body:** A stock transport order (document type UB for intra-company, and a type configured for intercompany use such as NB with supplying plant) moves stock between plants. Within one company code, it moves stock only. Between company codes, the stock movement must be paired with a billing step because legal entities exchange value. There are two broad designs. In the STO route, the receiving side raises a PO-based transport order and the supplier ships and bills. In the intercompany sales route, the receiving company places an ordinary sales order through a customer record. Both use billing type IV for intercompany billing. ### Pricing and the intercompany invoice **Body:** Intercompany pricing is a separate price. It is usually the transfer price, not the external sales price. PI01 uses a price per item from a condition record, and IV01 applies a percentage to the cost or sales price. The price is the base for the billing document IV. The IV billing document creates a receivable in the supplying company and, after the incoming invoice is posted via MIRO, a payable in the receiving company. Both entries are intercompany balances to be eliminated at consolidation. Transfer pricing is a tax and legal topic. Agree rates with finance and tax before you configure condition records. ### Reconciliation **Body:** Intercompany receivables and payables will never match unless goods issue, goods receipt and invoice are posted in the same period, so planned timing matters. Use a clearing process or an intercompany reconciliation app (the Fiori apps differ by release) to match open items. Run a simple stock in transit check, looking at delivered but not received quantities, to see where the process is stuck. **Code:** - -- Stock in transit: STO items issued but not fully received - SELECT EBELN, EBELP, MATNR, WERKS, MENGE, WEMNG - FROM EKPO WHERE EBELN IN (SELECT EBELN FROM EKKO WHERE BSART IN ('UB','NB')) - AND WEMNG < MENGE ## Pitfalls - Putting both plants in the same company code and then wondering why no billing happens. - Missing customer or vendor number on the plant, so the STO cannot determine the partner. - Using the external sales price for intercompany billing without tax review. - Posting goods issue and goods receipt in different periods, leaving large in-transit balances. - Missing account determination for the new combination. ## Ai Angle Finance IT teams use this to find intercompany documents that stopped between delivery, goods receipt and billing. Netray's ERPray can run this kind of lookup in plain language against your own SAP system, read-only by default, showing the query it ran and respecting SAP authorizations, with the model served on your own hardware when the system is on-prem. It explains and finds the data; it does not replace configuration decisions or post documents without human approval. ## Faq ### What billing type does SAP use for intercompany billing? **Answer:** The standard type is IV (intercompany billing), created from the delivery using copy control and an intercompany price condition. Your system may use a custom billing type derived from it. ### Is a stock transport order enough for intercompany transfers? **Answer:** Only if the plants are in the same company code. For different company codes you need the billing step so the legal entities record the sale and purchase, plus pricing and account determination. ### What is PI01 in SAP pricing? **Answer:** PI01 is the standard intercompany price condition type, a price per item maintained as a condition record. IV01 is the percentage variant used in intercompany billing. ### Does S/4HANA change the setup? **Answer:** The overall flow is the same as in ECC. The main differences are Business Partner for customer and vendor masters, the Universal Journal for postings, and new Fiori apps for monitoring and reconciliation. ## Search terms sap s4hana intercompany process, intercompany stock transfer order sap, intercompany billing IV sap, PI01 condition type, sap intercompany STO setup, sap intercompany reconciliation, OMGN delivery type checking rule, s4hana intercompany configuration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json