Fixed-fee Compliance Scoping for a US-parent SaaS Company

The compliance conversation at the point of India incorporation is relatively straightforward: you have a list of obligations, a clean slate, and a CA who designs the system from the first transaction. The conversation eighteen months later is a different exercise entirely. The subsidiary has grown, intercompany flows have multiplied, a capital injection happened without the right FEMA filing, and the finance team has changed twice. The question now is not “how do we set up compliance” but “how do we scope what we need, understand what is broken, and price a retainer that actually covers the right things.” This article addresses that specific problem. Every regulatory detail links to the relevant Treelife specialist guide; the focus here is on the engagement design, the health check methodology, and the scope letter construction.

What does a compliance health check for an already-live India subsidiary involve?

A compliance health check for an operational Indian subsidiary of a US parent is a bounded, deliverable-led audit across five regulatory zones: MCA/ROC filings, income tax and transfer pricing, FEMA/RBI reporting, GST, and labour/payroll. The output is a gap register that classifies each finding as a backlog item (remediation required before the retainer starts) or a recurring obligation (covered by the annual retainer going forward). This gap register is the only defensible basis for pricing the engagement.

Why “already live” scoping is a different exercise

A fresh India entry engagement is a design problem. An already-live subsidiary engagement is a diagnostic problem first and a design problem second.

The difference matters commercially. An advisor who quotes a fixed-fee retainer for an operational subsidiary without first conducting a health check is pricing against an unknown exposure. If they price too low, they absorb the remediation cost or cut corners on the steady-state work. If they price too high, the client walks. The health check converts the unknown exposure into a quantified gap register, which is the only fair basis for either party to agree a fee.

For the US parent’s finance team, the health check also serves a different purpose: it is the first time someone has looked at the India compliance picture as a whole rather than in functional silos. The CA handling the annual return does not know what the parent’s legal team did on FEMA. The finance team handling GST does not know whether transfer pricing documentation has been prepared. The health check connects these silos and produces the first unified view of what the subsidiary’s actual compliance position is.

The compliance health check: five examination zones

Zone 1: MCA and ROC filings

The examination covers: whether AOC-4 (financial statements) and MGT-7 (annual return) have been filed for every financial year since incorporation; whether ADT-1 (auditor appointment) was filed at the first AGM and at every renewal; whether all event-based filings are current, including DIR-12 for any director changes, SH-7 for any capital alterations, and INC-22A (active company tagging, if applicable); and whether DIR-3 KYC has been filed annually for every director.

The most common finding in this zone is not a missing annual return (those are usually filed because penalties are visible) but a missing event-based filing. Director changes, registered office changes, and increases in authorised share capital routinely happen without the corresponding MCA filing because no one on either the US parent’s or the Indian subsidiary’s team is monitoring the event-based trigger list.

Zone 2: Income tax and transfer pricing

The examination covers: whether income tax returns (ITR-6) have been filed for every assessment year; whether the statutory audit was completed on time; whether Form 3CEB (or Form 56 under the Income Tax Act 2025, effective 1 April 2026) was filed for every year in which the aggregate value of international transactions with the US parent exceeded ₹1 crore; whether contemporaneous TP documentation (the local file under Rule 84) exists for each of those years; and whether the intercompany services agreement is signed, current, and covers all actual transaction flows.

For the detail on what the TP documentation must contain and how the associated enterprise definition works under the Income Tax Act 2025, see Treelife’s guides on intercompany service fees and arm’s length pricing and transfer pricing documentation for foreign operations.

The most common finding: Form 3CEB has not been filed because the subsidiary’s CA treated it as optional or was not briefed on the intercompany flows. The aggregate ₹1 crore threshold under Section 92E of the Income Tax Act 1961 (now Section 172 of the Income Tax Act 2025) applies to the total across all transaction types with associated enterprises, not to any single stream. A subsidiary paying ₹40 lakh in management fees, billing ₹50 lakh in development services to the parent, and running a ₹15 lakh ESOP cross-charge has crossed ₹1 crore in aggregate even if no single stream does.

