MAP and DTAs in India: Resolving Double Taxation After an Adjustment

Where the Indian adjustment stands, and the counter-jurisdiction’s transaction is the other side of the same pricing, the taxpayer carries the price in two tax systems: the Indian adjustment increases the Indian income, and the counter-jurisdiction (where the related party sits) has not decreased its income correspondingly — the same economic value, taxed twice. The Mutual Agreement Procedure (MAP) is the mechanism that unwinds the double taxation: the competent authorities of the two jurisdictions agree, mutually, on the correct pricing, and the correlative adjustment follows in the counter-jurisdiction. This guide is the Indian side: the rules, the network, the application, the timelines, and what actually happens.

The framework

Element	The content
The MAP rules	Rules 90A, 90AA and 90AB of the Income-tax Rules — the application for the mutual agreement, the competent authority’s process, and the mutual agreement itself
The DTA network	India’s network of double tax avoidance agreements (90+ treaties) — the MAP chapter (the article on mutual agreement, inherited from the OECD model and updated through the MLI) is the treaty basis for the procedure
The MLI overlay	India’s participation in the Multilateral Convention updates the MAP provisions in the covered DTAs — the improved timelines (the notification where the case cannot be resolved within the period) and the binding nature of the agreement
The competent authority	The Indian competent authority (the CBDT’s designated authority) — the authority that receives the application, examines the case, and negotiates with the counter-authority

The MAP is a competent-authorities procedure: the taxpayer applies, the authorities negotiate, the taxpayer’s role is the application and the evidence — the negotiation is between the governments, on the treaty and the OECD standard.

The application: who, when, on what

Who. The taxpayer whose income was adjusted (the Indian entity, where the Indian adjustment is the double-taxation source) — or, in the reverse direction, the case where the counter-jurisdiction’s adjustment creates the double tax and the Indian correlative is the relief. The application is the taxpayer’s; the authority’s process runs on it.

When. The application is made where the assessment (incorporating the TP adjustment) is in place — the map in the audit defense guide: the TPO’s determination, the AO’s assessment, the appeals. The strategic question is the sequence: the MAP application runs in parallel with (or after) the domestic appeals — the taxpayer does not have to exhaust the appeals to apply for MAP, and the practical choice is the one that preserves both routes (the appeal holding the Indian position open, the MAP pursuing the correlative in the counter-jurisdiction).

On what. The application carries: the facts (the transaction, the pricing, the adjustment), the documentation (the TP file — the method, the pool, the range; the matrix that is the evidence), the analysis (why the adjustment is not arm’s length, per the OECD standard), and the correlative request (the adjustment in the counter-jurisdiction that unwinds the double tax). The application is, in substance, the TP defence written for the competent authority — the same record, the same arguments, the forum changed.

The process and the timelines

Stage	The content	The clock
The application	The taxpayer’s application to the Indian competent authority, with the full record	The filing — the date the clock starts
The examination	The competent authority examines the case — the adjustment, the documentation, the OECD-standard analysis	The authority’s process — the MLI’s improved provision: the notification to the taxpayer where the case cannot be resolved within the agreed period (the 90-day notification of the impasse, under the MLI-updated MAP article)
The negotiation	The competent authorities negotiate — the exchange of positions, the OECD standard as the common reference, the proposal and counter-proposal	The negotiation — the period runs, the impasse notification marks where it stalls
The mutual agreement	The agreement on the correct pricing — the Indian adjustment modified (or withdrawn) and the correlative adjustment directed in the counter-jurisdiction	The agreement — the binding instrument, implemented in both jurisdictions
The implementation	The Indian assessment modified per the agreement; the counter-jurisdiction’s correlative adjustment made (the income decrease, the refund or the credit)	The implementation — the taxpayer’s relief, in both systems

The timelines are the MAP’s practical constraint: the procedure is measured in years, not months, and the taxpayer’s cash position (the Indian tax paid on the adjustment, the interest running) is the cost of the wait. The strategic responses: the appeal route in parallel (the Indian position held open), the refund/interest claims on the correlative (where the counter-jurisdiction’s adjustment comes through), and the planning tool for the future years — the AAR (the advance ruling on the method) is the prevention that keeps the next year out of the MAP queue.

The correlative adjustment: the relief’s shape

The MAP’s output is the mutual agreement — the two authorities’ agreed position on the arm’s length price, and the adjustments that follow:

• The Indian side — the assessment modified: the adjustment reduced or withdrawn per the agreed price, the tax recomputed, the excess refunded (with the interest, where the agreement so provides).
• The counter-jurisdiction side — the correlative adjustment: the related party’s income decreased (or increased, in the reverse case) to match the agreed price — the counter-authority’s implementation, which is where the MAP cases stall (the counter-authority’s domestic law, the counter-taxpayer’s position, the counter-jurisdiction’s own examination).
• The symmetry — the agreement prices the transaction once; both jurisdictions apply the same price. The double taxation unwinds where both implementations land; the residual exposure is the one that lands only once, and the taxpayer’s record (the application, the documentation, the agreement) is the instrument for pressing the unimplemented side.

The practical outcomes, and the planning

The honest read of the Indian MAP practice:

• The cases that resolve — the clean double-taxation cases: the adjustment on a method/pool the counter-authority accepts as wrong, the documentation complete, the OECD-standard analysis sound. The agreement comes, the correlative follows, the double tax unwinds — slowly, and with the interest question on both sides.
• The cases that stall — the counter-jurisdiction’s non-implementation (the correlative not made, the counter-authority’s position divergent), the impasse (the notification, and the residual double tax), and the domestic appeal’s interaction (the Indian position changing on appeal while the MAP case runs). The stalling is the MAP’s known risk, and the taxpayer’s record is what it works with.
• The planning layer — the MAP is the remedy; the prevention is the position that does not need it: the documentation readiness that wins at the TPO stage, the AAR that fixes the method before the year, and the two-jurisdiction consistency in the group’s pricing (the investor’s home file and the Indian file, one economics) — the group that prices consistently in both directions is the group the MAP is not needed for.

The working position: the MAP application is prepared with the TP file — the same record, the same arguments, the competent-authority forum in mind from the first notice. The application that is the file, re-organized, is fast and strong; the application that is a new document, written for the forum, is the one that arrives late and thin.

See also

• TP audit defense — the domestic route
• India TP overview
• ETP — the two-jurisdiction consistency
• Group restructuring — where the double tax is born