Editor's Note:Winston Post is the sales and use tax lead at Ryan, a tax software company headquartered in Dallas, Texas, focusing on transaction tax issues impacting the technology industry. Ryan is the largest professional firm globally dedicated to corporate tax.

Recent high-profile tax disputes—including Apple's lawsuit against the Florida Department of Revenue over a $26 million tax bill—highlight the growing pressure on CFOs to accurately determine the tax sourcing of digital transactions. As businesses increasingly rely on infrastructure-as-a-service (IaaS) and cloud-based solutions, traditional tax compliance frameworks are struggling to keep pace with modern digital operations.

The stakes are significant. Remote work has driven corporate cloud spending to new highs, and as states compete for tax revenue, CFOs face mounting pressure to correctly fulfill tax obligations across multiple jurisdictions while managing increasingly complex digital service networks.

Digital Services: An Increasingly Complex Tax Puzzle

Consider this scenario: a company headquartered in California uses servers located in Washington State to sell digital subscription services to customers in Florida, whose end users are spread across the country. Where should tax be collected? The answer is not simple, and mistakes can be costly.

States adopt different sourcing methods, which can significantly impact tax burdens:

  • For income tax purposes, most states now use market-based sourcing, attributing revenue to where the customer receives the service. However, a growing number of states are implementing "customer's customer" sourcing, pushing the point of taxation to the end user's location—even if that location differs from the actual purchaser.
  • In the sales tax arena, destination-based sourcing dominates—meaning sourcing is determined by where the buyer receives the product—but complexity arises in determining the true destination of cloud-delivered services: is it the purchaser's headquarters, the server location, or where end users access and consume the service?

Multi-Point Use (MPU) Rules

States increasingly recognize that enterprise software purchased at a company's headquarters may be accessed across multiple jurisdictions. To address this, many states allow a multi-point use (MPU) exemption, permitting businesses to allocate tax based on actual usage patterns or apportionment ratios rather than the purchase location.

While this sounds beneficial, MPU introduces new compliance burdens. Massachusetts has proposed expanding documentation requirements for businesses claiming MPU benefits, including providing detailed evidence of in-state and out-of-state operations. Texas and Washington have updated their guidance, generally favoring taxpayers, but also setting new traps for bundled service transactions.

Federal Involvement Adds Complexity

The Internal Revenue Service (IRS) issued proposed rules earlier this year on sourcing income from cloud transactions, adopting a services-based approach that considers the location of resources and personnel responsible for service development and delivery. The proposal analyzes three factors: intangible assets, personnel, and tangible property contributions.

Industry groups have raised objections, particularly against including the intellectual property factor in the calculation. For CFOs, this means federal and state sourcing requirements may diverge, potentially necessitating dual compliance frameworks.

Practical Implications for Financial Leaders

These sourcing challenges present four immediate concerns for CFOs:

  1. Increased audit risk.States are eager to increase revenue, and digital service sourcing has become a key audit target. If sourcing methods are challenged, companies may face unexpected assessments years later.
  2. New system requirements.The fragmented rule system requires accurately tracking user locations, usage patterns, and service delivery points—most financial and tax management systems were not designed for this.
  3. Increased cost allocation work for FP&A teams.Understanding true geographic usage patterns is critical not only for tax compliance but also for accurate cost allocation and profitability analysis.
  4. Compliance documentation management.Finance leaders must work with technology and tax vendors to apply appropriate exemption certificate documentation.

A Sports Betting Model?

The trend is clear: sourcing requirements will become more granular and stringent. Sports betting companies already use advanced geolocation technology to meet regulatory requirements—similar precision may soon be expected in the tax arena.

State interest in taxing digital services is also growing, with multiple proposed taxes on data collection, digital advertising, and online platforms. As international jurisdictions implement their own digital services taxes, multinational companies face an increasingly complex compliance environment.

Navigating the Evolving Revenue and Tax Landscape

CFOs should take proactive steps to address these challenges:

  • First,Conduct a comprehensive review of current digital service arrangements to understand geographic footprint and potential sourcing risks, including mapping where services are billed, accessed, and consumed.
  • Second,Implement systems capable of tracking usage patterns across jurisdictions. This may require coordination between IT infrastructure, tax, and finance teams to ensure data collection and reporting capabilities are sufficient.
  • Third,Set clear location usage data requirements for vendors. Many IaaS providers can record relevant data but may not generate it automatically.

CFOs who proactively address how tax systems align with increasingly digital and cloud revenue sourcing will be better positioned to manage compliance risk and cost optimization, gaining an advantage in an increasingly digital world.