KPM Global : mainland versus zone franche for a software company

mainland versus zone franche for a software company

mainland versus zone franche for a software company à Dubaï et aux EAU — conseil en français sur documentation, demande, coordination avec les autorités et prochaines étapes.

  • Support en français
  • Expérience pratique aux EAU
  • Processus et délais clairs

Votre plan d'action

mainland versus zone franche for a software company

Processus guidé
1Consultation
2Juridiction
3Documentation
4Émission de licence

Processus clair, délais réalistes et suivi coordonné

Nous expliquons documents, délais, postes de coût et prochaines étapes avant de commencer.

500+
Clients accompagnés aux EAU
15+
Années d'expérience aux EAU
7/24
Support conseil
8
Domaines de service
Aperçu

mainland versus zone franche for a software company : aperçu

Choosing between a mainland and zone franche structure for a software or Software-as-a-Service company requires more than comparing licence packages. The decision can affect the activities the business may perform, its ability to work from customer sites, eligibility for government contracts, office and visa arrangements, tax treatment of subscription and intellectual-property income, and how comfortably banks and payment providers understand the operating model.

mainland versus zone franche for a software company exige de choisir la bonne structure, de revoir la documentation et de comprendre clairement les exigences officielles aux EAU. KPM Global accompagne les fondateurs en français.

Avant la demande ou le paiement, nous expliquons l'ordre, les délais réalistes, les postes de coût et les obligations ultérieures.

Notre équipe à Dubaï intègre création d'entreprise, visa, banque, fiscalité, PRO et voies juridiques dans un flux coordonné.

mainland versus zone franche for a software company exige de choisir la bonne structure, de revoir la documentation et de comprendre clairement les exigences officielles aux EAU. KPM Global accompagne les fondateurs en français.

Avant la demande ou le paiement, nous expliquons l'ordre, les délais réalistes, les postes de coût et les obligations ultérieures.

Notre équipe à Dubaï intègre création d'entreprise, visa, banque, fiscalité, PRO et voies juridiques dans un flux coordonné.

Pour qui

Pour qui convient mainland versus zone franche for a software company ?

  • Fondateurs et entrepreneurs ayant besoin d'une feuille de route claire pour mainland versus zone franche for a software company.
  • Investisseurs étrangers souhaitant entrer sur le marché des EAU avec des documents corrects et des délais réalistes.
  • Entreprises voulant comprendre à l'avance les exigences des autorités, des banques et des régulateurs.
  • Fondateurs recherchant un accompagnement en français, des coûts transparents et une coordination centralisée.
  • Équipes opérationnelles préparant création, renouvellement, fiscalité, visa ou revue bancaire.
  • Fondateurs et entrepreneurs ayant besoin d'une feuille de route claire pour mainland versus zone franche for a software company.
Comment nous aidons

Comment nous aidons

We focus on practical structuring — activity fit, jurisdiction choice, documentation, and post-licence banking and tax readiness.

Évaluation initiale

Nous analysons votre situation et expliquons les étapes de création en zone franche aux EAU.

Préparation documentaire

Nous recueillons, vérifions et structurons la documentation avant la demande ou le conseil.

Coordination avec les autorités

Nous coordonnons le processus avec les autorités de licence, les banques et les organismes concernés.

Plan de délais et coûts

Nous présentons clairement les étapes réalistes, les délais estimés et les coûts possibles.

Support post-création

Renouvellements, fiscalité, banque, PRO et conformité — nous restons votre point de contact.

Conseil en français

Nous expliquons clairement en français les exigences complexes des EAU et accompagnons chaque phase.

Processus

Flux de travail

Exact steps vary by activity, ownership, jurisdiction and regulator. Use this sequence as a practical planning guide.

  1. 1

    Consultation

    Nous clarifions l'objectif, la structure, les délais et les exigences de mainland versus zone franche for a software company.

  2. 2

    Revue des exigences

    Nous déterminons la juridiction adaptée, les documents, les autorisations et les risques potentiels.

  3. 3

    Préparation

    Nous préparons formulaires, justificatifs, documents sociétaires et demandes complémentaires.

  4. 4

    Soumission

    Nous coordonnons la soumission et répondons aux demandes des autorités ou des banques.

  5. 5

    Résultat et livraison

    Nous livrons le résultat et expliquons les obligations ultérieures et les dates clés.

  6. 6

    Support continu

    Accompagnement pour renouvellements, modifications, reporting et autres besoins d'entreprise.

Documents

Documents nécessaires

Requirements vary by shareholder type, activity and authority. Consistency across forms and supporting files is critical.

  • Passeports valides et, le cas échéant, données Emirates ID.
  • Licence existante, documents sociétaires ou informations sur la structure prévue.
  • Description de l'activité, marché cible, profil clients et modèle opérationnel.
  • Justificatif de domicile, contrats, factures ou documentation bancaire si requis.
  • Données financières, numéros fiscaux ou justificatifs de revenus si nécessaire.
  • Procuration ou autorisation de signature lorsqu'un représentant soumet la demande.
  • Autorisations sectorielles pour les activités réglementées.
  • Historique des demandes, renouvellements ou réponses antérieures des autorités.
Tarification

Facteurs de coût

