Transfer Pricing Risk: What Happens When Prices Are Challenged

A transfer pricing challenge is not a single event — it is a sequence: a targeting signal, a notice, an adjustment theory, a hearing, an appellate round, and a settlement posture. Knowing the sequence is what lets a team de-risk before step one, and manage credibly from step two.

The Indian sequence, step by step

1. Targeting. Cases are selected from data signals: CbCR ratios, sector watch lists, refund anomalies, sector-wide TPO drives (IT/ITeS, KPO, auto-components have each had drives). The CbCR’s entity-level ETR and intercompany ratios are the modern radar.
2. TPO notice. A show-cause notice under s.92(1) with the scope: which transactions, which years. The notice usually names the adjustment theory at a high level (method, pool, or price).
3. TPO assessment. The TPO recomputes — typically by substituting its own method, PLI, comparables pool, or all three — and issues an assessment order with the adjusted income. This order is the core exhibit of any appeal.
4. AAR (s.254). First appeal to the Appellate Authority. AARs often re-hear the comparability question with technical support.
5. ITAT. The Income Tax Appellate Tribunal — the forum where TP appeals are most frequently won or lost on the technical record.
6. ITAT → High Court → Supreme Court. Reserved for principle-setting facts.

Timelines are long (multi-year is normal) — which is why the position taken in the assessment order matters more than speed: the ITAT rarely re-opens questions that were never properly argued at the TPO stage.

The adjustment theories, in order of frequency

Theory	What the TPO does	Why it succeeds or fails
Wrong pool	Substitutes its own comparables (often a different NIC set or geography)	Fails when your pool’s screens are documented and reproducible; succeeds when your search is vague
Wrong PLI	Switches the PLI (e.g., OP/OC → OP/Sales) or recomputes it	Succeeds when the PLI definition isn’t consistent between tested party and pool
Method recharacterisation	Declares TNMM inappropriate; imposes CPM, GMM or a price	Succeeds when the FAR profile is weak or missing
Missing intangibles	Imputes a royalty to an unrecognised IP flow	The DEMPE pattern — see routine vs entrepreneurial
Benefit / add-on	Adds a margin or fee to a services transaction (management services, guarantee fee)	Fails when the benefit test and fee benchmark are documented
Working capital / adjustments	Recomputes or rejects your adjustments	Fails when adjustments are arithmetic with stated rates; succeeds when they are opinion

The cost stack of a challenge

A successful adjustment carries three costs, and the third is the one teams under-price:

1. Tax on the adjusted income.
2. Interest. s.234C (default interest) runs from the due date — on a multi-year old adjustment this is often 25-40% of the tax itself.
3. Penalty. s.271AA (failure to maintain contemporaneous documentation: 2% of the transaction value) and s.271BA (no 3CEB: ₹1,00,000) — and s.270A/270AAB if the case is recharacterised as undisclosed income (much harsher rates).

The penalty shield: if the contemporaneous documentation existed and was maintained per Rule 10D/10E by the due date, the penalty under 271AA/271BA does not apply — the adjustment (if any) is a tax question, not a penalty question. That single fact is why contemporaneous documentation is the highest-return item in the entire TP programme: it converts a defensible-but-late file from a penalty case into a merits case.

The audit triggers — what actually gets cases selected

In rough order of how often they appear in practice:

• The pool that doesn’t reproduce. A reviewer can’t re-run your search and get your pool.
• The PLI that doesn’t match the function. OP/Sales on a cost-plus service entity, or a PLI computed differently for tested party and pool.
• The FAR that contradicts the P&L. “Full risk” on paper, cost-plus economics in the accounts.
• The uncharged fee. A guarantee, a licence, or a support service with no documented arm’s-length charge.
• The CbCR that doesn’t reconcile. Entity-level CbCR numbers that diverge from the Local File financials.
• The static file. The same comparables and the same three-paragraph FAR for five straight years while the business changed.

The de-risking checklist

Run this before every filing season — it is the inverse of the trigger list:

1. Pool reproducible — exact NIC codes, filters, thresholds and data vintage in the working papers; a reviewer can re-run it.
2. PLI consistent — same definition, same denominator discipline, same normalisation for tested party and every comparable.
3. FAR matches the accounts — risk and function narratives reconciled to the P&L behaviour; DEMPE mapped for every intangible.
4. Every fee has a benchmark — services, guarantees, loans: each with a documented arm’s-length rate or the safe-harbour election.
5. Cross-document consistency — Local File, Master File, 3CEB, CbCR numbers reconciled to each other and to the books.
6. Contemporaneity proven — the documentation existed before the return due date; the proof is the file’s own creation trail (which is why an audit trail like Quartyl’s exists).
7. Refresh discipline — comparables and FAR re-examined annually, with changes documented as changes.

Items 1-5 are substance; items 6-7 are process. The teams that lose TPO cases most often fail 6 and 7 while believing they have 1-5 — because they can’t prove the substance was built contemporaneously.

The TP audit defence guide covers the TPO/AAR/ITAT stages in depth when a case is already in front of you.