Add-on: The TPO’s Premium Over the Benchmark Margin
The add-on defined: the premium the TPO adds to the benchmarked arm’s length margin — the adjustment theory, the arguments on each side and the documentation that answers it.
Definition
The add-on is the adjustment in which the TPO holds that the benchmarked arm’s length margin understates the tested party’s compensation — and adds a premium to the margin (the 3% add-on on the TNMM operating margin, the 50 bps on the cost-plus mark-up) to reach the “true” arm’s length level. It is one of the standard TPO adjustment theories alongside the method substitution and the pool substitution (catalogued in the audit defense guide) — and the one that runs inside the file’s own method: the TPO accepts the method, accepts the pool, and adjusts the level.
The arguments, as they stand in practice:
| The side | The position |
|---|---|
| The TPO | The tested party’s functions, assets or risks put it above the pool’s median member — the entity holds an asset (the brand, the network, the licensed technology) or performs a function (the discretion, the management) the pool members do not, and the pool’s margin prices the median member, not this one. The premium is the difference, quantified (the percentage, the bps) |
| The taxpayer | The pool is the comparability set — the members were selected on the comparability facts (the FAR, the assets, the risks), and a tested party that differs from its own pool on a material driver is a tested party mis-selected or mis-documented, not one entitled to a premium. The arm’s length range is the comparability result; adding to it is re-pricing outside the comparability the method requires |
| The documentation’s answer | The FAR record (the tested party’s actual functions, assets, risks, against the pool’s), the selection logic (why the pool members are comparable including on the drivers the TPO names), and the adjustments (the working-capital and the other comparability adjustments, applied, not asserted) |
The working rule: the add-on is fought on comparability, not on the percentage — the argument that moves the bench is “the pool is comparable on the driver you name” (with the record showing it), not “the premium is too high.” The percentage is the arithmetic of a position the record decides first.
Example
The tested party (an Indian distributor) benchmarks at the operating margin on OP/S; the pool’s IQR is 2.1%–3.4%, the tested party sits at 2.8%. The TPO finds the tested party holds the brand management function and the credit risk that the pool members (the plain distributors) do not, and adds a 1% add-on to the margin. The file’s answer: the FAR block documents the brand as licensed in (the brand owner is the related party — the tested party’s function is the distribution, the brand’s value priced at the royalty, not the margin), the credit-risk policy (the credit terms, the provisioning — against the pool’s), and the pool selection (including the members that carry the same credit profile). The comparability record, not the 1%, is the fight.
See also
- TP Audit Defense: the adjustment theories
- Tested Party · Functional Analysis
- Defending Your Accept-Reject Matrix
FAQ
Is the add-on the same as the method substitution? No — the three theories differ in what they attack. The method substitution changes the method (the file’s TNMM examined on the CUP); the pool substitution changes the comparables (the file’s pool replaced with the TPO’s); the add-on keeps the method and the pool and moves the level (the margin plus the premium). The add-on is the most document-intensive to answer, because it is argued on the comparability facts the file already stated.
Can the add-on be quantified by the taxpayer (as a concession)? In the settlement arithmetic, yes — the quantified concession (the add-on accepted at the lower percentage, against the adjustment withdrawn on the other theories) is part of the appeal strategy where the comparability record is mixed. It is a concession on the arithmetic of a losing comparability argument — the documentation that answers the add-on on comparability is what keeps the concession from being the position.
Where does the add-on show up in the documentation? Three places: the FAR block (the tested party’s functions/assets/risks, against the pool’s — the drivers the TPO will name, documented before it names them), the tested-party selection (the complexity comparison, the record of why the tested party is the less complex entity including on the drivers in question), and the benchmarking annex (the comparability adjustments, applied — the working capital, the extraordinary events, the scale — with their bases). The documentation weaknesses list carries the add-on exposure as the FAR block that does not answer the driver.
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
TP Audit Defense: TPO Proceedings, Scrutiny and Appeals
The Indian TP examination end to end: how the TPO proceeding runs, the adjustment theories, the AO interplay, the appeal route, and the documentation readiness that decides the outcome.
Read docTested Party: Definition, Selection Logic and Documentation
The tested party defined: the entity whose result is benchmarked against the comparable pool — selected as the least complex party, and documented as a decision.
Read doc