Zone 3: FEMA and RBI

The examination covers: whether FC-GPR was filed with the RBI within 30 days of every share allotment to a non-resident; whether the FLA (Foreign Liabilities and Assets) return has been filed annually through the FLAIR portal by 15 July of each year (for FY 2025-26, the RBI extended this to 31 July 2026); whether any outbound remittances to the US parent were processed with Form 15CA and Form 15CB in place; and whether any open compounding proceedings exist.

FC-GPR is the most frequently missed filing in this zone, and the pattern is predictable. The initial share allotment at incorporation is usually filed correctly because the incorporation agent handles it. Subsequent allotments, whether for fresh capital or an expanded ESOP pool, are decided by the US parent’s board and the 30-day India filing window closes before anyone on the India side is notified. The FLA return failure pattern is different: subsidiaries that have received FDI in prior years but have not raised fresh capital assume they no longer need to file. The obligation is based on outstanding foreign investment on the 31 March balance sheet, not on whether any transaction occurred during the year.

Zone 4: GST

The examination covers: whether GST registration is current; whether GSTR-1 and GSTR-3B returns have been filed monthly without gaps; whether the zero-rating treatment for export of services to the US parent has been correctly applied (requiring a valid Letter of Undertaking and meeting the Place of Supply conditions under the IGST Act 2017); and whether Reverse Charge Mechanism (RCM) obligations have been discharged on inbound service fees from the US parent, with self-invoices raised and IGST paid in cash before ITC is claimed.

The RCM obligation on inbound management fees and technical service charges from the US parent is the most consistently missed GST item. When the Indian subsidiary accrues a management fee payable to the US parent, IGST at 18% is payable in that month under Section 5(3) of the IGST Act read with Notification 10/2017-IT(Rate), regardless of when actual payment is made. Missing the self-invoice or delaying the RCM payment means the ITC cannot be claimed until the tax is actually paid in cash, which creates cascading timing differences across GST returns.

Zone 5: Labour and payroll

This is the zone most commonly excluded from the health check, and the most commonly underpriced in the retainer, for the same reason: the US parent’s finance team does not think of Indian labour law as a cross-border compliance issue. It is not, strictly, but the consequences of getting it wrong land on the subsidiary’s directors personally, and the discovery of a payroll compliance gap during a fundraise due diligence creates the same urgency as a FEMA compounding matter.

The examination covers: whether the subsidiary has PF (Employees’ Provident Fund) registration and is depositing contributions by the 15th of the following month; whether ESI (Employee State Insurance) registration is current and contributions are being filed correctly for employees with gross salary up to ₹21,000 per month; whether the salary structure has been updated for the 50% wage rule under the Code on Wages 2019 (which the four Labour Codes brought into operational effect in late 2025, increasing the PF contribution base for many employees); and whether Professional Tax registration and filings are current for the state(s) where the subsidiary has employees.

Treelife’s guides on PF compliance and ESI compliance cover the full obligations and penalty structure. The scoping point here is a different one: labour and payroll compliance is often handled by a third-party payroll processor with no line of sight to the retainer advisor. The retainer scope must either include a review of the payroll processor’s output or explicitly exclude it, with a named owner on the client’s side responsible for the payroll track.

How to separate backlog from recurring retainer

This is the most commercially important step in the scoping process, and the most commonly skipped. Blending backlog remediation into the annual retainer fee underprices the remediation work and overprices the ongoing compliance, which means the client feels overcharged within three months and the advisor is losing money on the clean-up.

The clean separation works as follows:

Backlog items are one-time remediation tasks with a definable end state. Examples: filing a compounding application for a delayed FC-GPR; preparing and filing two years of missed Form 3CEB/Form 56; drafting an amended intercompany agreement to cover all current transaction flows; filing retrospective DPT-3 returns for unreported loans. These are quoted as a fixed fee per item or as a project rate, with a defined scope and delivery timeline, outside the retainer.

