Skip to main content
Redian Software
Insurance solution

Reinsurance placement — accurate, auditable, automated

End-to-end reinsurance placement system: treaty management, facultative placements, automatic cessions, reinsurer accounting and statutory reporting for cedents and brokers.

CMMI Level 3 Appraised ISO Certified 200+ enterprises 5 regional hubs 9+ years of BFSI
Outcomes our customers see

The numbers we move.

Production benchmarks from real deployments — not vendor brochures.

  • 100%

    Cessions auto-calculated

    Treaty structure applied automatically as policies bind

  • 7 mo

    Avg. live in production

    From discovery to first statutory bordereau filed

  • Faster reinsurer settlement

    Statements reconcile to treaty terms first time

  • 60%

    Less manual reconciliation

    Bordereaux generated from the same ledger as policy data

What's in the platform

Capabilities, end to end.

A complete module list — designed to remove the gaps where vendor platforms typically leave you in spreadsheets.

  • 01

    Treaty management

    Configure proportional and non-proportional treaties once — layers, retentions, commission scales, profit commission, sliding scales, event limits and reinstatement premiums — and the engine applies that structure to every bound policy.

  • 02

    Facultative placement workflow

    Quote, slip and confirm facultative risks against a single record, with broker, cedent and reinsurer correspondence captured and timestamped for audit.

  • 03

    Automatic cessions engine

    Cessions calculate at bind time against treaty rules, with override controls for special acceptances and a full audit log of every adjustment.

  • 04

    Reinsurer technical accounting

    Premium and claim bordereaux, technical and financial statements, and account-current reconciliation in formats reinsurers and retrocessionaires accept without re-keying.

  • 05

    Statutory & solvency reporting

    Pre-built reports for IRA, IRDAI, NAICOM, CIMA and FSCA regulators, plus solvency II / risk-based capital extracts for actuarial and rating-agency submissions.

  • 06

    Claims recovery tracking

    Every claim ceded to treaty or fac is tracked through notification, advice, agreement and cash recovery, with aged-debt ageing on outstanding recoverables.

Who deploys this

Built for the operating environments we know best.

We've shipped this platform across the most common patterns — find the closest fit to your operating model.

  • Direct insurers

    General, life and health cedents placing proportional and non-proportional programmes across motor, fire, marine, engineering and MAT lines.

  • Reinsurance brokers

    Intermediaries running placements for multiple cedents who need broker-side accounting, multi-cedent statements and slip management.

  • Composite carriers

    Multi-line carriers in India, East Africa and West Africa managing treaty programmes across several lines of business and regulators.

  • Reinsurance companies

    Reinsurers and retrocessionaires accepting business who need the cedent-side view of incoming bordereaux and technical statements.

  • Captive insurers

    Corporate and group captives placing fronted programmes that need clean cession accounting and parent-company reporting.

  • MGAs and underwriting pools

    Delegated authority writers and pools who cede to fronting carriers and need treaty-aware bordereaux for their capacity providers.

Implementation

How a rollout unfolds.

Phased, milestone-driven, with parallel-run safety nets where regulators require them.

  1. 01Weeks 1-3

    Discovery & treaty mapping

    We document every active treaty, layer and special acceptance, mapping current spreadsheet logic onto the platform's treaty model. Output is a signed-off treaty register and gap list.

  2. 02Weeks 4-7

    Configuration & data migration

    Treaties, reinsurers, brokers and outstanding cessions are configured and historic in-force policies migrated. Output is a populated staging environment reconciled to the legacy ledger.

  3. 03Weeks 8-12

    Integration & accounting setup

    Integrate with core policy admin, claims and general ledger; set up bordereau templates and statutory report formats for the relevant regulator. Output is end-to-end data flow from binding to bordereau.

  4. 04Weeks 13-16

    UAT & parallel run

    Underwriting, accounts and compliance run real cessions in parallel with the legacy process for one quarter, reconciling to the rupee. Output is a sign-off pack from finance and the appointed actuary.

  5. 05Weeks 17-20

    Cutover & first close

    Production cutover with the first full quarterly close on the new platform, including reinsurer statements and statutory filings. Output is the first regulator-accepted return generated from the system.

  6. 06Month 6+

    Hypercare & optimisation

    90 days of hypercare with embedded support, followed by quarterly review of treaty performance, reinsurer ageing and recovery metrics. Output is a continuous-improvement roadmap.

Solution overview

In depth — how this platform runs.

