Intercompany Billing and Pricing: Internal Conditions and Automatic Account Determination
Explains how intercompany pricing conditions drive the internal invoice (IV) between the delivering and selling company codes, and how account determination posts the corresponding FI entries in both company codes.
Explanation
Intercompany sales only works correctly when two parallel financial views are kept consistent: the external customer invoice issued by the selling company code, and the internal intercompany billing document (commonly using billing type IV, though the exact type is client-configured) issued by the delivering company code against the selling company code as if it were a customer. Getting the pricing and account determination right for this internal document is where most functional consultants spend their configuration and support effort, because errors here directly cause unbalanced intercompany ledgers, blocked billing, or incorrect margin reporting. The internal price is captured through a dedicated pricing condition type (frequently referred to conceptually as an intercompany price condition) that is maintained in a separate condition record keyed by the delivering plant's sales organization and the ordering company code's sales organization, distinct from the customer sales price condition. This condition is included in the pricing procedure used for the intercompany billing document type, and it must be marked so it is relevant for account determination and, where required, statistical for the customer-facing pricing procedure so it does not distort the external price shown to the end customer. A common design decision is whether the intercompany price is a fixed transfer price, a cost-plus markup, or derived from a condition table keyed by material and delivering plant; whichever approach is chosen must be documented because it affects transfer pricing compliance and internal profitability reporting, not just SD configuration. Once pricing is correct, the billing document triggers account determination through the standard revenue account determination logic, but for intercompany billing the relevant condition type must be linked to account keys that post to intercompany revenue and intercompany cost of goods sold or clearing accounts rather than to normal external revenue accounts. This is configured through the account determination procedure assigned to the intercompany billing document type, with condition type to account key assignment done in the standard access sequence-based account determination configuration. It is critical that the account keys used for intercompany conditions are distinct from those used for customer conditions, because mixing them can post intercompany markup into external revenue lines and inflate reported turnover incorrectly. At the FI level, the internal billing document creates an accounting document where the delivering company code debits an intercompany receivable against the selling company code and credits intercompany revenue, while cost of goods sold is recognized in the delivering company code at the point of goods issue against the delivery. The selling company code, when it later posts its own vendor invoice or automatic clearing (in some configurations using EDI or IDoc-based automatic invoice receipt), records an intercompany payable and the corresponding cost of sales or inventory offset. Consultants must verify that the reconciliation accounts for intercompany trade partners are correctly assigned in each company code's customer/vendor master to avoid postings landing in the wrong reconciliation account. Common runtime issues include billing blocks caused by missing intercompany condition records, pricing errors when the condition table does not have an entry for a new material or plant combination, and split billing documents caused by different intercompany prices within one delivery. Troubleshooting typically starts with condition analysis in the billing document (checking which condition records were found and which are missing) before checking account determination analysis logs. In S/4HANA, the underlying account determination and pricing logic remains largely consistent with ECC, though embedded analytics and the ability to trace document flow through the universal journal give finance teams better visibility into intercompany balances without needing separate reconciliation reports.
Real project scenario
A retail group with company code 1000 (sales) and company code 2000 (manufacturing/delivering plant) went live with intercompany sales for a new product line. Within the first week, several intercompany billing documents failed to generate because the intercompany price condition record had not been maintained for the new material in the delivering plant's sales organization. The customer invoices were created and released to accounting, but no corresponding IV document existed, causing the intercompany receivable to be missing from company code 2000's books at month-end. The support team had to identify all affected deliveries via a document flow report, create the missing condition records retroactively, and manually trigger intercompany billing before the financial close, then work with the finance team to confirm no duplicate revenue had been posted.
Common mistakes
ā¢ Not maintaining the intercompany price condition record before go-live, causing billing document creation to fail or default to zero value ā¢ Using the same account key for both customer-facing and intercompany revenue conditions, corrupting external revenue reporting ā¢ Forgetting to mark the intercompany condition as statistical in the customer pricing procedure when it should not affect the external price ā¢ Overlooking reconciliation account setup for the intercompany trade partner in customer/vendor master records ā¢ Assuming the intercompany price will always equal cost, without agreeing a transfer pricing policy with finance and tax teams ā¢ Not testing split billing scenarios when a single delivery contains materials priced differently at the intercompany level
Best practices
ā¢ Maintain intercompany price condition records proactively whenever new materials or delivering plants are added to the intercompany process ā¢ Use distinct account keys for intercompany revenue/COGS conditions versus customer-facing conditions ā¢ Align the intercompany pricing methodology (cost-plus, fixed transfer price, market-based) with finance and tax/transfer-pricing stakeholders before configuration ā¢ Build a recurring reconciliation check comparing intercompany billing documents to corresponding customer invoices to catch missing or duplicate postings early ā¢ Use condition and account determination analysis tools on failed billing documents before escalating as a technical defect ā¢ Document the intercompany billing document type, condition types, and account keys in a functional design reference for support teams
Interview angle
Interviewers commonly probe whether a candidate understands that intercompany billing runs through a distinct pricing procedure and account determination path separate from the customer invoice, and whether they can explain how a missing intercompany condition record manifests as a billing block or zero-value document. Be ready to describe the difference between statistical and value-relevant conditions, and how you would troubleshoot a scenario where intercompany revenue posted to the wrong account.