The growth of Software-as-a-Service (SaaS) and cloud-based platforms has changed how multinational groups develop, distribute and monetise software. Subscription-based revenue, centralised technology ownership and locally delivered customer support create transfer pricing considerations that may differ from those arising in traditional software distribution models.

For groups operating through multiple jurisdictions, the central question remains whether the pricing of intra-group digital supplies reflects the functions performed, assets employed and risks assumed by each entity.

Characterising the Local Entity’s Role

A local group entity may operate as a reseller, a commission agent or a service provider supporting implementation and customer relationships. Although these arrangements may involve similar customer-facing activities, their economic characteristics are different.

A reseller typically contracts with customers and purchases the right to distribute the software. A commission agent facilitates customer acquisition while the principal retains the customer contract. A service provider may undertake implementation, technical support or customer-success activities without independently commercialising the platform.

The appropriate transfer pricing method and expected return depend on the actual arrangement. Contracts should therefore be reviewed alongside operational conduct to establish which entity controls the customer relationship, bears commercial risks and performs the relevant functions.

Ownership and Contribution to Platform Intangibles

SaaS businesses frequently derive value from platform code, algorithms, proprietary technology, brands and customer relationships. The legal ownership of these assets is relevant, but the transfer pricing analysis must also consider which entities develop, enhance, maintain, protect and exploit them.

For example, a local entity may contribute through software integrations, localisation, product development or the accumulation of customer data. Where these activities create value for the wider group, the nature and significance of the contribution should be examined rather than automatically treating the entity as a routine distributor.

The remuneration should reflect the functions actually performed and the extent to which the local entity contributes to the development or exploitation of valuable intangibles.

Subscription Revenue and Profitability Analysis

Unlike a traditional product sale, subscription revenue is generally recognised over the period during which access or services are provided. At the same time, customer acquisition costs may be incurred upfront.

This timing difference can affect reported profitability, particularly for businesses expanding rapidly. A local entity may incur substantial marketing and onboarding costs before the related subscription revenue is fully recognised.

Benchmarking should therefore consider the revenue model, accounting policies and relevant financial periods of the tested party and comparable companies. Multi-year analysis may provide useful context where individual-year results are affected by growth or subscription timing.

Pricing Bundled Digital Offerings

Customer contracts often combine software access with technical support, training, implementation and professional services. These components may involve different functions and economic returns.

Where the activities are separately identifiable and materially different, allocating the consideration on a reasoned basis may provide a more reliable result than applying one blended mark-up to the entire arrangement.

The allocation methodology should be consistent with the contractual structure, services delivered and financial reporting. Differences between the transfer pricing treatment and revenue allocation in the accounts may create avoidable questions during an examination.

Coordination with Indirect Tax and Withholding Tax

The characterisation of a digital supply may also affect withholding tax, goods and services tax and treaty treatment. Software access, cloud subscriptions and technical services may require different tax analyses depending on the contractual rights and actual nature of the supply.

The descriptions used in intercompany agreements, transfer pricing documentation and tax filings should therefore be reviewed together. A consistent characterisation helps reduce the risk of conflicting positions across tax and accounting records.

Conclusion

SaaS and cloud-based business models require transfer pricing policies that account for subscription economics, platform intangibles and the distinct roles of local entities. Groups should document the actual functions performed, assess contributions to technology and customer value, and maintain consistency between their transfer pricing, accounting and tax positions.