Le coût de mainland versus zone franche for a software company dépend de la structure, des délais, de l'état de la documentation et des exigences des autorités.

  • Forme sociétaire, juridiction et activité choisie.
  • Nombre d'associés, de visas, d'employés et de demandes liées.
  • Besoin d'autorisations supplémentaires, traduction, légalisation ou revue technique.
  • Urgence, complexité de la structure et volume documentaire.
  • Exigences de la banque, de l'autorité fiscale ou du régulateur sectoriel.
  • Forme sociétaire, juridiction et activité choisie.
  • Nombre d'associés, de visas, d'employés et de demandes liées.
  • Besoin d'autorisations supplémentaires, traduction, légalisation ou revue technique.

Les fourchettes affichées sont indicatives — pour un devis ferme, contactez KPM Global.

Calendrier

Calendrier estimé

Timing depends on document readiness, activity approvals, office selection and banking due diligence.

Jour 1

Analyse des besoins

Revoir l'objectif, les documents, les délais et l'ordre correct.

Semaine 1

Préparation documentaire

Recueillir et vérifier formulaires, justificatifs et preuves.

Semaines 2–3

Demande et autorisations

Coordonner les processus avec autorités, banques ou régulateurs.

Après approbation

Clôture

Livrer le résultat et expliquer les obligations ultérieures.

Complete Guide

mainland versus zone franche for a software company — detailed guide

In-depth explanations covering ownership, jurisdiction, licensing, visas, banking, tax and compliance.

Can maintain its core activities and substance in the zone franche

The answer changes if the company combines software subscriptions with implementation, hardware, regulated financial technology, healthcare data or customer-site services.

What Is a Software or SaaS Company?

A SaaS company generally gives customers online access to software hosted or managed by the provider. Customers normally pay a monthly, annual, usage-based or user-based fee rather than acquiring the underlying source code.

The licence activity must match what the company actually does. "Software development," "IT consultancy," "portal operation," "cloud services" and "software trading" can represent different regulatory and commercial functions.

  • A software company may conduct one or more activities, including:
  • Custom software development
  • Mobile application development
  • Web-platform development
  • Software publishing
  • Enterprise resource planning implementation
  • Customer relationship management solutions
  • Artificial-intelligence software
  • Data analytics
  • Cybersecurity software
  • Cloud-platform services
  • Software integration
  • IT consultancy
  • Managed technology services
  • Software maintenance
  • Technical support
  • Licensing of proprietary software
  • Resale of third-party software
  • SaaS subscriptions

Why the Revenue Model Matters

Before choosing mainland or zone franche, the fondateurs should separate each expected revenue stream.

A technology company may earn income from:

The correct activities and tax treatment can differ across these streams.

For example, a business developing its own subscription platform is not identical to a reseller purchasing licences from an overseas vendor. A company that installs servers and network equipment may need trading and technical activities in addition to software consultancy.

  • Recurring SaaS subscriptions
  • Software licence fees
  • Implementation projects
  • Custom development
  • Configuration and integration
  • Technical support
  • Maintenance agreements
  • Data processing
  • Hosting
  • User training
  • Hardware sales
  • Software resale commissions
  • White-label agreements
  • Marketplace commissions
  • Advertising
  • Intellectual-property royalties

What Is a Mainland Software Company?

A mainland company is licensed by the economic department of the emirate in which it is established. In Dubaï, the relevant economic licensing functions are administered through the Département de l'Économie et du Tourisme and its associated channels.

A mainland software or IT company may generally conduct its approved activities throughout the local market, subject to any sector-specific restrictions.

Depending on its licence, it may:

The company remains limited to the activities stated on its licence. A general software activity does not authorise regulated financial, healthcare, telecommunications or cybersecurity services where separate approvals are required.

  • Contract directly with EAU businesses
  • Maintain mainland premises
  • Place employees at customer sites
  • Bid for eligible public-sector projects
  • Employ technical and commercial teams
  • Provide implementation and support
  • Combine several compatible activities
  • Sell software subscriptions
  • Trade permitted technology products
  • Open additional branches
  • Invoice EAU and overseas customers

What Is a Zone franche Software Company?

A zone franche software company is incorporated and licensed by a specific zone franche authority.

The company may operate as:

Different free zones offer different activity lists, office solutions, visa allocations, ownership rules and technology communities. Some provide startup programmes, incubators, co-working facilities, investor networks and access to specialist service providers.

The company must comply with its zone franche's rules and should confirm how its proposed activities may be conducted outside the zone.

A zone franche software company can enter contracts with customers aux EAU, but the legality and appropriate licensing structure depend on the nature and location of the activity.

Relevant questions include:

Is the service delivered entirely online?

Are employees deployed to the customer's premises?

Is the company maintaining a permanent mainland office?

Does the contract require a mainland licence?

Is the customer a government entity?

Does the company install or maintain physical equipment?

Is the activity regulated?

Does the company market or sell directly from mainland premises?

  • A technology startup
  • A custom-development studio
  • A SaaS platform
  • A software publisher
  • A regional sales office
  • A technology consultancy
  • An intellectual-property holding and licensing business
  • A cloud-services provider
  • An artificial-intelligence company
  • A software reseller
  • Serving EAU Customers From a Zone franche

Where are the people performing the core work?

A remote subscription accessed by a customer is operationally different from a team permanently stationed at the customer's Dubaï office.

Where the activity creates a mainland operating presence or requires mainland authorisation, the company may need a branch, permit or separate mainland entity.

Dubaï Executive Council Resolution No. 11 of 2025 established a framework under which eligible Dubaï zone franche establishments may conduct approved activities outside their free zones and within Dubaï.

The available routes include:

