Transfer Pricing Documentation in India (FY 2026): Master File, Local File, and CbCR Explained for MNCs + a Practical Compliance Checklist

Introduction

If your India entity transacts with overseas group companies—management fees, software/services, royalties, cost allocations, intercompany loans, secondment arrangements, or even reimbursements—transfer pricing (TP) becomes a core compliance area.

The challenge is not that TP rules are “unknown.” The challenge is that TP documentation requires alignment across tax, finance, legal, HR (for secondments), and the overseas parent team. When alignment is missing, companies end up with:

  • inconsistent intercompany agreements
  • weak benchmarking support
  • delayed documentation
  • avoidable adjustments, penalties, and prolonged litigation

This article breaks down TP documentation for FY 2026 into a practical operating system: Master File, Local File, and CbCR—what they mean, who they apply to, and how to build a defensible documentation pack.

For hands-on support on TP documentation, benchmarking, and compliance planning, our Tax Advisory and Compliance team can help (including international tax and transfer pricing support).

Transfer pricing in India: what it is (and why documentation matters)

Transfer pricing rules ensure that transactions between related parties (Associated Enterprises) are priced at arm’s length—as if the parties were independent.

Documentation matters because during assessment, the tax authority typically asks:

  • What is the transaction?
  • Why is the pricing arm’s length?
  • What method was used?
  • What comparables support the margin/price?
  • Are agreements and actual conduct consistent?

The best TP documentation does two things:

  1. Explains the business reality (functions, assets, risks)
  2. Proves the pricing (method + benchmarking + computations)

The three pillars: Master File, Local File, and CbCR (plain-English definitions)

1) Local File (India entity-focused)

The Local File is the detailed documentation for the Indian taxpayer’s related-party transactions.

It typically covers:

  • entity overview and business model
  • transaction-by-transaction analysis
  • FAR analysis (Functions, Assets, Risks)
  • selection of TP method
  • benchmarking study and comparables
  • financial analysis and adjustments
  • supporting agreements and invoices

2) Master File (group-focused)

The Master File provides a high-level picture of the global group:

  • group structure and ownership
  • business lines and value chain
  • intangibles and IP ownership
  • intercompany financing
  • group TP policies
  • consolidated financials and key drivers

Think of it as: “How the group makes money globally, and where value is created.”

3) Country-by-Country Reporting (CbCR) (jurisdiction-level)

CbCR is a jurisdiction-wise snapshot of the group’s:

  • revenues
  • profits
  • taxes paid/accrued
  • employees
  • tangible assets

CbCR is designed to help tax authorities identify profit-shifting risk patterns across countries.

Who needs to file what (FY 2026 practical view)

Exact applicability depends on thresholds and group structure. Operationally, MNCs should assume TP documentation is relevant if:

  • the India entity has international related-party transactions (services, royalties, loans, cost allocations, etc.)
  • there are cross-border secondments or shared service arrangements
  • the India entity is a captive service provider, distributor, or contract manufacturer

A practical approach many CFOs use:

  • Local File: treat as mandatory if there are material related-party transactions
  • Master File/CbCR: evaluate based on group size and prescribed thresholds; coordinate with the parent team early because India filings depend on group-level data

Typical transaction types that create TP exposure in India

MNCs commonly face TP scrutiny in:

  • IT/ITES captive services (cost-plus models)
  • marketing support services
  • management fees and shared services
  • software licenses and royalties
  • intercompany loans and guarantees
  • reimbursement arrangements that look like services
  • secondment / deputation of employees

The documentation workflow that actually works (step-by-step)

Step 1: Create a transaction inventory

List every related-party transaction with:

  • counterparty name + country
  • nature of transaction
  • agreement reference
  • invoicing frequency
  • amount and currency
  • TP method used historically

Step 2: Align agreements with reality

A common audit problem: agreements say one thing, invoices and conduct show another.

Ensure:

  • scope of services is specific
  • deliverables and benefit test are documented
  • payment terms and mark-ups are clear
  • roles/responsibilities match actual operations

Step 3: Perform FAR analysis (don’t treat it as boilerplate)

FAR drives method selection and benchmarking.

For example:

  • Is India a low-risk captive service provider?
  • Does India own any IP?
  • Who bears market risk, credit risk, capacity risk?

Step 4: Select the method and build benchmarking

Benchmarking should be:

  • current and defensible
  • consistent with FAR
  • supported by a clear search strategy and filters

Step 5: Build the computation and reconcile to audited financials

Your TP numbers must tie to:

  • statutory financials
  • segmental accounts (if needed)
  • trial balance / GL

Step 6: Finalize documentation before deadlines (not after notice)

The biggest cost in TP is “documentation after the fact.”

Common mistakes that trigger notices (FY 2026 reality)

Mistake 1: “Reimbursement” without benefit evidence

If you pay group entities, maintain:

  • emails, reports, timesheets, deliverables
  • benefit narrative (why it was needed)

Mistake 2: Weak segmental accounting

If multiple lines exist, lack of segmentals can distort margins.

Mistake 3: Using outdated comparables

Benchmarking should be refreshed and defensible.

Mistake 4: Agreements signed late or not updated

Backdated or missing agreements are a red flag.

Mistake 5: Not aligning TP with withholding/FEMA documentation

Cross-border payments often involve:

  • withholding tax positions
  • Form 15CA/15CB documentation
  • FEMA purpose codes and bank narratives

When these don’t align with TP, scrutiny increases.

Practical TP documentation checklist (copy-paste)

A) Group-level pack (for Master File/CbCR coordination)

  • group org chart and ownership
  • global business lines and value chain note
  • list of intangibles and IP ownership
  • group TP policy and intercompany pricing approach
  • consolidated financials
  • CbCR data template (jurisdiction-wise)

B) India Local File pack

  • entity overview and business model
  • related-party transaction inventory
  • signed intercompany agreements (current)
  • invoices and supporting deliverables
  • FAR analysis (India vs group)
  • method selection memo
  • benchmarking study + comparable set
  • computation workbook + adjustments
  • reconciliation to audited financials / segmentals

C) Cross-functional evidence

  • HR secondment documentation (if any)
  • finance GL mapping and segmental support
  • legal review of agreements
  • tax positions on withholding and characterization

How Perfect Accounting can help (soft CTA)

Transfer pricing works best when documentation, accounting, and cross-border compliance are coordinated—not handled in silos.

We can support you with:

  • Local File documentation and benchmarking
  • Master File/CbCR coordination support with parent teams
  • intercompany agreement alignment and transaction mapping
  • audit support and risk mitigation planning

For broader tax and compliance support, explore Tax Advisory and Compliance services.

Final thought

In FY 2026, the safest TP strategy is not “find a margin that passes.” It’s to build a documentation trail that explains your business model clearly, ties to audited numbers, and matches how money actually moves across borders. When your Local File is audit-ready and your group coordination is clean, TP becomes manageable—and far less disruptive.