International Tax Compliance for Businesses Running Overseas Subsidiaries

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