Running a Wealth Firm in DIFC, ADGM or Onshore UAE: Software Rules, Costs, Timelines
DIFC, ADGM and onshore UAE regulators set different expectations on suitability files, statements, outsourcing and data. Here's how those differences shape your portfolio, CRM and reporting stack, what it typically costs and how long setup takes.
Your choice of regulator also decides your software stack
If you're setting up or relocating a wealth firm in the UAE, you're choosing between three regimes: the Dubai Financial Services Authority (DFSA) in the DIFC, the Financial Services Regulatory Authority (FSRA) in ADGM, and onshore regulation by the Securities and Commodities Authority (SCA) or the Central Bank of the UAE (CBUAE), depending on your activity. Most founders compare these on licence fees, office costs and hiring. Fewer ask how each regime shapes the software they'll have to buy, configure and defend to a supervisor.
They should. Your wealth management software UAE stack has to produce suitability evidence in the format your regulator expects. It has to generate client statements that meet local disclosure rules, sometimes in Arabic. It has to sit in a hosting arrangement that fits the outsourcing regime, and it has to process personal data under one of several data protection laws. A portfolio system that passes a DFSA review without trouble may need extra work before a CBUAE-supervised bank can use it.
This guide covers where the regimes differ, how those differences become requirements for portfolio management, CRM and reporting tools, and what typical 2026 budgets and timelines look like. It describes how the rules generally work. Before you commit to a licence category or hosting design, check with UAE-qualified regulatory counsel and the regulator itself.
DFSA, FSRA and onshore rules side by side
The two financial free zones run common-law regimes modeled on UK-style conduct rulebooks. Onshore regulation follows federal law and is split between two regulators: SCA licenses investment advisory, portfolio management and similar securities activities, while CBUAE supervises banks and finance companies, including their wealth and private banking arms. The table covers the four areas that most affect software selection.
| Area | DIFC (DFSA) | ADGM (FSRA) | Onshore (SCA / CBUAE) |
|---|---|---|---|
| Suitability | Conduct of Business (COB) module; client classification (Retail, Professional, Market Counterparty) drives assessment depth | Conduct of Business (COBS) rulebook; similar classification-led approach | SCA client classification and suitability rules; CBUAE consumer protection requirements for bank-distributed products |
| Client reporting | Periodic statement and disclosure rules in COB; content depends on client type and service | Periodic reporting under COBS; broadly comparable to DFSA | Bilingual (Arabic/English) disclosure expectations are common, especially for retail clients |
| Outsourcing | Firm stays fully responsible; material outsourcing is subject to notification and regulator scrutiny | Firm stays fully responsible; due diligence and notification expected for material outsourcing, plus cloud guidance | CBUAE outsourcing rules for banks generally require prior approval for material outsourcing; SCA expectations depend on licence type |
| Data protection | DIFC Data Protection Law No. 5 of 2020 | ADGM Data Protection Regulations 2021 | Federal Decree-Law No. 45 of 2021 (PDPL), with carve-outs; sector rules on customer data |
In practice, the free zones give you more freedom on hosting and vendor location. Onshore, a bank faces the most formal approval process, so build extra time in before contract signature.
What DFSA wealth management requirements and FSRA rules expect in a suitability file
DFSA wealth management requirements and the FSRA's rules for an ADGM asset manager look much alike. You classify the client and record the basis. You collect information on objectives, financial situation, knowledge and experience, and risk tolerance. You document why a recommendation or discretionary mandate fits. Professional Clients can get a lighter assessment, but you must record why they qualify, and supervisors look hard at thin evidence behind an opt-up classification.
Both free zones set minimum record retention periods, commonly in the range of five to six years or longer, and AML records fall under separate AML rules. Retention matters for software because a suitability record has to be reproducible years later: the questionnaire version, the answers, the resulting risk profile, the model portfolio assigned, and any overrides with the adviser's reasoning.
Onshore, SCA-licensed advisers and portfolio managers face comparable classification and suitability rules. Banks under CBUAE must also meet consumer protection standards on fair treatment, product suitability and fee disclosure. Confirm the exact retention period for your licence with counsel.
What this means for your CRM and onboarding tool
- Versioned questionnaires. When you change your risk questionnaire, old answers must stay tied to the old version. Many generic CRMs overwrite them.
- Immutable audit trail. Changes to risk profile, classification or mandate should be timestamped, attributed to a user and impossible to edit afterward.
- Linked evidence. Proof of wealth, the professional client opt-up notice and suitability reports belong on the client record, not in a shared drive.
- Drift alerts. Portfolio systems should flag when holdings move outside the client's profile. Supervisors ask how you monitor ongoing suitability, not only how you assessed it at onboarding.
Client reporting: statements, fees and the Arabic question
Reporting is where the three regimes cause the most rework. DFSA and FSRA rules set what periodic statements must show, typically holdings, valuations, transactions and charges, and how often they go out depending on service and client type. Discretionary managers usually carry stricter frequency and content obligations than advisory or execution-only firms. Both free zones expect clear cost and charge disclosure, which in practice means an all-in fee view across management fees, custody, transaction costs and product-level charges.
Onshore, the practical difference is language and format. Retail disclosures under CBUAE consumer protection standards are commonly expected in Arabic as well as English, and SCA licensees serving retail investors often face similar expectations. If your reporting engine can't render right-to-left Arabic properly, with correct number formatting, mixed-script tables and Arabic security names, you'll end up building statements by hand. That stops working beyond a few dozen clients.
Ask every reporting vendor three questions:
- Can it produce a full statement in Arabic and English from the same data, without a separate template build for each language?
- Can it show fees as both percentages and absolute amounts, aggregated across custodians?
- Does it store a frozen copy of every statement sent, so you can prove what the client received on a given date?
Multi-custodian aggregation is the other cost driver. UAE wealth clients often hold assets with Swiss, UK, Singaporean and local banks at once, and each custodian feed usually costs extra to set up and maintain.
Outsourcing and cloud: notification in the free zones, approval onshore
None of the three regimes bans cloud hosting or SaaS. They differ in how much paperwork stands between you and go-live.
In the DIFC and ADGM, the firm keeps full responsibility for any outsourced function. Expect to run due diligence on the provider, sign a written agreement with audit and access rights for you and the regulator, plan for exit and business continuity, and tell the regulator about material arrangements. Portfolio management, client reporting and core record-keeping are usually treated as material. Both regulators have published guidance relevant to cloud, and hosting outside the UAE is generally workable if you can show the risks are controlled.
Onshore banks face a tougher process. CBUAE outsourcing rules generally require prior approval for material outsourcing and a detailed risk assessment covering data location and cross-border transfers. Offshore hosting isn't impossible, but it adds weeks to procurement and pushes many banks toward UAE-region hosting. Major hyperscalers run UAE cloud regions, and many wealth vendors now offer in-country deployment for that reason.
Contract clauses to insist on
- Regulator access and audit rights written into the contract, not a promise to cooperate.
- A named hosting region, with notice and consent rights before it changes.
- A subcontractor list, with notification of changes.
- Exit assistance: data export in a usable format plus a transition period, commonly 6 to 12 months.
- Incident notification windows short enough for you to meet your own regulatory deadlines.
UAE data protection law for financial services: several laws, one client book
UAE data protection law for financial services depends on where your firm sits. DIFC entities fall under DIFC Data Protection Law No. 5 of 2020, overseen by the Commissioner of Data Protection. ADGM entities fall under the ADGM Data Protection Regulations 2021, overseen by the ADGM Office of Data Protection. Both are closely modeled on the EU GDPR. Expect lawful-basis analysis, data subject rights, breach notification, impact assessments for high-risk processing, and limits on transfers to jurisdictions without adequate protection. Registration or notification duties also apply. The DIFC law has specific provisions on autonomous and semi-autonomous systems, which matters if your platform uses automated profiling or recommendations.
Onshore, the federal Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) applies, with carve-outs. Among others, it excludes free-zone entities with their own data laws and certain banking and credit data governed by separate legislation. For CBUAE-supervised banks, sector rules on customer confidentiality and data location carry much of the weight. Implementation of the federal law has been gradual, so confirm the current status of executive regulations and enforcement with counsel.
Two practical consequences for buyers:
- Group structures complicate things. A DIFC manager with an onshore advisory arm and a London parent may face three or four data regimes for the same client record. Your CRM needs field-level access controls and a clear data map.
- Vendor DPAs need local terms. A standard GDPR processing agreement is a decent base, but it should name the DIFC or ADGM law and cover their specific transfer mechanisms.
Matching portfolio, CRM and reporting tools to your firm, with typical costs
Most UAE wealth firms end up with one of a few stack patterns. Small DIFC and ADGM managers and multi-family offices with a few hundred relationships usually pair a portfolio and reporting platform, such as Addepar, Masttro, Asset Vantage, Expersoft PM1 or Objectway, with a configurable CRM such as Salesforce Financial Services Cloud or Microsoft Dynamics 365. Larger managers and private banks tend to look at integrated suites from Avaloq, Temenos or InvestCloud, or platform providers such as FNZ. Firms with institutional mandates often add SS&C Advent for portfolio accounting. Availability and UAE presence vary by vendor, so verify each one.
For portfolio management software in Dubai or Abu Dhabi, first confirm the vendor has live UAE or GCC clients, Arabic statement output and data feeds for the custodians your clients actually use.
| Component | Boutique (under USD 1bn AUM) | Mid-size (USD 1bn–10bn) | Main cost drivers |
|---|---|---|---|
| Portfolio management and reporting | USD 40,000–150,000 per year | USD 150,000–600,000+ per year | AUM or account-based pricing, custodian feeds, alternatives coverage |
| Wealth CRM and onboarding | USD 150–350 per user per month, plus USD 30,000–120,000 configuration | Similar per-user rates; USD 150,000–500,000 configuration | Suitability workflow build, document management, integrations |
| Arabic and bilingual reporting templates | USD 10,000–40,000 one-off | USD 40,000–120,000 one-off | Right-to-left layout, number of report types |
| Custodian data feeds | USD 5,000–25,000 per custodian setup | Often bundled; per-feed fees still common | SWIFT vs file feeds, data cleansing |
| UAE-region hosting premium | 0–20% uplift | Negotiable | Dedicated instance vs multi-tenant |
These are typical 2026 market ranges. They vary widely by contract, reseller and negotiation, so confirm current pricing with vendors.
Setup timeline: a hypothetical 12-person DIFC manager
Say a 12-person team is launching a discretionary portfolio management firm in the DIFC, serving about 150 Professional Clients across five custodians, with a parent in Europe. A realistic software timeline, run alongside the licence application, looks like this:
| Phase | Typical duration | What happens |
|---|---|---|
| Requirements and shortlist | 3–5 weeks | Map COB suitability and reporting rules to functional requirements; shortlist 3–4 vendors |
| Due diligence and contracting | 4–8 weeks | Security review, outsourcing assessment, DIFC-specific DPA, regulator access clauses |
| Configuration and CRM build | 6–12 weeks | Suitability workflow, client classification, document templates |
| Custodian feeds and data migration | 6–14 weeks | Often the longest phase; custodian onboarding queues are outside your control |
| Testing and parallel run | 3–6 weeks | Reconcile positions, test statements, dry-run a regulatory record request |
Plan on roughly four to seven months from shortlist to go-live, since some phases overlap. An ADGM firm with the same profile would be similar. An onshore bank adding a wealth platform should add several weeks, plausibly six to twelve, for CBUAE approval and internal risk committees. Start software selection as soon as your regulatory business plan is drafted, because the regulator will ask about your systems and controls during authorization.
Red flags in vendor due diligence, and how to decide
Watch for these during demos and contract review:
- No UAE references. A vendor without a live DIFC, ADGM or onshore client is learning at your expense, especially on Arabic output and local custodians.
- Arabic "on the roadmap." If they can't show a finished bilingual statement, assume a custom build you'll pay for.
- Audit rights limited to the firm. The regulator needs access too. Pushback here is a serious problem for any regulated buyer.
- Suitability as free-text notes. If risk profiles and overrides aren't structured, versioned data, you can't evidence ongoing suitability.
- Vague hosting answers. "Global cloud" isn't an answer. You need a named region and a named subcontractor list.
- Expensive exit. Export fees or proprietary formats will hurt when you outgrow the platform.
The decision rule is simple. If you're a free-zone manager with mostly Professional Clients, put custodian coverage and suitability workflow first, and accept hosting outside the UAE if the contract terms are strong. If you're onshore or serving retail clients, put Arabic reporting and UAE-region hosting first, even at a 10–20% premium, because retrofitting either later usually costs more than the uplift. Before signing, ask each finalist to produce a sample suitability record and a bilingual statement from test data in a single session. A vendor that can't is unlikely to help you through a supervisory visit.
Quick answers
Can a DIFC or ADGM wealth manager host client data outside the UAE?
Generally yes. Neither the DFSA nor the FSRA bans offshore hosting, but you must assess the outsourcing risk, notify the regulator of material arrangements, and meet your zone's data protection transfer rules, usually through adequacy decisions or contractual safeguards. Onshore banks under CBUAE face a stricter prior-approval process, so many choose UAE-region hosting.
Do UAE wealth firms have to send client statements in Arabic?
It depends on the regime and client type. Onshore, retail disclosures are commonly expected in Arabic as well as English, and SCA licensees serving retail clients often face similar expectations. DIFC and ADGM firms usually operate in English, but many offer Arabic for client service reasons. Confirm your obligations with counsel and check bilingual capability before you sign.
How long should we keep suitability records?
Free-zone conduct rules and UAE AML rules each set minimum retention periods, generally in the range of five to six years or more, and the clock often runs from the end of the relationship. Many firms keep records for the longest applicable period. Your system should reproduce versioned records for that whole period, and counsel should confirm the exact schedule for your licence.
Is a generic CRM good enough for a regulated UAE wealth firm?
Only with heavy configuration. Out of the box, most generic CRMs don't version suitability questionnaires, lock audit history or link classification evidence to the client record, which are the things supervisors ask about. Financial-services editions such as Salesforce Financial Services Cloud or Dynamics 365 shorten the build, but budget for configuration work.
Written by the Wealth Deskplus editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.