KPO Transfer Pricing in India: A Benchmarking Guide

Knowledge Process Outsourcing (KPO) is one of the fastest-growing segments of the Indian offshore services industry. Equity research, financial modelling, legal and tax research, data analytics and pharmaceutical research are all routinely delivered from Indian captives to overseas parents — and each raises specific transfer pricing questions.

KPO vs BPO vs IT services

Dimension	IT services	BPO	KPO
Core input	Software engineering	Transaction processing	Domain knowledge & judgment
Typical PLI	OP/OC	OP/OC	OP/OC (higher margin band)
Key risk	Delivery/commercial	Volume & SLA	Knowledge attrition, IP
Classification (NIC)	62011, 62020	82110, 82920	74909, 69100, 69201
Comparability hurdle	Moderate	Low	High

The defining comparability issue for KPO is human capital. Profitability depends on the quality and stability of the analyst workforce, which is hard to observe in database financials — so a disciplined FAR analysis matters more than in a routine BPO benchmark.

Building the FAR profile

Functions. Identify the specific knowledge tasks: research, model building, report drafting, quality review. Distinguish core KPO functions from routine support (IT, HR, finance) that should not dominate the profile.

Assets. KPO entities employ few tangible assets but hold significant intangible value in databases, proprietary methodologies and trained teams. Where the tested party does not legally own these intangibles, the remuneration profile must reflect a risk-reduced, cost-plus character.

Risks. Typical profile: low market and credit risk (captive, cost-plus), moderate operational risk, and meaningful foreign exchange risk where the entity is remunerated in INR against INR cost. Currency movements are a common working-capital adjustment trigger.

Classification first

KPO activities rarely have a dedicated NIC code. Most map to 74909 — Other professional, scientific and technical activities n.e.c., with sub-profiles in 69100 (legal), 69201 (accounting and auditing) or 62020 (computer consultancy) depending on the service.

Automate the KPO benchmark

TP Analytics classifies the tested party, pulls the pool under the right NIC codes and applies FAR-based qualitative screens automatically.

Book a Demo

PLI choice and expected margins

OP/OC is the standard PLI. Benchmarking guidance and database evidence generally place KPO margins above BPO margins because of the knowledge intensity, but the spread is wide — which is precisely why the qualitative screen (trade description, skill profile) drives the final range. Never accept a KPO pool that contains routine BPO providers without a documented reason.

Comparability nuances specific to KPO

• Entity age and team stability. A young KPO with heavy hiring costs may show depressed margins that are not comparable to a steady-state pool.
• Captive vs third-party mix. A captive with a single-party revenue stream fails most related-party screens; use the same NIC code and segment screens as the tested party.
• Intangible ownership. Where the parent retains the IP but the entity bears development costs, consider a risk adjustment rather than rejecting the comparable outright.

Wrapping up

KPO benchmarking rewards preparation: a precise FAR profile, the right NIC codes, OP/OC with a clear cost base, and documented reasons for every inclusion and exclusion. For the PLI mechanics behind this workflow, read the TNMM PLI guide.