S/4HANA implementations: The relevance of transfer pricing

An S/4HANA transformation not only changes systems and processes. It also affects how intra‑group transactions are captured, priced, booked and documented. Transfer pricing should therefore already be taken into account during the design phase.

Many multinational companies are currently migrating to S/4HANA or rolling the system out step by step in their local entities. These transformations are usually driven by finance, IT and process objectives: processes are to be standardized, manual activities automated, data quality improved and a uniform basis for management reporting established.

What is often underestimated is that changes to cost allocations, profit centre structures, master data and reporting processes can have a direct impact on the calculation and substantiation of arm’s‑length transfer prices. For multinational companies, the ERP transformation therefore offers a particular opportunity to make transfer pricing processes more efficient, transparent and robust in audits. If tax requirements are only addressed shortly before go‑live, key system decisions have usually already been taken and can only be corrected with considerable effort.

The topic has gained additional relevance through the OECD consultation document published on 1 June 2026 on the revision of Chapter VII on intra‑group services in the OECD Transfer Pricing Guidelines. For intra‑group services, particular focus is placed on the proper delineation of the transaction, the benefit test, the choice of method, the determination of the arm’s‑length remuneration and documentation.

1. Cost allocations and project costs

Corporate groups often recharge intra‑group IT services using ERP‑supported allocation keys. With the introduction of S/4HANA, these keys are frequently redesigned or automated. At the same time, significant centrally bundled expenditures arise before and during implementation, for example for global concepts, SAP licences and implementation services. These costs and their intra‑group recharging are regularly relevant in tax audits.

The allocation model should reflect the concrete benefit received by the recipient entities and take the phased roll‑out into account. Key questions include:

• Which SAP modules are being implemented and what specific benefits do they provide to each entity?

• When do the entities go live and how are units that join later integrated into the allocation key?

• Which allocation drivers – such as number of users, transaction volumes or revenue – best reflect the expected benefit?

• How are timing differences between cost incurrence and recharge addressed, and is a financing component to be taken into account?

1. Early design and regular review of the model help ensure that the cost base and allocation keys remain consistent with German and OECD transfer pricing guidelines and can be robustly defended vis‑à‑vis the tax authorities.

2. Profit allocation and accounting treatment

The enhanced reporting capabilities of S/4HANA increase transparency regarding the profitability of individual entities, business units and product lines. This can reveal deviations that were not visible, or only visible with a delay, in the previous ERP system. For example, a routinely remunerated sales company could consistently achieve margins outside the target range set out in the transfer pricing policy, without this being immediately visible.

The accounting and tax treatment of project costs also affects profit allocation. If implementation or licence costs are capitalised, the start date, duration and amount of depreciation influence the future results of the participating entities. Running expenses, on the other hand, impact the respective period directly. For intra‑group recharges, it is therefore necessary to determine which cost base is decisive and whether, in addition to pure cost recharges, a remuneration for implementation, support or licensing services should be applied.

The design should be consistent with the functional and risk profiles of the entities involved and with the actual control over project decisions. Profit and margin monitoring established at an early stage reduces the need for subsequent corrections and facilitates defence in tax audits.

3. Master data, intercompany processes and responsibilities

Migration to S/4HANA regularly requires a comprehensive overhaul of master data and transaction processes. Incorrect assignments of transactions, products, cost centres or legal entities can significantly distort transfer pricing calculations. If such errors are embedded in automated processes, long‑term inconsistencies arise that are difficult and costly to correct after go‑live.

From a transfer pricing perspective, it should therefore be defined from which data sources the relevant information is drawn, how intercompany transactions are identified in the system, and who is responsible for data quality, posting logic, approvals and controls. Close coordination between tax, finance and IT functions already during the design and test phases is essential.

4. Contracts, documentation and audit trail 

Transfer prices must not only be documented, but also implemented consistently in day‑to‑day business and in the ERP system. S/4HANA can provide a transparent audit trail for intra‑group transactions. This requires that the tax “target picture” is translated into posting logics, accounts, cost objects, workflows and reporting requirements.

Intercompany agreements should concretely reflect the scope of services, the entities involved, the cost base, allocation keys and the remuneration mechanism. For IT services, a robust benefit test is also required documenting the economic or commercial advantage for each recipient entity. This is particularly relevant when local entities already operate under existing and functioning ERP systems. Purely group‑strategic activities and shareholder costs must be distinguished from chargeable services and excluded accordingly.

In US‑inbound structures, SAP licences, implementation services and ongoing IT services are often initially bundled in the US or in a central group entity and subsequently recharged to German group entities. For the German transfer pricing analysis, the following questions are particularly important:

• Is a pure cost reimbursement appropriate, or should an arm’s‑length mark‑up or other remuneration be applied for implementation, support, financing or licensing services?
• Is the recharge based on capitalized project costs, running expenses or a combination of both categories?
• Which costs belong in the allocation pool, which items must be excluded and which allocation key appropriately reflects the benefit?
• Is the recharge based on capitalized project costs, running expenses or a combination of both categories?
• Is a pure cost reimbursement appropriate, or should an arm’s‑length mark‑up or other remuneration be applied for implementation, support, financing or licensing services?

The transfer pricing characterization depends on the actual set‑up. S/4HANA‑related activities or certain components can, in particular, be classified as intra‑group IT services, as joint development activities under a cost contribution agreement, or as licensing or granting of intangible assets. Each characterization has its own requirements regarding delineation of the transaction, pricing method, contractual arrangements and documentation.

We recommend that transfer pricing be integrated into the transformation as a dedicated workstream within a holistic approach. In the design phase, the target picture for intercompany processes, cost allocations and data requirements should be defined. In the build and test phases, it should be verified whether posting logics, interfaces and reports correctly reflect the transfer pricing policy. Before go‑live, contracts, benefit tests, documentation and governance processes should be aligned with the system design. After go‑live, regular controls enable deviations to be identified at an early stage and the model to be adjusted to further roll‑outs or process changes.

An S/4HANA implementation is far more than a technical system migration. It changes how intra‑group transactions are captured, charged, monitored and documented. At the same time, the design phase is often the decisive moment to embed cost allocation and transfer pricing models sustainably in the system before the roll‑out.

Companies that integrate transfer pricing early into their transformation agenda can reduce tax risks, make processes more efficient and strengthen their defence capability vis‑à‑vis the tax authorities. For US companies with activities in Germany, transfer pricing is therefore not a downstream compliance requirement, but an integral component of a successful ERP transformation project.