The long-form view of capability, architecture and deployment model.

For cedents and reinsurance brokers running on spreadsheets, email chains and a patchwork of legacy ledgers, reinsurance placement is the part of the business where money quietly leaks — uncollected recoveries, missed cession deadlines, treaty slips that don't reconcile to bordereaux. Redian's Reinsurance Placement System gives underwriting, accounts and compliance teams a single platform that handles treaty, facultative and accounting workflows end-to-end, with an audit trail every cession can be traced back through.

This is built for insurers and brokers who place real volume — multiple treaties per line of business, several reinsurers per programme, statutory regulators that want bordereaux on a defined cadence — and who have outgrown the tools that got them this far.

What it does

The platform manages the full reinsurance lifecycle from treaty setup through cession, claims recovery and reinsurer settlement. Treaties are configured once with their full structure — layers, retentions, commission scales, profit commission, sliding scales, event limits — and the system applies that structure automatically as policies bind and claims register. Facultative risks that fall outside treaty appetite move into a placement workflow where underwriters, brokers and reinsurers exchange quotes and confirmations against the same record.

Every cession, premium statement and claim recovery is reconciled against the original treaty terms, so the numbers your accounts team produces match the numbers the reinsurer's technical accountant expects.

Where it fits

We deploy this system for three buyer profiles:

  • Direct insurers (cedents) — general, life and health insurers placing proportional and non-proportional programmes, typically running multiple treaties across motor, fire, marine, engineering and miscellaneous accident
  • Reinsurance brokers — intermediaries managing placements for multiple cedents, who need broker-side accounting, multi-cedent statements and a clear separation of placement records
  • Regional and specialty reinsurers — accepting business across India, East and West Africa, the GCC and the UK market

Most engagements sit alongside our Policy Administration System and Broker Management deployments, but the placement system runs equally well as a standalone product layered over a legacy PAS.

Core modules

Treaty management. Proportional treaties (quota share, surplus, combined), non-proportional treaties (per-risk XL, per-event XL, aggregate XL, stop loss), retrocession structures, and multi-layer programmes with reinstatement premium logic. Treaty slips are version-controlled so renewals don't overwrite the prior year's terms.

Automatic cessions. Rule-driven cession at the point of policy bind. The engine evaluates each risk against treaty scope — line of business, geography, sum insured bands, exclusions — and cedes the appropriate share in real time. Capacity is tracked per layer so underwriters see remaining treaty room before they write large risks.

Facultative placements. Structured workflow for individual risks: cession request, broker submission, reinsurer quote, terms negotiation, binding and slip issuance. Reinsurer panels are reusable across placements so the same security can be approached repeatedly with full history.

Reinsurer accounting. Premium statements, claim bordereaux, technical accounts, cash accounts, recovery processing and settlement against multiple currencies. Profit commission and sliding scale commissions are calculated on the configured cadence — quarterly, half-yearly or annually — without manual reworking.

Statutory and MIS reporting. Regulator-ready bordereaux in the formats expected by IRDAI, IRA Kenya, NAICOM, the UAE Insurance Authority and other regional regulators. Broker statements, ceding company statements, treaty performance dashboards and retention analysis are available to underwriters and reinsurance managers without going through IT.

Integration. Native links to policy administration, claims management and broker systems. Open APIs for general ledger posting, document management and external bordereaux exchange.

Why Redian

We've delivered insurance platforms for cedents and brokers across India, Kenya, Nigeria, Tanzania, the UAE and the UK — markets with very different regulatory rhythms but the same underlying placement mechanics. Redian is CMMI Level 3 appraised and ISO certified, with delivery hubs in Noida, Nairobi, Dubai, London and New York, so implementation teams sit in the same time zones as our clients' operations and regulators.

Our insurance practice combines reinsurance domain specialists, actuaries who understand treaty mathematics and engineers who have built PAS, claims and ML pricing engines for production insurers — not generalists learning the domain on your project.

Working with Redian

Most placement system engagements run 6–9 months from treaty configuration to first regulator-ready bordereaux, with phased rollouts by line of business so live placements aren't disrupted. Talk to our insurance team about your treaty structure and renewal calendar, or read how we've delivered comparable platforms in our case studies.

Why Redian

What makes this platform different.

