Transfers & services with IP
Example 24 — Services that carry embedded IP
Annex I · Example 24 · ¶86–88
OECD Guidelines 2022At a glance
Zhu lends staff to Company S for a similar Bank-B engagement. Those staff bring across Zhu's proprietary code from an earlier Bank-A engagement, and Company S embeds it in the deliverable. Is this a services transaction, an IP transfer, or both?
The parties
Zhu
Owner of proprietary ATM software code · supplies peopleservices · IP rights
Company S
Delivers ATM software to Bank B · uses Zhu staff and codeWhat happens
- Zhu develops and retains proprietary ATM software code during a Bank A engagement.
- Company S enters a separate Bank B engagement of similar character.
- Zhu agrees to support by providing staff who worked on Bank A; those staff have access to Bank A designs, know-how and code.
- Portions of Zhu's proprietary code are embedded in the software delivered by Company S to Bank B.
- The embedded portions are extensive enough to support a copyright-infringement claim against unauthorised use.
Analysis
Company S gets two things: Zhu employees' time and skill, plus rights in Zhu's proprietary code that ends up embedded in the deliverable.
What does Company S owe Zhu — a service fee, a royalty, or both?
OECD analysis · Pay for both services and IP
A transfer-pricing analysis should recognise that Company S received two benefits requiring compensation: services from the Zhu employees, and rights in Zhu's proprietary software used as the foundation for the Bank B system. The compensation paid by Company S should include both.
Key takeaway
When a service transaction carries embedded IP across an entity line, that IP is itself a transferred right. Price both legs — the service and the right.
Related: Chapter VI Section A (definition of intangibles) · Example 25 (services that don't transfer IP)