UAE Structuring for SaaS Founders: IP, Tax, and the 9% Corporate Tax Reality

SaaS is the highest-quality founder segment moving to the UAE — recurring revenue, high margins, customers in stronger currencies, and IP that travels with the founder. It is also the segment where generic UAE structuring advice fails most badly. The standard "Free Zone company, RAK ICC holding, Mashreq bank account" template was designed for trading and consulting businesses. Applied to a SaaS business without modification, it leaves money on the table at best and creates audit risk at worst.

This post is the playbook we walk SaaS founders through. It covers structure, IP location, transfer pricing, the corporate tax position on subscription revenue, payment processor routing, US sales-tax exposure, and what good substance looks like for a SaaS business specifically.

Why SaaS is different

Five features distinguish SaaS from typical structuring use cases:

• Revenue is recurring and predictable. Cash flow modelling is more reliable, which changes how aggressive you can be on cost discipline and tax planning.
• IP is concentrated and central. The codebase, the data layer, the brand, and the customer relationships are the entire business. Where the IP lives shapes everything else.
• Customers are global, but heavily US-skewed. Most B2B SaaS revenue comes from US and European customers. Few customers are UAE-resident, which has huge implications for VAT and qualifying-income status.
• The team is distributed. Engineering often sits in India, Eastern Europe, or LATAM. Sales is wherever the customers are. The founder may be the only UAE-resident decision-maker.
• The exit is real. Most B2B SaaS companies that reach USD 10m ARR are realistic acquisition targets. Build the structure for diligence-readiness from day one.

The recommended structure

For a venture-backable or independently-scaling SaaS business led by a UAE-resident founder, the architecture we recommend more than any other is:

• Apex: RAK ICC offshore holding company. Owned by the founder personally (and optionally by a foundation for long-term wealth planning).
• IP holding entity: Inside the apex or as a separate RAK ICC entity. Holds the codebase, trademarks, domains. Licenses them to the operating entity for a market-rate royalty.
• Operating entity: DMCC Free Zone Company (or IFZA for lower cost; DIFC if regulated). Contracts with customers. Employs UAE-based staff. Holds the Stripe and other payment-processor relationships.
• Foreign affiliates as needed: A US Delaware LLC if you have significant US enterprise sales. A UK Ltd if you need a UK presence for procurement reasons. These sit below the apex.

The principle: the IP owns the value; the operating company runs the business; the apex owns both and is what an acquirer ultimately buys.

Where the IP should live

Two competing pulls:

The case for keeping IP in the operating company: it is the simplest structure. No intercompany license. No transfer pricing exposure. No restructuring required to move IP if you outgrow the structure.