Dubaï subsequently introduced the Zone franche Mainland Operating Permit for eligible companies holding a Dubaï Unified Licence. The initial phase includes non-regulated fields such as technology, consultancy, design, professional services and certain trading activities.

A temporary permit may be useful for an eligible technology company performing a time-limited mainland project. A branch route may be more appropriate for recurring local operations.

Eligibility must be checked using the current activity list and procedures. A software-related description on a zone franche licence does not automatically qualify for every mainland technology activity.

A mainland company provides a clear structure for recurring work with EAU businesses.

It may simplify:

A company implementing systems at customer locations may require staff to work outside its own office for extended periods.

This can apply to:

A mainland structure can provide greater clarity for this operating model, although project and sector approvals may still be required.

A mainland licence does not guarantee tender eligibility, but it may be preferred or required for certain opportunities.

A growing software business may require a dedicated office for management, developers, sales teams, demonstrations and customer support.

A mainland company may be easier to scale when much of the workforce, management and customer delivery are based in mainland Dubaï.

A mainland company may require commercial premises appropriate to its activities and staffing plans.

A mainland juridical person is generally subject to the standard EAU Impôt sur les sociétés regime rather than the special Zone franche Impôt sur les sociétés regime.

Some fondateurs value proximity to technology companies, accelerators, investors and sector-specific infrastructure available within selected free zones.

Combining software, consultancy, hardware trading and regulated services can increase licensing and approval requirements.

A SaaS company can deliver its product digitally to customers across multiple markets while maintaining its headquarters and development operation in a EAU zone franche.

A suitable zone franche may provide:

A small founding team may begin with a shared or serviced office and increase its premises and visa capacity as the company grows.

Free zones are widely used by foreign fondateurs establishing wholly owned EAU technology businesses.

Full foreign ownership is also available for many mainland activities, so foreign ownership alone should not determine the choice.

A Qualifying Zone franche Person can benefit from a 0% Impôt sur les sociétés rate on Qualifying Income if every statutory condition is met.

For a software company, this analysis can be valuable—but it is also technically complex.

Some free zones offer legal frameworks, documentation and ecosystems commonly used by venture-funded companies. The precise suitability depends on the investor, investment round and exit plan.

  • Dubaï's Mainland Operating Routes for Zone franche Companies
  • A branch located on the Dubaï mainland
  • A branch licensed to conduct mainland activity while operating from the zone franche
  • A temporary permit for specified mainland activities
  • Advantages of a Mainland Structure for Software Companies
  • Direct Local Market Access
  • Customer onboarding
  • Local procurement
  • Vendor registration
  • Contract negotiation
  • Invoicing
  • Employee deployment
  • Customer-site access
  • Support and maintenance
  • Local dispute management
  • Better Fit for On-Site Technology Services
  • ERP implementation
  • Network configuration
  • Data-centre projects
  • System migration
  • Cybersecurity deployment
  • Hardware and software integration
  • Managed IT services
  • On-site support
  • Government Sous-traitance
  • Government and government-related customers may impose vendor-registration requirements covering:
  • Licence jurisdiction
  • Relevant activities
  • Local office
  • Technical experience
  • Audited financial statements
  • Tax registration
  • Information-security certifications
  • Professional indemnity insurance
  • Bid or performance guarantees
  • Flexible Mainland Premises
  • Compatible Commercial Activities
  • Where approved, the company may combine activities such as:
  • Software development
  • IT consultancy
  • Portal operation
  • Technology trading
  • System integration
  • Training
  • Technical services
  • Compatibility must be confirmed before incorporation.
  • Clearer Position for Local Hiring and Operations
  • Potential Disadvantages of a Mainland Structure
  • Higher Premises Costs
  • Standard Impôt sur les sociétés Position
  • Less Access to a Specialised Zone franche Ecosystem
  • Activity and External-Approval Costs
  • Advantages of a Zone franche Structure for SaaS Companies
  • Suitable for International Subscription Businesses
  • Specialist Technology Environment
  • Technology-focused activity options
  • Startup communities
  • Accelerators
  • Investor introductions
  • Co-working facilities
  • Flexible offices
  • Event and networking opportunities
  • Corporate-service infrastructure
  • Efficient Startup Packages
  • International Ownership and Management
  • Potential Zone franche Impôt sur les sociétés Treatment
  • Investor-Friendly Structuring
  • Potential Disadvantages of a Zone franche Structure

Mainland Operating Limitations

The company may need additional authorisation if it maintains mainland premises, deploys staff permanently outside the zone or performs activities requiring mainland licensing.

Some public-sector tenders or supplier-registration processes may prefer or require a mainland-licensed entity.

The company cannot assume that all SaaS subscription or software-licensing income is subject to 0% Impôt sur les sociétés.

A Qualifying Zone franche Person must maintain adequate substance. A licence and flexi-desk without appropriate people, assets and activity may not support the desired treatment.

The zone franche's available activity descriptions may not cover every element of the proposed business.

Software development generally involves creating, coding, testing, modifying or maintaining software.

IT consultancy generally involves advising customers on technology systems, architecture, implementation, security, transformation or process improvement.

A company may perform both, but it should obtain both activities where required.

The distinction matters because:

A SaaS company provides access to hosted software. A software trader or reseller may buy and resell third-party software licences.

A reseller should consider:

A company should not register only as a software developer if its main business is reselling licences developed by another provider.

The fondateurs should decide who will own:

Ownership should be supported by:

