Mexico: Clarification of the term “standardised software” for tax treaty purposes

International Tax Review is part of Legal Benchmarking Limited, 1-2 Paris Garden, London, SE1 8ND

Copyright © Legal Benchmarking Limited and its affiliated companies 2026

Accessibility | Terms of Use | Privacy Policy | Modern Slavery Statement

Mexico: Clarification of the term “standardised software” for tax treaty purposes

cuellar.jpg

lugo.jpg

David Cuellar


Sergio Lugo

On December 28 2012, the Mexican tax authorities published the MiscellaneousTax Regulations for fiscal year 2013, including a new rule intended to clarify the concept "standardised software" for purposes of interpreting article 12 (royalty payments) of the tax treaties signed by Mexico and also in light of Mexico's view that payments for the use of non-standardised software generally qualify as royalties. In general terms, Mexico follows the OECD Model Tax Convention to elaborate tax treaties with other jurisdictions and applies the commentaries on the OECD Model Tax Convention as a legal authority to interpret tax treaties. According to paragraph 28 of the commentaries on article 12, Mexico holds the position that payments related to software are classified as royalties when less than the full rights to the software are transferred; however, this rule should not be applicable in the following cases:

  • Payments for the use of copyrights on software for commercial exploitation if, and only if, the payment is made for the right to distribute standardised software copies and to the extent such copyrights do not include the right to customise or reproduce such software.

  • Payments for the use of copyrights for the sole use and benefit of the purchaser if, and only if, the software is completely standardised and not adapted/tailored to the purchaser.

In this context, new rule I.2.1.23 provides that standardised software includes the "commercial off the shelf (COTS)" software which is granted homogeneously and massively to any person in the market. In addition, rule I.2.1.23 provides that software which is specific or special should not qualify as standardised. For these purposes, specific or special software includes the following:

  • Software somehow adapted for the purchaser/user. When the software was standardised at the beginning but then adapted for the use of the purchaser/acquirer, such software should be considered as specific or special (and therefore not standardised) as from the moment the adaptation takes place.

  • Software designed, developed or produced for one user or a group of users, for the author or the person who designed, developed or produced the software.

In light of the recent clarification of the term "standardised software", multinational companies should carefully analyse each transaction on a case-by-case basis, including a comprehensive analysis of the corresponding agreements and the technical characteristics of the software to determine any potential tax consequences in Mexico.

David Cuellar (david.cuellar@mx.pwc.com) and Sergio Lugo (sergio.lugo@mx.pwc.com)
PwC

Tel: +52 55 5263 5816

Fax: +52 55 5263 6010

Website: www.pwc.com

more across site & shared bottom lb ros

More from across our site

The new managing director of R&D tax relief consultancy ForrestBrown tells ITR about his priorities for the business, where he’s focusing his time and what makes tax cool
PwC Australia’s response to its tax leaks scandal could give KPMG a useful case study, but so far there’s little sign of positive lessons learned
Tom Goldstein’s attempt to overturn his tax conviction was shot down; in other news, Deloitte promoted several tax partners in Italy
The tax advisory firm becomes the latest member of the Andersen Global network, which has more than 50,000 professionals worldwide
A revised Chapter VII signals a move away from mechanical TP approaches, stressing transaction understanding, functional analysis and context-driven documentation requirements
HMRC’s growing focus on evidencing tax decisions is shifting attention from technical accuracy to governance, requiring businesses to demonstrate how positions were reached and documented
Australia’s Department of Finance will also commission an independent review of KPMG’s governance, culture, ethics and integrity frameworks, it has revealed
In the second instalment of this two-part series, Jayne Stokes takes a practical approach to navigating the capital v revenue question for UK R&D claims for software development, and shares pointers for businesses
ITR's latest podcast considers how transformational the buyout could be in Ryan's quest for global advisory reach and analyses a recent boom in demand for private client advisory services
The event comes at an important moment for professionals dealing with practical realities related to this practice area
Gift this article