transfer pricing - Treelife

Form 48 Transfer Pricing: What to have ready before you file

Posted on 22 Jul, 202622 Jul, 2026 by Treelife

India’s transfer pricing certification has changed in ways that go beyond renaming a form. From Tax Year 2026-27, every person with international transactions or specified domestic transactions (SDTs) files Form No. 48 under Section 172 of the Income-tax Act 2025, replacing Form 3CEB which was prescribed under Section 92E of the Income Tax Act 1961. The form is structured, ID-linked, and machine-readable. What was a narrative certification has become a transaction-by-transaction data submission that the system cross-verifies against your tax audit report, your return, and, where applicable, against filings by foreign tax authorities under treaty exchange provisions.

The what-changed question is well-documented. The harder question — what your team needs to have in place before the certifying CA touches the form is what this article addresses.

Does Form 48 replace Form 3CEB entirely, or does Form 3CEB still apply?

Form 3CEB under Rule 10E of the Income Tax Rules 1962 continues to govern filings for FY 2025-26 (AY 2026-27) and all earlier years. The Form 3CEB due date for AY 2026-27 is 30/11/2026. Form No. 48 under Rule 85 of the Income Tax Rules 2026 applies from Tax Year 2026-27 (AY 2027-28) onwards. Both forms will be in simultaneous use during the AY 2026-27 filing season: Form 3CEB for past-year returns, Form 48 preparation for current-year transactions.

The statutory shift: what changes in substance, what does not

The Income-tax Act 2025 recodifies transfer pricing from Chapter X (Sections 92 to 92F) of the 1961 Act to Sections 161 to 173. The section-to-section mapping is:

Subject	Old section (IT Act 1961)	New section (IT Act 2025)
Associated enterprise definition	Section 92A	Section 162(1)
International transactions	Section 92B	Section 163
Specified domestic transactions	Section 92BA	Section 164
Arm’s length price methods	Section 92C	Section 165(1)
TP documentation	Section 92D	Section 171
Accountant’s report	Section 92E	Section 172
Rule for accountant’s report	Rule 10E (IT Rules 1962)	Rule 85 (IT Rules 2026)

Arm’s length pricing principles, the six methods (CUP, RPM, CPM, TNMM, PSM, and any other method), and the interquartile range framework carry forward from the 1961 Act. What changes is disclosure granularity, digital architecture, and two substantive clarifications that affect how Part E is computed.

For the detailed six-part structure of Form 48 and how it feeds into audit risk selection, see Treelife’s transfer pricing audit triggers guide. This article focuses on the three areas that structure guides do not cover: safe harbour interaction, block assessment exposure, and the tolerance band change.

Safe harbour and Form 48: the obligation that does not go away

The most common misconception about safe harbour under the new regime is that opting in removes the Form 48 filing requirement. It does not.

Section 167 of the Income-tax Act 2025, which replaces Section 92CB of the 1961 Act, defines safe harbour as circumstances in which tax authorities accept the declared transfer price without requiring a full ALP determination. The safe harbour rules under the Income Tax Rules 2026 have been expanded and recalibrated for Tax Year 2026-27 onwards, with revised margin bands for IT services, ITeS, KPO, contract R&D, data centres, and bonded warehouse operations.

But Sections 171 and 172 apply irrespective of whether safe harbour is exercised. This means:

The contemporaneous TP documentation (local file under Rule 84) must still be maintained for all international transactions, including those covered by safe harbour.
Form 48 must still be filed for all international transactions, including those for which safe harbour margins are claimed.
The safe harbour margin and the transaction details must be disclosed in Form 48. The TPO will not dispute the pricing for safe harbour-eligible transactions, but the form entry is still required.

The separate application form for safe harbour Form 49 for IT service providers under Rule 91, and the form under Rule 90 for all other eligible transactions is filed in addition to Form 48, not instead of it. Confusing the two is a compliance failure that surfaces only at the point of assessment.

Revised safe harbour margins for Tax Year 2026-27 (Rule 85 and Finance Act 2026 amendments):

Eligible transaction category	Margin / rate
IT services (software development)	15.5% of operating cost
IT-enabled services (ITeS)	15.5% of operating cost
Knowledge process outsourcing (KPO)	18% of operating cost
Contract R&D (software)	25% of operating cost
Contract R&D (generic pharmaceuticals)	25% of operating cost
Data centre services	15% of cost
Bonded warehouse component operations	2% of invoice value
Intra-group loans	RBI reference rate (PLR + 150 bps for foreign currency)
Corporate guarantees	1% of the amount guaranteed

These margins apply for a three-year block commencing from Tax Year 2026-27 unless modified by CBDT. Verify the margin band against the notified rules before relying on them, as sub-category eligibility conditions apply. Transactions with AEs in notified low-tax jurisdictions under Section 176 are excluded from safe harbour regardless of margin.

Treelife advises on safe harbour eligibility assessment, margin band confirmation, and coordinated filing of Form 49 and Form 48. See our transfer pricing advisory services.

Block transfer pricing assessments: what Transaction IDs mean across years

The Income Tax Rules 2026 introduce block transfer pricing assessments as a new procedural mechanism. A block assessment covers multiple tax years in a single proceeding. This is designed to reduce repeat scrutiny of the same transaction structures across successive years.

The practical effect runs in both directions. For a company with clean, well-documented TP positions, a block assessment means fewer separate audit cycles. For a company with a weak or evolving TP position, it means an adverse finding in one year can be extrapolated across the block period.

Form 48’s Transaction ID architecture is the mechanism that makes block assessments viable. Because every transaction stream has a persistent identifier (T-1, T-2, and so on) linked to a specific AE and transaction type, the department can track the same transaction across Tax Year 2026-27, 2027-28, and 2028-29 without reconstructing the structure. A change in method, a change in comparable set, or a change in the benchmarked margin that is not adequately explained in the documentation will be visible at the block level.

What this means for filing preparation:

