The Platform
The back-office infrastructure behind accurate reinsurance.
Closes your books in hours. Satisfies IFRS 17 auditors. Recovers premium leakage. Without rebuilding your team.
Bordereaux
5 files uploaded
| Filename | Fmt | Status | Rows | Flagged | Uploaded | |
|---|---|---|---|---|---|---|
Q3-2025_xl-treaty_bordereaux.xlsx | Excel | Validated | 1,847 | 3 | 2h ago | |
Q3-2025_proportional_treaty.xlsx | Excel | Validated | 634 | 0 | 2h ago | |
Q2-2025_recon_final.csv | CSV | Complete | 2,103 | 7 | 3 days ago | |
Q2-2025_marine_cargo_treaty.xlsx | Excel | Complete | 218 | 1 | 3 days ago | |
Q1-2025_annual_bordereaux.xlsx | Excel | Complete | 3,291 | 12 | 3 months ago |
Showing 5 files · af-south-1 · Zero data egress
cedeos.co/bordereaux
Developed in consultation with senior actuaries and reinsurance executives across East African, West African, and Gulf markets. Currently in pilot evaluation.
Avg GWP leakage
industry benchmark
Target quarterly close
Regulatory frameworks
African & Asian markets
All metrics carry source methodology. 2.5% is an industry benchmark. < 3 hrs is a target based on pipeline architecture. Pilot validation in progress.
The cost of the status quo
Every reinsurance platform in Africa was built for London first.
The consequence is not inconvenience. It is systematic financial leakage.
The Leakage Problem
The average insurer writing $50M GWP is exposed to $1.25M per year in reinsurance premium leakage. Not fraud. Process failure — systematic errors that pass every manual spot-check because they look correct in aggregate.
$1.25M/yr exposure at $50M GWP — 2.5% industry benchmark
The Treaty Problem
An 80-page XL treaty cannot be applied to bordereaux data by conventional software. Reinstatement clauses on page 47 referencing definitions in clause 14.2 are enforced manually — by actuaries who should be doing more important work.
KES 110K per reinstatement error · KES 4M+ per aggregate breach
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 back to source. The answer is a shared drive named 'Q2_recon_v4_FINAL_actual.xlsx.'
IFRS 17 CSM traceability — required by external audit since Jan 2023
Before CedeOS
Q2_recon_v4_FINAL_actual.xlsx
Reinstatement calc — manual lookup
6-week actuarial review cycle
Spot-check only — no clause trace
14 disputed items with reinsurer
After CedeOS
Validated output — 2h 44m total
Reinstatement: §14.2 applied automatically
Every row clause-cited and logged
99.1% accuracy — AI + math verifier
Zero disputed items — pre-submission
Projected Impact
The exposure is quantifiable. The methodology is validated.
Based on industry leakage benchmarks applied to treaty reinsurance portfolios across African and Asian markets.
Recoverable leakage/yr at $50M GWP
Target quarterly close
Post-submission disputes with pre-submission validation
Error categories invisible to manual review
Methodology: 2.5% average GWP leakage is an established industry benchmark across African and Asian reinsurance markets. Financial impact projections based on analysis of East African XL programme structures and published treaty terms. Pilot validation in progress. Assessment available on request.
Why CedeOS
Built for these markets. Not adapted.
| Dimension | CedeOS | Existing Alternatives |
|---|---|---|
| Geography | Africa, Asia, MENA — native | Built for Lloyd's / London market |
| Data Residency | Regional by architecture (af-south-1, me-central-1) | US/EU cloud — conflicts with POPIA, SAMA |
| IFRS 17 | CSM/Loss Component calculations native | Not supported or bolted on |
| Deal Type | Treaty reinsurance (insurer → reinsurer) | Delegated authority (MGA → insurer) |
| Compliance | IRA, NAICOM, FSCA, SAMA, SECP, CBK, DIFC, IFRS 17 | No African/Asian framework coverage |
Every reinsurance platform in Africa was designed for London first. CedeOS was built here.
How it works
From any format to validated submission. Five layers.
Ingestion
Any format. Email, Excel, CSV, PDF, SFTP, REST API. 40+ column naming conventions normalised automatically.
Normalisation
Currency at transaction-date central bank rates. Takaful Wakala/Mudaraba separation. Confidence-scored per field.
Validation
Row-level check against treaty clauses. Reinstatement calculations. Aggregate retention monitoring. Five error categories with clause citation.
Compliance
Real-time monitoring across 8 frameworks. IFRS 17 CSM and Loss Component native. Regional processing enforced by architecture.
Reporting
Validated submission. CFO leakage dashboard. Complete audit trail from source policy to financial statement.
Pipeline architecture designed for African and Asian bordereaux formats. Regional processing: af-south-1 (Africa), me-central-1 (Gulf).
Live Pipeline — KE-GEN-01882 · CedeOS Insurance Q3
ProcessingIngest
Excel · 1,847 rows
Extract
99.3% confidence
Validate
3 flags · 2 review
Compliance
IRA KE · IFRS 17
Report
Generating…
The Platform
Six modules. One pipeline.
See all modulesRow-by-row. Every quarter.
Bordereaux Intelligence
Every row validated against treaty clauses before any figure enters the accounts. Any format, any currency, automatically.
$1.25M/yr exposure at $50M GWP
Learn moreIdentified before submission.
Leakage Analytics
Every discrepancy quantified in local currency and USD. CFO-ready recovery summary. Trend by cedant and treaty period.
2.5% avg GWP leakage — benchmark
Learn more83 pages. Applied automatically.
Treaty Validation Engine
Full clause extraction with citation trace. Every reinstatement computed. Aggregate retention monitored.
KES 4M+ per aggregate breach
Learn moreIRA. NAICOM. FSCA. SAMA.
Compliance Shield
Real-time monitoring across 8 frameworks. IFRS 17 CSM/Loss Component native. Regional processing by architecture.
8 frameworks automated
Learn moreAny format. One pipeline.
Multi-Channel Ingestion
Email, SFTP, dashboard, REST API, PDF. 40+ column naming conventions normalised without analyst overhead.
40+ naming conventions
Learn moreImmutable. 7-year retention.
Audit & Evidence Layer
Every decision logged with reasoning trace and clause citation. Tamper-evident chain. Court-ready.
Full IFRS 17 CSM traceability
Learn moreInfrastructure
Designed for regulated markets. Auditable by design.
CTOs and chief actuaries evaluating CedeOS ask the same questions. Here are the answers.
Regional Data Processing
Data processed in the region where the risk was written. Africa: af-south-1. Gulf: me-central-1. By architecture, not configuration.
Security Posture
AES-256 at rest. TLS 1.3 in transit. Single-tenant available. No cross-border transfer by default.
API & Integration
REST API + webhooks. SFTP for legacy systems. JSON/CSV payloads. Direct system-to-system for modern PAS.
IFRS 17 Audit Trail
Every transformation recorded with input, output, and governing rule. Source policy → financial statement. One click.
Access Control
Role-based access. MFA. Full user action log. Exportable for external audit review.
Implementation
Weeks, not months. First validated output within first engagement week. Team with direct African and Asian market experience.
The Path
From first conversation to validated bordereaux in four weeks.
Day 0
Technical Brief
Architecture, data residency, IFRS 17 approach, regulatory coverage. Everything your CTO and chief actuary need to evaluate.
Week 1
Pilot Assessment
Submit one quarter of bordereaux data. We return a leakage estimate, treaty gap analysis, and compliance exposure report. No commitment.
Week 2
Live Demo
20 minutes using your actual data. We show you the projected leakage, treaty gaps, and compliance exposure specific to your operation.
Week 4
First Validated Close
Pilot go-live. First quarterly close on CedeOS. Target: under 3 hours. Full audit trail for external review.
Get started
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. No slides. No sales pitch.