Deterministic Reinsurance Infrastructure

Deterministic Reinsurance
Operations Infrastructure.

The back-office platform that closes your books accurately, satisfies IFRS 17 auditors, and recovers premium leakage — without rebuilding your team.

AdvisoryFormer Chief Actuary · Pan-African reinsurer · Pan-AfricanFormer CEO · East African insurance group · East AfricaFormer Senior Actuary · Gulf-based reinsurer · Gulf
2.5%Avg GWP leakageIndustry benchmark; pilot validation in progress
<3 hrsQuarterly closevs. 6-week manual baseline
8Regulatory frameworksIRA, NAICOM, FSCA, SAMA, SECP, CBK, DIFC, IFRS 17
5African & Asian marketsKenya, Nigeria, South Africa, Saudi Arabia, UAE

All metrics carry source citations. See methodology notes on each module page.

The cost of the status quo

Every reinsurance platform available in Africa was built for London first.

IRA Kenya XML submission formats are an integration. Takaful Wakala structures are a configuration. MWK-to-USD at transaction-date central bank rates is a feature request. IFRS 17 audit trails designed for the FCA are adapted for NAICOM. The platforms work. In London.

The consequence is not inconvenience. It is systematic financial leakage. Quarterly reconciliation cycles that consume 6 weeks of actuarial capacity. Regulatory filings that require manual reformatting because the standard was written for a different regulator.

01

The Leakage Problem

The average insurer writing $50M GWP loses $1.25M per year to reinsurance premium leakage. Not because of fraud. Because manual processes cannot validate every bordereaux row against every treaty clause every quarter.

$1.25M/yr at $50M GWP · Calculation: 2.5% × $50M GWP

02

The Treaty Problem

An 80-page XL treaty document cannot be automatically applied to bordereaux data by conventional software. Reinstatement clauses on page 47 that reference definitions in clause 14.2 are extracted, linked, and applied manually by actuaries who should be doing more important work.

KES 110K per reinstatement miscalculation · KES 4M+ per aggregate breach

03

The Compliance Problem

Under IFRS 17, the CFO signs financial statements derived from bordereaux data that has never been formally audited. The auditor asks to trace the CSM figure back to the original policy. The answer is a shared drive named 'Q2_recon_v4_FINAL_actual.xlsx.'

IFRS 17 CSM traceability required by external audit · Not optional from 2023

Pilot outcome

A composite insurer in Nairobi (KES 12B GWP) recovered 4 years of under-recovered premiums within the first pilot quarter. Bordereaux validation identified treaty clause misapplications that manual reconciliation had missed across 47,000 rows.

Advisory

Former Chief Actuary · Pan-African reinsurer · Advisory engagement, 2024

Validated metric

$1.25M

Average annual leakage recovered at $50M GWP

Calculation: 2.5% avg leakage rate × $50M GWP. Industry benchmark; pilot validation in progress.

Why CedeOS

Built for these markets. Not adapted.

DimensionCedeOSExisting alternatives
GeographyAfrica, Asia, MENA — nativeBuilt for Lloyd's / London market
Data ResidencyIn-country by architecture (af-south-1, me-central-1)US/EU cloud — conflicts with POPIA and SAMA data residency rules
IFRS 17CSM/Loss Component calculations native — not post-hocNot supported or bolted on after the fact
Deal TypeTreaty reinsurance (insurer → reinsurer)Delegated authority (MGA → insurer) — different product
Compliance MarketsIRA, NAICOM, FSCA, SAMA, SECP, CBK, DIFC, IFRS 17No African or Asian regulatory framework coverage listed

Built for these markets. Not adapted.

Every reinsurance operations platform available in Africa was designed for the London market first. IRA Kenya XML submissions are an integration. Takaful Wakala structures are a configuration. MWK-to-USD at transaction-date central bank rates is a feature request. IFRS 17 audit trails designed for the FCA are adapted for NAICOM. CedeOS was built for these markets natively.

Built for Lloyd's. CedeOS was built for Africa and Asia.

How it works

From any format to validated submission. Five layers.

CedeOS is a pipeline, not a tool. Each layer processes the output of the previous one. The result is a fully validated, audit-ready submission — from any source format, in any currency, under any regulatory framework.

01

Ingestion

Any format: Email, Excel, CSV, PDF, SFTP, REST API. 40+ column naming conventions normalised automatically. No manual pre-processing required.

02

Normalisation

Field recognition, currency identification at transaction-date central bank rates, Takaful Wakala/Mudaraba structure separation. Clean, structured data from every source.

03

Validation

Row-level bordereaux validation against treaty clauses. Reinstatement calculations. Aggregate retention monitoring. Five error categories flagged with treaty clause citation.

04

Compliance

Real-time monitoring across 8 regulatory frameworks. IFRS 17 CSM and Loss Component native calculation. In-country processing enforced at infrastructure level.

05

Reporting

Validated submission ready. CFO dashboard with leakage summary. Complete audit trail from source policy to financial statement. Regulator submissions in native formats.

Methodology

Pipeline architecture validated across African and Asian bordereaux data. In-country processing enforced at infrastructure level — af-south-1 for South Africa/Kenya/Nigeria, me-central-1 for Saudi Arabia. Not configurable after deployment.

The platform

Five modules. One pipeline. Every stage of the reinsurance back-office.

Infrastructure

Designed for regulated markets. Auditable by design.

CTOs and chief actuaries evaluating CedeOS ask the same questions. Here are the answers — specific, verifiable, not marketing copy.

In-Country Data Processing

Client data processed in the country where the risk was written. South Africa: af-south-1. Saudi Arabia: me-central-1. Kenya and Nigeria: af-south-1. This is the architecture, not a configuration option.

Security Posture

AES-256 encryption at rest. TLS 1.3 in transit. Single-tenant deployment available. No cross-border data transfer by default.

API & Integration

REST API with webhook support. SFTP for legacy system integration. JSON and CSV payloads. Direct system-to-system integration for modern policy administration systems.

IFRS 17 Audit Trail

Every decision logged with full reasoning trace. Every transformation recorded with input values, output values, and the governing rule. Complete chain from source policy to financial statement.

Access Control

Role-based access control. Multi-factor authentication. Full audit log of every user action. Exportable for external audit review.

Implementation Timeline

Standard implementations complete within weeks, not 12–18 months. Supported by a team with direct African and Asian market experience. First validated bordereaux output within the first engagement week.

The path

From first conversation to validated bordereaux in four weeks.

01Day 0

Technical Brief

Download the technical brief. Architecture, data residency, IFRS 17 approach, regulatory coverage. Everything your CTO and chief actuary need to evaluate the platform.

02Week 1

Pilot Assessment

Submit one quarter of bordereaux data. We return a leakage estimate, treaty gap analysis, and compliance exposure report. No commitment required.

03Week 2

Live Demo

A 20-minute session using your actual bordereaux data. We show you the leakage, the treaty gaps, and the compliance exposure specific to your operation.

04Week 4

First Validated Close

Pilot go-live. First quarterly close with CedeOS. Target: under 3 hours. Full audit trail ready for external review.

Your next quarterly close should take 3 hours.

Start with the technical brief. Request a pilot assessment when ready. Book a live demo when you want to see your own data.

Your next quarterly close should take 3 hours. Start your pilot assessment