Year-on-year consistency in Transaction IDs and AE IDs matters. A transaction that was T-1 in the first Form 48 should not become a different transaction in Year 2 unless the underlying intercompany structure has changed.
Changes in benchmarking approach between years need to be documented. An unexplained shift from TNMM to CPM, or a reduction in the number of comparables, will appear as a data anomaly across the block.
The Transaction Master Register (an internal ledger assigning unique IDs to every intercompany transaction stream) should be maintained from the first Form 48 filing and updated quarterly, not reconstructed annually.

Block assessments also interact with APAs. An APA acknowledgement number entered in Row 8 of Part C maps a covered transaction out of Part E for that year. If the APA expires or is terminated during the block period, the transition back to benchmarked pricing must be reflected cleanly in the subsequent Form 48 without creating an unexplained gap.

The Section 167 tolerance band clarification

The Income-tax Act 2025 resolves a question that was actively litigated under the old Section 92C: does the tolerance band apply when there is only one comparable?

Under the old regime, Section 92C(2) allowed a 3% variation (or 1% for wholesale trading) from the arithmetic mean of arm’s length prices. There was sustained dispute about whether the band applied where only a single comparable existed, with some tribunals holding it did not because there was no “range” to speak of. The matter created real exposure for companies in niche transaction categories with thin comparable databases.

Section 167 of the Income-tax Act 2025 expressly confirms that the tolerance band applies in all cases, including where a single comparable is used. The computation illustration from the Income Tax Department’s Form 48 FAQ confirms this: where one comparable exists, the comparable’s own margin is the arithmetic mean, and the tolerance band applies directly to it.

The impact on Part E is concrete:

A company with one comparable at 22% gross margin, claiming 3% tolerance, has an arm’s length range of 21.34% to 22.66% (i.e., the comparable minus and plus 3% of the comparable’s value). Transactions priced within this band do not require adjustment.
Under the old contested interpretation, the same company faced the argument that the band did not apply, requiring the price to exactly match the single comparable.
The Section 167 clarification should be documented in the TP study and reflected in the Part E computation entered in Form 48. A company that has been operating under the conservative assumption should now revisit whether prior-year ALP adjustments were necessary.

This matters most for companies in specialised service categories (specific intangible licensing, niche financial instruments, unique manufacturing arrangements) where database searches routinely return one or two comparables.

What the certifying CA must now independently verify

The scope of a CA’s certification liability has expanded materially under Form 48 compared to Form 3CEB. The formal obligations under Section 172 are the same certify that international transactions have been priced at arm’s length but the form architecture means the CA is now certifying specific data points, not narrative descriptions.

Under Form 3CEB: The CA certified the method selected, the aggregate transaction value, and the arm’s length price range. The underlying benchmarking study, comparables, and interquartile range were in the TP documentation file that the CA reviewed but did not reproduce in the form.

Under Form 48: The CA must verify that:

AE IDs and Person IDs are correctly assigned and consistent with the relationship codes under Section 162(1)
Transaction IDs match the correct AE and transaction type combinations
Part E entries — number of comparables, margin or mark-up for each comparable, arithmetic mean or median, tolerance band applied, computed ALP, and adjustment if any are arithmetically correct and match the TP study
APA transactions in Row 8 of Part C correspond to actual agreements with correct acknowledgement numbers
Part B auto-populated totals reconcile with the financial statements and the tax audit report
Note 14 cost and expense disclosures are complete, including items like parent-borne stock option costs and shared service allocations that may not appear in the Indian subsidiary’s own books

A mismatch between Form 48, the tax audit report, and the financial statements will be detected automatically. The CA should not certify Form 48 without running a reconciliation across all three. In practice, this means the CA needs the TP study, the audited financials, the tax audit report draft, and the intercompany cost allocation data from the parent entity to be ready before Form 48 is opened.

Filing readiness: what to have in place before October 2026

Table: Form 48 pre-filing readiness checklist

Area	Action	When
Transaction Master Register	Build or update register with AE IDs, Person IDs, and Transaction IDs for all FY 2026-27 intercompany flows	By June 2026
TP study	Commission or update for Tax Year 2026-27 with transaction-specific benchmarking for each Transaction ID	By August 2026
Safe harbour assessment	Confirm eligibility and revised margin band applicability; prepare Form 49 application if IT services	By July 2026
APA mapping	Confirm which transactions are APA-covered; extract acknowledgement numbers, dates, and coverage extent for Row 8	By August 2026
Note 14 data from parent	Issue formal data request to parent for cost allocations, stock option charges, and shared service costs not in Indian books	By April 2026
Reconciliation draft	Cross-reference Part B auto-populated totals against financials and draft tax audit report	By September 2026
CA briefing	Brief certifying CA on all of the above before any form entry begins	By September 2026
Form 48 submission	File on e-filing portal before due date	By 31/10/2026

Common mistakes that create post-filing exposure

Not requesting Note 14 data from the parent in time. Cost allocations, parent-borne ESOP charges, and shared service costs that are recharged to the Indian entity often exist only in the parent’s books. These must be disclosed in Form 48. If the parent does not provide the data before filing, the disclosure is incomplete. Issue the data request at the start of the financial year, not in September.

Using the same method for aggregated and standalone benchmarking without explanation. If a transaction is partly aggregated with other transactions and partly benchmarked on a standalone basis, both approaches must be reflected in Part E. The system provides for this, but many TP studies do not document the split clearly enough for the CA to enter the data correctly.

Changing the comparable set without a documented rationale. Block assessment visibility means a reduction in the number of comparables between Year 1 and Year 2 of Form 48 will appear as an anomaly. If the change is justified (a comparable was delisted, acquired, or became functionally dissimilar), document it in the TP study.

Filing Form 48 before the TP study is complete. Part E requires actual benchmarking data. Filing with estimated or placeholder entries creates a mismatch that will surface if the final TP study differs from what was entered. The form must reflect the completed study.

Assuming safe harbour removes all documentation and filing obligations. As set out above, it does not. Form 48 and the local file under Rule 84 are mandatory even for safe harbour-covered transactions.

