Tested Party: Definition, Selection Logic and Documentation

Definition

The tested party is the entity whose profit level is measured against the comparable pool — in the one-sided methods (TNMM and its kin), the party that is assumed to be routine, whose result the comparables evidence, and whose position inside the arm’s length range is the study’s conclusion. Everything else in the transaction is held constant: the tested party is the variable the method tests.

The selection logic is the OECD’s: the tested party should be the entity with the least complex functions and risks, for which the most complete and reliable data exists — so that the one-sided comparison has the best chance of being meaningful. The party that owns the valuable unique intangibles, or controls the key entrepreneurial risks, is generally not the tested party: it is the residual, and its return is not what a pool measures.

The six-question test (in one line each)

1. Functions — narrow, specified, contract-based? → toward tested party.
2. Assets — no valuable unique intangibles? → toward.
3. Risks — bounded, not entrepreneurially controlled? → toward.
4. DEMPE — no DEMPE role in valuable intangibles? → toward.
5. Data — clean financials, the PLI denominator available? → toward.
6. Uniqueness — a pool of standalone comparables actually exists? → toward (if no pool exists, the party is not benchmarkable at all).

The full application, with the documentation pattern and the TPO objections it pre-empts, is in tested party selection.

Why the selection is a documented decision

The tested party selection is the first substantive decision of a study and the first one a TPO re-litigates. The file must show it as a decision — the candidate parties, the six questions answered per party with the facts, the considered-and-set-aside pattern (“Entity B was considered and set aside because it performs the DEMPE functions for the group’s X intangible; Entity A was selected because…”) — because an asserted selection is an invitation to the challenge and a documented one is a page reference.

Example

A distribution transaction between an Indian entity (owns the brand, the customer relationships, the pricing decisions; bears demand risk) and a foreign entity (operates logistics and order-processing under a service-level agreement). The six questions point at the foreign operator: specified functions, no owned intangibles, bounded risks, a pool of standalone distributors exists. It is the tested party, benchmarked at the routine return; the Indian entity carries the residual.

See also

• Tested party selection guide
• Functional Analysis
• Routine Return

FAQ

Is the tested party always the lower-margin entity? No — the test is complexity and comparability, not the margin level. A higher-margin entity with a narrow, specified, contract-based role is a fine tested party; a low-margin entity that owns the group’s core IP is not.

Can the tested party change between years? Yes — when the facts change (a reorganisation, a new product line, a changed risk allocation), the FAR changes, and the selection is re-made and re-documented. Silently rolling last year’s tested party across a structural change is one of the fastest routes to the TPO recomputing the whole study on its own selection.

Does the tested party have to be the taxpayer? No — Indian practice allows benchmarking the foreign related party where the data is better and it is the less complex party; the cross-border selection, and its reason, belong in the file.