Shared Services: The Intra-Group SSC That Needs a Benefit Test

Definition

Shared services (the SSC — the shared service centre) is the group arrangement in which a single group entity performs a service function (the IT, the finance/accounting, the HR/payroll, the customer support, the procurement) for multiple group entities, and the cost of that function is allocated to the benefiting entities by an allocation key (the headcount, the revenue, the transaction count, the usage measure) rather than each entity performing the function itself. In transfer pricing, the SSC’s charge to the benefiting entities is a controlled transaction with a standing examination question: did the benefiting entity get a benefit (the benefit test — the charge is [arm’s length] (/docs/glossary/alp) only where the service benefits the chargee, the OECD services chapter logic and the Indian Rule 10AA [safe harbour] (/docs/glossary/safe-harbour) family’s core condition), and at what mark-up (the LVAS — the low value-adding services — are cost or cost-plus-a-prescribed-margin; the higher-value shared service earns the [benchmarked mark-up] (/docs/benchmarking/benchmarking-study-guide)). The [SSC guide] (/docs/transactions/shared-services-tp) carries the full treatment: the benefit analysis, the cost pool design (the costs in the pool — the direct, the allocated overheads, the excluded costs), the allocation keys (the measure, the data, the consistency), and the mark-up question (the [LVAS] (/docs/glossary/lvas) treatment vs the [benchmarked return] (/docs/benchmarking/benchmarking-study-guide)). The SSC’s [FAR] (/docs/glossary/far) is the service provider profile (the function — the service performed; the assets — the centre’s limited base; the risks — the operational risk of performing the service, not the commercial risk of the chargees’ businesses) — the [FAR affinity] (/docs/glossary/far-affinity) characterization in Quartyl captures the service provider profile as one of its deterministic candidates.

The SSC, in one charge:
  1. The function (the service performed — the IT, the finance, the HR, the support — for multiple group entities)
  2. The cost pool (the costs in the pool — the direct, the allocated overheads, the excluded costs)
  3. The allocation key (the measure — the headcount, the revenue, the transactions, the usage — the data, the consistency)
  4. The mark-up (the LVAS cost/cost-plus-prescribed, or the benchmarked return — the benefit test first)

The element	The content
The function	The service performed for multiple group entities (the IT, the finance/accounting, the HR/payroll, the customer support, the procurement) — the SSC guide’s fact pattern
The cost pool	The costs in the pool — the direct service costs, the allocated overheads (the allocation stated), the excluded costs (the costs that do not benefit the chargees — the exclusion documented)
The allocation key	The measure (the headcount, the revenue, the transaction count, the usage) — the data behind it, the consistency across the period, the key’s arm’s length logic (the key a comparable service provider would use)
The mark-up	The LVAS treatment (cost, or cost plus the prescribed margin — the Rule 10AA safe harbour where the conditions met) or the benchmarked return (the higher-value service, the TNMM on the service comparables)

The working read (the SSC guide): the SSC’s transfer pricing is the services family (the [services benchmark] (/docs/methods/how-to-choose-method) — the OP/OC or the cost-plus logic, the [PLI] (/docs/glossary/profit-level-indicator) on the service function), and its standing examination questions are the three the guide works: (1) the benefit (did the chargee benefit — the [benefit analysis] (/docs/transactions/shared-services-tp), the charge justified by the service’s value to the chargee, the no-benefit charge the [penalty] (/docs/glossary/penalty-protection) and the TPO’s adjustment target — the duplicate service and the parental cost (the cost of the parent’s own function, charged to the subsidiary) the named exclusions); (2) the pool and the key (the costs in the pool correct — the exclusion documented; the key appropriate — the measure matching the benefit, the data supporting it, the consistency held); and (3) the mark-up (the LVAS treatment where the service is low-value-adding (the Rule 10AA safe harbour’s ≤5% on the total value, the [safe harbour guide] (/docs/documentation/safe-harbour-india)); the benchmarked return where the service is higher-value (the service comparables, the [TNMM] (/docs/glossary/tnmm), the [accept-reject matrix] (/docs/glossary/accept-reject-matrix) the service pool’s)). The intercompany agreement (the service agreement) is the SSC’s legal form — the benefit, the pool, the key and the mark-up stated in the agreement, the [intercompany agreements guide] (/docs/transactions/intercompany-agreements)’s standing point (the agreement matching the economics).