Treelife practitioner note

In the Form 48 preparation work we have run at Treelife across Indian subsidiaries of US, UK, and Singapore-headquartered groups, the single most common structural failure is the absence of a Transaction Master Register. Companies that have been filing Form 3CEB for several years have typically reported transactions at an aggregate level by broad type: technology services, management fees, royalties. Form 48 requires the same transactions to be disaggregated to the AE-and-transaction-type level, assigned stable identifiers, and benchmarked separately where the functions and risks differ.

The companies that go into the October 2026 filing window most exposed are those with omnibus intercompany fee arrangements a single services fee that bundles software licences, cloud infrastructure recharges, technical support, and data access without documented sub-classification. Under Form 3CEB, that bundle was reported as one transaction. Under Form 48, each sub-category is a separate Transaction ID with its own Part E entry. Unbundling that at year-end, without prior-period documentation of what the components are and how they are priced, is expensive.

The second pattern we have seen is companies that opted into safe harbour in prior years under the old Rule 10TD regime and assumed the same opt-in mechanics continue. The new Rules 90 and 91 have different eligibility conditions, different forms (Form 49 for IT services), and a three-year block structure. Companies need to re-evaluate eligibility under the new rules and confirm that the revised margin bands cover their actual operating profit margins before relying on safe harbour for Tax Year 2026-27.

FAQs

Q: Who must file Form 48?
A: Every person who has entered into any international transaction or specified domestic transaction during Tax Year 2026-27 must obtain a Form 48 certification from a chartered accountant and file it on the Income Tax e-filing portal. There is no minimum transaction value threshold for international transactions. Form 48 can only be filed online; no offline submission is permitted.

Q: What is the due date for Form 48?
A: Form 48 must be filed on or before one month before the due date for furnishing the income tax return under Section 263(1) of the Income-tax Act 2025. For companies with international transactions, the ITR due date is 30/11/2026 for AY 2027-28, making the Form 48 due date 31/10/2026. Confirm against CBDT extension circulars issued closer to the deadline.

Q: What is the penalty for not filing Form 48?
A: Failure to furnish the accountant’s report under Section 172 attracts a penalty of ₹1,00,000. In addition, if the failure results in a TP adjustment, the underreported income carries a further penalty of 50% of the additional tax computed on the adjustment. Failure to maintain TP documentation under Section 171 attracts 2% of the value of each international transaction for which documentation was not maintained.

Q: If I opt into safe harbour, do I still need to file Form 48?
A: Yes. Safe harbour under Section 167 removes ALP litigation risk for eligible transactions, but Sections 171 and 172 apply regardless. Form 48 must be filed for all international transactions, including those for which safe harbour margins are claimed. Form 49 (the safe harbour application) is filed separately.

Q: Does Form 48 replace the transfer pricing study?
A: No. The TP study (local file maintained under Section 171 read with Rule 84) is a separate document that must be prepared and retained. Form 48 is the accountant’s certification. Part F requires the taxpayer to confirm explicitly that TP documentation has been maintained, making this confirmation a statutory obligation rather than an implicit one.

Q: How does the Section 167 tolerance band work if I only have one comparable?
A: The Income-tax Act 2025 resolves the previously contested position. The 3% tolerance band (1% for wholesale trading) applies even where there is only one comparable. The comparable’s own margin is treated as the arithmetic mean, and the tolerance band is applied directly to it. Document this position in the TP study and reflect it in the Part E computation.

Q: What is a block transfer pricing assessment and how does Form 48 create exposure?
A: Block TP assessments allow the department to scrutinise multiple tax years in a single proceeding. Form 48’s Transaction ID architecture makes year-on-year tracking automatic. Unexplained changes in benchmarking method, comparable set, or margin between successive Form 48 filings will be visible at the block level and can form the basis for a block adjustment.

Q: What is APA mapping in Form 48 and why does it matter?
A: Transactions covered by an Advance Pricing Agreement (APA) must be disclosed in Row 8 of Part C of Form 48 with the APA date, acknowledgement number, and coverage extent. These transactions are excluded from Part E (ALP computation). Failing to map APA transactions means the system may flag missing Part E entries for those transactions, creating an apparent compliance gap.

Q: What is Note 14 and why does it require data from the parent?
A: Note 14 covers cost and expense disclosures for certain transaction categories, including parent-borne stock option costs, allocated shared service costs, and charges not recorded in the Indian subsidiary’s own books. This data typically resides with the parent entity and must be formally requested at the start of the compliance season. Filing without complete Note 14 data produces an incomplete disclosure that a certifying CA should not sign.

Q: Does Form 48 apply for Tax Year 2025-26 (AY 2026-27) returns due in November 2026?
A: No. AY 2026-27 returns are filed under the Income-tax Act 1961 using Form 3CEB. The Form 3CEB due date for AY 2026-27 is 30/11/2026. Form 48 applies from Tax Year 2026-27 (AY 2027-28) onwards.

Q: Can data from Form 48 be shared with foreign tax authorities?
A: Yes. CBDT has confirmed that Form 48 data can be cross-verified with other filings and may be shared with foreign tax authorities under applicable tax treaty exchange-of-information provisions. This is a material change from Form 3CEB, which sat in a national silo.

Q: How do deemed international transactions appear in Form 48?
A: Deemed international transactions (transactions considered international by virtue of a prior arrangement involving a third party, under Section 163 of the IT Act 2025) are reported in Part C of Form 48 under a separate sub-section. The third-party counterparty is assigned a Person ID (P-1, P-2, and so on), distinct from AE IDs. These were often underdisclosed in Form 3CEB and require careful identification before Form 48 is completed.

Q: For investors reviewing a target company, what does Form 48 change in TP diligence?
A: From AY 2027-28 onwards, TP diligence will include Form 48 filings in addition to Form 3CEB for earlier years. Form 48’s transaction-level data makes it easier to identify undisclosed transaction streams, gaps in APA mapping, and benchmarking methodology inconsistencies. Any open TP exposure can affect deal valuation or trigger indemnity clauses in the SPA. Buyers should request Form 48 alongside the TP study during due diligence.

