Irvine Analytics Get in touch
Analytics Catalog/SAP S/4HANA/Sales and Distribution/Intercompany sales
Explore the catalogModulesSales and DistributionBilling registerThe ledger-wave twin
SAP S/4HANA · Sales and Distribution · Control

One sale, two books, paired

The internal invoice posts automatically and agrees only with its own price list. May ran fourteen flows worth 186,300.00; twelve paired clean, and the two that booked 1,850.00 apart got named causes the day they posted.

RuleReconcile the two sides of every intercompany flow continuously, because the selling and delivering companies bill each other from price lists that drift apart.
Neverassume the automatic intercompany invoice means the books agree. It posts what its price list says, and the other side posted what its list said.
14 flows in May one group, two books 186,300.00 crossed the internal invoices Two flows apart 1,850.00 of drift
Intercompany billing automates the posting, not the agreement. The drift lives in diverged price lists.
◆ May flows, reconciledfourteen flows, two apart.
Intercompany, May 2026Count
Cross-company flows billed14
Internal invoices, both sides agreeing12
Flows booking apart2
The two mismatchesApart by
Flow 7, list price diverged1,100.00
Flow 11, freight on one side only750.00
Drift, May1,850.00

The 186,300.00 of internal invoices sits inside the register’s documents, typed as intercompany. The same disease on another platform is the ledger wave’s intercompany page: two books, one transaction, drift until reconciled. Sample values are illustrative, never client data.

◆ The automation that agrees with itselfprice lists drift, postings follow.

The delivering company bills the selling company automatically from its own price list, and the selling side books from its agreement. When the lists diverge, both postings succeed and the group mismatch is born clean. Practitioners report consolidation finding in weeks what a daily pair-off finds at posting.

Use case
Problem
Intercompany invoices auto-post from drifting price lists, both sides look correct locally, and consolidation inherits the argument.
What we build
Every flow paired continuously, both sides compared at posting, drift named by cause, and the price-list divergence fixed at the master.
What you get
Group books that agree before the close asks: drift in the open per flow, causes named, and the one-sided freight caught the day it posts.
How far apart are your intercompany books right now?
We pair every flow and name the drift.
Talk to us
Terms on this page
SAP
The vendor. Systems, Applications, and Products in data processing.
HANA
SAP’s in-memory database, the platform S/4 runs on.
SD
Sales and Distribution, the order-to-cash module.
intercompany flow
One sale shipped by a sister company; two books involved.
internal invoice
The automatic billing between the companies.
drift
The difference two correct-looking postings create.
pair-off
Matching both sides per flow at posting time.