Documents Required for Transfer Pricing Compliance in India: Filing Guide

If your Indian entity bills or is billed by a foreign parent or sister company, the tax office expects a paper trail proving those prices are fair. For finance controllers running intercompany flows between a global HQ and an India subsidiary, that paper trail is the single thing an assessing officer asks for first. Getting it wrong is expensive, and the rules are specific about what to keep and when to file.

This guide sets out what transfer pricing documentation is, the three-tier structure India follows, the exact forms, thresholds and deadlines, the penalties for missing them, and the challenges finance teams actually hit. It explains the rules rather than giving tax advice, so treat your Chartered Accountant as the final word. Xflow builds tools for transfer pricing flows, and clean inward-remittance records help, but the filings below are your obligation, not ours.

Transfer pricing documentation is the formal record that shows the prices your company charges related entities for goods, services, funding or intellectual property match what unrelated parties would have agreed in the same situation. That benchmark is the arm's length principle, and it is the whole point of the exercise.

For a SaaS firm or a Global Capability Centre (GCC), the related-party transactions are usually software development billed to the parent, support services, cost-plus mark-ups, management fees or royalties on intellectual property. Each of these is an international transaction between associated enterprises under Indian law, and each needs a documented arm's length justification. The documentation is your evidence file if the transaction is questioned.

India's regime sits in Sections 92 to 92F of the Income Tax Act, 1961, and the documentation duty comes from Section 92D read with the Income Tax Rules, as set out on the Income Tax Department site. If you are new to the mechanics, our primer on transfer pricing in taxation covers the fundamentals before you file.

India adopted the three-tier structure set out in the OECD's Base Erosion and Profit Shifting (BEPS) Action 13, so a multinational group prepares the same layered file the world over. The three tiers work together, and each answers a different question for the tax authority. The full standard is in the OECD BEPS Action 13 final report.

Master File

The group-level picture. It typically includes:

• The group's legal and ownership structure and where entities sit geographically.
• A description of the business, the main value drivers and the supply chain.
• The group's intangibles, who owns them and how they are used.
• Intercompany financing arrangements across the group.
• The group's consolidated financial and tax positions.

Local File

The entity-level detail for the transactions booked in India. It usually covers:

• A profile of the local entity and its management reporting lines.
• The nature, terms and value of each international transaction with associated enterprises.
• A functions, assets and risks (FAR) analysis for the Indian entity.
• The transfer pricing method chosen and why it is the most appropriate.
• The comparability or benchmarking analysis that proves the price is arm's length.

Country-by-Country Report (CbCR)

The numbers by jurisdiction. It reports, per country:

• Revenue split between related and unrelated parties.
• Profit before tax, tax paid and tax accrued.
• Stated capital, accumulated earnings, employee headcount and tangible assets.
• A list of the constituent entities operating in each jurisdiction.

The tiers must tell a consistent story. If your Local File claims India carries limited risk while the Master File describes India as the group's main engineering hub, that gap is exactly what an audit looks for. Choosing the right transfer pricing methods for each transaction is what holds the Local File together.

India maps the three tiers onto specific forms, each with its own threshold, rule and deadline. The table below sets out the documents required for transfer pricing compliance, current as of the FY 2024-25 filing cycle (assessment year 2025-26). Thresholds and dates are notified by the government and do change, so confirm the current position with your CA before filing.

A few points that trip teams up. The Local File is not filed with the return, it is maintained under Rule 10D and handed over only when the officer asks, but the ₹1 crore threshold catches most SaaS and GCC entities in year one.

The Form 3CEB accountant's report has no threshold. If you had even one international transaction with an associated enterprise, a practising Chartered Accountant must certify Form 3CEB, and it is due by 31 October. For taxpayers with international transactions, the income tax return itself is due by 30 November.

Part A of Form 3CEAA is a quiet trap. Every Indian constituent of an international group files Part A regardless of size, while the fuller Part B kicks in only above the revenue and transaction thresholds, as the Form 3CEAA itself sets out. Pulling these pieces into one defensible narrative is the job of a well-built transfer pricing report.

Take TechCo India, a GCC that bills its US parent ₹40 crore of software-development services at cost-plus 15% during FY 2024-25. The group's consolidated revenue is ₹18,000 crore, and there are no intangible-property transactions with the parent. Here is how the obligations fall out:

• Local File: the ₹40 crore international transaction is well above the ₹1 crore threshold, so TechCo must maintain a full Local File under Rule 10D and keep it ready by the return due date.
• Form 3CEB: mandatory regardless of value, so a Chartered Accountant certifies it and TechCo files by 31 October.
• Master File, Part A: as an Indian constituent of an international group, TechCo files Part A of Form 3CEAA no matter what.
• Master File, Part B: the group clears the ₹500 crore revenue test, but the ₹40 crore of transactions is below the ₹50 crore limb and there are no intangibles above ₹10 crore. Both limbs are not met, so Part B does not apply. This is the detail teams get wrong.
• CbCR: group revenue of ₹18,000 crore is above the ₹6,400 crore threshold, so the group files a Country-by-Country Report through the parent, and TechCo files the Form 3CEAC notification in India.

Change one number and the answer changes. If TechCo billed ₹60 crore instead, Part B of the Master File would trigger. These interactions play out across large groups too, which is why documentation in transfer pricing in multinational companies needs a single owner tracking every entity's thresholds.

