What the UAE Savings Scheme asks of a fund manager's operations

Fund managers moving into UAE workplace savings are finding that the operational shape of the category is unlike anything they have run before. The UAE Savings Scheme, and the broader alternative end-of-service framework it sits within, is not a distribution channel attached to an existing fund. It is an administrative system with a monthly cycle, a regulated intake, and a member relationship that has to survive employer turnover, leaver events, and audit scrutiny across years. Retail platforms and private wealth infrastructure were not designed for any of this.

This piece sets out what the UAE Savings Scheme requires operationally, why the workplace lifecycle breaks most platforms built for other purposes, and what a fund manager should look for before assuming an existing back office will extend.

What is the UAE Savings Scheme?

The UAE Savings Scheme is a voluntary federal framework under which onshore private sector employers can pay monthly contributions into an approved investment fund instead of carrying end-of-service gratuity as an accrued liability. It was enabled by Cabinet Resolution No. 96 of 2023 and is administered by MoHRE, with funds licensed by the Capital Markets Authority (CMA). It follows the alternative end-of-service model that DIFC introduced through DEWS in February 2020. We cover the scheme itself, including contribution rates and what happens to accrued gratuity, in our explainer.

The scheme is not a product. It is a regulated container within which fund managers, administrators, custodians, and employers coordinate to a defined operational calendar.

Who administers a UAE Savings Scheme fund?

Administration sits across several distinct roles that procurement teams often conflate. The licensed fund manager holds the CMA licence and MoHRE approval and carries the regulatory responsibility. The fund administrator handles unit pricing, NAV calculation, and the member ledger. The custodian holds assets. A platform provider delivers the technology that connects employers, members, contribution flows, and reporting. In DIFC's DEWS, a separate scheme operator and trustee sit above these; the federal scheme places that responsibility with the licensed fund manager.

One institution may hold several of these roles. It is uncommon for one to hold all of them well. A fund manager entering the workplace segment needs to decide, early, which functions it will build, which it will license, and which it will delegate to a specialist. Delegation moves the work; it does not move the responsibility.

What does the workplace operational lifecycle involve?

The lifecycle covers nine stages that repeat every month, per employer, per member: employer onboarding, contribution processing, bank reconciliation, fund pricing and NAV, trade execution, member portfolios, withdrawals, reporting and compliance, and the operations layer that runs exception handling across all of them.

Each stage has its own failure modes. Employer onboarding means ingesting payroll data in whatever shape the employer sends it, mapping it to member records, and handling joiners, leavers, and salary changes without breaking the audit trail. Contribution processing must accept files that arrive early, late, in the wrong format, or with corrections attached. Bank reconciliation must match receipts to expected contributions and hold unmatched cash without pricing units against it. Fund pricing and NAV must run on a defined cycle and survive a late correction upstream. Trade execution must respect switch instructions received before a cut-off and defer those received after. Member portfolios must show the position accurately in Arabic and English. Withdrawals must be processed against verified leaver evidence, and under the federal scheme the employee is entitled to payment within 14 days of the employment ending. Reporting must satisfy the fund manager, the employer, and the regulator from the same underlying ledger.

A platform designed for retail subscriptions, or for private wealth mandates, will handle two or three of these stages well. It will not handle the coordination between them.

Why do most platforms struggle with the workplace lifecycle?

Most platforms were designed for a different transaction shape. Retail investment platforms are built around a member who initiates their own contributions, chooses their own funds, and manages their own account. Workplace savings inverts every one of those assumptions. Contributions arrive from the employer, on the employer's schedule, in the employer's format. Members are enrolled by their employer and may not log in for months. Fund choice is often defaulted. The relationship survives the member changing job, the employer changing provider, and the fund manager changing custodian.

Private wealth infrastructure has the opposite problem. It handles bespoke mandates well but cannot process ten thousand members priced daily against a defined fund set with sub-account level attribution.

Both categories of platform can be extended. The extension is rarely cheap and rarely fast. A fund manager evaluating whether to build on an existing back office should map its current stack against the nine lifecycle stages and mark which ones will require net-new development.

What do fund managers underestimate about the UAE Savings Scheme?

