Transfer Pricing Documentation India: 2026 Checklist

Transfer pricing documentation refers to the records an Indian company must keep and file to prove that its dealings with related parties abroad are priced at arm's length. It matters because when your international transactions cross set thresholds, the Income-tax Act requires a specific set of documents, and missing any of them typically triggers a penalty even if your pricing was correct.

For an IT-services or SaaS exporter billing a US or EU parent, the framework is three-tier: a Local File (your TP study under Rule 10D), a Master File (Form 3CEAA) where group and transaction limits are met, and Country-by-Country reporting (Form 3CEAD) for the largest groups.

On top of these sits the accountant's report, Form 3CEB, which almost every exporter with related-party billing has to file. This guide maps each document to its form, threshold and due date, updated for FY 2025-26 (AY 2026-27), and resolves the conflicting numbers you see across the web.

The table below is dated to AY 2026-27 and sourced to the Income Tax Department, Rule 10D, Rule 10DA and Rule 10DB. Where public sources disagree, the reconciled figure is noted underneath.

Conflicts this table resolves: Some pages still quote the Specified Domestic Transaction (SDT) limit as ₹5 crore; the current figure under section 92BA is ₹20 crore, per the Income Tax Department. The CbCR limit is also shown elsewhere as ₹5,500 crore; it was revised to ₹6,400 crore (aligned to the OECD EUR 750 million standard) under Rule 10DB. The ITR filing date for a taxpayer with international transactions is 30 November 2026, one month after Form 3CEB.

Because these numbers sit inside a transfer pricing regime that changes with each Finance Act, treat any undated figure you find elsewhere with caution and confirm against the source below each row.

Transfer pricing documentation is the evidence file that shows the price you charged (or paid) a related party abroad is the same price two unrelated parties would generally have agreed. It exists because section 92 of the Income-tax Act deems related-party income to be computed at the arm's length price, and the burden of proving that price sits with the taxpayer.

For an Indian exporter, the "related party" is usually a foreign parent, subsidiary or group company. The documentation records what was supplied, how the price was set, and which transfer pricing methods support it. It is prepared contemporaneously, meaning it should exist by the return filing date, not be reconstructed after a notice arrives.

Rule 10D sets out the core Local File. It lists thirteen mandatory items plus a set of supporting documents. The mandatory items generally cover:

• Ownership and group structure showing the shareholding chain to the foreign parent.
• A profile of the multinational group and the business of each associated enterprise.
• The nature, terms and value of each international transaction.
• A functions, assets and risks (FAR) analysis for both sides of the transaction.
• Records of comparable uncontrolled transactions or companies.
• The transfer pricing method selected and why it is the most appropriate.
• Working papers showing the arm's length price computation and any adjustments.

The supporting documents generally include the intercompany service agreement, invoices, ledgers, board minutes, official publications and market data relied on, and any correspondence that fixed the price. A detailed transfer pricing report ties these together into a single defensible study.

Transfer pricing documentation checklist

Tick each item as you build the file. Each line names the document, the form it maps to, and who it applies to.

• Group structure chart to the ultimate foreign parent (Local File, Rule 10D; every exporter with related-party dealings)
• Business profile of each associated enterprise (Local File, Rule 10D; every exporter with related-party dealings)
• Signed intercompany service agreement, current for the year (supporting document, Rule 10D; every exporter billing a foreign group company)
• Schedule of each international transaction with value and currency (Local File, Rule 10D; every exporter above the ₹1 crore aggregate limit)
• FAR (functions, assets, risks) analysis (Local File, Rule 10D; prepared for the tested party, usually the Indian unit)
• Selection and justification of the transfer pricing method (Local File, Rule 10D; every exporter, TNMM for most captive units)
• Comparable company set and benchmarking working with the mark-up range (Local File, Rule 10D; every exporter)
• Arm's length price computation and any adjustment (Local File, Rule 10D; every exporter)
• Invoices, contracts and inward-remittance records for each transaction (supporting document, Rule 10D; every exporter receiving foreign billing)
• Accountant's report signed by a chartered accountant (Form 3CEB, section 92E; every taxpayer with an international transaction)
• Master File Part A and Part B, plus the filer intimation (Form 3CEAA and Form 3CEAB; constituent entities meeting the group and transaction limits)
• Country-by-Country report or the parent-filing notification (Form 3CEAD or Form 3CEAC; constituents of a group above ₹6,400 crore)

Following transfer pricing best practices means building this file as the year runs, not in October.

Two Xflow pages, two jobs: This page covers what to maintain and file. For how the tax officer reviews it during scrutiny, see the separate transfer pricing audit guide.

Most guides stop at the generic three-tier framework. IT and software exporters have a specific pattern that the rules treat in a particular way, so it helps to spell it out.