Recurring obligations are the repeating annual and monthly filings that represent the steady-state compliance cost of running the subsidiary. These are the items that go into the retainer.

The health check output should produce a two-column gap register: backlog items with a remediation cost estimate, and recurring obligations with their frequency and the annual retainer allocation. Presenting both to the US parent’s CFO at the same time, with clear separation, is also the most effective way to get approval for the backlog spend. Bundling it into a higher retainer fee obscures the cost and creates ongoing friction.

Table: Backlog vs recurring: how to classify common items

Item	Classification	Why
Late FC-GPR compounding application	Backlog	One-time remediation; terminates once compounding is settled
FLA return filed for all missed years	Backlog	Discrete remediation exercise
Amended intercompany services agreement	Backlog	One-time drafting; then annual review becomes recurring
TP local file for Year 1 and Year 2 (missed)	Backlog	Preparatory; then annual refresh becomes recurring
Annual statutory audit coordination	Recurring	Repeating; CA appointment and audit management
AOC-4 and MGT-7 filing	Recurring	Annual MCA obligation
FLA return (going forward, annual)	Recurring	Annual FEMA obligation
Form 56 / TP local file refresh	Recurring	Annual TP obligation
GST return filing (GSTR-1 and GSTR-3B)	Recurring	Monthly obligation
DIR-3 KYC	Recurring	Annual director obligation
DPT-3 (if applicable)	Recurring	Annual obligation
Payroll review / PF and ESI compliance monitoring	Recurring or separate retainer	Depends on whether payroll processor is in scope

The five variables that drive retainer scope and price

Once the health check is complete and the backlog is separated, the retainer is scoped against five variables. These determine both what is included and what the annual fee should be.

1. Number of active intercompany transaction streams

A subsidiary that only receives capital from the US parent and bills it for software development services has two streams. One that also receives a management fee, participates in a cost-sharing arrangement for cloud infrastructure, runs an ESOP cross-charge, and has an inbound technology licence from the parent has five or six streams. Each stream needs its own pricing method reference in the TP documentation, its own TDS and FEMA analysis, and its own line in the annual compliance calendar. This is the single largest driver of complexity and, therefore, of price.

2. Whether the TP documentation is being built from scratch or refreshed

A first-year TP local file for a subsidiary with three or four transaction streams is a substantial piece of work: FAR analysis, benchmarking study, method selection, comparable search, and pricing determination. An annual refresh of an existing, well-structured file is significantly less work. If the health check shows no prior TP documentation, the retainer should be priced for a first-year build in Year 1 and a lower refresh fee in subsequent years.

3. Complexity of the FDI and equity history

A subsidiary with a single share allotment at incorporation and no subsequent capital events has a clean FEMA file. One that has had three rounds, an ESOP pool, a secondary sale involving a US investor, and a convertible note instrument has a much larger FEMA surface area. The FEMA complexity drives the time cost of the annual FLA return and any event-based RBI filings.

4. GST exposure type

A subsidiary that exclusively renders services to its US parent, invoiced in US dollars under a zero-rated LUT arrangement, has a limited domestic GST profile. A subsidiary that also sells SaaS licences to Indian customers, sub-licences technology from the US parent (with an inbound RCM obligation), and engages domestic vendors adds a full monthly GST cycle to the retainer scope.

5. Whether secretarial compliance is bundled or separate

Board meetings, AGM, statutory register maintenance, and event-based ROC filings can be bundled with the tax and FEMA retainer or scoped as a separate secretarial retainer. Most US-headquartered SaaS companies operating a lean India subsidiary prefer a single retainer with a single point of accountability. The risk of splitting the mandate is a coordination gap between the secretarial advisor and the tax advisor at the point when an event-based filing (say, a director change) has TP or FEMA implications (the director may also be the key approver of intercompany transactions).

What does a well-scoped retainer cost?