The most underestimated stage is bank reconciliation. Contribution files and cash receipts do not arrive together, do not agree on totals, and do not always identify themselves clearly. Employers submit corrections after files have been processed. Cash arrives in the scheme account before or after the corresponding file. A single AED 4,000 discrepancy on a 4,000-employee payroll must be resolved before units are priced, or the error compounds across every subsequent month.

Reconciliation is the stage that determines whether the rest of the lifecycle runs cleanly. It is also the stage that receives the least attention in most platform evaluations. Fund managers used to running institutional mandates against a monthly custodian statement will find that workplace reconciliation operates at a different granularity and a different rhythm entirely.

The second underestimated area is member communication in Arabic. Not translation, but native Arabic member journeys that match the English experience in weight, tone, and functionality. A platform that treats Arabic as a secondary rendering will produce statements that fall short the first time a member opens one on their phone.

What should a fund manager ask before selecting a platform?

Procurement instinct is to build a feature matrix. The questions that predict a successful workplace savings deployment are operational rather than featural. How does the platform handle a contribution file that arrives with a salary correction after units have been priced? How long does employer onboarding take from signed agreement to first contribution processed? What is the reconciliation cut-off, and what happens to unmatched cash between cut-off and resolution? How are backdated joiners handled? How is a mid-month leaver priced? What is the audit trail for a member who switches portfolios the day before a NAV run? What does the reporting look like on day 25 of the month, not on demo day?

A platform that answers those questions with specifics has been run operationally. A platform that answers with capabilities has not.

Where Cohlay sits in the consideration set

Cohlay is one of the platforms a fund manager entering the UAE Savings Scheme should evaluate. It is DIFC-incorporated, built from the first line for the UAE workplace lifecycle, and works through licensed fund managers and administrators rather than approaching employers directly. Cohlay is not the only option, and the right selection depends on the fund manager's existing infrastructure, target segment, and view on build versus buy. What the platform offers is a system designed against the nine lifecycle stages as they run in the UAE, rather than a retail or private wealth system extended sideways. Whether that fit is worth pursuing is best answered against a specific set of operational scenarios rather than a feature list.

Frequently asked questions

Is the UAE Savings Scheme mandatory for private sector employers?

No. The federal scheme under Cabinet Resolution No. 96 of 2023 is voluntary for onshore UAE private sector employers, who may keep end-of-service benefits as an accrued liability or move the obligation into an approved fund. DIFC runs its own mandatory scheme, DEWS, for employers in its jurisdiction, and ADGM operates its own voluntary arrangements. Once an employer enrols an employee in the federal scheme, participation is mandatory for that employee.

What is the difference between the UAE Savings Scheme and DEWS?

DEWS is the DIFC Employee Workplace Savings plan, mandatory for DIFC employers since February 2020 and supervised within the DIFC. The UAE Savings Scheme is the federal voluntary framework for onshore employers, administered by MoHRE with funds licensed by the CMA. Both are alternative end-of-service arrangements, but they sit under different regulators, different structures, and different participation rules.

Who can provide a fund under the UAE Savings Scheme?

Funds offered under the federal scheme must be licensed by the CMA and approved by MoHRE. The licensed fund manager carries the regulatory responsibility; administration, custody, and technology can be delegated but the responsibility cannot. DIFC and ADGM have their own licensing routes for their own schemes. Most fund managers keep the licence and partner for administration and platform rather than build every function.

How long does employer onboarding take on a workplace savings platform?

It varies by platform and employer. A well-designed platform should take a mid-sized employer, several hundred to a few thousand employees, from signed agreement to first contribution processed in days rather than weeks. Larger or multi-entity employers take longer. The usual bottleneck is payroll data mapping and bank account setup, not platform configuration.

What happens if a contribution file has errors?

The file is held in a validation state until the employer corrects the data or an agreed correction rule is applied. Units should not be priced against unvalidated contributions, because the error compounds across every subsequent month. A sound workflow flags the error, notifies the employer, and holds the cash in suspense until the file clears.

Can a fund manager use its existing back office for the UAE Savings Scheme?

Yes, if it already handles daily unit pricing, member-level attribution, employer contribution intake, and workplace-specific reconciliation. Most retail and private wealth back offices handle some of these but not all. Extending is possible; the question is scope, cost, and time to a stable monthly cycle.

One question, for the operations lead: on your current infrastructure, how many days into the month can a single AED 4,000 reconciliation break go unresolved before it starts affecting member pricing?