Paying a developer does not always resolve every ownership issue automatically. The contract should expressly allocate IP rights.

  • Government Procurement Restrictions
  • Impôt sur les sociétés Complexity
  • Substance Requirements
  • Activity Restrictions
  • Software Development Versus IT Consultancy
  • Contracts may describe different deliverables.
  • Professional liability risks differ.
  • Customer procurement categories may differ.
  • Staff qualifications may be relevant.
  • Tax analysis may differ between services and IP income.
  • A regulator may supervise particular activities.
  • SaaS Versus Software Trading
  • Vendor authorisation
  • Territory restrictions
  • End-user licence terms
  • Tarification rules
  • Renewal commissions
  • Support obligations
  • Data access
  • Tax treatment
  • Whether the activity is trading, agency or service provision
  • Proprietary Software and Intellectual-Property Ownership
  • Source code
  • Object code
  • Algorithms
  • Databases
  • Documentation
  • User-interface designs
  • Domain names
  • Trademarks
  • Patents
  • Application programming interfaces
  • Training data
  • Improvements and updates
  • Founder IP-assignment agreements
  • Employee invention and copyright clauses
  • Contractor IP assignments
  • Development agreements
  • Licensing contracts
  • Open-source software policies
  • Repository and access controls
  • Trademark registrations where appropriate
  • Software-development records

Zone franche Impôt sur les sociétés and SaaS Income

A zone franche company is within the EAU Impôt sur les sociétés regime. It does not receive an automatic exemption.

To be treated as a Qualifying Zone franche Person, the company must satisfy requirements including:

The Federal Tax Authority's Zone franche Persons Guide identifies copyrighted software as a form of Qualifying Intellectual Property.

However, this does not mean every dirham of SaaS revenue automatically benefits from a 0% Impôt sur les sociétés rate.

The rules use a nexus approach. The qualifying amount is connected to the research-and-development expenditure incurred to develop the relevant IP.

The company may need to track:

Income exceeding the amount determined under the applicable formula, and income from non-qualifying intellectual property, may be subject to 9% Impôt sur les sociétés.

Trademarks and other marketing-related intellectual property are not treated as Qualifying Intellectual Property merely because they are owned by a zone franche company.

A SaaS subscription can include several economic components:

The contract and accounting records should distinguish material revenue streams where their tax treatment or delivery differs.

Simply describing all revenue as "software services" or "licence income" may not reflect the true arrangement.

A software company should maintain records supporting:

EAU TVA may apply to software development, software licences, subscriptions and electronically supplied services.

A EAU-resident business must generally register for TVA when its taxable supplies and imports exceed AED 375,000 over the previous 12 months or are expected to exceed that threshold within the next 30 jours. Voluntary registration may be available above AED 187,500, subject to the conditions.

The applicable TVA treatment depends on factors including:

A foreign customer does not automatically make the supply zero-rated. Every condition for zero-rating must be satisfied.

A TVA-registered EAU SaaS company will generally need to charge TVA on taxable subscriptions supplied aux EAU, subject to the applicable place-of-supply rules.

Selling software internationally can create tax obligations outside the EAU.

A EAU licence does not replace conformité in the countries where customers receive the software.

A software company may act as:

The EAU's federal personal-data protection framework regulates the processing of personal data, subject to its scope and exemptions. DIFC and ADGM operate separate data-protection regimes within their respective jurisdictions.

A SaaS company should address:

The correct data-protection framework depends on where the entity is established, where processing occurs and which customers and individuals are affected.

Cloud software commonly transfers personal data between:

Contracts and policies may need to cover:

Customers in regulated sectors may impose stricter localisation or security requirements.

Enterprise and government customers may request recognised security certifications, independent audit reports or detailed security questionnaires.

Some software businesses require more than an ordinary technology licence.

Additional regulation may apply when the platform involves:

Calling a business "technology" does not remove sector-specific regulation.

A fintech platform, for example, may require financial regulatory assessment even if it does not directly hold customer funds.

It should also address:

The right office arrangement depends on the company's team, visa needs, customer expectations and tax position.

A small SaaS startup may begin with a co-working or serviced-office package where permitted. A larger development company may require a dedicated office with sufficient capacity for its team.

A flexi-desk alone does not establish that every substantive requirement is satisfied.

Both mainland and zone franche companies may sponsor eligible owners and employees, subject to their licence, establishment registration, premises and available quota.

A technology company may require visas for:

Software companies may face detailed conformité reviews because their revenue is digital and international.

Banks and payment providers may request:

A EAU company licence does not guarantee a bank account, merchant account or payment gateway.

Fondateurs expecting external investment should consider:

The lowest-cost incorporation package may not offer the best structure for institutional investment.

Before incorporation, fondateurs should understand whether their preferred investors require a particular jurisdiction, holding-company arrangement or constitutional framework.

A mainland structure may be preferable when:

A zone franche may be preferable when:

The fondateurs are prepared to assess the Zone franche Impôt sur les sociétés conditions properly.

A growing technology group may use:

It should be used only when the commercial advantages justify the additional burden.

  • Maintaining adequate substance in a zone franche
  • Deriving Qualifying Income
  • Not electing to use the standard Impôt sur les sociétés regime
  • Complying with transfer-pricing requirements
  • Meeting the de minimis requirement
  • Preparing audited financial statements
  • Satisfying the rules applicable to its income and activities
  • A software company must identify whether its revenue represents:
  • Service income
  • Income from intellectual-property ownership or exploitation
  • Income from transactions with another Zone franche Person
  • Income attributable to a mainland permanent establishment
  • Other qualifying or non-qualifying income
  • The customer's location alone does not provide a complete answer.
  • Copyrighted Software as Qualifying Intellectual Property
  • Each software asset or product family
  • Development expenditure
  • Employee development costs
  • Outsourced development
  • Related-party development costs
  • Acquisition costs
  • Subscription or licensing income
  • Embedded IP income
  • Updates and improvements
  • Why SaaS Revenue Requires Careful Classification
  • Access to software
  • Hosting
  • Data storage
  • Customer support
  • Maintenance
  • Updates
  • Implementation
  • Training
  • Customisation
  • Analytics
  • Impôt sur les sociétés for a Mainland SaaS Company
  • A mainland juridical person is generally subject to the standard EAU Impôt sur les sociétés rates:
  • 0% on taxable income up to AED 375,000
  • 9% on taxable income exceeding AED 375,000
  • Impôt sur les sociétés is imposed on taxable profit rather than revenue.
  • Subscription revenue recognition
  • Deferred revenue
  • Development expenditure
  • Capitalised development costs
  • Amortisation
  • Cloud-hosting costs
  • Contractor payments
  • Marketing expenses
  • Related-party charges
  • Foreign tax credits
  • Bad debts
  • Employee share-based arrangements
  • TVA on Software and SaaS Services
  • Customer location
  • Whether the customer is a business or consumer
  • Place of establishment
  • Fixed establishments involved
  • Where the service is used and enjoyed
  • Whether the service is electronically supplied
  • Export-of-services conditions
  • Supporting evidence
  • Related-party arrangements
  • SaaS Sales to EAU Customers
  • The business should ensure that its billing system can:
  • Validate customer information
  • Distinguish business and consumer users
  • Apply the appropriate TVA treatment
  • Issue compliant tax invoices
  • Record credit notes
  • Processus refunds
  • Capture subscription periods
  • Reconcile payment-gateway settlements
  • Retain evidence of customer location
  • International SaaS Sales
  • Depending on the market, the company may need to assess:
  • Foreign TVA or sales-tax registration
  • Digital-services taxes
  • Marketplace collection rules
  • Permanent establishment
  • Withholding tax
  • Local invoicing requirements
  • Consumer cancellation rights
  • Data localisation
  • App-store tax treatment
  • Data Protection Responsibilities
  • Data controller
  • Data processor
  • Sub-processor
  • Joint controller
  • Technology vendor with limited data access
  • Lawful processing
  • Transparent privacy notices
  • Purpose limitation
  • Data minimisation
  • Data accuracy
  • Security controls
  • Retention periods
  • Data-subject requests
  • Breach management
  • Cross-border transfers
  • Processor agreements
  • Sub-processor controls
  • Deletion and return of data
  • Cross-Border Data Transfers
  • Customers
  • EAU servers
  • Overseas hosting providers
  • Analytics tools
  • Payment processors
  • Support platforms
  • Group companies
  • Subcontractors
  • The company should map these data flows before launch.
  • Hosting locations
  • Transfer safeguards
  • Government-access requests
  • Encryption
  • Backups
  • Data residency
  • Sub-processor changes
  • Return or deletion at termination
  • Cybersecurity and Cloud Risk
  • A software licence does not certify that the platform is secure.
  • The company should implement controls appropriate to its business, including:
  • Access management
  • Multi-factor authentication
  • Encryption
  • Secure development practices
  • Code review
  • Vulnerability management
  • Penetration testing
  • Backup and recovery
  • Incident response
  • Audit logging
  • Vendor-risk assessment
  • Business continuity
  • Employee security training
  • Regulated Technology Activities
  • Payments
  • Lending
  • Banking
  • Assurance
  • Investments
  • Actifs virtuels
  • Santé
  • Telemedicine
  • Éducation
  • Télécommunications
  • Digital identity
  • Government data
  • Recrutement
  • Gambling or gaming
  • Transport et logistique services
  • Artificial Intelligence Companies
  • An AI company should clearly define whether it provides:
  • AI software development
  • Automated decision systems
  • Generative AI tools
  • Data analytics
  • Computer vision
  • Machine-learning consultancy
  • Model hosting
  • AI-enabled SaaS
  • Data-labelling services
  • Ownership of training data
  • Rights to model outputs
  • Third-party model terms
  • Confidentiality
  • Personal-data processing
  • Bias and discrimination risks
  • Human oversight
  • Model security
  • Accuracy statements
  • Restricted-use cases
  • Office and Substance Requirements
  • A Qualifying Zone franche Person must maintain adequate substance. This may require appropriate:
  • Core income-generating activity
  • Qualified employees
  • Operating expenditure
  • Physical assets
  • Management and decision-making
  • Supervision of outsourced activities
  • Visas and Employment
  • Fondateurs
  • Directors
  • Software developers
  • Product managers
  • Sales professionals
  • Customer-support personnel
  • Cybersecurity specialists
  • Data analysts
  • Administrative employees
  • Remote developers located outside the EAU require suitable contracts covering:
  • Employment or independent-contractor status
  • Confidentiality
  • IP assignment
  • Data access
  • Security
  • Equipment
  • Tax responsibility
  • Governing law
  • Banking and Payment Gateways
  • Business plan
  • Product demonstration
  • Website or platform access
  • Customer terms
  • Privacy policy
  • Subscription pricing
  • Founder profiles
  • Funding evidence
  • Contracts and invoices
  • Countries served
  • Expected transaction volumes
  • Refund policy
  • Source-code or IP ownership evidence
  • Data-security information
  • The business should also confirm whether the payment provider supports:
  • Recurring billing
  • Multiple currencies
  • Usage-based invoices
  • Trial periods
  • Refunds
  • Chargeback management
  • International cards
  • Application marketplaces
  • Raising Investment
  • Share classes
  • Voting rights
  • Founder vesting
  • Employee incentives
  • Convertible instruments
  • Investor protections
  • Board composition
  • Reserved matters
  • Propriété de propriété intellectuelle
  • Exit rights
  • Company-law flexibility
  • Due-diligence readiness
  • When a Mainland Company Is Usually Better
  • EAU customers will generate most revenue.
  • Staff will regularly work at customer premises.
  • Government procurement is a key strategy.
  • The business includes hardware installation or technical work.
  • A substantial mainland office is required.
  • Customers insist on a mainland vendor.
  • The company wants a straightforward standard Impôt sur les sociétés position.
  • Local implementation revenue is more important than IP licensing.
  • When a Zone franche Company Is Usually Better
  • The SaaS platform serves international customers.
  • Most services are delivered remotely.
  • The company owns and develops proprietary software.
  • The business wants a technology-focused ecosystem.
  • The initial team is small.
  • Flexible premises are important.
  • The EAU entity will act as a regional headquarters.
  • The company can maintain adequate substance.
  • When a Hybrid Structure May Be Appropriate
  • A zone franche parent with a mainland branch
  • A zone franche IP owner with a mainland operating company
  • A mainland company with a zone franche development subsidiary
  • A EAU holding company with separate operating entities
  • A hybrid model can separate IP, local operations and investment, but it increases:
  • Licence costs
  • Accounting obligations
  • Transfer-pricing requirements
  • Contractual complexity
  • Banking administration
  • Tax analysis
  • Governance responsibilities
  • Mainland Versus Zone franche Setup Processus