Regulatory references:

Section 172, Income-tax Act 2025 (accountant’s report obligation)
Section 171, Income-tax Act 2025 (documentation requirements)
Section 167, Income-tax Act 2025 (safe harbour — replaces Section 92CB of IT Act 1961)
Section 162(1) and 162(2), Income-tax Act 2025 (associated enterprise definition)
Section 163, Income-tax Act 2025 (international transactions)

International Tax Compliance for Businesses Running Overseas Subsidiaries

Posted on 30 Jun, 202630 Jun, 2026 by Treelife

An Indian company with one foreign subsidiary has one set of recurring filings to track. An Indian company with three foreign subsidiaries across three jurisdictions does not have three times the filings. It has the same filings, repeated per entity, layered on top of group-level thresholds that only activate once the combined numbers cross a certain size, all running on three different calendars that were never designed to talk to each other. The technical content of international tax compliance, transfer pricing, withholding tax, FEMA reporting, foreign tax credit, has not changed much in the last two years. What has changed is the number of Indian companies that now sit on the multi-entity side of this problem rather than the single-entity side, because outbound expansion into the US, UAE, Singapore and UK has become routine rather than exceptional for funded and profitable Indian businesses. This guide is built for that stage: not how to set up a foreign subsidiary, but how to run the compliance machine once two or more are already live.

What makes multi-jurisdiction compliance different from single-jurisdiction compliance?

Multi-jurisdiction tax compliance is not single-jurisdiction compliance multiplied by the number of entities. It is single-jurisdiction compliance multiplied by the number of entities, plus a layer of group-level obligations that only switch on past certain consolidated thresholds, plus the coordination cost of running three unsynchronised calendars against each other. A company with a US Delaware C-Corp and a Singapore Pte Ltd does not just file twice. It files an Annual Performance Report (APR) for each subsidiary by 31 December, an FLA return covering both subsidiaries combined by 15 July, one consolidated Form 3CEB covering all international transactions with both entities by 31 October, and separately tracks whether the combined group has crossed the master file threshold of Rs 500 crore in consolidated revenue (Income Tax Rules, Rule 10DA) or the CbCR threshold of Rs 6,400 crore (Rule 10DB), at which point two entirely new filings activate that did not exist when there was one subsidiary.

The compliance risk in single-jurisdiction structures is mostly technical: did the company apply the right withholding rate, file the right form, meet the right threshold. The compliance risk in multi-jurisdiction structures is mostly operational: did the team realise that the FLA return due on 15 July needs figures as of 31 March, while the company’s own management accounts for one subsidiary close on a calendar year basis, so the data simply is not ready in the same shape at the same time. In the cross-border engagements Treelife has run for companies with two or more live foreign subsidiaries, the single biggest cause of remediation work is not a wrong filing. It is a missed one, because nobody owned the calendar across all entities together.

How do the FEMA, income tax and subsidiary fiscal year calendars collide?

The collision is structural, not accidental. FEMA-related filings (FLA return, APR) run on India’s financial year ending 31 March. Schedule FA in the Indian income tax return runs on the calendar year ending 31 December, regardless of when the Indian entity’s own financial year closes. The foreign subsidiary’s own statutory accounts run on whatever fiscal year that jurisdiction uses, calendar year for most US states and Singapore, April-March for some UK entities depending on incorporation date, and the UAE typically calendar year unless elected otherwise. A single Indian parent with subsidiaries in two of these jurisdictions is reconciling three non-aligned years simultaneously, every single year, not once at setup.

This matters in practice. Schedule FA for the assessment year 2026-27 requires reporting all foreign assets and income held at any point between 1 January 2025 and 31 December 2025. The FLA return for the same broad period requires figures as of 31 March 2026. A company that prepares one data pull to satisfy both filings, using either calendar by default, will misreport one of them, because the underlying balances of an ODI investment can genuinely differ between 31 December 2025 and 31 March 2026 if there was a capital infusion, a loan disbursement, or a valuation change in the intervening quarter. Treating these as the same data exercise is the single most common multi-jurisdiction error Treelife encounters in compliance health checks.

Which filings consolidate across all foreign subsidiaries and which apply separately?

This distinction is where most confusion sits, because the forms look similar but follow opposite logic.

Filings that consolidate across all foreign AEs into one submission: Form 3CEB, the transfer pricing accountant’s report under Section 92E of the Income Tax Act, is filed once by the Indian entity, covering every associated enterprise the entity transacted with during the year, foreign subsidiary in Singapore, foreign subsidiary in the US, any other AE, all reported within the same form with separate disclosure rows per AE. The FLA return follows the same consolidated logic: one return per Indian entity, capturing total outstanding ODI across all foreign subsidiaries combined, not one return per subsidiary.

Filings that apply separately for each foreign subsidiary: The APR under FEMA’s Overseas Investment Rules must be filed separately for each foreign subsidiary, by 31 December each year, based on that subsidiary’s own audited financial statements (or unaudited, where the host jurisdiction does not mandate an audit and the Indian entity self-certifies). A dormant subsidiary with zero activity still requires an APR; there is no dormancy exemption. Local tax returns, GST or VAT equivalents, and payroll filings in each foreign jurisdiction are obviously entity-specific and follow that jurisdiction’s own deadlines entirely outside Indian law.

The practical risk in multi-entity structures is treating a consolidated filing as if it were per-entity (filing three separate Form 3CEBs when one consolidated form was required, which creates internal inconsistency across the three) or treating a per-entity filing as if it were consolidated (filing one APR covering two subsidiaries, which RBI’s AD bank will reject on review).

