Transfer pricing for tech startups: documentation that survives an audit

Most Indian tech startups end up with a multi-jurisdictional structure within eighteen months of their Series A. A Delaware C-Corp for the US customer contracts. A Singapore Pte Ltd holding the IP. A UK subsidiary for the European go-to-market team. The Indian entity becomes the development centre — engineering, product, sometimes part of sales.

The moment the first inter-company invoice goes out, transfer pricing applies. Section 92 of the Income-tax Act read with Rule 10A onwards. We have walked through enough TPO assessments to know which invoices the Transfer Pricing Officer will pull, which documents they will ask for, and where the file usually breaks.

The four transactions that get pulled

In our experience defending Indian tech-services subsidiaries of founder-owned global groups, four inter-company transactions are mis-priced more often than the rest. We walk through each.

Management services charge

The pattern: the US parent invoices the Indian subsidiary for a management services charge, calculated as a percentage of Indian-entity revenue. The justification is that the parent provides board oversight, US legal services, finance support, HR policy and senior management time.

The problem: the TPO will ask for the benefit test. What specifically did the Indian subsidiary receive in return for the charge? If the answer is 'general oversight', the charge gets disallowed wholly under Section 37 read with the OECD-style stewardship principle.

Documentation that holds: a detailed services agreement listing specific deliverables (board meeting minutes, audit support, group-level treasury services, IT systems access). Time-tracking by the US parent showing hours spent on Indian-subsidiary work. Cost build-up showing direct costs and an arm's-length mark-up — typically 5–10% on a cost-plus basis for low-value-adding intra-group services per OECD guidance.

IP licensing royalty

The pattern: the Singapore holdco owns the IP, licenses it to the Indian entity for sub-distribution to Indian customers, and charges a royalty of 6–10% of Indian revenue.

The problem: who actually developed the IP? If the Indian engineering team built 70% of the codebase, the IP economic ownership sits in India regardless of the legal ownership in Singapore. The TPO will apply DEMPE — Development, Enhancement, Maintenance, Protection, Exploitation — and conclude that the Indian entity is the economic owner. The royalty paid to Singapore gets re-characterised and disallowed.

Documentation that holds: a DEMPE matrix showing exactly which functions sit in which jurisdiction, headcount and senior personnel by location, R&D spend by entity, decision-making for product roadmap by entity. If the IP genuinely sits in Singapore, prove it with senior engineers, product managers and budget authority in Singapore. If it does not, restructure before the assessment rather than after.

Software development cost-plus

The pattern: the Indian entity provides software development services to the US parent under a cost-plus mark-up arrangement. Cost-plus 15% is the most common rate seen in the market.

The problem: 15% is the floor. The TPO benchmark database typically returns inter-quartile ranges of 17–22% for comparable Indian software development services companies (Persistent, Mindtree, Tata Elxsi historical comparables). If the entity has been pricing at cost-plus 15%, the TPO will adjust upward to the median.

Documentation that holds: a properly run Comparable Uncontrolled Price or Transactional Net Margin Method analysis with at least 8–10 comparables, three-year weighted average margins, working capital adjustments, capacity utilisation adjustments. Mark-up set at or near the median, not the lower quartile. Cost base properly built — direct costs, indirect costs, exclusion of pass-through items like recharged software licenses.

Marketing services charge

The pattern: the Indian subsidiary's sales team helps the US parent close Indian customers, but the contract sits with the US parent and the customer pays the US parent. The Indian entity receives a commission or a marketing fee — sometimes 5%, sometimes 10%.

The problem: if the Indian sales team is doing lead generation, demos, negotiation and contract signature, they are not running marketing — they are running sales. The function is commission agent at best, or fully-fledged distributor at worst. The arm's-length compensation is materially higher than a marketing fee.

Documentation that holds: a FAR analysis — Functions, Assets, Risks — that honestly characterises what the Indian team does. If they sign contracts on behalf of the US parent, the dependent agent PE risk also opens up.

The three-tier documentation framework

Section 92D read with Rule 10D requires three layers of documentation for groups above defined thresholds.

Local File. Mandatory if related-party transactions exceed ₹1 crore in the financial year. Contains entity-level information, controlled transactions, functional and risk profile, comparability analysis, conclusion on arm's-length pricing. Filed with the return; produced on TPO demand.