Step 1: Define the Product

Document what the software does, who uses it, how customers access it and whether it enters a regulated sector.

Step 2: Identify Every Revenue Stream

Separate subscriptions, licences, implementation, customisation, support, training, resale and hardware income.

Step 3: Map the Customers

Estimate the proportion of revenue expected from:

  • EAU mainland customers
  • EAU zone franche customers
  • Government entities
  • Overseas businesses
  • Overseas consumers
  • Related companies

Step 4: Determine Where Work Will Be Performed

Identify where management, development, customer support, sales and implementation teams will work.

Step 5: Select the Activities

Choose accurate software, consultancy, portal, cloud, trading or technical activities.

Step 6: Check Regulatory Requirements

Confirm whether financial, healthcare, educational, telecommunications or other sector approval is needed.

Step 7: Compare Jurisdictions

Review licence scope, customer access, office, visas, banking, tax, investor expectations and annual cost.

Step 8: Establish the Company

Complete trade-name approval, incorporation documents, licensing, office arrangements and establishment registration.

Step 9: Assign Intellectual Property

Execute founder, employee and contractor agreements ensuring the company owns or validly licenses the software.

Step 10: Implement Tax and Accounting

Register for Impôt sur les sociétés, assess TVA, create subscription accounting and establish IP-expenditure tracking.

Step 12: Arrange Banking and Payments

Apply for a business account and suitable recurring-payment facilities with complete commercial documentation.

The total cost may include:

Costs vary significantly between jurisdictions and packages. Fixed prices should not be quoted without confirming the activities, actionnaires, office and visa requirements.

A straightforward non-regulated software company may be incorporated relatively quickly when its documents and activities are clear.

Banking, payment processing and regulated-sector approvals should not be represented as guaranteed within a fixed timeframe.

Technology supporting payments, healthcare or investments may still be regulated.

Unclear ownership can create serious problems during investment, banking, customer due diligence or sale of the company.

Each developer should transfer the necessary rights and protect confidential information.

International SaaS sales can create TVA, sales-tax or registration obligations abroad.

Implementation, hosting, support and licensing elements may require separate analysis.

A basic privacy-policy template does not replace a complete data and security framework.

Service-level and security statements should be accurate and measurable.

A hybrid structure can be valuable, but unnecessary entities increase annual costs and conformité.