For a US-parent SaaS subsidiary with a turnover between ₹2 crore and ₹50 crore, one to three intercompany transaction streams, and a standard GST profile (zero-rated export of services, no Indian customer billing), a bundled annual retainer covering statutory audit coordination, income tax return, TP local file and Form 56, FLA return, GST filings, and secretarial compliance typically runs ₹7 lakh to ₹18 lakh per annum. The spread is driven primarily by TP complexity.

Retainers quoted below ₹4 lakh for the full stack are typically excluding transfer pricing documentation (the most labour-intensive component) or pricing for a simpler structure than the actual facts present. Retainers quoted above ₹25 lakh without a clearly differentiated scope usually reflect large-company pricing that does not apply to a lean subsidiary.

What the scope letter must explicitly exclude

The scope letter matters as much as the scope. Items that are not explicitly excluded are, in practice, included, because the client’s expectation expands to fill any ambiguity. The following categories should always be written out of a fixed-fee retainer, with the exclusion language precise enough to be unambiguous in a billing dispute.

Litigation, assessments, and responses to tax notices. A transfer pricing adjustment notice, a GST show-cause notice, or an income tax scrutiny order each require a different kind of work (often involving appearing before an authority, preparing detailed submissions, and engaging specialists) that cannot be priced into a steady-state retainer. These should be quoted separately, either at an hourly rate or as a fixed fee per notice with a defined scope of response.

Due diligence support for a fundraise. A fundraise creates a compressed, high-intensity review window where investors’ counsel examines the subsidiary’s compliance position in detail, often requesting documents for periods outside the current retainer year. This is a separately scoped engagement, typically priced on a project basis. Building it into the retainer fee creates a perverse incentive: the advisor wants the fundraise to close quickly; the investor wants thorough review. These should not share a fee.

Restructuring and intercompany agreement amendments. A change to the intercompany agreement, a revision to the transfer pricing method, a change in the subsidiary’s functional profile from cost centre to limited-risk distributor, or the addition of a new transaction stream are each scope events that require fresh analysis. They should trigger a change order, not be absorbed into the existing retainer.

US tax obligations. Form 5471 (information return for US persons with interest in foreign corporations), GILTI analysis under Section 951A of the Internal Revenue Code, the US parent’s foreign tax credit computation for Indian withholding taxes: all of these sit with a US-qualified CPA and are out of scope for any India compliance retainer. The two advisors need to communicate, particularly on intercompany pricing and the withholding tax credit mechanics, but they operate under separate professional licences.

Payroll processing and salary structure advisory (unless specifically included). The India compliance retainer typically covers a review of payroll compliance status, not the operational running of the payroll. If the subsidiary uses a third-party payroll processor, the retainer advisor’s role is to audit the processor’s output, not replicate it.

The US-India coordination failure: why it happens and how to fix it

The single structural problem that causes more compliance failures in US-parent SaaS subsidiaries than any regulatory complexity is a calendar mismatch. The US parent’s finance team operates on a US fiscal calendar and a US decision-making rhythm. Indian compliance obligations operate on a 30-day trigger from events that happen on the India side, on Indian regulatory deadlines, and in response to Indian authority communications that reach the subsidiary’s registered email and physical address. These two clocks do not naturally synchronise.

The failure pattern is consistent: the US parent approves a fresh capital injection in a board meeting. The resolution is documented in the US and filed with the Delaware Secretary of State. No one notifies the India compliance advisor. The Indian subsidiary allots shares. Sixty days pass. The 30-day FC-GPR window closes. A FEMA compounding matter is created.

The fix is not finding a more attentive advisor. It is a structural protocol: a one-page trigger document that sits with both the US CFO or controller and the Indian subsidiary’s director, listing the four events that require an immediate notification to the India compliance team within five working days:

• Any share allotment or capital event involving the Indian subsidiary
• Any new intercompany payment type or amendment to the services agreement
• Any equity structure change (secondary sale, convertible note conversion, ESOP vesting and exercise events)
• Any director appointment, resignation, or change in director residency status