Master File. Form 3CEAA, mandatory if the consolidated group revenue exceeds ₹500 crore and the Indian entity has related-party transactions above ₹50 crore. Contains group organisational structure, business description, intangibles, intercompany financial activities, financial and tax positions.

Country-by-Country Report. Form 3CEAD, mandatory for groups with consolidated revenue above €750 million (approximately ₹6,800 crore at current rates). Most founder-owned groups do not hit this threshold, but the ones that do — Razorpay, Zepto, Postman at scale — must file.

What we see go wrong

Three patterns recur in our IBC and tax representations.

First, the documentation is prepared retrospectively. The Form 3CEB filed by the chartered accountant is treated as the documentation. It is not — it is a disclosure of related-party transactions. The actual transfer pricing study is a separate analytical document. We have seen TPOs ask for the study, receive a one-page summary, and proceed to adjust the price unilaterally.

Second, the inter-company agreements are inconsistent with the transfer pricing study. The agreement says cost-plus 10%; the study uses cost-plus 15%; the actual invoice runs cost-plus 12%. Three different numbers in three different files. Pick one and run it consistently.

Third, the comparables become stale. The TP study from FY 2021-22 is reused in FY 2024-25 with the same comparables. The TPO will run their own search using current data and find variance. The study should be refreshed every two financial years at minimum.

Transfer pricing is not a documentation exercise. It is a pricing decision that must be defensible on the merits before the documentation can be useful. Get the price right first; document second.

What we do on engagement

We do not run the FAR analysis in a conference room and call it done. We sit with the engineering manager, the finance head and the founder. We map the actual functions performed. We test where the senior decisions are made. We pull the headcount file. We look at the email traffic on a product roadmap decision and ask which entity actually drove it.

If the structure cannot survive a DEMPE challenge, we recommend restructuring before the audit. The cost of moving senior IP-development personnel to the jurisdiction of legal ownership is meaningfully lower than the cost of a primary adjustment, a corresponding adjustment failure, double taxation and a Mutual Agreement Procedure at the competent authority.

What an APA can do

For groups where transfer pricing exposure is significant and recurring, the Advance Pricing Agreement under Section 92CC is worth considering. The APA fixes the arm's-length price (or methodology) for the covered international transactions for up to five future years, with an optional roll-back for four prior years.

Three flavours: unilateral (between the taxpayer and CBDT), bilateral (involving the foreign tax authority) and multilateral (more than two jurisdictions). For inter-company IP licensing and management services charges, the bilateral APA is the gold standard — both jurisdictions commit to the same arm's-length determination, eliminating double taxation risk.

Application fee under Rule 10G: ₹10 lakh for transactions up to ₹100 crore, ₹15 lakh for transactions up to ₹200 crore, ₹20 lakh for higher amounts. Timeline from application to signed APA: 24-36 months currently, though the CBDT has been accelerating throughput in recent cycles.

We have seen APAs lock in cost-plus 17% for software development services, royalty rates of 4-6% on IP licensing, and management services charges with defined cost-pool methodologies. Once signed, the certainty is worth materially more than the application cost.

The MAP route when assessment fails

Where a transfer pricing adjustment in India produces double taxation — the foreign entity is taxed on income that India has also taxed — the Mutual Agreement Procedure under the relevant DTAA is the recovery mechanism. Article 25 of most India DTAAs provides for MAP.

Filing window: typically within three years of the first notification of the action that caused taxation (the assessment order). MAP runs at the competent authority level — Joint Secretary (Foreign Tax Division) in India, the equivalent in the partner jurisdiction. Resolution timelines: 24-48 months. Outcome: bilateral agreement on the correct arm's-length price, with corresponding adjustments in both jurisdictions.

MAP is not a remedy of first instance. It is what we use when the assessment-side defence has failed and the corresponding adjustment from the foreign jurisdiction is not forthcoming. The cost of MAP — professional fees, internal time over 3-4 years — is justifiable only where the double-tax exposure is meaningful (typically ₹5 crore upwards).

The founder running a global tech group out of India faces transfer pricing scrutiny as a default outcome, not an edge case. Build the file before the notice arrives.