Filing	Scope	Due date	Governing law
FLA return	Consolidated, all foreign assets/liabilities	15 July (provisional), 30 September (revised)	FEMA 1999, A.P. (DIR Series) Circular No. 45
Annual Performance Report (APR)	Separate, per foreign subsidiary	31 December	FEMA Overseas Investment Rules 2022
Form 3CEB	Consolidated, all foreign AEs	31 October	Section 92E, Income Tax Act
Schedule FA, FSI, Form 67	Consolidated, calendar year basis	With ITR (typically 31 October for companies with TP audit)	Income Tax Act, Black Money Act 2015
Master file (Form 3CEAA)	Group-level, if thresholds met	Aligned with ITR due date	Rule 10DA
CbCR (Form 3CEAD)	Group-level, if Indian parent is UPE or ARE	12 months from end of parent’s reporting year	Rule 10DB

What changes once the group crosses Rs 500 crore or Rs 6,400 crore consolidated revenue?

A company running two small foreign subsidiaries and a company running a global group with the same two subsidiaries but Rs 600 crore in consolidated revenue face genuinely different compliance regimes, not just a bigger version of the same one. Below the threshold, the company’s obligations are Form 3CEB, FLA, and APR, the standard transfer pricing and FEMA reporting layer. Once consolidated group revenue crosses Rs 500 crore and the aggregate value of international transactions exceeds Rs 50 crore (or Rs 10 crore where intangible property is involved), the master file obligation activates under Rule 10DA, requiring disclosure in Form 3CEAA of the group’s global business description, intangible property positions, financing arrangements, and a copy of the group’s consolidated financial statements. This is a materially heavier disclosure than the local file analysis already required for Form 3CEB.

Separately, if consolidated group revenue crosses Rs 6,400 crore and the Indian entity is the ultimate parent entity of the group (or has been designated as the alternate reporting entity), Country-by-Country Reporting under Rule 10DB activates, requiring Form 3CEAD with jurisdiction-by-jurisdiction disclosure of revenue, profit, tax paid, and headcount for every entity in the group, filed within 12 months of the end of the parent’s reporting year. Groups operating across enough jurisdictions to approach this scale should also track the OECD’s Pillar Two global minimum tax framework. India has not yet enacted a domestic GloBE top-up tax regime as of this writing, but Indian groups with foreign subsidiaries in jurisdictions that have implemented Pillar Two (most of the EU, UK, several Asian jurisdictions) may already be inside scope for a top-up tax assessed abroad, even where the Indian parent itself has no domestic GloBE filing obligation yet. This is worth a dedicated review with international tax counsel rather than an assumption either way, since the rules are evolving by jurisdiction.

Q: Does crossing the master file threshold in one year mean we are permanently in that regime?
A: No. The threshold is tested annually against the relevant financial year’s consolidated revenue and transaction value. A company can move in and out of master file applicability year to year if its numbers move around the Rs 500 crore line, though falling back below the threshold after several years of filing typically invites a closer look from the tax officer rather than an automatic pass.

How do DTAA, TRC and Form 10F work as a recurring obligation rather than a one-time setup?

A common assumption among finance teams who set up a foreign structure two or three years ago is that DTAA documentation was a one-time exercise completed at the time the foreign entity was incorporated. It is not. A Tax Residency Certificate (TRC) issued by the foreign jurisdiction’s tax authority and Form 10F filed with the Indian tax department both need to be current for the financial year in which a payment is being made, not merely on file from the year the structure was set up. India’s tax treaties with over 90 countries can reduce withholding on dividends, royalties, interest and fees for technical services from the domestic rate of 20 to 50 percent down to 5 to 15 percent depending on the treaty, but every concessional rate applied during the year requires a valid, current TRC and Form 10F for that specific year.

In a multi-jurisdiction structure, this means the finance team is renewing TRC and Form 10F separately for the US subsidiary, the Singapore subsidiary, and the UAE subsidiary, each on that jurisdiction’s own TRC issuance timeline (the IRS issues Form 6166 with its own processing lag; Singapore’s IRAS and the UAE’s Federal Tax Authority each have their own). If the TRC for one entity lapses mid-year and a management fee or royalty payment is made before it is renewed, the Indian entity is obligated to withhold at the domestic rate on that specific payment, the treaty rate cannot be applied retroactively to a payment already made without it. Recovering the excess TDS typically requires the foreign entity to file an Indian return, which carries its own permanent establishment risk if not handled carefully.

Can our own employees create a taxable presence for the Indian company in the subsidiary’s country?

Yes, and this is the risk most Indian groups have analysed in only one direction. Most compliance reviews ask whether the foreign subsidiary’s activity creates a problem for the Indian parent under FEMA or transfer pricing. Far fewer ask whether the Indian parent’s own people, visiting, supervising, or seconded to the foreign subsidiary, create a permanent establishment (PE) for the Indian company inside that subsidiary’s jurisdiction. The risk runs both ways, and the outbound direction gets far less attention once a structure is past its setup year and into routine operations, precisely the stage this guide is written for.

A service PE typically arises where personnel render services in the host country beyond a treaty-specified threshold, commonly 90 days in a 12-month period for unrelated parties, but as low as 30 days where the services are rendered to an associated enterprise, which is exactly the relationship between an Indian parent and its own foreign subsidiary. A dependent agent PE arises separately if an Indian employee, while present in the subsidiary’s country, habitually negotiates or concludes contracts on behalf of the Indian parent rather than the local subsidiary. Neither trigger requires a fixed office. A founder who spends extended stretches in the US subsidiary’s office directing strategy, or a finance lead who routinely signs vendor agreements while physically present there, can create exactly this exposure without anyone in the group having decided to.

The OECD’s November 2025 update to the Commentary on Article 5 of the Model Tax Convention adds a further test relevant to founders and senior staff who split time between India and a foreign subsidiary: if an individual works from a location in the host country for less than 50 percent of their total working time over any 12-month period, that location generally does not create a PE for the employer. This is a useful safe harbour for occasional travel, but it cuts the other way for anyone, commonly a co-founder or country head, who effectively splits their working year close to evenly between India and one subsidiary’s jurisdiction.

