Employment Insurance
- Andy Woollatt
1. Description
This page provides a detailed overview of the data requirements necessary for initiating a Employment insurance quotation request within the UAE Open Finance framework. It must be read in conjunction with the https://openfinanceuae.atlassian.net/wiki/x/t5QlEw page to ensure alignment with the end-to-end quotation process.
The data outlined here includes both mandatory fields, which must be collected to generate a valid quote, and optional fields, which can enhance the accuracy and personalization of the quotation. TPPs can utilise this information to structure their data collection and submission process when requesting quotes from LFIs, either from all available institutions or based on user selection.
If pre-populated data from existing user insurance policy(ies) is used or will be leveraged during the quotation process, the https://openfinanceuae.atlassian.net/wiki/x/bJQlEw framework must also be referenced. This ensures compliance with UAE Open Finance data-sharing protocols and transparency in data utilisation.
1.1 Scope
The Employment Insurance Quotation Process supports the quotation and application for the government-mandated Involuntary Loss Of Employment (ILOE) scheme.
2. Employment Insurance Data Sharing Clusters
As part of the Employment insurance data sharing consent set-up between the TPP and user, the TPP must either:
Specify the data required from the user’s insurance account(s) to provide the requested service, or
allow the user to select which data clusters the TPP can access.
Both the TPP and the user must confirm the type(s) of insurance policy the TPP will access.
The agreed-upon data permissions, along with confirmation of the insurance type, must be included in the Pushed Authorization Request (PAR) body.
2.1 Data Cluster Permissions
The data permissions permitted for Employment insurance are:
Data Cluster language | Permission | Permissions Language | Examples of Information available |
|---|---|---|---|
Your Insurance Policies |
| Your Insurance Policy ID and basic policy information | Provide policy identifiers to facilitate retrieval of other policy details. |
Your Customer Details |
| Your basic information | Provides your full name, address, contact details and date of birth |
| Your detailed information | Provides your full details held by the Insurance provider including your identity details, employment details. Your full name, address, contact details and date of birth will also be provided. | |
Your Product Details |
| Your Employment detailed policy information | Provides all policy data held by the Insurance provider |
Your Premium Details |
| Your insurance premiums | Provides the details of the premium paid or being paid, along with confirmation of future renewal premiums when applicable. |
Your Payment Details |
| Your Premium payment bank account details | Provides the bank account details used or being used to make the insurance premiums. |
3. Quote UX Guidelines & Data Capture
3.1 Insurance Quote Data Capture
The Quote dataset outlined in the tables below represents a broader set of data that may be required by LFIs to generate a quote. This comprehensive dataset accounts for variations in LFI quotation processes and differences in when specific data points are collected from the customer.
While TPPs may collect and include this data in the Quote API request body, there is no Open Finance Standards requirement for LFIs to utilize all provided data if it is not part of their quotation process.
Capturing and submitting a fuller dataset at the quotation stage aims to:
Improve the relevance and accuracy of the generated initial quote premium.
Minimize unexpected premium increases during the final application, reducing customer frustration and drop-offs.
Reduce the need for additional data collection by the LFI if the customer chooses to proceed with the quote.
Enable earlier detection by the LFI of potential underwriting issues that could result in the customer’s application being declined.
3.2 Quote UX Requirements & Guidelines
3.2.1 Language Requirements
TPPs MUST:
Provide user-facing channels that are bilingual, supporting both Arabic and English.
Ensure that data values in API requests are provided in English, as the Standards APIs do not support Arabic
3.2.2 Quote Data Capture Field Order
TPPs MAY:
Define the order in which required customer and insurance information is collected or presented for verification when a data-sharing arrangement exists, ensuring alignment with their commercial strategy and user experience preferences.
Control how conditional fields are displayed or omitted, allowing the presentation of the required fields to adjust dynamically based on the data entered by the customer in associated fields.
3.2.3 Enumeration Options
TPPs MAY:
Define how API enumeration options are presented to the User during the quote application process, as this falls within their remit and is not dictated by these Standards, allowing flexibility based on the TPP’s customer experience principles and commercial considerations.
3.2.4 Optional Data
TPPs MUST:
When a question is relevant to the customer and the data is available, the information must be captured and included in the Quote API request body even if 'No' is reflected in the 'Required' column within the Data Cluster tables.
3.3 Employment Insurance Quote Data Clusters
The data provided within the tables reflect the following ‘Required’ states:
Mandatory Fields ("Yes" in the ‘Required’ Column)
Fields marked as "Yes" in the Required column are mandatory in the Quote API request body. If this data is missing, the API Hub will reject the request, or the LFI will be unable to generate a quote premium.Conditional Fields ("Conditional" in the ‘Required’ Column)
Fields marked as "Conditional" are required based on the customer’s response in an associated field. The Guidelines column specifies when this data must be provided. Failure to include required conditional data may prevent the generation of a quote premium due to missing information.Optional Fields ("No" in the ‘Required’ Column)
Fields marked as "No" are optional, as the question and data may not be relevant to all customers. If a field is not applicable, its absence will not trigger a 400 rejection response from the API Hub or prevent the LFI from generating a quote premium.
The Guidelines column, where applicable, will also reflect the options that must be presented to the customer for selection. These options are aligned with the enumerations within the Quote API request body.
The API Field column provides clarification on the Quote API request body field to which the customer’s response must be mapped by the TPP.
3.3.1 Customer
| UX Field Label | Required | Guidelines | Quote API Field |
|---|---|---|---|---|
|
|
|
|
|
1.01 | Salutation | No | Options are: Mr, Mrs, Miss, Ms |
|
1.02 | First Name | Yes |
|
|
1.03 | Middle Name | No |
|
|
1.04 | Last Name | Yes |
|
|
1.05 | Marital Status | Yes | Options are: Single, Married, Divorced, Widowed |
|
1.06 | Gender | Yes | Options are: Male, Female |
|
1.07 | Nationality | Yes |
|
|
1.08 | Date of Birth | Yes |
|
|
1.09 | Country of Birth | Yes | The Country where the customer was born |
|
1.10 | Mobile Number | Yes |
|
|
1.11 | Email Address | Yes |
|
|
1.12 | Primary Language | No | Options available are: English, Arabic, Other |
|
1.13 | Address | Yes |
|
|
1.13.01 | Address Type | Yes | The type of address being provided. |
|
1.13.02 | Building Number | Yes | The house, unit, apartment, or villa number assigned to the property. For new developments where a building number has not been assigned, this can reflect the plot number. |
|
1.13.03 | Building Name | No | The name of the building or community where the address is located |
|
1.13.04 | Street Address | Yes | The street address or road name of the property |
|
1.13.05 | Area | Yes | The specific district, neighbourhood, or locality where the address is situated |
|
1.13.06 | PO Box | No | The P.O. Box number assigned for mail delivery |
|
1.13.07 | City | Yes | The municipality or city of the property |
|
1.13.08 | Emirate | Yes | The Emirate where the address is registered. Options are: Abu Dhabi, Ajman, Dubai, Fujairah, Ras Al Khaimah, Sharjah, Umm Al Quwain |
|
1.13.09 | Country | No | The country associated with the address |
|
3.3.2 Employment
| UX Field Label | Required | Guidelines | Quote API Field |
|---|---|---|---|---|
|
|
|
|
|
2.01 | Profession | No | The individual's Profession |
|
2.02 | Job Title | No | Individual's job title |
|
2.03 | Designation | No | An individual's professional qualifications, special licenses and certifications |
|
2.04 | Nature of Employer Business | No | Nature of employer business |
|
2.05 | Profession Description | No | A description of the individual's Profession |
|
2.06 | Employer Name | No | Employer name |
|
2.07 | Employer Address | No | The address details of the individual's employer |
|
2.07.01 | Building Number | Yes | Employment Building number |
|
2.07.02 | Building Name | No | The name of the building or community where the address is located |
|
2.07.03 | Street Address | Yes | The name of the street or road |
|
2.07.04 | Area | No | The district, community, or neighbourhood |
|
2.07.05 | PO Box | No | The P.O. Box number assigned for mail delivery |
|
2.07.06 | City | Yes | The Emirate where the Employment is located |
|
2.07.07 | Emirate | Yes | The emirate where the address is registered |
|
2.07.08 | Country | No |
|
|
2.08 | Employment Status | No | The individual's employment status |
|
2.09 | Start Date | No | Individual's employment start date |
|
2.10 | Source of Income | No | Source of the individual's income as a free form description |
|
2.11 | Income Currency | No | Income currency |
|
2.12 | Monthly Income | No | Monthly income in AED |
|
2.13 | Annual Income | No | Annual income in AED |
|
2.14 | Details of any additional employment income / compensation | No | Provided when the individual has additional income they wish the application to take into account |
|
2.14.01 | Description | Yes | Free form description of the additional compensation |
|
2.14.02 | Amount (AED) | Yes | The amount of the additional compensation |
|
3.3.3 Identity
| UX Field Label | Required | Guidelines | Quote API Field |
|---|---|---|---|---|
|
|
|
|
|
3.01 | Emirates ID | Yes | Emirates identification number |
|
3.02 | Emirates ID Expiry Date | No | Emirates ID expiry date |
|
3.03 | Passport Number | No | Passport number |
|
3.04 | Passport Issue Date | No | Passport issue date |
|
3.05 | Passport Expiry Date | No | Passport expiry date |
|
3.06 | Passport Issue Country | No | Select from list |
|
3.07 | Visa Number | No | Visa number |
|
3.08 | Visa Issue Date | No | Date the Visa was issued |
|
3.09 | Visa Expiry Date | No | Date the Visa will expire |
|
3.10 | Visa Emirates Issuance | No | Options are: Abu Dhabi, Ajman, Dubai, Fujairah, Ras Al Khaimah, Sharjah, Umm Al Quwain |
|
3.3.4 Coverage
| UX Field Label | Required | Guidelines | Quote API Field |
|---|---|---|---|---|
|
|
|
|
|
4.01 | Scheme Category | Yes | For Involuntary Loss of Employment Insurance (ILOE) confirmation of the customer's Salary Category. |
|
4.02 | Sector | Yes | For Involuntary Loss of Employment Insurance (ILOE) confirmation of the customer's employment Sector |
|
4.03 | Policy Term Required | No | The insurance policy term in years and months |
|
4.04 | Premium Payment Frequency | Yes | Confirmation of the premium payment frequency. |
|
@ CBUAE 2025
Open License and Contribution Agreement | Attribution Notice