This protocol takes thirty minutes to establish and prevents compounding applications. Its absence is the reason most FEMA backlogs accumulate.

The retainer scope letter should specify who holds this protocol on each side, by name and role. Without a named owner, the protocol exists as a document but not as a practice.

The labour law stack: where foreign-owned SaaS subsidiaries miss

Labour and payroll compliance is the area of Indian law most underweighted in the compliance conversation between US finance teams and India advisors. It is not cross-border, which means the US parent’s legal counsel does not surface it. It is not tax, which means the TP advisor does not own it. It is managed by the payroll processor, who has no reason to flag structural problems unless they create a visible filing error.

The four Labour Codes, which became operationally effective alongside the Income Tax Act 2025 in April 2026, have materially changed the compliance surface for Indian subsidiaries. Three changes are directly relevant to US-parent SaaS subsidiaries:

The 50% wage rule under the Code on Wages 2019 requires that at least 50% of an employee’s CTC (Cost to Company) must be classified as “wages” (essentially basic salary and dearness allowance). For many SaaS subsidiaries that structured salary packages with high allowances to reduce PF contributions, this rule has increased the PF contribution base and therefore the employer’s statutory cost, without the employee receiving more cash. Subsidiaries that have not updated their salary structures since the Labour Codes came into force are carrying an understated PF liability that will surface at the first EPFO audit or due diligence.

Form 138 under the Income Tax Act 2025 replaces Form 24Q for TDS on salaries. Any quarterly TDS return filed using the old form number from April 2026 onwards fails portal validation. US-parent subsidiaries whose payroll processors have not updated their compliance software to the new Act’s terminology are filing incorrect TDS returns.

ESI applicability to multi-city teams. The ESIC’s geographic coverage expansion means that employees working in smaller cities, including tier-2 cities where many SaaS subsidiaries have engineering teams, may now be within ESI coverage even if the employer’s main office is in a metro where ESI was previously handled differently. Subsidiaries with distributed teams need a city-by-city ESI applicability check.

The retainer scope letter should specify who is responsible for verifying payroll processor compliance with the Labour Codes: whether that is the retainer advisor reviewing the processor’s output quarterly, or the client’s HR team maintaining a direct relationship with the processor outside the retainer.

Ind AS vs US GAAP: the reconciliation obligation

This is the obligation that is most consistently not briefed to the US parent’s finance team, and it is not technically a compliance issue at all, which is why it falls through the gap.

When a US-parent SaaS company incorporates an Indian subsidiary, the US parent reports in US GAAP. The Indian subsidiary is required by the Companies Act 2013 to prepare and file financial statements with the ROC in accordance with Indian Accounting Standards (Ind AS), which converge with IFRS but are not identical to US GAAP. For a subsidiary below the Ind AS threshold (consolidated net worth below ₹250 crore and annual turnover below ₹500 crore on a standalone basis), Indian GAAP (AS) standards apply rather than Ind AS.

The practical problem: the US parent’s finance team consolidates the Indian subsidiary’s financials into the parent’s US GAAP statements. The Indian subsidiary files Ind AS or Indian GAAP financial statements with the ROC. These are not the same documents, and they will not reconcile without adjustment entries. Revenue recognition differences (particularly around multi-year SaaS contracts, where Ind AS 115 and ASC 606 may produce different timing), lease capitalisation differences (Ind AS 116 vs ASC 842), and share-based payment accounting differences can produce materially different profit and net asset figures for the same entity across the two frameworks.

The ROC-filed financial statements are the ones that Indian tax authorities, FEMA compliance reviewers, and transfer pricing officers use as their baseline. If the Indian subsidiary’s TP study uses US GAAP-based financials while the ROC-filed statements follow Indian GAAP, the benchmarking and margin analysis in the TP study will reference figures that do not match the entity’s official financial record. This creates a discrepancy that a TPO reviewing the TP documentation alongside the ITR-6 and the ROC filing can use to open a documentation challenge.