Where the Indian parent seconds an employee to a foreign subsidiary rather than having them travel on a short visit, the structuring of that secondment matters as much as its duration. If the seconded employee remains legally and economically an employee of the Indian parent while working under the foreign subsidiary’s day-to-day control, tax authorities in either jurisdiction may treat this as a service PE of the Indian entity in the host country, or alternatively recharacterise the arrangement and apply withholding to the cost reimbursement between the two entities as a fee for technical services. Getting the secondment agreement right, specifying who has the right to terminate the individual’s assignment, who directs daily work, and how costs are recharged, materially changes which of these outcomes applies.

Common mistakes that cost businesses time and money in multi-jurisdiction structures

Treating the FLA return and Schedule FA as the same data pull. As covered above, these run on different calendars, 31 March for FLA and 31 December for Schedule FA, and using one dataset for both produces a mismatch that draws RBI or income tax scrutiny on cross-verification.

Filing the APR for active subsidiaries but skipping dormant ones. A foreign subsidiary that has not commenced operations, or has gone dormant after an early pivot, still requires an APR by 31 December. There is no automatic dormancy exemption under the Overseas Investment Rules. Indian companies routinely discover this gap only when applying for a fresh ODI into a new jurisdiction and the AD bank flags the missing prior-year APR.

Letting TRC renewal lapse for one entity while tracking it correctly for others. When a company has three foreign subsidiaries, the renewal discipline applied diligently to the largest or oldest entity often does not extend to a newer or smaller one, and that is precisely the entity where a lapsed TRC goes unnoticed until a withholding query arises.

Not tracking aggregate days for founders and senior staff who travel to a foreign subsidiary. Travel that looks occasional in isolation, a founder visiting the US entity for two weeks every quarter, can aggregate close to the 30-day associated-enterprise PE threshold across a year, and most companies have no single log tracking this across all foreign jurisdictions combined.

Assuming master file and CbCR thresholds are tested per entity rather than at consolidated group level. A company with three foreign subsidiaries, none individually large, can still trigger master file obligations because the threshold is tested against consolidated group revenue and aggregate international transaction value across all entities combined, not against any single subsidiary’s standalone numbers.

Missing the 90-day repatriation window after a subsidiary disinvestment. Where one foreign subsidiary in a multi-entity structure is sold or wound down, sale proceeds must be repatriated to India within 90 days under the Overseas Investment Rules, and documentary evidence of repatriation must go to the AD bank. This deadline is frequently missed specifically in multi-entity groups because the wind-down of one entity gets less attention than the ongoing operations of the others.

Late filing of the FLA return alone carries a flat Late Submission Fee of Rs 7,500 per return, separate from any FEMA penalty under Section 13 that can run up to three times the amount involved or Rs 2 lakh plus Rs 5,000 per day of continuing default. Across three subsidiaries with overlapping lapses, these figures compound entity by entity rather than netting against a single combined exposure.

Treelife’s practitioner note

In the cross-border compliance engagements we have run at Treelife for companies with foreign subsidiaries in two or more jurisdictions simultaneously, the pattern is consistent: the company’s individual filings are usually technically correct when reviewed in isolation, the transfer pricing methodology is sound, the FLA figures reconcile to the balance sheet, the APRs are filed. What breaks is the sequencing across entities, an APR for the UAE subsidiary filed correctly on 28 December, while the equivalent filing for the US subsidiary was overlooked because the team assumed the CA handling the US entity’s IRS filings would also flag the Indian-side APR requirement, which is a different filing under a different statute entirely.

A specific pattern we have flagged more than once in FY 2025-26 reviews relates to Section 161 of the Income-tax Act 2025 (the successor provision to Section 92C, effective from 1 April 2026), which restates the arm’s length principle for international transactions. Companies with multiple foreign AEs sometimes prepare a single transfer pricing study covering the largest subsidiary relationship in depth and apply a lighter, less defensible benchmarking exercise to smaller AE relationships, on the assumption that materiality protects them. Form 3CEB requires disclosure of every AE relationship regardless of value, and a Transfer Pricing Officer reviewing the larger relationship in detail routinely pulls the smaller AE disclosures into the same audit once the file is open. Treating every AE relationship, however small, with the same documentation rigour from year one is materially cheaper than reconstructing it during an active TP audit.

Frequently asked questions

Q: Do we need a separate transfer pricing study for each foreign subsidiary, or one combined study?
A: One consolidated local file is acceptable in principle, but it must analyse each AE relationship separately within that file. A combined narrative that does not distinguish the functional and risk profile of the US relationship from the Singapore relationship will not withstand scrutiny if either is reviewed individually by a Transfer Pricing Officer.

Q: What does professional support for multi-jurisdiction compliance typically cost?
A: Fees are usually structured per filing type plus a coordination retainer, rather than per entity, since the coordination work (calendar tracking, cross-checking data consistency across filings) does not scale linearly with the number of subsidiaries. A typical structure with two to three foreign subsidiaries should expect the coordination layer to add meaningfully less than doubling or tripling single-entity advisory fees.

Q: What is the realistic timeline to get a multi-jurisdiction compliance calendar fully in order if we are starting from a gap?
A: A compliance health check across all entities typically takes two to four weeks to complete, depending on how many years of historical filings need review. Remediation of any identified gaps, including any RBI compounding applications if FEMA contraventions are found, can take an additional one to six months depending on the nature and number of gaps.

Q: What documentation do we need to keep on hand across all entities at all times?
A: Current TRC and Form 10F for every foreign subsidiary for the financial year in question, the most recent transfer pricing study covering every AE relationship, the prior year’s FLA acknowledgment and APR filings for each subsidiary, and the consolidated group financial statements if the company is anywhere near the master file or CbCR thresholds.

Q: How does cross-border tax compliance interact with FEMA’s two-layer subsidiary restriction?
A: The Overseas Investment Rules restrict ODI structures to a maximum of two layers of step-down subsidiaries to prevent complex round-tripping. A company running multiple foreign entities should check this restriction at the structuring stage rather than the compliance stage, since unwinding a non-compliant layered structure after the fact is significantly more disruptive than the original FEMA filing would have been.

