Every multinational group with more than one entity has intercompany service charges. A US subsidiary provides software engineering to the parent. A shared services center handles payroll for six affiliates. The parent’s legal team reviews contracts for a subsidiary. Each of these needs a transfer price, and that price needs documentation.
For many mid-market companies, intercompany services are the first transfer pricing issue they encounter. The amounts look small compared to goods or IP transactions, so they get less attention. That is a mistake. Services are where documentation tends to be weakest, and tax authorities have learned to start there.
Can You Charge for This at All?
Before debating markups, there is a threshold question that many companies skip: does this service pass the benefit test?
The benefit test asks whether the recipient entity gets economic value from the service. Would an independent company have paid for it, or performed the activity itself? If the answer is no, the charge is not defensible.
The clearest case: shareholder activities. Costs the parent incurs for its own benefit as a shareholder, like maintaining its stock exchange listing, investor relations, board governance, and consolidated group reporting. These are parent costs. They cannot be charged downstream regardless of the markup.
Where it gets harder is the gray zone. Consider a parent’s global cybersecurity team. They protect the entire group, including subsidiaries. That is a benefit. But what about the parent’s strategic planning function? If the strategic plan is set at the group level and the subsidiary simply executes, is the subsidiary benefiting from a service or receiving a directive? The answer depends on the facts, and the documentation needs to address it explicitly.
A real-world scenario: a European parent charges its US subsidiary a management fee that includes a line item for “strategic oversight.” On audit, the IRS asks what strategic decisions the subsidiary received input on, what alternative the subsidiary would have pursued without the input, and what an independent company would have paid for comparable advisory services. If the answers are vague, the entire line item gets disallowed.
The 5% Safe Harbor Is Narrower Than You Think
The OECD’s 2015 guidance introduced a simplified approach for low-value-adding intra-group services: charge cost plus 5%, with reduced documentation. Several countries have adopted this.
The temptation is to route as many services as possible through this safe harbor. But the qualifying criteria are specific. The service must be supportive in nature, not part of the core business of any group entity, and must not involve the use of significant intangibles or the assumption of significant risk.
What qualifies: general accounting, HR administration, basic IT helpdesk, payroll processing, travel booking.
What does not qualify: software engineering, contract R&D, strategic consulting, procurement, sales and marketing strategy, financial advisory. Any service that is itself a revenue-generating activity, that requires specialized expertise, or that uses proprietary tools or methodologies falls outside the safe harbor.
Companies that apply the 5% safe harbor to services that do not qualify are taking a position that will not survive audit scrutiny. The safe harbor provides simplified documentation requirements, not immunity from review.
Why Bundling Creates the Most Exposure
The most common structural problem with intercompany service charges is the bundled management fee. One invoice, one amount, covering everything from IT support to strategic advisory to legal to HR.
Here is what happens when this gets audited. The tax authority asks for a breakdown by service category. The company provides one, retroactively. The authority applies the benefit test to each category and disallows shareholder activities that were buried in the bundle. It then asks for benchmarking support for the remaining categories. The company has one benchmarking study (if any) against a generic comparable set that does not match any individual service. The authority rejects the benchmark and substitutes its own, typically for each service category separately.
The result: partial disallowance of the charge, plus penalties for insufficient documentation. The irony is that the underlying services may have been priced within arm’s length ranges. The problem was structural: the bundling made it impossible to demonstrate.
The fix is not complicated, but it requires upfront work. Categorize services into functional groups: administrative and back-office, IT and technology services, finance and accounting, R&D and engineering, sales and marketing support. Each group gets its own cost pool, its own allocation method, and its own markup based on a benchmarking study that matches the functional profile.
The CompPress library is organized along these lines: ten service profiles, each with its own comparable set and arm’s length range using net cost plus markup and FY 2022-2024 financials.
Setting the Price: Three Decisions
Once services are categorized, the pricing structure follows.
First, the cost base. Which costs are included? Direct labor and materials, obviously. But what about parent allocations for shared infrastructure? What about stock-based compensation? These choices change the markup materially. The treatment needs to match how comparable companies report their costs. For a detailed discussion, see our article on net cost plus markup.
Second, the allocation method. For services provided to multiple affiliates, costs need to be divided. The allocation key should reflect the actual consumption of the service: headcount for HR services, number of users for IT, revenue or transaction count for finance. Arbitrary splits (dividing equally across all entities) are easy to challenge because they rarely reflect reality.
Third, the markup. For services outside the low-value-adding safe harbor, this comes from a benchmarking study. The functional analysis determines the tested party’s profile, and the benchmarking study identifies the arm’s length range. Typical ranges vary: roughly 3% to 11% net cost plus markup for complex services like software engineering, lower for routine support functions.
What the Documentation Needs to Show
Four things, in order of how often they cause problems on audit:
The benefit test. Not a one-line statement (“services benefit all group entities”) but a specific explanation for each service category. What was provided, why it has value to the recipient, and why an independent party would have paid for it.
The cost base and allocation. What costs are in, what is out, and how shared costs are divided. Changes in methodology from year to year, without justification, are a red flag.
The intercompany agreement. A written contract describing the services, pricing mechanism, and payment terms. In many jurisdictions, no agreement means no deduction, regardless of whether the pricing is arm’s length.
The benchmarking support. Either the low-value-adding safe harbor (with evidence that the services qualify) or a benchmarking study matching the functional profile. Not both. Not neither.
A Closing Note
Intercompany services are the transfer pricing issue that affects the most companies and receives the least documentation effort. The framework is well established. The companies that get into trouble are not the ones that set the wrong markup by two percentage points. They are the ones that cannot answer a basic question: what exactly did the subsidiary receive, and why should it pay for it?
Frequently Asked Questions
What is the benefit test for intercompany services?
The benefit test asks whether the service provides economic value to the recipient, meaning whether an independent party would have been willing to pay for it. Services that benefit only the parent (shareholder activities, investor relations, group-level compliance) generally cannot be charged to subsidiaries.
What is the OECD safe harbor for low-value-adding services?
The OECD's 2015 guidance provides a simplified approach: a 5% markup on costs for services that are supportive in nature, not part of the core business, and do not require significant intangibles. Not all countries have adopted this safe harbor, and qualifying criteria vary by jurisdiction.
How do I allocate costs for shared services?
Common allocation keys include headcount, revenue, number of transactions, or time spent. The key should reflect the actual driver of the cost. IT costs might be allocated by number of users. Finance costs by number of transactions. The method should be documented and applied consistently.
Should management fees be treated differently from other intercompany services?
Management fees are intercompany service charges, and the same framework applies. The challenge is that management fees often bundle multiple services with different functional profiles. Unbundling them into identifiable categories with separate benchmarks is more defensible than a single blended markup.