Controlled Transaction: Definition, Thresholds and Coverage
A controlled transaction defined: a transaction between related parties on terms differing from independent dealings — the unit to which transfer pricing law applies.
Definition
A controlled transaction is a transaction between related parties in which the price, or other terms, differ from what independent parties would have agreed on comparable circumstances — or, in the statutory sense, a transaction between related parties that the law treats as subject to the arm’s length standard regardless. It is the unit of transfer pricing law: the arm’s length principle applies to controlled transactions, and the documentation obligations are triggered by them.
In India, the coverage sits in section 92: an international transaction between associated enterprises (the related-party test of section 92(2) — ownership, voting power, participation in management, or the other listed connections), plus the specified domestic transactions the section adds (certain related-party loans and the other listed cases). A controlled transaction is what section 92(1) requires to be priced at arm’s length.
Why the definition matters
Three consequences attach to a transaction being “controlled”:
- Pricing — it must be priced (or its terms set) at arm’s length.
- Documentation — it drives the Local File obligation where the thresholds are met, and the Form 3CEB schedule of international transactions.
- Audit — it is the unit the Transfer Pricing Officer examines: the adjustment, if any, is an adjustment to the transaction’s price.
Identifying the controlled transactions — completely, and split into their components (the services element vs the goods element vs the finance element of one intercompany relationship) — is the first scoping act of any study.
Example
A group charges its Indian subsidiary ₹4.2 cr for “IT services” under a single agreement. The transaction carries two components — development services and a support service at different economic profiles — and the Local File must document both, because the controlled transaction as priced is not one thing: it is two, each with its own arm’s length position.
See also
- Related Party
- Rule 10D — the documentation the transactions trigger
- Related parties & controlled transactions guide
FAQ
Are all related-party transactions controlled transactions? All related-party transactions are in scope for the analysis — the law presumes the arm’s length standard applies between associated enterprises. “Controlled” in the descriptive sense is where the terms actually differ from independents; the practical point is that every related-party transaction must be shown to be arm’s length, which is why the scoping step lists them all.
Does the size of the transaction matter for the definition? Not for the definition — a small related-party loan is still a related-party transaction. Size matters for the obligations: the documentation thresholds (the entity’s revenue for the Local File) and, for intra-group loans, the mark-to-market threshold.
Run the screens as a study, not a spreadsheet
Quartyl applies the method, PLI and screening steps above as a pipeline — and keeps a documented reason for every exclusion.
Related docs
Related Party: Definition and Ownership Tests (India and OECD)
A related party defined: the associated-enterprise tests — ownership, voting power, participation in management, and the other listed connections — that put a counterparty in transfer pricing scope.
Read docRule 10D: Local File Requirements Under India's TP Rules
Rule 10D defined: the rule prescribing what the contemporaneous local documentation must contain — and the blocks that make up the Local File in an Indian transfer pricing examination.
Read doc