Reinsurance software

Reinsurance software is the system a cedent or a reinsurer uses to run ceded and assumed business: agreements, premium and claims data exchange, recoveries, settlements, and period close. The DICEUS reinsurance platform, known internally as the Reinsurance Financial and Data Exchange Platform, does all of it in one place.

Book a demo Reinsurance software dashboard

Who this platform is best for

It suits small and mid‑size cedents and reinsurers that already have a core system and need the reinsurance side to stop living in spreadsheets and email. It also suits reinsurers that receive data from many cedents in different formats and need one accepted version.

It is not the right choice if you are looking for a broker placement platform, a replacement for your general ledger, or a single report you could build in your data warehouse.

What does the platform support?

Who can use the platform?

Cedents, brokers, and reinsurers can use the platform. One side reports ceded business and tracks recoveries, the other validates what arrives and books it. Access is limited by agreement and role.

Cedent side

  • Reinsurance managers
  • Accounting / Finance
  • Claims (financial view)
  • Underwriting / Risk (optional)

Reinsurer side

  • Finance and accounting
  • Claims finance
  • Underwriting (optional)
  • Partner / Client managers
  • Audit / Compliance (read‑only)

What it replaces

Most reinsurance reporting still runs on spreadsheets passed between the cedent’s finance team and the reinsurer’s. That works until the files start to diverge.

Core functional domains

The platform covers financial data exchange, claims financial management, settlements and accounting views, and — optionally — underwriting and quotation.

Partner and agreement management

With the DICEUS reinsurance software you manage partners and agreements, onboard a cedent, and control access with optional SSO or MFA. The platform supports detailed treaty and facultative program setup and serves as the reference every financial and claims figure is checked against.

Partner and user management

  • Cedent onboarding
  • User and role management
  • Access limited by agreement and role
  • Secure authentication (SSO / MFA optional)

Agreement and program management

  • Treaty and facultative agreements
  • Participation, shares, layers
  • Periods, currencies, limits
  • Amendments and versions
  • Reference context for all financial and claims data
Partner directory in the reinsurance platform

Financial data submission and validation

The platform handles financial bordereaux management in multiple currencies. Data is submitted by Excel, CSV or API, checked and mapped against your agreements, and kept with a full version history and a clear status. Comments and audit records make every figure traceable.

Financial data covered

  • Written and earned premium
  • Commissions and brokerage
  • Corrections
  • Multi‑currency support

Data submission

  • Excel / CSV upload
  • API‑based submission
  • Agreement‑based validation
  • Mapping and version history datasets

Control and traceability

  • Versioning of submissions
  • Status flow: Draft → Submitted → Validated → Accepted / Rejected → Booked
  • Comments and clarification loop
Recoverables overview in the reinsurance platform

Claims financial management

Structured claims financial management gives you a complete view of paid, outstanding and recoverable amounts. It handles allocation at layer and reinsurer level, calculates shares automatically, manages notifications and updates, tracks disputes, and keeps agreement links and a claim‑level audit history.

Because every claim movement is tied to the agreement it falls under, the recoverable position is a system figure rather than a number someone rebuilds at period end.

Scope

  • Financial view of claims (not claims handling)
  • Paid, outstanding, and recoverable amounts
  • Layer- and reinsurer‑level allocation

Functionality

  • Claim financial notifications
  • Multiple updates per claim
  • Automatic share calculation
  • Status tracking / dispute flags

Traceability

  • Link to agreements
  • Claim‑level audit trail
  • Historical view of changes

Settlements, accounting, and period close

This module supports financial closure and reporting. Postings stay in your finance system. If you are also looking at the ledger itself, see our insurance general ledger platform.

Settlements

  • Statement of account generation
  • Period-based aggregation
  • Amounts due / payable
  • Settlement status
  • Payment confirmation records

Accounting view

  • Receivables and payables
  • Currency handling
  • Support for period closing and reconciliation
Settlements in the reinsurance platform

Audit, controls, and reporting

The platform provides audit, control and reporting tools: traceability, data versioning, and structured access for governance. Premium and claims data can be exported by partner and by agreement. For portfolio‑level analysis across lines and years, exported data is usually taken into an insurance data warehouse rather than kept in spreadsheets.

Audit and governance

  • Audit trail (who, when, what)
  • Data revision and comparison
  • Evidence for internal and external audits
  • Read‑only audit access

Reporting

  • Premium vs claims overview
  • Outstanding and recoverables
  • Partner‑ and agreement‑level views
  • Export to Excel
Operational analytics hub in the reinsurance platform

Optional business modules

These optional modules extend the platform but are not required for the financial core.

Quotation and placement

  • Reinsurance quotation requests
  • Indicative and firm quotes
  • Multiple quote versions
  • Quote to agreement conversion
  • Broker participation (if required)