Q: If our foreign subsidiary in one jurisdiction pays tax locally on its own profits, do we still owe Indian tax on the same income?
A: Indian tax law taxes the parent on dividends received from the foreign subsidiary, not on the subsidiary’s underlying profits directly, unless Controlled Foreign Corporation-style attribution rules apply, which India does not currently have in the form some other jurisdictions do. Foreign tax already paid by the subsidiary locally is generally not creditable against the parent’s Indian tax on dividends; what is creditable is foreign withholding tax on the dividend itself, claimed via Form 67 under the relevant DTAA.

Q: Do family-owned or founder-led companies face different rules from VC-funded ones for multi-jurisdiction compliance?
A: The statutory obligations, FLA, APR, Form 3CEB, are identical regardless of ownership structure. What differs in practice is governance bandwidth, a founder-led company without a dedicated finance team is more exposed to the coordination failures described in this guide, since there is often no single internal owner tracking all entities’ calendars together.

Q: What happens to compliance obligations if one foreign subsidiary is restructured into a holding company above the others?
A: Inserting an intermediate holding entity changes the AE relationships for transfer pricing purposes, every transaction the Indian parent previously had directly with the operating subsidiary may now route through the new holding entity, requiring a fresh transfer pricing analysis and an updated APR reflecting the revised shareholding chain at the AD bank.

Q: Can our Indian employees create a tax problem for us just by working closely with a foreign subsidiary?
A: Yes. If an Indian employee spends extended or recurring time physically present in a foreign subsidiary’s country, particularly while directing or supervising work for the Indian parent rather than purely the local entity, this can create a service or dependent agent permanent establishment for the Indian company in that jurisdiction, separate from and in addition to the local subsidiary’s own tax position. This risk is rarely tracked because most compliance attention goes to the inbound direction, foreign staff creating a PE in India, rather than the outbound one.

Q: Does the DPIIT recognition of the Indian parent affect compliance obligations for its foreign subsidiaries?
A: DPIIT recognition and the associated Section 80-IAC benefits apply to the Indian entity’s own domestic tax position and do not extend to, or modify, the foreign subsidiaries’ compliance obligations, which run entirely under FEMA and the Income Tax Act’s international transaction provisions regardless of the parent’s DPIIT status.

Q: What is the most common edge case that catches multi-jurisdiction structures off guard?
A: A change in the immediate investor’s residence partway through the year, for example, a Singapore subsidiary being acquired by or merged into a new holding jurisdiction, changes the country attribution for FLA reporting purposes mid-year. The FLA return requires reporting by the immediate investor’s country of residence at the reporting date, not the structure that existed for most of the year, and this is one of the more common sources of RBI queries on cross-verification.

Q: If we are about to cross the Rs 500 crore master file threshold for the first time, what should we do differently this year?
A: Begin preparing the Form 3CEAA documentation, group business description, intangible property mapping, financing arrangement details, well before the filing deadline rather than at the same time as the standard Form 3CEB, since the master file’s disclosure scope is considerably broader and first-year preparation typically takes longer than anticipated.

Regulatory references:

Section 92E, Income Tax Act, 1961 (Form 3CEB, transfer pricing accountant’s report)
Section 161, Income-tax Act, 2025 (arm’s length principle, effective 01/04/2026, successor to Section 92C)
Rule 10DA, Income Tax Rules (master file, Form 3CEAA, Rs 500 crore / Rs 50 crore thresholds)
Rule 10DB, Income Tax Rules (Country-by-Country Reporting, Form 3CEAD, Rs 6,400 crore threshold)
FEMA, 1999, Section 13 (penalties for contravention)
A.P. (DIR Series) Circular No. 45 dated 15 March 2011 (FLA return)
Foreign Exchange Management (Overseas Investment) Rules, 2022 (APR, two-layer restriction, 90-day repatriation)
Schedule FA, Schedule FSI, Form 67, Income Tax Act, 1961 / Income-tax Act, 2025
Black Money (Undisclosed Foreign Income and Assets) and Imposition of Tax Act, 2015
Article 5, OECD Model Tax Convention (permanent establishment), as updated by the November 2025 Commentary update on remote work and mobile employees

Transfer Pricing: A Comprehensive Guide for Founders, CFOs, and Startups

Posted on 20 May, 202521 Jul, 2025 by Treelife

DOWNLOAD PDF

In an increasingly interconnected global economy, startups and growing companies face the challenge of managing cross-border operations efficiently while complying with complex tax regulations. One critical area demanding attention is transfer pricing the pricing of transactions between related companies operating in different jurisdictions.

This comprehensive guide demystifies transfer pricing concepts, methods, regulatory frameworks, common challenges, and best practices, helping founders, CFOs, and finance teams navigate this complex terrain with confidence.

What is Transfer Pricing and Why Is It Important?

Transfer pricing refers to the price charged for goods, services, or intangible assets (like intellectual property) exchanged between related entities within the same multinational group. For example, when a U.S.-based startup sells software licenses to its Indian subsidiary, the price charged is a transfer price.

Why does this matter? Transfer pricing directly affects how profits are allocated among the entities and, consequently, how much tax is paid in each jurisdiction. Incorrect transfer prices can trigger tax audits, adjustments, penalties, and in some cases, double taxation where the same income is taxed in more than one country.

With estimates showing that over 60% of global trade occurs between related parties, governments worldwide prioritize transfer pricing enforcement to protect their tax base. For startups scaling internationally, understanding and managing transfer pricing is crucial to avoid costly disputes and maintain investor confidence.

Fundamentals of Transfer Pricing: The Arm’s Length Principle

The Arm’s Length Principle (ALP) is the foundation of transfer pricing globally. It requires that transactions between related parties be priced as if they were conducted between independent, unrelated parties under similar circumstances. This principle ensures fairness and prevents multinational companies from shifting profits artificially to minimize taxes.

For startups, this means intercompany transactions—whether for goods, services, royalties, or loans—must be priced at fair market value. Applying ALP involves comparing related-party transactions with similar transactions between independent parties, often through benchmarking studies and economic analyses.

