Plain English
When head office runs a shared IT system or HR function for the whole group, the cost has to be split among the subsidiaries somehow. An allocation key is that 'somehow' — headcount, revenue, number of transactions, IT tickets raised — chosen to reflect, as closely as possible, how much each entity actually benefits from or uses the service. Pick the wrong key and you're effectively mispricing dozens of intercompany charges at once, even if the total cost pool itself is entirely correct.
Technical definition
Cost allocation keys are the quantitative bases — such as headcount, revenue, assets, sales volume, IT users, or transaction counts — applied to distribute a pooled cost among the recipients of a shared service, selected so as to reasonably reflect the actual or expected benefit received by each entity, as required under OECD Chapter VII guidance on intra-group services.
Why it matters
The allocation key, not just the total cost pool, is frequently the actual point of dispute in a tax audit — two groups can have identical, well-documented total costs but produce very different, and differently defensible, entity-level charges depending on which key is used.
How it works in practice
- 01Identify the cost driver that most closely correlates with each entity's use of or benefit from the underlying service.
- 02Select a single key per service category, avoiding one-size-fits-all keys across dissimilar services.
- 03Gather reliable, auditable data to populate the key (e.g. headcount by entity as of a fixed date).
- 04Apply the key consistently period over period, documenting any change and its rationale.
- 05Periodically test whether the key still reflects actual usage as the business evolves.
Worked example
Revenue-based key mispricing an IT support charge
A group allocates its centralized IT support costs using revenue as the key, on the assumption that larger entities generate more IT tickets. Analysis of the helpdesk system shows this is not true: a small, headcount-heavy manufacturing subsidiary generates three times the ticket volume of a much larger but highly automated trading entity. Switching the key from revenue to number of active users (a proxy closely correlated with actual ticket volume) shifts a material portion of the cost from the trading entity to the manufacturing subsidiary, materially changing both entities' local margins and requiring updated local file narratives in both jurisdictions.
Common mistakes
- Using a single group-wide key (usually revenue) for structurally different service types.
- Never revisiting the key after the underlying business or headcount changes materially.
- Using unaudited or informally maintained data to populate the key.
- Changing the key year to year without documenting or explaining the rationale.
Audit red flags
- The same allocation key applied to IT, HR and legal services despite very different usage drivers.
- Allocation key data that cannot be traced to an underlying, verifiable source.
- A key change coinciding suspiciously with a shift in group profitability patterns.
Documentation & data
Documents to hold
- Allocation key selection rationale per service category.
- Underlying data source and calculation for each key (e.g. headcount snapshot date).
- History of key changes with business justification.
Data you need
- Usage or consumption data per entity for each shared service (tickets, transactions, headcount).
- Prior years' allocation calculations for consistency checks.
- Organizational changes (M&A, restructurings) that may affect key inputs.
Who owns this internally: Group tax designs the methodology; finance/controlling maintains and applies the underlying data.
Jurisdiction notes
- OECD
- Chapter VII requires that allocation keys be capable of measuring the actual or expected benefit reasonably, without prescribing a specific method.
- Germany
- German tax authorities frequently challenge allocation keys during audits and request the underlying usage data, not just the resulting percentages.
Notes by role
Advisors & consultants
When reviewing a group's service charge policy, test the allocation key against actual usage data before accepting the cost pool as correctly built.
CFOs & finance leaders
An allocation key that shifts material cost between entities changes local profitability and, potentially, local management bonus outcomes — worth flagging beyond tax.
Frequently asked
- Can multiple allocation keys be used within the same service charge?
- Yes — a single management fee can be built from several sub-cost-pools, each with its own tailored key, rather than forcing one key across dissimilar cost types.
- Is headcount always an appropriate key?
- No — headcount works well for HR-type services but poorly correlates with, for example, IT infrastructure costs driven by data volume or number of systems.
Sources & status
- Primary source
OECD Transfer Pricing Guidelines, Chapter VII (allocation and apportionment methods)
OECD, 2022
- Our interpretation
Practical allocation key selection standards
This glossary, 2026
Reference material only, not advice on a specific fact pattern. Reviewed 2026-06-30.
Careers
How this shows up in the job
Designing and defending allocation keys is bread-and-butter work in operational transfer pricing engagements — a strong topic for case-study interview questions.
Careers in transfer pricing