Underwriting and risk support

  • Risk summary
  • Exposure / limit structures
  • Aggregates and erosion monitoring
  • Portfolio‑level views
  • Read‑only actuarial or pricing inputs

Want to see our reinsurance platform in action?

Book a call for a demo

Data standards and integration

The platform acts as a controlled integration hub and uses ACORD (Association for Cooperative Operations Research and Development) as the data exchange and validation standard between the systems you already run: policy administration, claims, accounting and ERP, and broker platforms.

Role of ACORD

  • Common data exchange standard
  • Validation reference for financial and claims data
  • Integration contract between systems

Integration options

  • Cedent PAS systems
  • Claims systems
  • Accounting / ERP
  • Broker platforms

On the cedent side the data usually comes from a policy administration system and a claims management system. Both can feed the platform directly, so the reinsurance view is built from the same records the business already runs on.

Architecture principles

Implementation

The platform goes in core first: partners and agreements, then financial data, then claims and settlements. Optional modules are switched on afterwards.

  1. Agreements and partners.

    We load your treaty and facultative structures, participations, layers, periods and limits. You confirm which agreements go in and the periods they cover.

  2. Submission mapping.

    We map the formats your teams already produce, so nobody has to change how they assemble data. You provide real submissions and statements to map against.

  3. Integration and access.

    We connect the source and target systems, configure validation rules, and set up roles, access by agreement and authentication.

  4. First period close.

    You name the finance and claims owners who will validate the first close. We run it with them, against real data, before go‑live.

How this compares with the alternatives

Spreadsheets and core‑suite modules each solve part of the problem. This platform was built around the whole ceded and assumed lifecycle.

DICEUS platform
Spreadsheets and email
Reinsurance module in a core suite
Built in
Kept separately
Built in
System‑owned
By agreement, informally
Internal only
ACORD, file and API
Email attachments
Usually thin
At submission
After the fact
Varies
Reconciled
Rebuilt each period
Partial
On a timetable
Waits on one person
Tied to core release
Who and when
In mailboxes
Core audit only
Structured
New workbook
Core change request

What do you get with the platform?

You get structured financial control, with data acceptance and settlement rules you can apply. Validation at submission, structured partner onboarding and end‑to‑end auditability are what make it efficient rather than merely tidy.

Financial control

  • System‑owned acceptance point
  • Received, accepted and recognized data kept distinct
  • Settlement gated by a formal agreement

Why DICEUS

Frequently asked questions

Can the system handle both treaty and facultative business?

Yes. Both are set up as agreements with their own participations, shares, layers, periods and limits. Facultative cases are handled individually; treaties carry the recurring structure each period of data is validated against.

We are a cedent, not a reinsurer. Is this for us?

Yes. Cedents use it to report ceded business, track recoverables and keep one accepted version of every statement. Access is limited by agreement and by role, so each partner sees only the data that belongs to them.

How does our data get into the platform?

By file upload or API, with ACORD as the reference for structure and validation. Mapping the formats you already produce is part of implementation, so your teams do not have to change their process before they can start.

We are replacing a legacy reinsurance system. Where do you start?

With a discovery phase. We take one of your treaties and one period of real data, run it through the platform, and show you what maps cleanly, what the validation rejects, and why.

Can we start with part of the platform?

Yes. Agreements, financial data and claims form the core; quotation, placement and risk support are optional. Any module can be switched on later without rebuilding what is already running.

Can you load our open treaties and past statements?

Open treaties and in‑force participations can be loaded, and so can historical statements. How much history to take is agreed per client, because the useful depth depends on how clean the older periods are.

Where does it run, and how long does implementation take?

Cloud, on‑premises, or a hybrid of the two. The model is agreed during scoping and depends on your infrastructure and data residency requirements. Implementation typically takes two to six months.

Other ready-made software products

Let’s talk about your project needs

gartner
5/5
6 reviews
clutch
4.9/5
49 reviews

    Contact us

    100% data privacy guarantee

    Thank you!
    Your request has been sent
    We will get back to you as soon as possible

    USA (Headquarters)

    +19293091005 2810 N Church St, Ste 94987, Wilmington, Delaware 19802-4447

    Denmark

    +4566339213 Copenhagen, 2900 Hellerup,
    Tuborg Havnepark 7

    Poland

    +48573568229 ul. Księcia Witolda, nr 49, lok. 15,
    50-202 Wrocław

    Lithuania

    +37069198546 Vilnius, LT-09308, Konstitucijos ave.7
    6th floor

    Faroe Islands

    +298201515 Smærugøta 9A, FO-100 Tórshavn,
    Faroe Islands

    UAE

    +19293091005 Emarat Atrium, 423 Al Wasl Area, Dubai,
    P.O. Box 112344

    Jordan

    +962787500100 Swafeya, Waklat St. 2, Office 302,
    Amman