Transfer Pricing Methods: How to Set the Right Price

Several internationally recognized methods exist to determine arm’s length prices, each with specific applications:

Comparable Uncontrolled Price (CUP) Method: Compares the price charged in a related-party transaction to that charged between independent parties for comparable goods or services. CUP is preferred when exact comparables exist but is often challenging due to differences in terms or products.
Resale Price Method (RPM): Starts from the price at which a related party resells goods to independent customers, subtracting an appropriate gross margin. Useful for distributors or resellers who add limited value.
Cost Plus Method (CPM): Adds an appropriate markup to the costs incurred by a supplier in a related-party transaction. Commonly applied for manufacturing or service transactions.
Transactional Net Margin Method (TNMM): Examines the net profit margin relative to a suitable base (e.g., costs or sales) of a related party compared to independent firms. TNMM is flexible and widely used when exact price comparables are unavailable.
Profit Split Method (PSM): Allocates combined profits from related-party transactions among entities based on their relative contributions. Applied in highly integrated operations or where unique intangibles are involved.

Choosing the right method requires careful consideration of the transaction type, data availability, and functional analysis.

Global and India-Specific Transfer Pricing Regulations

OECD Guidelines and BEPS

The Organisation for Economic Co-operation and Development (OECD) provides internationally accepted transfer pricing guidelines adopted by over 120 countries. Its Base Erosion and Profit Shifting (BEPS) project strengthened rules on transparency and documentation, introducing mandatory country-by-country reporting and master/local file documentation.

Indian Transfer Pricing Framework

India’s transfer pricing laws, under the Income Tax Act, 1961, align closely with OECD standards but have unique features:

Applicability: Transfer pricing applies to international transactions and certain specified domestic transactions (SDT), particularly when entities claim tax holidays or other benefits.
Documentation: Companies must maintain contemporaneous documentation including a Local File, Master File, and, where applicable, Country-by-Country Reports.
Compliance: Filing an accountant’s report (Form 3CEB) is mandatory for entities engaged in international transactions.
Penalties: Non-compliance or inadequate documentation can lead to penalties amounting to a percentage of the transaction value, alongside interest and additional tax demands.
Advance Pricing Agreements (APA): India’s APA program allows taxpayers to pre-agree transfer pricing methods with authorities, reducing audit risk.

Challenges in Transfer Pricing Compliance

Finding Comparables: Identifying reliable independent comparables is difficult, especially for unique intangibles or services.
Documentation Burden: Preparing and maintaining extensive, contemporaneous documentation requires resources and expertise.
Risk of Tax Adjustments: Tax authorities globally scrutinize transfer pricing aggressively, leading to adjustments, interest, and penalties.
Double Taxation Risk: Disputes over transfer pricing can result in the same income being taxed in multiple jurisdictions, requiring costly resolution mechanisms.
Changing Regulations: Businesses must keep up with evolving rules, reporting requirements, and safe harbor provisions.

Best Practices for Startups and CFOs

Develop a Clear Transfer Pricing Policy: Establish a well-defined policy detailing how intercompany prices are set, the rationale behind decisions, and procedures for regular review.
Adhere to the Arm’s Length Principle: Ensure all transfer prices reflect what independent parties would agree upon under similar circumstances.
Clearly Define Roles and Responsibilities (FAR Analysis): Conduct a thorough analysis of Functions, Assets, and Risks (FAR) for each related entity and document them precisely.
Maintain Robust Documentation (Local File): Prepare comprehensive, contemporaneous documentation detailing intercompany transactions, functional analyses, and benchmarking studies.
Consider Advance Pricing Agreements (APAs): For complex or high-value transactions, explore APAs with tax authorities to gain prior certainty on pricing methods and reduce dispute risks.
Utilize Safe Harbors (if available): Leverage safe harbor provisions, such as those offered in Indian transfer pricing regulations, to simplify compliance where applicable.
Ensure Intercompany Agreements are in Place: Formalize all significant related-party transactions through written agreements outlining terms, pricing, and responsibilities.

Real-World Case Studies

Coca-Cola vs. IRS:

One of the most prominent examples discussed in the guide is the transfer pricing dispute involving Coca-Cola and the U.S. Internal Revenue Service (IRS). This case highlights the complexity and financial risks associated with transfer pricing compliance, especially for multinational corporations with substantial intangible assets.

Background

Coca-Cola faced scrutiny over the allocation of profits between its U.S. headquarters and foreign subsidiaries involved in the manufacturing and distribution of concentrate. The IRS challenged the transfer pricing methodology used for royalty payments on intangible assets, asserting that Coca-Cola’s pricing undervalued the profits attributable to the U.S. operations.

Key Issues

Valuation of Intangible Assets: The core of the dispute centered on the appropriate valuation of Coca-Cola’s brand and related intangibles transferred to foreign affiliates.
Profit Allocation: Determining how much profit should be allocated to the U.S. entity versus foreign subsidiaries based on their contributions and risks.
Functional Analysis: Evaluating the functions performed, assets used, and risks assumed by each entity was critical to justify pricing.

Outcome

The U.S. Tax Court upheld the IRS’s adjustments, significantly increasing Coca-Cola’s taxable income in the United States. The case underscored the importance of a rigorous transfer pricing framework, especially in valuing intangibles and conducting detailed functional analyses.

Conclusion

Transfer pricing is a complex but critical area in international business and taxation. Startups, CFOs, and finance teams must understand and apply transfer pricing principles to maintain compliance, reduce tax risks, and support sustainable growth.

By adopting a clear transfer pricing policy, maintaining robust documentation, choosing appropriate methods, and staying abreast of evolving regulations—especially under India’s regime and global OECD standards—businesses can confidently navigate transfer pricing challenges.

If your company needs assistance in managing transfer pricing risks or compliance, Treelife’s experts are ready to help. Reach out to priya@treelife.in for tailored solutions.

Startup

Investor

Going Global