Executive answer
In technology, commercial labels do not determine the transaction. “SaaS,” “platform fee,” “cloud,” “support” or “development” may include licenses, services, hosting, data, financing and different rights. Transfer pricing should delineate what each entity receives, who develops and controls the product, who bears failure and who turns technology into Mexican revenue.
A local affiliate may only support sales or may choose roadmaps, write code, train models, manage data, adapt products and develop market. The contractual label does not replace analysis. Return should relate to actual functions, assets, risks and rights.
An effective file follows a product from idea to user: design, development, infrastructure, security, launch, acquisition, support and monetization. It connects technical decisions and repositories to agreements and accounts without unnecessarily exposing code.
Digital product map
Identify the product, modules, platform, API, app, data, models, brand and services. Record legal owner, developers, product owners, funders, operators and sellers.
Map development, license, SaaS access, hosting, cloud, support, marketing, sales, commission, payments, data and corporate services. Separate bundles when components differ.
Organize discovery, build, beta, launch, scale, maintenance, migration and retirement. Functions and risk evolve.
Software development
Document who sets roadmap, architecture, priorities, budget, acceptance, releases and technical debt. Commits and headcount locate activity but do not prove control.
Distinguish coding to specification, design, product management, DevOps, QA, security and support. A routine center may earn cost plus when it does not control material risks; a team deciding product and bearing failure may need another analysis.
Retain tickets, approvals, charts, employment terms, cost and repository references. Do not reproduce secrets in the study.
Review contractor and open-source contributions because rights and obligations affect exploitation.
Data and models
Map source, consent, cleaning, storage, labeling, training, analysis and monetization. Identify who determines purpose and access, incurs cost and benefits.
Technical possession is not economic ownership. Contractual rights, privacy and control matter. An affiliate generating valuable local data may contribute more than processing it.
For AI models, document datasets, compute, prompts, fine-tuning, evaluation, guardrails and decisions. Separate third-party technology from proprietary development.
Cloud and infrastructure
Break down compute, storage, network, licenses, support, observability and security. Identify contracting account, users, regions and consumption.
Cost recharges need benefit, allocation keys and no duplication. Metered usage may outperform revenue or headcount. Retain consumption reports.
If the center negotiates discounts or assumes commitments, analyze procurement, capacity risk and credits. Do not automatically mark up pass-through spend or exclude it without functions analysis.
SaaS and license characterization
Read the rights: use, copy, modify, distribute, sublicense, access, hosting, updates and support. “SaaS” does not decide whether the transaction is a service, royalty or combination.
Separate standard software from copyright or know-how rights where facts require. Review treaties, withholding, VAT and deductibility independently from price.
Choose a base such as users, transactions, consumption, sales or fixed fee to match scope. Compare territory, exclusivity, SLA, data and support.
Zugzwang’s Tech TP Operating Model Review connects product, code, data, cloud, rights, market and accounts before setting charges and returns.
Product and local decisions
Interview product managers and technical leads about feature priorities, releases, markets, incidents and accepted risk. Compare conduct with agreements.
Local adaptation may be routine configuration or reusable development. Document scope, ownership and use elsewhere. If the group replicates a Mexican solution, test whether original remuneration covered it.
Incidents reveal control: who orders rollback, notifies, compensates customers and bears SLA. Preserve postmortems.
Commercialization and market development
Map pricing, discounts, sales, partners, onboarding, customer success, churn and brand. Identify who decides and funds acquisition.
A limited affiliate executing a playbook differs from one creating channels and relationships. Measure duration and intensity of local investment and rights over customers and data.
Reconcile commissions, rebates, free trials and credits to net sales and the intercompany formula.
Support and customer success
Separate help desk, technical support, implementation, training, success and custom development. Record tickets, levels, hours and deliverables.
Support may be included in a license or separately charged. Avoid duplication. Determine beneficiaries when a center serves several entities.
Custom work may create IP or be a service. Review customer and intercompany agreements.
Cybersecurity and liability
Identify who sets controls, monitors, responds, notifies and bears fines or compensation. Local spending does not establish risk.
Separate corporate, product and customer security. Document services, benefit tests and allocation keys.
A breach may result from design, configuration, vendor or operation. Use postmortems for economic analysis without exposing sensitive detail.
Methods and comparables
Cost plus may suit routine development or support with a refined base. A CUP may test comparable licenses or services. TNMM may test distribution or services. Profit split may apply to integrated unique contributions.
Evaluate comparables by product, IP, stage, recurring revenue, churn, R&D, data and risk. A consultancy is not a platform; a reseller is not a SaaS principal.
Do not use a revenue percentage as a universal rate. Explain rights and economics.
Cost base and allocations
Map payroll, contractors, stock compensation, cloud, licenses, capex, marketing and shared cost. Define what receives a markup and why.
Allocate by consumption, users, tickets, compute, hours, transactions or expected benefit. Document changes. Revenue may be unsuitable for infrastructure.
Reconcile pools to trial balance, invoices and payments. Avoid inconsistent capitalization.
Losses and scaling
A technology company may invest before monetization. Document business case, funding, decisions, period and recovery. A “startup” narrative does not justify indefinite losses.
Bridge budget to actual through users, price, churn, sales, cloud, headcount, marketing and incidents. Assign control.
If a routine Mexico entity bears scaling losses or global commitments, revisit the formula.
Operational TP and metrics
Monitor ARR or the relevant commercial metric, users, consumption, gross margin, cloud per unit, tickets, headcount, churn, charges and true-up. Reconcile SaaS metrics to accounting.
Establish a product-finance-tax-legal committee. Review launches, agreements, IP changes, incidents and adjustments.
Maintain data lineage and versions. Automation without consistent definitions creates faster mistakes.
Payments, marketplaces and agency
Map who contracts with users, collects, processes payments, bears fraud, refunds and handles chargebacks. A payment processor may provide a service, while an entity setting price and controlling customers may perform a broader commercial role.
For app stores and marketplaces, separate platform commission, withheld tax, advertising and fulfillment. Reconcile platform reports to revenue and the intercompany base. Determine whether a foreign entity acts as principal or agent from rights and conduct.
Promotions, credits and free periods need an approver and accounting treatment. Bookings do not replace statutory revenue or cash. Maintain a bridge from user to invoice, collection, fee and recognition.
Acquisitions and migrations
When the group acquires a startup or migrates a product, inventory code, customers, agreements, data, brand, people and liabilities. Determine what moves between entities and whether functions, assets, risks or profit potential require compensation.
Integration may move Mexican developers to a global roadmap without updating agreements. Trigger review of IP, cost pools, services and remuneration. Document sunset, consolidation and user-migration decisions.
If a local entity abandons a product it developed, analyze value and alternatives before treating the event as an administrative reorganization.
Finance, stock compensation and capitalization
Define treatment of stock-based compensation in cost bases and comparables consistently. Review who grants, records and receives the service. Do not exclude it solely because it creates no local cash outflow.
Reconcile capitalized development, amortization and expense between accounting and the formula. An accounting asset does not determine economic ownership, while current deduction does not eliminate a multiyear benefit.
For intercompany balances, collection terms and cloud commitments, analyze working capital and financing. A routine center should not fund the principal indefinitely without explanation.
International expansion and Mexican presence
For a Mexico launch, separate technical localization, marketing, sales, invoicing, support and compliance. Determine which entity contracts and whether personnel create tax nexus. Transfer pricing does not replace permanent-establishment, VAT or withholding analysis.
Document territory and remote use. A global license charged to Mexico needs local benefit and allocation; a platform accessed in Mexico may require characterization even without a local provider entity.
Align customer agreements, privacy notices, invoicing and the intercompany model. Three different narratives are difficult to defend.
Internal audit and response
Sample developers, tickets, users, cloud consumption, licenses and charges. Verify performance, beneficiary, rights and reconciliation. Test new modules and duplicate services.
Ask who controls roadmap, what IP Mexico created, which charge includes support, which data creates value, which commitment caused a loss and which true-up remains unexecuted. Record amounts and remediation.
For a request, use an index connecting the agreement, FAR, method, sample and figure. Protect secrets with controlled access; do not withhold essential evidence or provide full repositories unnecessarily.
Control calendar
Before budgeting, approve headcount, roadmap, cloud and pricing. Reconcile metrics and margin monthly. Review IP, cost pools, allocations and agreements quarterly. Before close, simulate charges, withholding, VAT and true-up.
After filing, measure forecast accuracy, incidents and manual adjustments. Turn findings into owned system and agreement improvements.
Service materiality
For central product, security, legal, finance or data services, retain requests, work, output, users and benefit. A cost allocation does not establish that Mexico received a service. Separate shareholder activity and duplicated local work.
Use keys connected to consumption or expected benefit and review them annually. A user count may fit software access; tickets may fit support; compute may fit infrastructure. Document judgment.
Connect the charge to electronic invoices, withholding, VAT, accounting and payment. Pricing and deductibility evidence should be tested together but not confused.
Agreements and change control
Agreements should define deliverables, rights, data, security, SLA, price, cost base, created IP, termination and true-up. Align conduct.
Trigger tax review for a new module, country, dataset, license, development center, migration or acquisition. A form should capture the decision, economics and date.
Do not backdate documents to manufacture control. Explain prior periods and adjust prospectively.
Defense file
Include the product map, FAR, agreements, roadmap, RACI, repository references, cloud, data, market, cost pools, methods, comparables and reconciliation.
Sample tickets, releases, charges and users. Prove benefit and performance. Protect secrets and personal data with an index and access controls.
Preserve annual versions. Platforms evolve; the file must show each period’s facts.
Illustrative example
Mexico was contracted as a development center, but its product managers prioritize a regional roadmap and create a module adopted globally. Historical cost plus should be reviewed: authority, risk, rights and use may show a larger contribution. Commit counts alone are insufficient.
If the parent set specifications, controlled acceptance and Mexico coded under supervision, cost plus may remain coherent. Conduct decides.
Conclusion
Technology requires translating architecture and operation into economic transactions. Software, data, cloud, market and support should not be compressed into a generic charge.
A clear model allocates return to real decisions and contributions, avoids duplication and keeps agreements, metrics and accounting reconciled as the product changes.
Request a Tech TP Operating Model Review to map the product, rights, teams, charges and profitability before the next launch or close.
Verified official sources
- Mexican Chamber of Deputies, current Income Tax Law, Articles 76, 179 and 180.
- OECD, Transfer Pricing Guidelines 2022, Chapters I, VI and VII.
- OECD, Transfer Pricing Country Profile: Mexico.
Verification closed on August 2, 2026. Confirm rights, treaties, privacy, agreements and product facts.