A transfer pricing policy document is the internal rulebook that says how your group sets intercompany prices before the financial year, not after. It records the pricing method for each transaction type, the mark-up or royalty rate, the comparables relied on and the reasoning, so every entity applies the same logic.

It is not a statutory form, but it is the backbone of the Local File and the first thing a good adviser drafts. A written policy means your India entity and your parent book the same transaction the same way, which keeps the Local File, the Master File and the CbCR consistent.

Without one, teams reconstruct the reasoning at filing time, and reconstructed reasoning is weaker under scrutiny. Setting the policy up front is also the cleanest input into any transfer pricing audit that follows.

The penalties are steep and they stack, which is why documentation is treated as non-negotiable. The figures below reflect the position as of July 2026 and are set out on the department's penalties page; a CA can confirm what applies to your facts.

• Section 271AA: failure to keep or furnish documentation, or reporting a transaction incorrectly, attracts 2% of the value of the international transaction. Missing the Master File carries a separate penalty of up to ₹5,00,000.
• Section 271BA: failure to file the Form 3CEB accountant's report attracts ₹1,00,000.
• Section 271G: failure to produce documents the officer specifically requests attracts 2% of the value of the transaction in question.

Put numbers on it. If TechCo from the example above failed to keep its Local File ready, Section 271AA could apply at 2% of ₹40 crore, which is ₹80 lakh. Miss Form 3CEB on top and that is another ₹1,00,000 under Section 271BA. A transfer pricing adjustment that raises taxable income can also trigger under-reporting or misreporting penalties running at 50% to 200% of the tax on the adjusted amount, and where the arm's length price is contested across borders it can lead to double taxation until relief is sorted. The cost of preparing documentation on time is a fraction of the cost of not having it.

Knowing the rules is the easy part. The friction shows up in execution, and the same problems recur across SaaS and GCC finance teams:

• Finding comparables: benchmarking a cost-plus GCC or a niche SaaS licence against independent companies is hard when few true comparables exist, and databases lag the market.
• Contemporaneous documentation: the record has to reflect the position at the time the transactions happened, not a version stitched together the week before the deadline.
• Multi-entity coordination: groups with several Indian constituents must pick a designated entity and file Form 3CEAB at least 30 days before the Master File due date, which needs sign-off from the parent well in advance.
• Deadline confusion: the 31 October date for Form 3CEB and the 30 November date for the return and Form 3CEAA get mixed up every year, and a missed intimation cannot be cured later.
• Shifting thresholds: the ₹1 crore, ₹500 crore and ₹6,400 crore limits are notified figures that can change, so last year's assessment of what applies is not automatically this year's.
• Reconciling the money to the record: the amounts actually remitted between entities have to tie back to the documented arm's length price, and opaque bank FX makes that reconciliation harder than it should be.

A structured read of transfer pricing problems and challenges helps teams anticipate where an assessment tends to probe.

Most gaps are process gaps, not knowledge gaps. Set the policy before the year starts, refresh the benchmarking annually, and keep the FAR analysis current as functions move between the parent and the India entity.

Diarise the intimation and filing dates as hard internal deadlines, not soft ones, and reconcile intercompany invoices to settlements each quarter rather than at year end. Teams that treat documentation as a rolling exercise rather than a March scramble avoid most transfer pricing challenges that surface during an assessment.

A few habits separate a file that holds up from one that invites questions. Keep a contents checklist for the Local File so nothing is missing:

• Ownership structure and a group organisation chart.
• A description of the Indian entity's business and industry.
• Nature, terms and value of every international transaction, with agreements attached.
• The FAR analysis, method selection and the reason the method fits.
• The comparability study, search strategy and the accepted comparable set.
• Any advance pricing agreement or prior-year position relied on.

Version-control the file, keep the workings behind every number, and make sure the story matches across all three tiers. Wider transfer pricing best practices go further, but consistency and contemporaneous records carry most of the weight in an assessment.

Documentation proves the price was right. The money actually moving has to match that record, and this is where the payments layer meets the tax file. When a global HQ funds an India GCC or pays for services, the inward remittance, the conversion rate and the purpose code all become part of the evidence that the transaction happened as documented. Aligning both sides is a core part of cross border tax compliance.

Reconciling inward remittances to the documented price

If the invoice says one amount and the settled figure differs because of opaque bank FX, or the eFIRA does not tie back to the purpose code, you spend audit time reconciling instead of defending the method. Understanding the tax on inward remittances alongside your transfer pricing position keeps both records pointing at the same number.

Where the receiving account fits

Xflow holds final RBI Payment Aggregator - Cross Border (PA-CB) authorisation for both exports and imports as of February 2026, settles inward flows the next business day (T+1) through AD-1 banking partners including JPMorgan Chase, and converts at the live mid-market rate with no markup, with eFIRA auto-issued on settlement. Xflow is ISO 27001 and SOC 2 certified. A receiving account that settles at the live mid-market rate gives the India entity a clean settlement record that lines up with what you filed, which is what an assessing officer wants to see.

Xflow does not prepare your transfer pricing documentation, and documentation is a different job from pricing the transactions, which is why running the steps to conduct transfer pricing risk assessment alongside your filings is worth it.

Receiving accounts built around this reconciliation problem settle at the mid-market rate with no markup, so the FX figure lines up with the file from day one.

Transfer pricing documentation is a fixed set of forms with fixed deadlines, and the penalties for missing them are large enough that the paperwork pays for itself. Get the policy written early, keep the file contemporaneous, and make sure your intercompany payments reconcile to it.