The UN Just Put AI on the Transfer Pricing Table

Start with the problem most transfer pricing practitioners are tracking the wrong forum for. When people think about how AI-delivered cross-border services will be taxed, the reflex is to look at the OECD - Pillar One, Amount B, the endless refinements to the arm's-length principle for baseline distribution and marketing functions. That's not wrong, but it's incomplete. There is a second, quieter negotiation running in parallel at the United Nations that could end up mattering just as much, and it is the one actually putting AI's name on paper right now.

Here's what changed. The UN Framework Convention on International Tax Cooperation has been negotiating, since early 2025, a framework treaty plus two 'early protocols' - one on dispute resolution, and one specifically on taxing cross-border services. The Co-Leads published a draft text of that services protocol on 20 July 2026, and during the Fifth Session of negotiations, held at UN Headquarters from 3 to 13 August 2026, multiple member states pushed to have artificial intelligence explicitly captured within its scope. That same session saw other states raise concerns about overlapping nexus claims for service fees, and a separate bloc pushing for optionality in how the protocol's provisions get applied. In other words: the machinery for deciding which country gets to tax AI-delivered services is being built right now, in a forum most Indian TP practitioners aren't reading transcripts of.

Why this matters more than it looks: India occupies an unusually exposed - and unusually powerful - position in this specific fight. On one hand, India has historically been among the loudest voices for expanding source-country taxing rights over digital and cross-border service income; the UN process exists substantially because countries like India argued the OECD's two-pillar solution didn't go far enough for market/source jurisdictions. On the other hand, India is also the world's largest base for AI-enabled global capability centres and IT/ITeS delivery - the exact category of cross-border service flow this protocol is trying to pin down. If the AI carve-out in the services protocol ends up defining nexus or taxing rights in a way that diverges from how OECD Pillar One and Amount B treat the same AI-delivered functions, Indian-headquartered groups and Indian subsidiaries of multinationals could find themselves benchmarking the same intercompany service flow against two different rulebooks depending on which counterparty jurisdiction is involved. That is not a hypothetical compliance headache; it is a structural one, because transfer pricing documentation is built around a single delineated transaction and a single most-appropriate-method choice, not a dual-track nexus test.

There is also a functional-analysis problem lurking underneath the treaty politics. Cross-border services protocols, going back to earlier UN work like Article 12B on automated digital services, tend to draw bright lines based on where a service is 'delivered' or 'consumed.' AI complicates that in the same way it complicates DEMPE analysis for intangibles: an AI system trained in one jurisdiction, fine-tuned or RAG-augmented with client data in a second, and delivering inference-based output to end customers in a third doesn't map cleanly onto any single-jurisdiction nexus concept the drafters are likely working from. If negotiators write a definition of 'AI services' into the protocol without engaging with how multi-jurisdictional AI pipelines actually function, they risk creating a nexus rule that transfer pricing professionals will spend the next decade trying to reconcile with functional reality - much the way 'significant people functions' language under the OECD's authorized approach took years of practice to operationalize.

The open question, and the one worth writing toward rather than around: does India's negotiating position on this protocol actually reflect an analysis of how Indian GCCs and IT exporters would be affected if AI services get a distinct, UN-defined nexus test that differs from OECD treatment - or is India's source-country advocacy here running on inertia from an earlier era of BPO and call-centre economics, before AI-native delivery models existed? That's not a rhetorical question so much as a genuine gap in the public record; the UN's own tracking shows the draft protocol text was only published in July 2026 and is still being contested clause by clause. A practitioner with both technical AI fluency and TP grounding is unusually well positioned to make that case publicly before the text hardens - which may be the real opportunity here, separate from whatever the final protocol says.