SAP Cross Company Code Clearing

The Hackett Group put excess working capital across European companies at roughly €1.4 trillion in its 2025 Europe Working Capital Survey, equivalent to around 14% of aggregate revenue. A large share of that sits in the seams between legal entities, in balances that net to zero across the group but stay open on individual ledgers because nobody has cleared them yet. For a multi-entity manufacturer running dozens of SAP company codes, SAP cross company code clearing is where that cash stalls. Standard SAP clears open items automatically inside a single company code, but not across them, and the difference shows up every month-end as hours of manual work.

For the finance lead who owns the close, the cost is felt as days. The group cannot consolidate until the slowest entity finishes, and intercompany items are routinely the last thing to agree. For the accounts clerk doing the clearing, the cost is felt as repetition: opening the same accounts, matching the same offsetting items by hand, posting the same journals, then doing it again next month because the process never got faster.

What standard SAP automatic clearing F.13 actually does

SAP has a capable automatic clearing engine. Transaction F.13, which runs the program SAPF124, groups open items that net to zero and clears them without manual intervention. The matching criteria are configured in OB74: assignment field, amount, document or reference fields, and so on. It works across customer, vendor and G/L accounts, and a well-configured F.13 run can clear a high volume of routine items overnight (SAP Help Portal, SAPF124).

Where F.13 does not reach, the manual transactions take over. F-03 clears G/L accounts by hand. F-44 clears vendor accounts by hand. An accountant opens the account, selects the offsetting items, confirms the balance is zero, and posts. For a single entity with tidy ledgers, that is a small task. The volume is the problem, not the mechanism.

The constraint that matters for a group is the boundary F.13 runs inside.

Can SAP clear open items across company codes automatically?

No. SAP automatic clearing through F.13 operates within a single company code only. It cannot automatically clear open items that span two or more company codes. Those cross-company items are cleared by hand using F-03 or F-44, or routed through intercompany clearing accounts someone configures and maintains.

Why SAP cross company code clearing is still manual work

The standard answer to cross-company balances is the intercompany clearing account, configured in OBYA. You define a pair of clearing accounts for each company-code relationship, and cross-company postings route through them so each entity’s books stay balanced. That keeps the accounting correct. It does not make the clearing automatic.

Two limits surface as a group grows. First, the configuration scales by relationship, not by entity. Ten company codes that all transact with each other imply a large grid of OBYA pairings to set up and keep current. Add a country, restructure a division, or onboard an acquisition, and the grid has to be revisited. Second, even with OBYA in place, the open items sitting on those clearing accounts still need clearing. F.13 will only clear them within each company code’s own postings, so the cross-entity matching, the part where an item on entity A offsets an item on entity B, comes back to F-03 and F-44 and a person working through the list.

The result is a predictable month-end pattern. Intercompany rarely agrees first time. Someone exports the open items from each entity, lines them up in a spreadsheet, finds the mismatches, chases the counterpart team for the missing document, and posts the corrections by hand. At a handful of entities, that is an afternoon. Across dozens of company codes in several countries, each with its own currency and local team, it is a standing item on the close calendar that consumes days and does not shrink year on year.

It compounds at the seams precisely where large manufacturers are most exposed. Anglo American runs finance across 56 sites in 15 countries and consolidated a federated patchwork of finance teams onto one S/4HANA platform (Berkeley Partnership). Diageo is consolidating three SAP ERP systems into one S/4HANA estate spanning 180 countries (SAP UK News, May 2023). The more company codes a group brings onto one platform, the more cross-company clearing it inherits, and standard SAP hands every one of those items back to a person.

The close days and trapped cash this creates

The cost lands in several places, and a finance director feels each of them.

Close duration is the visible one. Intercompany clearing tends to sit on the critical path because consolidation cannot complete while entity ledgers still carry uncleared cross-company items. A clearing process that runs by hand sets the floor on how fast the group can close, regardless of how good the rest of the close is.

Working capital is the quieter cost. An open item on a clearing account is cash the group cannot see clearly. Balances that net to zero across entities still read as open receivables and payables on individual ledgers until they are cleared, which clouds the cash position the treasury team is trying to manage. That is the slice of the Hackett figure that sits inside the reconciliation gap rather than in genuine trading terms.

Then there is control and audit. Manual clearing across entities means manual journals, and manual journals mean more for internal audit to test and more places for an error to enter. A group running statutory reporting in fifteen jurisdictions cannot afford the cross-company clearing step to be the weak link in its controls evidence.

There is also a human cost. The person doing this work is usually skilled and senior enough to be trusted with intercompany. They spend the back half of every month on repetitive matching that a machine could do, and the organisation loses the analysis they would otherwise produce.

How to clear open items across company codes in SAP without leaving SAP

The gap is specific and well understood: no automatic clearing across company codes. That makes it a clean thing to close, because the fix has to do exactly one job and do it inside the system the data already lives in.

Two architectural routes exist. One is an external platform that extracts SAP data on a schedule, reconciles it in its own cloud, and posts the results back. That adds a second system, a second copy of the data, a second security and residency review per country, and a second integration to re-validate at every S/4HANA release. The other is an add-on that runs inside SAP, using the existing logins, authorisations and audit trail, with no data leaving the SAP boundary.

The BEST Open Item Clearing module takes the second route. It automates bulk clearing of open items across multiple company codes and account types using intelligent matching, all inside SAP. The module is built to apply matching rules across entities in a single run, so the cross-company items that F.13 hands back to F-03 and F-44 are matched and cleared automatically rather than by hand. Clearing posts through the same SAP documents and authorisations the team already uses, and the audit trail stays inside SAP where the auditor can see it.

Dis-Chem, Italtile and Netcare run Open Item Clearing for exactly this class of work, reducing manual clearing effort and the error rate that comes with it. The scale picture for what SAP-native reconciliation automation handles at multi-entity volume is clearest in BEST’s matching results elsewhere in the suite: Heineken Beverages runs Vendor Recons at a 99% auto-matching rate across more than 700 reconciliations a month, and Bacardi completed 40% more reconciliations through Balance Sheet Recons after moving the work into SAP. Those are vendor-statement and balance-sheet results rather than cross-company clearing figures, but they show the throughput an in-SAP matching engine sustains for a multinational drinks group at month-end.

The module carries three current SAP certifications, including S/4HANA Cloud Private Edition for RISE with SAP and BTP integration, so it travels with a migration rather than becoming a separate project to re-approve.

What to do with the gap

If your group runs more than a handful of SAP company codes, cross-company clearing is already costing close days and tying up cash you cannot see, whether or not it shows up as a line on anyone’s report. The question for the next close is how much of that work still needs a person.

Map it first. Count the company-code pairs that transact with each other, look at how many open items sit on the intercompany clearing accounts at month-end, and time how long the manual clearing actually takes across the group. The number is usually larger than the close calendar admits, because the work is spread across local teams and never aggregated.

Then decide where the matching logic should run. For a group already on SAP, or consolidating onto S/4HANA, keeping cross-company clearing inside SAP avoids re-solving residency, integration and audit for every entity. To see Open Item Clearing match and clear a live cross-company set, book a demo.

Sources: The Hackett Group 2025 Europe Working Capital Survey; SAP Help Portal (program SAPF124); Berkeley Partnership (Anglo American S/4HANA transformation); SAP UK News (Diageo, May 2023).