Nobody wants to talk about this. It is not exciting. It does not show up in investor decks. It does not generate press releases. It is the part of international expansion that produces PowerPoint slides titled "Legal/Compliance Considerations" that get two slides in a strategy review and are assumed to be manageable.
The companies that have discovered otherwise will tell you: compliance is load-bearing infrastructure. Get it wrong and it can stop deals, create legal liability, generate regulatory penalties, and — in the worst cases — force you to stop operating in markets you've already entered. This is not legal advice; use local counsel and tax advisors before making market-specific commitments. The operating point is simpler: compliance has to be designed before you commit to a market.
Tax Treatment of Software
Software is taxed differently in different countries, and the differences matter more than most companies realize.
VAT/GST. Most countries outside the US have value-added tax or goods-and-services tax rules that can apply to software. Depending on customer type, thresholds, local rules, and registration status, you may need to register, charge the correct rate, and remit regularly. The penalties for non-compliance can be significant, and they can apply retroactively.
Withholding tax. Some countries withhold a percentage of payments to foreign vendors. If you're receiving software license revenue from a customer in India, Brazil, or France, you may be subject to withholding tax on those payments unless a tax treaty reduces the rate. If you haven't registered for treaty benefits, the withholding is at the full statutory rate — and the customer may not even know to tell you.
Permanent establishment risk. This is the one that scares finance teams. If you have people operating in a country — even temporarily, even contractors — you may inadvertently create a permanent establishment, which means that country's tax authority can tax your global profits attributed to that PE. This requires legal advice by country.
Software-specific tax treatment. Some countries tax software as a service differently from software as a license. Some have specific digital services taxes. The treatment affects your pricing, your margin, and your compliance obligations. It needs a local tax advisor.
The Sequencing Question
There is a real tension between "build compliant infrastructure before you enter" and "we need to prove demand before we invest in infrastructure." Every operator faces this.
The resolution: separate proof-of-concept from commercial scale, but do not confuse a pilot with a compliance holiday. A pilot can narrow scope: synthetic data instead of production data, limited users, restricted integrations, explicit contractual limits, and defined data handling. It cannot ignore obligations that actually apply. What you cannot do is sign enterprise contracts, store production customer data, and operate at scale while hoping the infrastructure is close enough.