Example

An Indian SSC providing IT support and finance/accounting to five group entities (the Indian manufacturing sub, the Indian trading sub, the two overseas subs, the holding). The [SSC guide] (/docs/transactions/shared-services-tp) treatment:

The element	The treatment
The benefit	Each chargee benefits (the IT support it receives, the finance function it does not staff) — the benefit analysis per chargee, documented; the holding’s own governance cost excluded from the pool (the parental cost — the named exclusion)
The cost pool	The SSC’s direct staff costs + the allocated overheads (the allocation stated) — the excluded costs (the holding’s governance, the SSC’s own capital cost where not benefiting) documented
The allocation key	The IT: the user count (the measure — the data, the consistency); the finance: the entity count weighted by the transaction volume (the measure matching the benefit)
The mark-up	The IT support: the LVAS (the low-value-adding — the Rule 10AA safe harbour where the conditions met, the ≤5% on the total value); the finance: the benchmarked return (the service comparables, the TNMM on the OP/OC, the pool’s accept-reject matrix)

The intercompany service agreement states the benefit, the pool, the key and the mark-up — the economics the [SSC guide] (/docs/transactions/shared-services-tp) works, in the legal form. The Local File carries the [benefit analysis], the pool and key documentation, and the mark-up treatment (the safe harbour election, the [Form 3CEFA] (/docs/documentation/safe-harbour-india) where elected; the benchmark, where not) — the SSC’s file, the three examination questions answered on the record.

See also

• Shared Services TP Guide
• LVAS (Low Value Adding Services)
• Intercompany Agreements
• Rule 10AA

FAQ

What is the benefit test, and why does it decide the SSC’s charge? The benefit test is the [arm’s length] (/docs/glossary/alp) condition on the service charge: the charge is justified only where the chargee benefits from the service (the service’s value to the chargee — the [OECD services chapter] (/docs/regulations/oecd) logic, the Indian [Rule 10AA] (/docs/glossary/rule-10aa) condition). The no-benefit charge (the service the chargee does not use, the duplicate service the chargee performs itself, the parental cost — the parent’s own governance charged to the subsidiary) is the TPO’s adjustment target and the [penalty] (/docs/glossary/penalty-protection) exposure — the [benefit analysis] (/docs/transactions/shared-services-tp) (per chargee, documented) is the defence, and the cost pool’s excluded costs (the costs that do not benefit the chargees) are where the benefit test is operationalized (the exclusion documented, the pool justified).

Cost or cost-plus — when does the SSC earn a mark-up? The LVAS (the low value-adding services — the routine, the no-unique-intangibles, the no-significant-risk) are charged at cost or cost plus the prescribed margin (the Rule 10AA safe harbour’s ≤5% on the total value, the [safe harbour guide] (/docs/documentation/safe-harbour-india)’s prescribed) — the low-value service earns no entrepreneurial return. The higher-value shared service (the service carrying a unique capability, a significant function, a risk) earns the benchmarked return (the service comparables, the [TNMM] (/docs/glossary/tnmm) on the OP/OC, the [PLI] (/docs/glossary/profit-level-indicator) on the service function — the SSC guide’s mark-up section). The line is the service’s value-adding character (the [FAR] (/docs/glossary/far) of the service performed) — the [LVAS] (/docs/glossary/lvas) treatment for the low-value, the benchmark for the higher-value, and the characterization (which the service is) documented in the Local File.

Why does the allocation key matter to the examination? The key is the arm’s length measure of how much of the pool each chargee bears — the key a comparable service provider would use (the measure matching the benefit: the user count for the IT, the transaction volume for the finance), and the key’s data and consistency (the measure stable across the period, the data supporting it, the allocation reconciling to the pool) are the examination’s checks. A key that does not match the benefit (the revenue key for a service the chargees consume by usage, not by revenue) is the comparability defect — the allocation not justified by the benefit, the charge’s [arm’s length] (/docs/glossary/alp) position undermined. The [SSC guide] (/docs/transactions/shared-services-tp) carries the key’s design (the measure, the data, the consistency) as the allocation’s defensibility.