Loading...
Loading...
A practitioner guide to shared services transfer pricing: service characterization, benefit test, shareholder and duplicate services, cost pools, allocation keys, cost plus vs TNMM, OECD LVAS, documentation, audit issues, and a worked example.
Borys Ulanenko
CEO, ArmsLength AI
Continue exploring
Browse the full resource library or contact us if you want recommendations for your specific use case.
Shared services transfer pricing sets the charge for centralized functions provided by one group entity to others. Common examples include finance, HR, IT support, procurement support, legal administration, facilities, and back-office operations.
A defensible charge answers four questions:
Most routine shared services are priced using cost-based methods. Qualifying low-value-adding services may use the OECD simplified 5% markup where local rules accept it. Higher-value or specialized services need a standard transfer pricing analysis.
For the broader documentation angle, see TP documentation for intercompany services and cost plus in transfer pricing.
Shared services are centralized activities performed for multiple group entities. The provider may be a headquarters entity, regional hub, shared service center, or specialized group company.
| Service category | Typical examples | Initial pricing question |
|---|---|---|
| Finance and accounting | Accounts payable, bookkeeping, routine reporting | Cost-based charge or LVAS if conditions are met |
| HR | Payroll, recruiting administration, training logistics | Cost pool with headcount or usage allocation |
| IT support | Helpdesk, maintenance, license administration | Cost pool, ticket volume, users, or devices |
| Legal administration | Routine contract support, entity maintenance | Cost pool, matter counts, or direct charge |
| Procurement support | Vendor coordination, routine sourcing support | Cost plus or allocation by spend, where benefit tracks spend |
| Management services | Strategy, senior leadership, business planning | Higher scrutiny; may require full benchmark |
| Technical services | Engineering, specialized IT development, product support | Usually full arm's length analysis |
The category name is a starting point. A service called "IT support" may be routine helpdesk work, or it may be software development that creates intangibles. The pricing depends on the activity, not the label.
Service characterization should separate routine support from higher-value activities.
Routine support services usually:
These services often fit cost plus, TNMM with net cost plus, or the OECD LVAS simplified approach where available.
High-value services may involve:
These services should not be dropped into a routine shared services pool without analysis. The provider may need a higher return, or a different method may be more reliable.
Do not mix routine payroll processing, senior management, R&D, and treasury trading in one cost pool with one markup. Mixed pools are hard to defend because the benefit, risk, and arm's length return differ by service type.
The benefit test asks whether the recipient receives economic or commercial value from the activity. Under OECD Chapter VII, an intra-group service is recognized where the activity provides value that an independent enterprise would have been willing to pay for or perform in-house.
Evidence of benefit can include:
The benefit does not need to create immediate profit. Maintenance, compliance, and risk reduction can be real benefits. The file should connect each service category to the recipient's business.
| Charging approach | Best use | Evidence needed |
|---|---|---|
| Direct charge | Services performed for one identifiable recipient | Time records, project codes, invoices, matter IDs |
| Indirect allocation | Services benefit multiple entities and cannot be traced efficiently | Cost pool, allocation key, beneficiary list, rationale |
Direct charging is usually stronger where practical. Indirect allocation is accepted for shared services, but the allocation key must track expected benefit.
Before applying any markup, remove non-chargeable activities.
Shareholder activities benefit the parent in its capacity as owner rather than the subsidiary as an operating business. Examples often include:
These costs should not be allocated to subsidiaries merely because the group performs them centrally.
A duplicate service is an activity already performed by the recipient or by another provider, unless the duplication is temporary, deliberate, and commercially reasonable.
Examples:
Incidental benefits arise from being part of a group, without a service being rendered to the recipient. A subsidiary may benefit from the group's reputation or purchasing scale, but that alone does not prove a chargeable service.
Auditors usually ask for two things first: proof that the service happened and proof that the recipient benefited. Cost calculations matter only after those two points are established.
A cost pool should include only costs related to chargeable services.
Pass-through costs should be handled separately where the provider acts as an agent or coordinator without adding value to the underlying item. If the provider performs procurement, vendor management, integration, or quality control, a markup on some portion of the activity cost may be appropriate.
The file should show which costs are marked up, which are passed through, and why.
The allocation key should approximate the benefit expected by each recipient.
| Service | Possible allocation key | Watch-out |
|---|---|---|
| Payroll | Employee headcount or payroll runs | Expat payroll and complex payroll may need separate treatment |
| IT helpdesk | Tickets, users, devices, or application seats | High-use entities may be undercharged by simple headcount |
| Finance | Invoice count, transaction volume, revenue, or headcount | Revenue can be poor for low-transaction holding entities |
| HR administration | Headcount | Senior hiring or special projects may need direct charge |
| Legal support | Matter count, hours, or direct charge | High-value litigation should not be buried in routine pool |
| Procurement support | Addressable third-party spend | Exclude spend not supported by the procurement team |
| Facilities | Square meters or headcount | Remote teams may need separate key |
A good allocation key is stable, explainable, and supported by data. Changing keys year to year is possible, but the file should explain why the new key better reflects benefit.
Shared services are usually cost-driven. That points to a cost-based return, but the exact method matters.
The OECD cost plus method is a traditional transaction method. It tests a gross mark-up on costs for a comparable service transaction. It works best where the service provider performs similar services for both related and unrelated parties, or where external gross mark-up data is reliable.
TNMM tests operating profit over total operating costs. It is often used for shared service centers because comparable company net-margin data is more available than gross service mark-up data.
Net cost plus = Operating profit / Total operating costs
The OECD LVAS approach is a separate simplification for qualifying low-value-adding services. It uses a 5% markup on the relevant cost pool and avoids detailed benchmarking, but only where the local jurisdiction accepts the approach.
| Situation | Likely approach |
|---|---|
| Routine service center, no unique intangibles | TNMM with net cost plus or cost plus |
| Same services also sold to third parties | Internal CUP or cost plus may be strong |
| Qualifying low-value services in adopting jurisdiction | OECD LVAS 5% simplified approach |
| Specialized engineering or software development | Full benchmark, possibly higher return |
| Strategic management or treasury risk control | Full facts analysis; routine markup may be too low |
For method selection generally, see how to choose the best transfer pricing method.
The OECD simplified approach for low-value-adding intra-group services is elective and limited. In broad terms, qualifying services are supportive, are not part of the group's core profit-making activities, do not require unique and valuable intangibles, and do not involve significant risk.
Common qualifying categories may include:
Common exclusions include:
Under the OECD approach, qualifying LVAS are generally charged at cost plus 5%, using a simplified benefit test and allocation framework.
Local law controls whether the OECD simplified approach is available. Some jurisdictions accept it, some modify it, and some use separate regimes. The United States has the services cost method under Treas. Reg. Section 1.482-9 for qualifying covered services, which can allow charging at cost where all requirements are met. That is not the same as the OECD 5% LVAS approach.
The 5% LVAS markup is not a generic shared-services benchmark. It applies only to qualifying services and only where the relevant jurisdiction accepts the simplified approach.
Check the OECD Transfer Pricing Country Profiles and local guidance before applying LVAS in a local file.
| Section | What to include |
|---|---|
| Service catalogue | Service categories, providers, recipients, and period covered |
| Benefit test | Expected benefit for each recipient or recipient group |
| Evidence of rendition | Tickets, reports, time records, emails, deliverables, meeting materials |
| Non-chargeable exclusions | Shareholder, duplicate, incidental, pass-through, and extraordinary costs removed |
| Cost pool | GL accounts, employee costs, third-party costs, overheads, and reconciliation |
| Allocation keys | Key selected for each service, data source, and benefit rationale |
| Markup or method | LVAS, cost plus, TNMM, CUP, or other method with support |
| Agreements | Intercompany service agreement, pricing policy, true-up terms |
| Calculations | Cost pool, markup, allocations, invoices, year-end true-up |
| Local rules | LVAS adoption, services cost method, withholding tax, VAT/GST, deductibility rules |
Documentation should also reconcile the service charge to the recipient's accounts. The recipient should be able to identify the expense and explain why it paid the charge.
Generic management fees are often challenged when the file has no service catalogue, deliverables, or recipient-level benefit analysis.
Parent-level governance, investor reporting, and ownership costs are easy to allocate mechanically. They should be filtered before charging subsidiaries.
Headcount may work for HR. It may not work for legal, procurement, or IT applications. Overuse of one key suggests convenience rather than benefit.
Marking up third-party costs can be wrong where the service center acts only as a payment conduit. If the service center manages the vendor or adds value, document the specific activity.
Authorities often challenge use of 5% for R&D, strategic management, treasury, technical development, or marketing. These services usually need a standard benchmark.
Provider-side cost schedules are not enough. The recipient should have evidence that it requested, received, used, or benefited from the services.
Even if the transfer pricing method is sound, service charges can create indirect tax and withholding tax issues. Align invoices, contracts, tax codes, and service descriptions.
Group ServicesCo provides shared services to five operating subsidiaries. The relevant service categories are:
ServicesCo has no unique intangibles and does not perform strategic management, R&D, treasury, or sales functions. Local rules in the recipient jurisdictions accept the OECD LVAS approach for these services.
| Cost item | Amount | Treatment |
|---|---|---|
| Payroll team salaries and benefits | EUR 600,000 | Included |
| IT helpdesk salaries and benefits | EUR 750,000 | Included |
| Accounts payable team | EUR 400,000 | Included |
| Helpdesk software | EUR 100,000 | Included |
| Parent investor relations | EUR 120,000 | Excluded shareholder activity |
| Third-party software recharged at cost | EUR 300,000 | Pass-through, no markup |
Chargeable LVAS cost pool:
EUR 600,000 + EUR 750,000 + EUR 400,000 + EUR 100,000 = EUR 1,850,000
5% markup:
EUR 1,850,000 x 5% = EUR 92,500
Total marked-up charge:
EUR 1,942,500
| Service | Cost pool | Allocation key |
|---|---|---|
| Payroll | EUR 600,000 | Payroll headcount |
| IT helpdesk | EUR 850,000 | Tickets closed |
| Accounts payable | EUR 400,000 | Invoice count |
The third-party software pass-through is allocated to the entities that use the licenses, without markup. The investor relations cost is not charged.
The file supports the charge because it shows the services were rendered, the recipients benefited, non-chargeable costs were removed, allocation keys track benefit by service category, and the 5% LVAS markup is available under local rules.
Shared services transfer pricing sets the charge for centralized services provided by one group entity to other group entities. The charge usually starts from service costs, then applies a markup or method supported by transfer pricing rules.
The benefit test asks whether an independent enterprise in comparable circumstances would pay for the activity or perform it internally. If the recipient does not receive a real business benefit, the charge is usually not arm's length.
Generally no. Costs incurred by a parent in its capacity as shareholder should be excluded. Only activities that benefit the subsidiary's business can be charged.
There is no universal markup. Qualifying OECD LVAS may use 5% where local rules accept the simplified approach. Other services need arm's length support from CUP, cost plus, TNMM, or another appropriate method.
No. Local adoption varies. Some jurisdictions accept the OECD approach, some modify it, and some use different regimes. The US services cost method is a separate rule and can allow cost-only charging for qualifying covered services.
Use the key that best reflects benefit. Headcount may fit HR, tickets may fit IT helpdesk, invoice counts may fit accounts payable, and spend may fit procurement support. Avoid one key for all services unless the benefit pattern genuinely supports it.
Qualifying LVAS under an accepted simplified approach may not need detailed benchmarking. Higher-value or non-qualifying services usually require standard arm's length support, often through benchmarking.