The retainer scope letter should specify which financial statements are used as the basis for each compliance output (TP study, ITR-6, FEMA filings) and which framework those statements follow. Where the US parent’s consolidation requires a formal GAAP reconciliation, that reconciliation should be a named deliverable in the retainer.

When a fixed-fee retainer stops working

A fixed-fee retainer is the right model when the subsidiary’s compliance profile is stable and definable. Three situations signal that the model needs to be renegotiated:

A fundraise. The due diligence process creates compressed, multi-team review work that sits outside the retainer’s steady-state scope. The advisor who holds the retainer is usually the right person to support the diligence, but under a separate project fee, not by absorbing the work into the existing arrangement.

A transfer pricing audit or income tax assessment. Once a notice is issued, the work changes character: submissions must be prepared, authorities must be engaged, and appeal timelines must be managed. This work cannot be fixed-fee in advance because neither party knows at the time of retainer signing how complex the response will be.

A significant structural change to the subsidiary. Adding a second India entity, converting the subsidiary from a cost centre to a limited-risk distributor, transitioning from one TP method to another, or restructuring the ESOP pool each require fresh analysis. The correct approach is a change order against the existing retainer, with the new scope and fee agreed before the work starts. Advisors who absorb structural changes into the existing retainer without a change order are building an unsustainable engagement.

Common scoping mistakes and how to avoid them

Quoting before conducting the health check. The retainer fee quoted to a US parent’s CFO before anyone has looked at the subsidiary’s actual compliance position is a guess. If the health check reveals three years of missed Form 56 filings and two open FEMA compounding matters, the retainer scope and the backlog scope are both different from what was initially quoted. Starting with the health check protects both sides.

Letting the US parent’s counsel set the scope. US legal counsel does not know Indian compliance obligations in operational detail. A scope defined by the US parent’s counsel will typically be organised around concepts that make sense in the US (securities compliance, employment law, data protection) and miss the India-specific obligations (FEMA trigger protocol, Form 56, RCM self-invoice, Professional Tax by state) that create actual exposure. The India compliance advisor should prepare the scope, not accept it.

Not naming the US-side coordinator in the engagement letter. The retainer produces outputs that depend on information flowing from the US parent (capital decisions, new agreement types, director changes). If no one on the US side is named as the point of contact responsible for notifying the India team within five working days of a trigger event, the protocol exists on paper but fails in practice. The engagement letter should name the coordinator by role and ideally by name.

Scoping for the subsidiary’s current size rather than its likely size in twelve months. A subsidiary with twenty employees will cross the ESI threshold (ten employees) only if it has not already done so. But the more common miss is a subsidiary approaching the ₹250 crore net worth threshold that triggers the Ind AS transition: if that threshold will be crossed in the retainer year, the financial statements framework changes mid-year and the compliance cost increases. Price for where the subsidiary will be, not where it is.

Treating the labour and payroll track as someone else’s problem. The payroll processor does not know when the intercompany agreement was amended, or that the ESOP exercise by an Indian employee creates a cross-charge that has TP implications. The statutory audit CA does not know whether the payroll processor has updated its salary structure templates for the 50% wage rule. The retainer advisor who takes the whole-of-entity view is the only person in the structure who can see these intersections. Explicitly owning the payroll review function, even if the payroll processing is outsourced, is what distinguishes a genuine compliance partner from a filing service.

Treelife practitioner note

In the cross-border SaaS subsidiary engagements we run at Treelife, the health check almost always surfaces a finding that the client did not expect to pay for and did not know existed. The most consistent one is the TP documentation gap: three or four years of intercompany transactions above the ₹1 crore aggregate threshold, with no contemporaneous local file and no Form 56. The subsidiary’s CA had been filing the annual return and the tax audit on time. No one had asked whether Form 56 was being filed, because no one on the finance team knew it existed.