Independent reasons clients pick us over incumbents and over generic global platforms.

  • BFSI specialism, not a generic platform

    Insurance is one of our four core practices. The team that builds your placement system has shipped core banking, PAS, broker management and claims platforms for the same buyers.

  • Regulator-aware by design

    Statutory bordereaux formats for IRDAI, IRA Kenya, NAICOM, CIMA and FSCA ship pre-built. We update them when the regulator updates them.

  • Built for emerging-market cedents

    Multi-currency, multi-entity, multi-regulator from day one — designed for African, South-Asian and GCC insurers who place internationally but report locally.

  • CMMI Level 3, audit-ready delivery

    Every cession, override and adjustment is logged with user, timestamp and reason — the audit trail your internal audit, statutory auditor and reinsurer's technical accountant all need.

Tech & integrations

What the platform talks to.

Open APIs, standard integrations, configurable from day one.

  • Java
  • Spring Boot
  • TypeScript
  • React
  • Node.js
  • Python
  • PostgreSQL
  • Oracle
  • MS SQL
  • Redis
  • MongoDB
  • Apache Kafka
  • Docker
  • Kubernetes
  • AWS
  • Azure
  • NGINX
  • Keycloak
  • Apache Camel
  • Jasper Reports
  • Power BI
  • Tableau
  • REST APIs
  • SOAP
  • SFTP
  • Twilio
  • SendGrid
  • Zoho One
  • Salesforce
Proof from production

A deployment that mirrors your use-case.

Real customer · real numbers · real go-live. Most of our work is under NDA — this is one we can share publicly.

InsuranceKenya

Insurance Distribution Platform for Kenya-based InsureMe

Client · InsureMe

  • Live

    Multi-insurer aggregator

  • M-Pesa

    Secure payment + Lipa PolePole

  • Real-time

    Policy generation

InsureMe — Kenya's digital insurance aggregator — runs on a Redian-built platform comparing policies across insurers, processing M-Pesa payments and issuing policies in real time with NTSA/KRA verification.

Tech stack

AngularNode.jsMySQL
Frequently asked questions

Everything you wanted to ask before the demo.

Don't see your question? Ask us directly →

Can the system handle both proportional and non-proportional treaties in the same programme?

Yes. Quota share, surplus, facultative-obligatory, excess of loss (per-risk, per-event, aggregate) and stop-loss are all modelled natively, including reinstatement premium logic and event limit tracking. Mixed programmes — for example a quota share with an XL on the retention — are configured as a single linked structure so cessions cascade correctly.

How does it integrate with our existing core policy admin and claims systems?

We integrate via REST APIs, message queues (Kafka or RabbitMQ) or scheduled SFTP files, depending on what your incumbent system supports. We have prior integrations with major PAS platforms used in Africa, India and the GCC, and a documented data-contract approach that means the integration scope is fixed during discovery, not discovered during build.

What statutory reporting formats are supported out of the box?

IRDAI returns for Indian cedents, IRA Kenya quarterly returns, NAICOM Nigeria, CIMA (CIPRES) for francophone Africa, and FSCA South Africa ship as pre-built bordereau and statement templates. We also generate solvency II / risk-based capital extracts and rating-agency data packs (AM Best, S&P) on request.

Can our reinsurance broker and our reinsurers see the same data we do?

Yes. The platform supports role-scoped external user access — your placing broker can see the slips, statements and recoveries they are responsible for, and reinsurers can be given read-only access to their cessions and bordereaux. All external access is audit-logged.

How long does a typical implementation take?

Seven to nine months from contract to first statutory close, depending on the number of active treaties and the state of the source data. A single-line, single-regulator cedent can be live in five to six months; a multi-line composite with 30+ active treaties and three regulators typically takes nine.

What happens to historical treaties and outstanding recoveries during migration?

In-force treaties and open cessions are migrated as a reconciled opening balance, validated against your legacy ledger to the cent before cutover. Closed historical treaties can be archived in the platform for audit and run-off reporting, or kept in the legacy system if that is cheaper — we will recommend based on the audit and regulator implications.

Is the system available as SaaS or only on-premise?

Both. We deploy on AWS, Azure and GCP as a managed SaaS, on the client's private cloud or on-premise — whichever the regulator and data-residency rules require. Cameroon, Kenya, India and UAE deployments span all three models in production today.

Still figuring it out? Tell us your operating environment and we'll send a tailored architecture and pricing within one business day.

Book a demo
See it live

Ready for a tailored Reinsurance Placement System walkthrough?

Tell us your regulator, your incumbent system and the outcome — we'll send a demo plan and pricing within one business day.