A captive IT-services unit or Global Capability Centre (GCC) usually bills its foreign parent on a cost-plus basis. The most common method here is the Transactional Net Margin Method (TNMM), benchmarked on the operating profit to operating cost ratio (OP/OC). Your documentation has to justify that mark-up against a set of comparable Indian software-development companies.

SaaS and product companies add a second question: Who owns the intellectual property? If the Indian entity develops IP that the parent monetises, the FAR analysis and the intercompany agreement must reflect that, because it changes which entity is the tested party.

These points feed the same transfer pricing in multinational companies rules, but the evidence an exporter needs is more specific: signed master service agreements, statements of work, timesheets or effort records, and the inward-remittance trail proving the billed amount was actually received.

Worked example: An ITeS exporter with a US parent

Consider an illustrative Bengaluru company, a wholly owned subsidiary of a US parent, that provides software-development and support services under a cost-plus arrangement.

• Operating cost base for FY 2025-26: ₹35 crore.
• Agreed TNMM mark-up on operating cost: 15%.
• Amount billed to the US parent: ₹40.25 crore (a single international transaction).

Here is what the numbers trigger:

• Local File and TP study: International transactions of about ₹40 crore far exceed the ₹1 crore aggregate limit, so a full Rule 10D file is mandatory and must be contemporaneous.
• Form 3CEB: Required, because there is an international transaction. It is due 31 Oct 2026, and the company's ITR is due 30 Nov 2026.
• Master File (Form 3CEAA): The ₹40 crore transaction is below the ₹50 crore limb, so Part B is not triggered on value. However, if the US-parent group's consolidated revenue exceeds ₹500 crore, Part A of Form 3CEAA is still required from every Indian constituent entity, regardless of the monetary limbs.
• CbCR (Form 3CEAD): Only if the group's consolidated revenue exceeds ₹6,400 crore. The US parent usually files this in its home country; the Indian entity may only need the Form 3CEAC notification.
• Retention: The whole file must be kept for 8 years from the end of the assessment year, so a FY 2025-26 file is held until the end of AY 2034-35.

This single scenario shows why threshold precision matters: change the billed amount to ₹52 crore and the Master File Part B obligation switches on.

The two dates that catch exporters out are the accountant's report and the return. For AY 2026-27:

• Form 3CEB: 31 October 2026.
• Income tax return (TP case): 30 November 2026.
• Form 3CEAA (Master File): 30 November 2026.
• Form 3CEAB (intimation): at least 30 days before the Master File date.
• Form 3CEAD (CbCR): within 12 months of the group's reporting year end.

Filing Form 3CEB but missing the intercompany documentation behind it is the most common gap. The report certifies that documentation exists; if it does not, the certification is exposed.

The penalties are separate from any tax adjustment, so they apply even where your pricing is later accepted. The grid below is drawn from the relevant sections of the Income-tax Act.

A 2% penalty on a ₹40 crore transaction is ₹80 lakh, which is why the documentation file, not just the form, is the thing to get right.

Under Rule 10D, the information and documents must be kept for eight years from the end of the relevant assessment year. When the Assessing Officer or Transfer Pricing Officer issues a notice under section 92D, you generally have 30 days to furnish the documents, extendable by a further 30 days on request.

Because the window is short, a ready file beats a reconstructed one every time. A structured transfer pricing risk assessment each year keeps the file current and flags the transactions most likely to draw a query.

There is a genuine transition to flag. For FY 2025-26 (AY 2026-27), the accountant's report remains Form 3CEB, filed under Rule 10E of the Income-tax Rules, 1962. The Income-tax Act, 2025 renumbers this report as Form 48 (under the draft 2026 Rules), and that form is expected to apply from Tax Year 2026-27 (AY 2027-28) onwards.

Verify before you file: For the current filing season (AY 2026-27), Form 3CEB is the established form. Treat Form 48 as the version coming for the next year and confirm the applicable form with your chartered accountant and the Income Tax Department before filing, since the 2026 Rules were still being finalised as of 2026.

Transfer pricing documentation lives or dies on evidence that the billed amount was actually invoiced, received and coded correctly. This is where your cross-border receiving setup does real work, though it sits alongside the TP study rather than replacing it.

When an IT-services exporter receives parent billing through Xflow, each payment carries an automatically issued eFIRA and is tagged with the purpose code for inward remittance that matches software or IT services.

That gives you a matched set: intercompany invoice, inward remittance, FIRA and purpose code, all pointing to the same transaction. During a query, that clean trail is what proves the ₹40.25 crore in the worked example was received exactly as documented.

The same records support your wider cross-border tax compliance obligations, from export of services under GST to the repatriation of export proceeds timelines. Settlement at the mid-market rate, rather than a marked-up bank rate, also keeps the received amount matching the invoice, which avoids the small reconciliation gaps that make a file look untidy. You can estimate that difference below.

Where related-party pricing raises broader questions such as double taxation or recurring transfer pricing challenges, a clean payment record shortens the conversation with both your CA and the tax officer.