The second consistent finding is the intercompany agreement that stopped reflecting reality somewhere around month fourteen. The agreement was drafted well at incorporation. It covered development services at cost plus a 12% margin. By month fourteen, the subsidiary was also running a cloud infrastructure reimbursement and billing the parent for customer success services in a different geographic market. Both of these were happening under informal email arrangements. Neither appeared in the agreement. Both created undocumented intercompany flows that look, to a transfer pricing officer, indistinguishable from payments with no arm’s length basis.

The health check converts these invisible exposures into visible, quantified items that can be resolved in a controlled way before a notice arrives or a due diligence process begins. The compounding application for the late FC-GPR costs a fraction of what it costs to address during a live fundraise with a closing deadline. The backdated TP documentation, prepared before the assessment year closes, is more defensible than documentation assembled after a notice is issued.

On the retainer design itself: the clearest sign of a well-structured engagement is that the client’s US finance team receives a monthly or quarterly compliance status report, by obligation rather than by exception, showing what was filed, what is upcoming, and what decisions from the US side are needed in the next thirty days. If the retainer does not include a periodic status report, the US finance team has no visibility until something goes wrong. And things go wrong predictably when there is no visibility.

FAQs

Q: What is a compliance health check for an Indian subsidiary and what does it cost?
A: A compliance health check is a bounded diagnostic audit across five regulatory zones: MCA/ROC filings, income tax and transfer pricing, FEMA/RBI, GST, and labour/payroll. The output is a gap register classifying findings as backlog items (one-time remediation) or recurring obligations (ongoing retainer scope). At Treelife, health checks for US-parent SaaS subsidiaries are typically scoped as a fixed-fee project of ₹75,000 to ₹1.5 lakh depending on the number of financial years in scope and the number of transaction streams, with the output directly informing the retainer quote.

Q: Is the compliance health check mandatory before starting a retainer?
A: Not legally, but commercially it protects both sides. An advisor who quotes a retainer without a health check is pricing against unknown exposure and will either absorb the remediation cost or create a billing dispute when the backlog surfaces. From the client’s perspective, a health check that surfaces a ₹6 lakh compounding liability before the retainer starts is more valuable than discovering it during a due diligence process.

Q: What is the minimum annual retainer cost for a US-parent SaaS subsidiary in India?
A: For a lean subsidiary with one or two intercompany transaction streams, turnover below ₹10 crore, and a simple GST profile, the minimum realistic fee for a bundled retainer covering statutory audit coordination, income tax, TP local file and Form 56, FLA return, GST, and secretarial work is around ₹6 lakh to ₹8 lakh per annum. Any quote below ₹4 lakh for the full stack is excluding material components, most commonly the TP local file or the secretarial work.

Q: Can we use our US parent’s CPA for the India compliance retainer?
A: No. Indian statutory audit, transfer pricing certification (Form 56), and tax filing require a Chartered Accountant registered with the ICAI (Institute of Chartered Accountants of India). FEMA compliance requires advisors familiar with RBI practice. GST return filing requires India GST registration. US CPAs do not hold these qualifications. The two sets of advisors should coordinate on intercompany pricing and the foreign tax credit mechanics, but they operate under separate professional frameworks.

Q: How does a fixed-fee retainer handle transfer pricing if our intercompany flows change during the year?
A: A change in intercompany flows, whether a new transaction stream, a revised pricing formula, or a change in functional profile, is a scope event. The correct process is a change order: the new scope is defined, the additional fee is agreed, and the TP documentation is updated before the first invoice is raised under the new arrangement. Retainers that absorb scope changes without a change order produce either underpaid advisors or underserved clients.

Q: Does the retainer cover coordination with the US parent’s CPA on GILTI and Form 5471?
A: This should be explicitly addressed in the scope letter. Coordination with the US CPA on intercompany pricing data, Indian withholding tax certificates, and the Indian subsidiary’s financial statements is typically included (it takes time but is a defined deliverable). Preparing or reviewing the Form 5471 or the GILTI computation is a US tax obligation that sits entirely with the US CPA and is outside any India retainer.

