Company code mergers, carve-outs and post-merger harmonisation in SAP.
The legal merger is signed. SAP has not noticed.
A merger completes on paper long before the systems agree. Until the company codes are brought together, finance runs two sets of books, closes twice, reconciles intercompany balances that no longer exist between separate legal entities, and explains the gap to auditors. A company code merger closes that gap — and it is a data and reporting exercise before it is a technical one.
Company code merger
The absorbed entity's balances, open items, assets and master data move into the surviving company code. The classic Buchungskreisverschmelzung after a legal merger.
Carve-out and divestment
The mirror case: one entity leaves. Its data is extracted into a separate system or company code, and cleanly removed from the group it is leaving.
Chart of accounts harmonisation
Two entities, two account structures, one target. Mapping is designed once and applied to balances, open items and whatever history comes with them.
Org structure alignment
Controlling areas, operating concerns, plants, sales organisations and purchasing organisations remapped so the merged entity reports as one business.
Opening balances, or the whole history
This is the first decision, and it drives everything else — effort, audit position, and how long the old company code has to stay alive.
| Opening balance transfer | Full history transfer | |
|---|---|---|
| What moves | Balances and open items at the merger date | Line items and documents for the agreed periods, remapped |
| Effort | Lower — weeks rather than months | Higher — mapping and reconciliation per period |
| Reporting continuity | Comparatives need the old code or a separate report | Prior-year comparatives available natively in the target |
| Old company code | Stays open read-only for historical reporting | Can be retired sooner once history is validated |
| Audit position | Simple to explain: a transfer at a defined date | Needs documented mapping and traceability per document |
| Typical fit | Small entity, clean books, merger at year end | Large entity, mid-year merger, history needed in the target |
What has to be decided and reconciled
The technical merge is the easy part. These are the decisions that determine whether the first close after the merge is quiet or painful.
Finance
- Legal merger date versus technical merge date
- Fiscal year variant alignment
- Chart of accounts mapping
- Local and group currency treatment
- Open AR and AP items with their ageing
- Fixed assets with depreciation history
- Retained earnings and equity accounts
Tax & compliance
- VAT registration and tax code mapping
- Tax reporting for the pre-merger period
- Withholding tax configuration
- Statutory reports still owed by the absorbed entity
- Retention obligations for the source data
- Audit trail from merged records back to origin
Master data
- Duplicate business partners across both entities
- Duplicate materials and article numbers
- Payment terms and bank details
- Pricing and condition records
- Credit limits and credit segments
- Dunning and correspondence settings
Controlling & logistics
- Controlling area and operating concern
- Cost centres, profit centres and hierarchies
- Internal orders and WBS elements
- Plants, storage locations, sales organisations
- Inventory and valuation
- Number ranges and document numbering
The list is long, but it is finite. What derails merges is discovering an item on it three weeks before the technical merge date — not the item itself.
The absorbed entity still owes reports
A merged company code is not a deleted one. The pre-merger period continues to attract statutory reporting, tax filings and audit questions, and the data behind them must remain accessible for the full retention period — commonly ten years under Swiss and German rules. Design for that from the start rather than discovering it during the first audit.
- The old company code typically stays open for reporting and closed for posting, with a documented block rather than an informal agreement
- Statutory and tax reports for the pre-merger period are identified up front, with a named owner for each
- Every merged record keeps a reference to its source entity, document and period, so any figure can be traced back
- Retention and archiving are designed alongside the merge, not deferred to a later clean-up project
- The merge approach, mapping rules and reconciliation results are documented as audit evidence while the work is being done
From legal close to one set of books
Merges are usually driven by a fixed legal date. The plan below works backwards from it, with the technical merge deliberately placed at a period boundary wherever the legal position allows.
- 0101
Legal and reporting requirements
2–3 weeksEstablish the legal merger date, which entity survives, what the absorbed entity still owes in statutory reporting, and what the auditors expect to see. Everything downstream depends on getting this right.
Merger dateReporting obligationsAudit expectations - 0202
Data assessment
3–4 weeksProfile both company codes: volumes, open items, asset registers, duplicate rates across business partners and materials, and any configuration that differs between them in ways that will not simply merge.
Volume profileDuplicate analysisConfiguration gap list - 0303
Mapping and design
4–8 weeksAccount mapping, org unit mapping, number range strategy and the rules for everything that exists twice. This is where the balance-versus-history decision is locked in and signed off by finance.
Account mappingOrg unit mappingRoute decision signed - 0404
Duplicate resolution
runs in parallelBusiness partners and materials existing in both entities are matched, reviewed and merged by the data owners. Started early, because it is the workstream most likely to run long and it cannot be rushed at the end.
Match listsSurvivor rulesMerged master data - 0505
Test merges
2–3 cyclesFull merge runs in a copy of production, each reconciled against both source company codes and validated by finance. A test close on the merged code proves the result before it matters.
Reconciliation resultsTest closeDefect log - 0606
Merge cutover
period boundaryPosting block on the absorbed code, final reconciliation of both sides, the merge run, then verification before postings are released. Placed at a period end wherever the legal merger date permits.
Posting blockMerge runRelease to post - 0707
First close and audit pack
4–6 weeksSupport through the first close on the merged entity, and assembly of the evidence pack: mapping documentation, reconciliation results and traceability from merged records back to their origin.
First closeAudit packHandover
Where company code merges go wrong
Merges rarely fail on the merge run itself. They fail on the things around it.
Frequently asked
Do we have to merge the company codes at all?
Not always. If the entities remain legally separate, keeping separate company codes is correct. The merge becomes necessary when a legal merger means one entity no longer exists and finance is expected to report as a single company. Some groups also merge purely to simplify a landscape that grew through acquisitions.
Can we merge mid-year?
Yes, and it is common, because the legal date rarely lands on a fiscal year end. It costs more: tax and statutory reporting for the pre-merger period needs a clear plan, and the merged entity’s first annual report has to reflect both periods. Where the legal position allows any flexibility, a period boundary is easier.
What happens to the old company code?
Usually it stays in the system: open for reporting, closed for posting, retained for the full statutory retention period. Deleting it is rarely appropriate and rarely necessary.
How long does a company code merger take?
An opening balance transfer for a small, clean entity can run in six to ten weeks. A full history transfer for a large entity with duplicate master data and a mid-year date is a three- to six-month engagement. The duplicate resolution workstream is the usual driver.
Can this be done during an S/4HANA migration?
Yes, and combining them is often the efficient choice — you are already moving and reconciling the data. It works particularly well with a selective transition, where the merge mapping is applied as records transfer. It does raise the stakes of a single cutover, so it needs deliberate planning.
How do we keep the auditors comfortable?
By producing the evidence while the work happens rather than reconstructing it afterwards: documented mapping rules, reconciliation results per test cycle, traceability from every merged record back to its source, and a clear statement of the merge approach. We involve audit during design, not at the end.
Merger signed, systems not yet aligned?
Send us the legal merger date and the shape of both entities. We will come back with a realistic route — opening balances or full history — the workstreams involved, and where the schedule is tight.
This page is general information about SAP system and data transformation work. It is not legal, tax or accounting advice and does not replace binding advice from your auditors or advisors. Retention periods, reporting obligations and merger requirements differ by jurisdiction and by case.