Before choosing mainland or zone franche, confirm:

  • Documents Commonly Required
  • Individual Shareholders
  • Passport copies
  • EAU visa copies, where applicable
  • Emirates IDs, where applicable
  • Residential-address information
  • Contact details
  • Passport photographs
  • No-objection certificate where required
  • Corporate Shareholders
  • Certificat d'incorporation
  • Memorandum and articles
  • Board resolution
  • Good-standing or incumbency evidence
  • Ownership structure
  • UBO information
  • Authorised-signatory documents
  • Attested documents where required
  • Business Documents
  • Business plan
  • Product description
  • Revenue model
  • Customer profile
  • Website or demonstration
  • Software architecture summary
  • Founder CVs
  • Funding evidence
  • IP assignments
  • Customer or vendor contracts
  • Data-flow information
  • Regulatory approvals where applicable
  • Costs and Cost-Determining Factors
  • Company registration
  • Annual licence
  • Selected activities
  • Trade-name fees
  • Establishment card
  • Office or co-working space
  • Immigration registration
  • Investor and employee visas
  • Assurance maladie
  • External approvals
  • Bank and payment-provider setup
  • Legal agreements
  • Trademark registration
  • Accounting software
  • Tax registration
  • Audit
  • Data-protection conformité
  • Cybersecurity testing
  • Annual renewal
  • Expected Calendrier
  • The total operational timeline may be longer because it can include:
  • Émission de licence
  • Enregistrement establishment
  • Visa processing
  • Corporate bank-account review
  • Payment-gateway onboarding
  • TVA registration
  • Customer-security reviews
  • Regulatory approval
  • IP assignment
  • Contract preparation
  • Common Mistakes to Avoid
  • Choosing the Cheapest Licence Without Checking the Activity
  • A low-cost licence may not cover the complete business model.
  • Describing a Regulated Platform as Ordinary Software
  • Assuming All Zone franche Income Is Tax-Free
  • SaaS and IP income require detailed Impôt sur les sociétés analysis.
  • Leaving Intellectual Property With a Founder or Freelancer
  • Using Overseas Contractors Without IP Assignments
  • Ignoring Foreign Digital-Tax Rules
  • Treating All Subscription Revenue as the Same
  • Underestimating Data Protection
  • Promising Security or Performance Without Support
  • Creating Two EAU Companies Too Early
  • Practical Structure-Selection Checklist
  • The software product is clearly defined.
  • All revenue streams have been identified.
  • The customer markets are known.
  • EAU and international revenue estimates are available.
  • The required business activities have been checked.
  • Regulated-sector exposure has been assessed.
  • Customer-site work has been considered.
  • Government procurement plans are documented.
  • Office and visa requirements are known.
  • The IP owner has been selected.
  • Founder and developer IP assignments are ready.
  • Zone franche Impôt sur les sociétés eligibility has been reviewed.
  • TVA treatment has been mapped.
  • Foreign digital-tax exposure has been considered.
  • Data flows and hosting locations are documented.
  • Privacy and security obligations have been assessed.
  • Banking and payment-gateway requirements are understood.
  • Investor expectations have been considered.
  • The complete annual cost has been calculated.
  • A mainland permit or branch route has been evaluated where relevant.

Final Recommendation

A mainland company is generally the stronger option for a software business built around EAU implementation projects, customer-site work, government procurement or substantial local operations.

A zone franche company is often attractive for an internationally focused SaaS platform, proprietary software developer, remote technology business or regional headquarters—particularly where the fondateurs value a technology ecosystem and can maintain genuine zone franche substance.

However, a zone franche should not be selected solely because of assumptions about 0% Impôt sur les sociétés, and a mainland company should not be selected solely because it appears to offer unrestricted trading. The decision should reflect the company's revenue, intellectual property, employees, customers and operating locations.

KPM Global Services LLC can help fondateurs establish a legally appropriate and commercially workable software or SaaS company aux EAU.

Our assistance may include:

KPM Global Services does not guarantee licences, regulatory approvals, bank accounts, payment gateways, investment or tax outcomes. Final decisions remain with the relevant autorités and service providers.

  • How KPM Global Services Can Assist
  • Mainland and zone franche comparison
  • Business-model assessment
  • Software and technology activity selection
  • Création d'entreprise and licensing
  • Shareholder and constitutional documentation
  • Mainland branch or operating-permit support
  • Visa and establishment services
  • Impôt sur les sociétés registration
  • Qualifying Zone franche Person assessment support
  • TVA registration and transaction mapping
  • Subscription-accounting setup
  • Intellectual-property structuring coordination
  • UBO and conformité support
  • Banking-assistance documentation
  • Continuing accounting, tax and licence-renewal support
  • 3. Questions fréquentes

1. Is mainland or zone franche better for a SaaS company?

A zone franche may suit an internationally focused SaaS platform operating remotely, while mainland may be better for a company focused on EAU implementation projects, customer-site work and government contracts. The right choice depends on the complete operating model.

2. Can a foreigner own 100% of a EAU software company?

Full foreign ownership is available for many mainland and zone franche software activities. Restrictions must still be checked for the exact activity and any regulated sector.

3. What licence does a SaaS company need à Dubaï?

The licence may include software development, software publishing, portal operation, IT consultancy, cloud services or related activities. The correct selection depends on how the product is developed, hosted and sold.

4. Can a zone franche software company sell subscriptions to EAU customers?

It may sell subscriptions to EAU customers, subject to its licence, the nature and location of the activity, mainland operating requirements, TVA and any sector regulation.

5. Can zone franche employees work at mainland customer sites?

This depends on the activity, project and licensing arrangement. Where a mainland operating presence is created, a branch or permit may be required. Site and professional requirements may also apply.

6. Can a Dubaï zone franche technology company obtain a mainland permit?

Eligible companies may apply under Dubaï's mainland operating framework. Technology was included among the initial non-regulated activity categories, but the exact activity and current eligibility list must be checked.

7. Does a EAU SaaS company need a physical office?

The premises requirement depends on the licensing authority, activity, visa quota and staffing plan. Some free zones offer shared or serviced-office options, while larger operations may require dedicated premises.

8. Does a zone franche SaaS company pay Impôt sur les sociétés?

Yes, it falls within the Impôt sur les sociétés regime. A Qualifying Zone franche Person may receive 0% on Qualifying Income, but other income may be taxable at 9%, and all qualifying conditions must be satisfied.

9. Is copyrighted software Qualifying Intellectual Property?