The case for separating IP into the apex: tax flexibility (the apex can charge a royalty back to the operating company, reducing operating-company profit). Exit flexibility (an acquirer can buy the operating business while you retain the IP and license it, or buy both). Asset protection (operating-company liabilities don't reach the IP).

For SaaS businesses with USD 1m+ ARR and a clear growth trajectory, the IP-separated structure is usually worth the setup cost (USD 2–4k extra) and ongoing complexity. Below that threshold, single-entity is often simpler.

If you choose the separated structure, the intercompany license needs proper documentation: a written license agreement at a market-rate royalty, with transfer-pricing analysis supporting the rate. UAE corporate tax law follows OECD transfer-pricing principles closely. A royalty of "whatever leaves the right amount of profit" will not survive review.

The 9% corporate tax question

UAE corporate tax applies to your operating entity at 9% above the AED 375k threshold — unless the entity qualifies as a Qualifying Free Zone Person (QFZP) and earns qualifying income, in which case the rate is 0%.

For SaaS specifically, the QFZP analysis turns on two questions: (a) is the underlying activity a qualifying activity, and (b) are the customers qualifying counterparties?

Software licensing to non-UAE customers is generally treated as qualifying activity for QFZP purposes. Sales to non-UAE customers are sales to non-UAE persons, which are qualifying counterparties. So a typical B2B SaaS business selling primarily to US, European, and Asian customers, from a Free Zone entity, is usually well-positioned to qualify for 0%.

What can break QFZP status: (i) too much UAE-mainland customer revenue (above the de minimis threshold of AED 5m or 5% of revenue), (ii) failing economic substance tests, (iii) classifying the activity wrongly. Sloppy thinking here is expensive — losing QFZP means 9% on all income, not just the non-qualifying portion.

Transfer pricing on the royalty

If you separate IP into a holding entity and license it back, the license fee is a related-party transaction governed by transfer-pricing rules. Get this right:

• Document the royalty rate. Use industry benchmarks (typically 5–15% of net revenue for SaaS IP licenses, varying by sector and product maturity).
• Justify in writing. A short transfer-pricing memorandum produced once and refreshed annually is enough for most sub-USD 10m businesses. Larger groups need formal TP documentation.
• Apply consistently. Don't vary the royalty rate based on what's tax-convenient — that's exactly what authorities look for.
• Pay the royalty in cash, not just journal entries. Tax authorities probe paper-only royalties that are never actually settled.

Stripe, Apple, and the payment-processor question

SaaS businesses typically receive customer payments through Stripe, with App Store revenue routed through Apple, Google Play royalties through Google, and enterprise deals via wire transfer. Where these processors deposit funds shapes a lot of the practical setup.

Stripe in the UAE is fully supported and integrates with Mashreq, Emirates NBD, and most major banks. You set up Stripe under the operating entity, with the entity's UAE bank account as the destination for payouts. Currency: USD payments are converted to AED at deposit time by default — for businesses with USD-denominated cost bases (USD-paid contractors, USD subscriptions), consider Stripe's multi-currency settlement option to receive USD directly.

Apple App Store and Google Play distribute payments through their own structures (e.g., Apple's Irish subsidiary). Your operating entity contracts with Apple/Google as the developer; payouts arrive in your UAE bank account. The legal contracting party should match the entity that owns the relevant developer account.

For enterprise deals, wire transfers can come into the operating entity's bank account directly. Larger UAE banks process inbound USD wires quickly and at reasonable rates.

US sales tax exposure

The US sales-tax landscape changed in 2018 with the Wayfair decision. State and local tax (SALT) authorities can require remote sellers to collect sales tax once they cross economic nexus thresholds — typically USD 100,000 of revenue or 200 transactions in a state per year.

For B2B SaaS founders, two things matter. First, many states treat SaaS as a taxable service. Second, even if the seller is non-US (your UAE entity), states can still require sales-tax collection if economic nexus is met. The traditional "we're a foreign company so we don't need to worry about US sales tax" position is largely wrong post-Wayfair.

Practical steps: (i) review your US revenue by state at least annually, (ii) identify states where you have nexus, (iii) register and file in those states, (iv) consider using a tax-automation provider (Avalara, TaxJar, Quaderno) to track and remit.

This is not strictly a UAE structuring issue, but it is the most-missed compliance item for SaaS founders moving to the UAE and assuming they have "left tax behind".

Substance for a SaaS business

UAE Economic Substance Regulations require that businesses claiming residency benefits actually conduct their core income-generating activities in the UAE. For a SaaS business, what does that look like?

• Strategic decision-making in the UAE. The founder and senior leadership take material business decisions in the UAE — documented in board minutes, calendar evidence, and travel records.
• Real office presence. A genuine office (not just a virtual mailing address) where founder and any UAE-resident staff actually work. For early-stage SaaS, a single small private office in DMCC or a Wework-style premium membership is sufficient.
• UAE-employed staff proportionate to revenue. At USD 1m ARR, the founder alone might be enough. At USD 5m+, expect tax authorities to expect more UAE-resident headcount.
• Operating expenditure in the UAE. Office rent, salaries, professional fees actually paid from the UAE entity in the UAE.

For SaaS specifically, the substance test is easier to pass than for trading businesses because the value-creation locus is genuinely the founder and small senior team. Get the founder credibly UAE-resident, hold the right meetings in the UAE, and substance flows from there.

What good banking looks like

For SaaS founders, the bank choice matters more than for other UAE businesses because of integration with Stripe and the need for USD/multi-currency handling.

Our default recommendations:

• Mashreq Neo Biz: SaaS-friendly. Strong USD handling. Good Stripe integration. Online onboarding is faster than incumbents.
• Emirates NBD: The premium choice. Strong international wires, good for clients who deal with large enterprise customers.
• WIO: Newer digital bank with strong founder appeal and good APIs. Lower fees, less established for very large transactions.
• RAK Bank: Underrated for SaaS. Decent USD support and friendly to startups.

We typically open two accounts: a primary operating account (Mashreq or Emirates NBD) for Stripe and customer revenue, and a secondary account (often WIO) for vendor payments, payroll, and operating cash. Two accounts reduce risk if either bank has temporary issues — a failure mode SaaS founders care about more than other founder types because customer payments cannot easily be paused.

If you have a US co-founder

US persons (citizens or green-card holders) face the strictest cross-border tax regime in the world. A US co-founder in an otherwise UAE structure triggers Subpart F, GILTI, and PFIC considerations that can materially change the calculation.

This is the topic we treat most carefully on initial calls. Three principles:

1. Disclose US-person status upfront. The structure built around it differs from the standard architecture.
2. Get US tax counsel involved early. UAE structuring without US-side coordination is a recipe for surprises at year-end filings.
3. Consider US-friendly entity choices (Delaware LLC under the apex, S-corp election where applicable). Sometimes the UAE entity should be structured as a check-the-box entity for US purposes; sometimes not.

If you are a SaaS founder considering UAE structuring — or you have already moved and want to validate that the structure your formation agent set up is appropriate for SaaS specifically — book a strategy call. SaaS structuring is a niche within UAE advisory, and we work with this segment more than most. We will assess what you have, identify gaps, and recommend the changes that matter.

Related reading