Q: What triggers the Ind AS requirement for an Indian subsidiary of a US parent?
A: Under the Companies (Indian Accounting Standards) Rules 2015, Ind AS applies when a company meets any of the prescribed criteria in Phase I or Phase II rollout. For most US-parent SaaS subsidiaries, the relevant trigger is holding company status, where the Indian subsidiary is a subsidiary of an Ind AS-reporting entity, or the standalone net worth threshold of ₹250 crore. Before those thresholds are crossed, the subsidiary reports under Indian GAAP (Accounting Standards). The shift from Indian GAAP to Ind AS is a significant transition event that should be built into the retainer as a separately scoped workstream in the year it occurs.

Q: What is the consequence of not filing the FLA return in prior years?
A: Each missed FLA return year is a separate FEMA contravention under FEMA 1999. Remediation requires a compounding application to the RBI for each missed year. The compounding fee is determined on a case-by-case basis by the RBI; for first-time voluntary disclosures without other aggravating factors, the settled amount is typically modest. The risk is that a missed FLA return is discovered during a fundraise or acquisition due diligence, at which point the remediation must happen under a deadline, which increases both the cost and the probability of an adverse settlement. Proactive disclosure is always cheaper.

Q: What is the POEM risk for the US parent from the Indian subsidiary’s operations?
A: Place of Effective Management (POEM) is a risk for the US parent rather than the Indian subsidiary. If key management and commercial decisions for the US parent as a whole are made in India (whether by India-based directors or through India-based control of the parent’s board), the US parent could be treated as an Indian tax resident and taxed on its global income. For an operating US-parent SaaS company with genuine US-based management and board meetings held in the US, the POEM risk is typically low. It rises where the US parent is a thin holding entity with all substantive management in India. See Treelife’s dedicated guide on POEM in India for the full ABOI test and documentation requirements.

Q: What happens to the retainer if the Indian subsidiary gets a transfer pricing assessment notice?
A: A transfer pricing assessment notice moves the engagement outside the retainer’s scope. The response to a TPO notice, including preparing and submitting the local file if not already done, responding to information requests, attending hearings, and instructing counsel for any appellate proceedings, is separately scoped and quoted. The retainer advisor is usually the right person to manage this process because they hold the compliance history, but the engagement shifts to an hourly or project fee for the assessment period. This should be stated explicitly in the original scope letter so there is no ambiguity when a notice arrives.

Q: Should the payroll compliance work be in the retainer or handled separately?
A: This depends on whether the subsidiary uses a third-party payroll processor. Where it does, the typical retainer arrangement is a quarterly payroll compliance review: the retainer advisor reviews the processor’s filings, confirms PF and ESI deposits are current, checks the salary structure against the Labour Code wage definition, and flags any discrepancies. The actual payroll processing stays with the processor. Where there is no third-party processor and the subsidiary’s finance team runs payroll directly, the retainer scope should explicitly include payroll filings or refer them to a named specialist.

Regulatory references:

• Companies Act 2013, Sections 92, 137, 139, 149 (annual filing, audit, director residency)
• Income Tax Act 2025, Section 172 (accountant’s report, formerly Section 92E of the 1961 Act)
• Income Tax Act 2025, Section 171 (documentation obligation)
• Income Tax Rules 2026, Rule 84 (local file and master file)
• Income Tax Act 2025, Section 192 / Form 138 (TDS on salaries, replacing Form 24Q)
• Foreign Exchange Management Act 1999
• FEMA Notification No. 20(R), NDI Rules, Schedule I (FC-GPR obligation)
• RBI circular: Migration to CIMS portal for FEMA reporting, effective 30 June 2026
• RBI FLA return extension notification, July 2026 (extended to 31 July 2026 for FY 2025-26)