Copyrighted software can constitute Qualifying Intellectual Property under the Zone franche Impôt sur les sociétés rules. The qualifying income must be determined using the applicable nexus approach and supported by development-expenditure records.

10. Are trademarks Qualifying Intellectual Property?

Marketing-related intellectual property such as trademarks is not included within Qualifying Intellectual Property merely because it is owned by a zone franche company.

11. Is all SaaS subscription income treated as IP income?

Not necessarily. A subscription may include software access, hosting, support, implementation and other services. The legal agreement and economic substance must be reviewed.

12. Does a SaaS company have to register for TVA?

A EAU-resident business must generally register when taxable supplies and imports exceed AED 375,000 or are expected to exceed that amount within the specified period. Voluntary registration may be available above AED 187,500.

13. Are subscriptions sold to overseas customers automatically zero-rated?

No. The supply must satisfy all conditions for zero-rating. Customer location alone is insufficient.

14. Does the EAU company need to collect tax in foreign countries?

Possibly. Digital services can create TVA, GST, sales-tax or other obligations in customer jurisdictions. Each target market must be reviewed.

15. Who should own the source code?

Normally, the operating or designated IP-owning company should possess clear ownership or licensing rights. Founder, employee and contractor agreements must support that position.

16. Can developers outside the EAU work for the company?

Yes, subject to appropriate employment or contractor arrangements. The contracts should cover IP ownership, confidentiality, security, tax responsibility and data access.

17. Can a software company open a bank account without EAU customers?

Potentially, but the bank will assess the business model, fondateurs, countries served, source of funds and expected transactions. Approval is not guaranteed.

18. Can the company obtain a recurring-payment gateway?

Potentially. Payment providers apply their own licensing, ownership, product, risk and website requirements. Some business models receive enhanced review.

19. Does a fintech SaaS company need regulatory approval?

It may. If the platform performs or facilitates regulated financial activity, approval may be required even if the company describes itself as a software provider.

20. Which structure is better for raising investment?

It depends on investor preferences, share-structure requirements and exit plans. Some zone franche jurisdictions are popular with startups, but the structure should be reviewed before incorporation.

21. Can a mainland company own software intellectual property?

Yes. Propriété de propriété intellectuelle is not restricted to zone franche companies. The ownership must be legally documented and supported by contracts and development records.

22. Can a zone franche company bid for EAU government contracts?

Possibly, depending on the tender and the company's licensing position. Some procurements may require a mainland licence, vendor registration, security certification or local premises.

23. Is a mainland branch necessary for every zone franche SaaS company?

No. The need depends on where and how it operates. A remotely delivered subscription model may differ from recurring on-site implementation and support.

24. Should the company use separate entities for IP and operations?

Only where commercial, investment, liability or tax considerations justify the additional complexity. Related-party agreements and transfer pricing must be managed correctly.

25. Can KPM Global Services select the right jurisdiction?

KPM Global Services can review the product, activities, customer markets, team, IP, tax position and growth plans before comparing suitable mainland and zone franche options.

Points de vigilance

Erreurs fréquentes

  • Choisir juridiction ou forfait sans revoir l'activité réelle.
  • Soumettre avec une documentation incomplète et perdre du temps en corrections.
  • Ne pas planifier les délais de renouvellement, d'enregistrement fiscal ou de revue bancaire.
  • Comparer uniquement le prix de base et ignorer visa, bureau, traduction et frais officiels.
  • Reporter le conseil jusqu'à l'apparition de sanctions, retards ou blocages.
  • Choisir juridiction ou forfait sans revoir l'activité réelle.
Pourquoi KPM Global

Pourquoi KPM Global Services ?

Conseil centré sur les EAU

Accompagnement pratique de notre équipe à Dubaï, qui travaille au quotidien avec les autorités, les banques et les régulateurs.

Documentation claire

Checklists structurées, délais réalistes et périmètre transparent — vous saurez ce que couvre le service avant de commencer.

Services interconnectés

Création d'entreprise, visa, banque, comptabilité, TVA, impôt sur les sociétés, PRO et juridique dans un même plan de conseil coordonné.

Sans offres génériques

Les recommandations s'adaptent à l'activité, aux associés, à la juridiction et au plan opérationnel — sans formules standardisées.

Guide-backed setup planning

Recommendations follow the practical decision order used in our EAU formation guides — not generic cheapest-package selling.

Free tool

Compare zone fees & visas

Calculate and check before you speak to an advisor — FTA-aligned thresholds, instant results, PDF export.

Matrice ZF

Annuaire complet business et fiscal des EAU

Consultation gratuite

Demander un devis — mainland versus zone franche for a software company

Partagez vos besoins — notre équipe de conseil aux EAU vous répondra avec des prochaines étapes concrètes et un périmètre transparent.

Vous préférez WhatsApp ?

Écrivez-nous directement : +971 55 249 0091

Écrire sur WhatsApp

Réserver en ligne

Planifiez une consultation à un horaire qui vous convient.

FAQ

mainland versus zone franche for a software company — Questions fréquentes

Réponses pratiques sur mainland versus zone franche for a software company aux EAU.

La durée dépend de la juridiction, de l'état de la documentation, des autorisations et de la complexité de la structure. Après la revue initiale, vous recevrez un calendrier réaliste.

Prêt à démarrer avec mainland versus zone franche for a software company ?

Parlez à KPM Global Services pour un conseil pratique aux EAU — consultation gratuite, sans engagement.