Expert verified
Your Form 3CEB was filed on time and approved by your statutory auditor, yet you receive a notice 18 months later questioning the margin earned by your Indian subsidiary on services provided to its parent company.
Your filing was neither late nor incomplete, then what triggered the scrutiny? In most cases, the scrutiny often relates to a few recurring areas in Indian transfer pricing assessments, including related-party transaction thresholds, the transfer pricing method selected, the comparables used for benchmarking, and the way intra-group costs are allocated across Indian locations.
This checklist covers seven key areas that a ₹100 crore-plus Indian subsidiary of a multinational should review before filing this year’s Form 3CEB. This is to ensure that the supporting documentation is strong enough to withstand scrutiny, not just at the filing stage, but also if the assessing officer examines the underlying transactions and their substance.
Who Needs to File Form 3CEB and Why MNC Subsidiaries Get Flagged for Scrutiny
Section 92E of the Income Tax Act requires every person who has entered into an international transaction or a specified domestic transaction (SDT) during the previous year to obtain a report from a chartered accountant in Form 3CEB. The form must be filed along with the income tax return.
The applicability is broad:
- International transactions: Any transaction with an associated enterprise, regardless of value. Even a single rupee of international related-party transaction triggers the filing requirement.
- Specified domestic transactions (SDTs): Domestic related-party transactions classified as SDTs require Form 3CEB when the aggregate value exceeds ₹20 crore in a financial year.
As a ₹100–500 crore MNC subsidiary, you are most certainly required to file Form 3CEB . The real issue you need to address is whether the documentation behind the filing will withstand scrutiny.
Why MNC subsidiaries face higher scrutiny
An MNC subsidiary usually has related-party transactions across several parts of its P&L, procurement, exports, royalties, management fees, financing, technology, and shared services. Each can become a transfer pricing question.
Risk is higher where there are:
- High-value international transactions relative to turnover
- Notable variations in operating margins compared to industry peers
- Gaps or inconsistencies between Form 3CEB, the transfer pricing study, and the financial statements
- Significant royalty or management/service payments
- Aggressive transfer pricing policies (e.g., thin profit margins, high royalty payments)
- Transactions with associated enterprises in low-tax or no-tax jurisdictions
The key CFO issue is that the Indian subsidiary carries the local tax risk, even when pricing policies are designed or controlled by the global parent. A global policy does not, by itself, establish compliance with Indian transfer pricing requirements.
The financial consequences can also be significant.
Failure to maintain required documentation or furnish information can attract penalties of 2% of the value of the relevant international transaction under Sections 271AA and 271G, while failure to furnish the accountant’s report can attract a ₹1 lakh penalty under Section 271BA. Where a transfer pricing adjustment results in under-reported or misreported income, penalties under Section 270A may apply in addition to the resulting tax liability.
Note: Form 3CEB is being replaced by Form 48 under the Income-tax Act, 2025. While the arm’s-length principles remain unchanged, Form 48 requires significantly more transaction-level detail, including benchmarking, comparable ranges, unique transaction IDs, and APA mapping. This means more supporting evidence will need to be captured upfront rather than left solely to the transfer pricing study.
Trigger Point 1: Related Party Transaction Value Thresholds Across Group Entities
The first control point for the CFO is ensuring whether all related-party transactions across the group have been identified, classified and aggregated correctly.
Know which threshold applies:
International transactions have no threshold. Every international transaction with an associated enterprise must be reported in Form 3CEB.If your Indian subsidiary imports raw materials from the parent company, pays royalties, receives technical services, or has any other cross-border related-party transaction, it must file Form 3CEB.
Specified domestic transactions, ₹20 crore aggregate threshold. Domestic related-party transactions classified as SDTs require Form 3CEB only when the aggregate value exceeds ₹20 crore in a financial year. Examples of SDTs include transactions between:
- Two units of the same entity (e.g., head office and branch)
- An entity and its specified domestic related party
- An entity and its associated enterprise where the transaction is not international
A separate ₹1 crore aggregate threshold applies to the requirement to maintain contemporaneous transfer pricing documentation under Rule 10D. For most MNC subsidiaries, routine imports, exports and intra-group services will cause this threshold to be crossed.
Risk areas:
The most common error is assuming that only “large” transactions need to be reported. For international transactions, size does not matter, every transaction counts.
The second common error is missing the aggregation requirement for SDTs. A series of small domestic related-party transactions may cross the ₹20 crore threshold when aggregated, triggering the Form 3CEB requirement even though no individual transaction appears significant.
Even if a transaction is below the threshold, it may still be scrutinised. The Transfer Pricing Officer (TPO) can ask for documentation for any transaction that appears in the return. If the documentation is incomplete or absent, the TPO can make an adjustment based on its own analysis.
What to check:
Before Form 3CEB is finalised, management should have a single, group-wide transaction map covering all international and relevant domestic related-party transactions. Each transaction should be classified, aggregated and reconciled to the general ledger, intercompany agreements and financial statements.
The objective is not simply to determine whether a threshold has been crossed. You must establish that the company knows what it has transacted with its group entities, how those transactions have been priced, and whether the documentation supports that position.
At PKC, we start with transaction mapping. We build the related-party universe first and then determine the reporting, documentation and transfer pricing requirements for each transaction.
Trigger Point 2: Choice of the Most Appropriate Method
Once transactions have been identified, the next question is how their arm’s length price (ALP) has been determined.
Section 92C provides six methods:
- Comparable Uncontrolled Price (CUP)
- Resale Price Method (RPM)
- Cost Plus Method (CPM)
- Profit Split Method (PSM)
- Transactional Net Margin Method (TNMM)
- Any other method prescribed by the CBDT under Rule 10AB.
The choice of method is not neutral. Each method produces different results. The TPO will challenge the method if it does not appear to be the “most appropriate” given the nature of the transaction, the availability of reliable data, and the degree of comparability.
Risk areas:
A common weakness is carrying forward the method used in previous years without reassessing whether it remains appropriate.
Another is applying the same method across different transaction types simply for convenience.
For example, TNMM is often appropriate for routine arrangements such as captive IT/ITES services, contract manufacturing or limited-risk distribution, where reliable net-margin comparables are available. By contrast, CUP may be more appropriate for certain royalty or financing transactions where reliable third-party pricing can be identified.
The choice is crucial because a change in method or even a change in the comparable set used under the same method can affect the arm’s length range and, consequently, the company’s tax exposure.
So, it’s not only about “Which method was used?” but “Why is this the most appropriate method?”
The transfer pricing file should clearly connect the method selected to the transaction’s functional, asset and risk profile and explain why alternative methods were less reliable. A conclusion that just states the method used, without demonstrating why it is preferable to the alternatives, can become an early point of challenge by TPO during an assessment.
When we do this for our clients, for each material transaction, we perform a method review that tests the selected method against the transaction profile, data availability and alternative methods. We aim to ensure that the method is commercially logical, technically supportable and capable of being defended before the TPO.
Trigger Point 3: Benchmarking and Comparable Company Selection
Once the method is chosen, the next step is benchmarking, selecting comparable companies or transactions to determine the arm’s length price.
For TNMM, this usually means comparing the tested party’s operating margin with that of independent companies performing broadly similar functions and assuming comparable risks.
Comparable selection is one of the most contested areas in Indian transfer pricing assessments.
Risk areas:
The most common error is using a narrow set of comparables that produce a favourable result but are not truly comparable. The TPO will reject comparables that are not functionally similar, that operate in different industries, or that have different sizes or risk profiles.
Another common error is failing to conduct a proper comparability analysis. The documentation must show that the comparables are truly comparable, not just that they operate in the same broad industry.
The analysis should consider the functions performed, assets employed and risks assumed, as well as contractual terms, business strategies and relevant market conditions.
For example, a captive software development centre with limited market and commercial risk should not automatically be benchmarked against full-fledged software product companies that own significant intellectual property and assume substantial market, marketing and inventory risks.
Also, a global benchmarking study cannot simply be transplanted into the Indian file. The Indian subsidiary’s functional profile, cost structure, risk allocation and local comparable universe need to be assessed independently.
This is especially important where the parent’s global tax team provides a standard benchmarking set. A range that is appropriate in another jurisdiction may not necessarily be defensible before the Indian TPO.
Before signing off, management should ask:
Are these companies genuinely comparable to our Indian entity, and can we clearly explain why each key comparable was included or excluded?
If the TPO rejects material comparables and substitutes its own set, the resulting arm’s length range and potentially the tax liability can change significantly.
PKC combines database-driven benchmarking with a transaction-specific functional analysis, documenting the rationale for both inclusion and exclusion of comparables. We ensure that the resulting range represents the true economics of the Indian business, rather than simply yielding an attractive figure.
Trigger Point 4: Intra-Group Services and Cost Allocation Across Multiple Locations
Intra-group services are a recurring transfer pricing risk for MNC subsidiaries. This happens where finance, HR, IT, legal, procurement or other functions are centralised at a regional or global level and their costs are allocated to India.
The main question here is, can the Indian entity demonstrate that the service was actually provided, and was charged on a reasonable and arm’s length basis?
Risk areas:
The most common error is accepting the parent company’s allocation methodology without questioning whether it is arm’s length. The parent company may allocate costs based on a global formula, revenue, headcount, or some other metric, that does not reflect the value received by the Indian subsidiary.
Another common error is failing to document the services actually provided. The TPO will ask: What services were provided? Who received them? What was the benefit to the Indian subsidiary? If the documentation is vague or absent, the TPO may disallow the deduction entirely.
For subsidiaries operating across multiple plants, branches, warehouses or offices, management should also be able to explain why costs were allocated to each location and whether the allocation key reflects actual usage or benefit.
For example, an IT support cost allocated to every location may require further justification where certain locations have limited IT requirements. Similarly, an allocation key that changes materially from year to year without a documented business reason can create questions about consistency and reliability.
For intra-group services, the documentation must demonstrate:
- The services were actually provided
- The services provided a benefit to the Indian subsidiary
- The allocation methodology is reasonable and arm’s length
- The charges are consistent with what an independent party would pay for comparable services
At PKC we review the intra-group service arrangements, assessing whether the services are actually provided, whether the allocation methodology is arm’s length, and whether the documentation is sufficient to withstand TPO scrutiny.
Trigger Point 5: Intangibles and Royalty Payments
Royalty payments for the use of a parent company’s brand, technology, know-how or other intellectual property are a high-risk area in transfer pricing.
Again, the real issue here is whether the royalty rate is arm’s length and whether the intangible actually generates value for the Indian subsidiary.
Risk areas:
The first risk is relying on a globally determined royalty rate without an India-specific benchmarking analysis. The rate may reflect group-wide commercial considerations but still need to be tested against Indian transfer pricing requirements.
The second is whether the underlying intangible actually creates value for the Indian business. Management should be able to demonstrate that the IP is being used and contributes to the business through factors such as technology, product differentiation, customer access or brand value.
Another issue arises where the Indian subsidiary makes substantial marketing, advertising or market-development investments. If the subsidiary is building significant local brand value while also paying a royalty to the parent, the TPO may examine whether the subsidiary is appropriately compensated for its contribution.
This is where DEMPE, development, enhancement, maintenance, protection and exploitation of the intangible becomes relevant. Legal ownership alone does not necessarily answer which group entity is contributing to the value of the intangible.
Before filing, the CFO and management should verify three things:
- Is the royalty rate benchmarked?
- Is the revenue base consistent with the agreement and actual invoicing?
- Can we demonstrate the value received and the actual use of the IP?
The licence agreement, payment terms, revenue base, benchmarking analysis and actual business practices should all tell the same story.
There is also a separate withholding-tax compliance dimension for payments to non-resident group entities, including the applicable rate and treaty documentation.
A significant transfer pricing adjustment can have implications beyond the additional tax. Where applicable, secondary adjustment provisions under Section 92CE can create a requirement to repatriate the excess amount to India or trigger an additional tax consequence if it remains outstanding.
PKC conducts benchmarking studies for royalty rates and other intangible-related transactions, assessing whether the rates are arm’s length and whether the documentation is sufficient to withstand TPO scrutiny.
Trigger Point 6: Documentation Timelines and Master File Requirements for Larger Groups
The Income Tax Act requires that transfer pricing documentation be maintained “contemporaneously” meaning it should be prepared by the due date for filing the accountant’s report in Form 3CEB, which is typically 31 October following the end of the financial year.
For an MNC subsidiary, the documentation framework can have three layers:
- Local File, entity-level documentation covering the business, transactions, functional analysis, transfer pricing policy and benchmarking.
- Master File (Form 3CEAA), group-level information covering the MNE group’s global operations, intangibles, financing and transfer pricing policies. The detailed Part B requirements are triggered based on prescribed group and Indian transaction thresholds.
- Country-by-Country Report (CbCR) applies to qualifying large multinational groups based on the prescribed consolidated revenue threshold, with separate Indian notification requirements where the report is filed by an overseas group entity.
The important point for a CFO is that these thresholds are group-level as well as India-specific. A growing Indian subsidiary may become subject to additional requirements because the group’s global revenue or the Indian entity’s transaction profile has changed.
Risk areas:
The most common error is treating the documentation as a year-end compliance exercise rather than a year round process. The documentation should be prepared as transactions occur, not reconstructed at year-end.
Another common error is failing to update the documentation for changes in the business: new transactions, new locations, new entities, changes in transfer pricing policies.
Management should establish a clear annual process covering threshold testing, transaction mapping, documentation updates, review and filing deadlines. Responsibility should be clear between the Indian finance team, tax advisers and the global tax function.
Trigger Point 7: Common Errors That Invite Transfer Pricing Scrutiny
Beyond the specific trigger points above, there are common errors that recur across transfer pricing assessments. These errors are process failures that invite scrutiny:
Error 1: Inconsistent treatment across entities
If the Indian subsidiary treats a transaction one way and the parent company treats it differently, the inconsistency will be flagged. The TPO will ask: Why is there a difference?
Error 2: Inadequate functional analysis
The functional analysis is the foundation of the transfer pricing documentation. If it is incomplete like missing key functions, assets, or risks, the TPO will question the entire benchmarking study.
Error 3: Margin at the lower end of the range without justification
If the tested party’s margin is at the lower end of the arm’s length range, the TPO will ask why. If there is no business justification such as a start-up phase, a market entry strategy, or extraordinary competition, the TPO may adjust the margin to the median or higher.
Error 4: Missing or incomplete documentation
The TPO can ask for documentation at any time. If the documentation is incomplete or missing, the TPO may make an adjustment based on its own analysis and the taxpayer will have limited ability to challenge it.
Error 5: Cost allocation formula changed year to year without a stated reason
This reads as results-driven rather than principle-driven the moment two years are compared by the TPO.
Error 6: Related-party definition applied inconsistently across Companies Act, GST, and income tax filings
A related party disclosed under one law and omitted under another is an easy inconsistency to spot and is likely to raise questions.
Now the question most CFOs ask here is “Our parent company handles transfer pricing globally. They provide the documentation we need. Why do we need to engage a local advisor for this?”
The parent company’s transfer pricing team focuses on the global picture, while the Indian TPO assesses the Indian entity specifically, its functions, assets, risks, transactions, and profitability.
Global documentation may not cover India-specific functional analysis, industry analysis, or benchmarking using Indian comparables.
A trusted and experienced local advisor like PKC Management Consulting complements the parent team with Indian regulatory expertise, TPO experience, and local benchmarking capabilities.
If your Form 3CEB is due again this year and any of these seven points hasn’t been reviewed since your last filing, or if your group is approaching the Master File or CbCR thresholds without anyone having formally confirmed it, schedule a call with PKC to review your transfer pricing documentation before it’s tested by someone else.
FAQs
Q1: Who is required to file Form 3CEB, and how does group structure affect the requirement?
Every person who has entered into an international transaction or a specified domestic transaction during the previous year is required to file Form 3CEB. For international transactions, there is no minimum threshold. For specified domestic transactions, the requirement applies when the aggregate value exceeds ₹20 crore in a financial year. The group structure is important because each entity must file its own Form 3CEB if it has reportable transactions.
Q2: What is the due date for transfer pricing documentation and Form 3CEB?
Form 3CEB must be filed by the due date for filing the income tax return. For entities required to file Form 3CEB, the ITR due date is 30 November following the end of the financial year. The transfer pricing documentation (Local File) must be maintained contemporaneously, meaning it should be prepared by the due date for filing Form 3CEB (typically 31 October following the end of the financial year). The Master File (Form 3CEAA) is due by 30 November.
Q3: What is the arm’s-length principle in transfer pricing between group entities?
The arm’s-length principle requires that transactions between associated enterprises be conducted at prices and on terms that would have been agreed upon between independent parties in comparable circumstances. The principle is enshrined in Section 92 of the Income Tax Act and is the foundation of India’s transfer pricing regime. The goal is to ensure that profits are not shifted between related parties to reduce tax.
Q4: What documents make up a complete transfer pricing file (local file and master file) for a larger group?
A complete transfer pricing file includes:
- Local File: Entity-level documentation covering the nature of the business, organisational structure, industry analysis, functional analysis (functions performed, assets employed, risks assumed), benchmarking study, and details of related-party transactions.
- Master File: Group-level documentation providing an overview of the MNE group’s global operations, transfer pricing policies, and allocation of income and economic activity. Filed in Form 3CEAA.
- Country-by-Country Report (CbCR): For groups with consolidated revenue exceeding ₹5,500 crore, filed within 12 months of the end of the parent entity’s accounting year.
Q5: What happens if transfer pricing documentation is inadequate during assessment?
If the documentation is inadequate, the TPO may:
- Reject the taxpayer’s transfer pricing analysis
- Substitute its own analysis and determine the arm’s length price
- Make a transfer pricing adjustment, increasing the taxpayer’s taxable income
- Impose interest on the additional tax demand
- Impose a penalty of ₹1 lakh under Section 271BA for failure to maintain documentation
The burden of proof is on the taxpayer to demonstrate that its transfer pricing is arm’s length.
Q6: How does PKC support ₹100 Cr+ MNC subsidiaries with transfer pricing compliance?
PKC provides end-to-end transfer pricing support for MNC subsidiaries and large Indian groups:
- Transaction mapping: Identifying all related-party transactions and assessing reporting and documentation requirements
- Benchmarking studies: Conducting rigorous comparability analysis using recognised databases
- Documentation preparation: Building and maintaining a complete transfer pricing file (Local File, Master File, CbCR where applicable)
- Form 3CEB filing: Preparing and filing the accountant’s report
- Assessment support: Defending transfer pricing positions during TPO assessments and litigation
- Year-round advisory: Quarterly reviews and real-time support for new transactions or changes in the business
PKC begins with a diagnostic, a 4–6 week review of the group’s related-party transactions, transfer pricing policies, documentation, and risk exposure and provides a roadmap for building a defensible transfer pricing compliance framework.
