Policy Administration System Software for Insurers across the UAE

Six connected capability areas: (1) Configurable product factory for UAE personal, commercial, and Takaful products alongside the core. (2) IFRS 17 sub-ledger integration with external calculation engines. (3) Takaful fund segregation with Wakalah/Mudarabah fee treatment and surplus distribution. (4) CBUAE reporting layer with configurable return schemas. (5) Shari'ah governance workflow for operators running Takaful windows. (6) Leadership dashboards for core platform health, reconciliation status, and return readiness.

Around those six, most insurers also want: bilingual Arabic document generation alongside the core document layer, UAE PASS identity integration for digital channels, and a reporting layer feeding actuarial and finance systems.

Core replacement - moving from Premia or TCS BaNCS to Guidewire or Sapiens - is an 18-36 month programme with implementation-to-licence multiples of 2x-5x during the first phase. For stable cores serving an operation reasonably, the replacement lift often exceeds the value recovered.

Augmentation keeps the core, adds a surgical layer above it, and closes UAE-specific gaps without the replacement lift. Where replacement eventually happens, the augmentation layer typically moves forward with the new core because the UAE-specific gaps persist regardless of vendor.

The integration layer reads from the core underwriting and claims records, applies contract grouping and cashflow generation logic, and feeds IFRS 17 calculation engines - Moody's Analytics RiskIntegrity, SAS Insurance Analytics, Aptitude Software IFRS 17, Sapiens IFRS 17, or Milliman IntelliScript. Reconciliation between core GL and IFRS 17 liability calculations runs continuously.

Variance above configurable thresholds flags as exception for actuarial and finance review. The 33% of UAE insurers reporting variance above 5% in 2025 between actuarial and finance teams is what this layer is designed to prevent.

Under the Insurance Law, the Takaful fund operates as a separate legal entity from the operator's shareholder fund. The platform enforces this at data model level - premiums, claims, investment income, and operator fees flow through segregated ledgers. Wakalah and Mudarabah fee calculations are first-class workflows.

Surplus distribution follows actuarial sign-off and Shari'ah board review, with participant-pool calculation and distribution mechanisms structured. The CBUAE Shari'ah governance three-lines-of-defence model is supported with Internal Shari'ah Supervisory Committee workflow and Higher Shari'ah Authority reporting patterns.

CBUAE returns - quarterly prudential, annual statutory, FIA Template V2, thematic review responses - are produced against configurable schemas. When the CBUAE issues a format update, the change is applied as configuration rather than code release.

FIT programme integration points (SupTech, EDM, Aani, Jaywan touchpoints where relevant) are treated as first-class integrations rather than bolt-ons. As the CBUAE-Accenture FIT programme expands its data surface, the reporting layer absorbs new requirements.

Product configuration - coverages, endorsements, rating factors, wordings, document templates - lives in the factory layer. New product variants deploy through configuration rather than core platform releases.

The core continues to hold policy records, premium accounting, and claims. The factory feeds product definition into the core at bind. When the UAE market needs a new product variant quickly - for example around new mandatory coverage rules - the factory cadence replaces the core release cycle as the constraint.

Here's where custom policy administration augmentation typically sits.

Core platforms - we sit alongside Guidewire, Sapiens IDITSuite and CoreSuite, Duck Creek, Fadata INSIS, Premia, TCS BaNCS Insurance, Oracle Insurance, and FINEOS for core policy, claims, and billing.

IFRS 17 engines - we integrate with Moody's Analytics, SAS, Aptitude, Sapiens IFRS 17, and Milliman for sub-ledger and liability calculation.

Document and analytics - we exchange with DocuWare and OpenText for content, and with Tableau and Power BI for reporting.

Integration approach is scoped during discovery. We don't ask you to rip and replace anything that works.

Discovery runs six to eight weeks (longer than line-specific builds due to core platform assessment scope). Working with your IT leadership, underwriting, finance, actuarial, and compliance teams, we map current core stack, IFRS 17 practice, Takaful workflow where applicable, and CBUAE reporting. Output is a detailed report covering current-state map, augmentation architecture, integration scope against the core, phased implementation plan, and fixed-price build proposal.

Build for an initial augmentation layer runs sixteen to twenty-four weeks from discovery completion. Full product factory, IFRS 17 integration, and CBUAE reporting rollout phases in over twelve to twenty-four months depending on core platform count and line mix.

Pricing varies materially by core platform, line mix, and Takaful scope. A bracket isn't published; discovery produces a fixed-price proposal with no obligation to proceed.