Reinsurance broking software that follows the placement as it actually happens — submission intake, market panel, written and signed lines, premium allocation, closings, endorsements and claims. Configured to your lines, currencies, cedants and commission structures rather than to a vendor's fixed model.
Most reinsurance broking operations do not run inside a system. They run across a spreadsheet that holds the panel, an inbox that holds the responses, a folder of Word templates that becomes the closing, and a broker's memory that holds the rest. It works, in the sense that deals get placed. What it costs is visibility: nobody except the broker running a placement can say where it stands, what has been signed, or what is still out.
That cost compounds. Line status drifts from what the markets actually agreed. Closings are retyped from the slip and the slip is retyped from the submission. A claim arrives and someone reconstructs which reinsurers were on the risk and at what share. Month end becomes archaeology.
Regure holds the deal as a structured record from the moment the submission arrives, and every stage after it works from that record — the placement, the premium, the closings, the endorsements and the claims.
For the underlying market concepts, see the reinsurance, cedant and slip policy glossary entries.
Send a single submission and we will run it through the chain in a working session — read it, structure the deal, build the premium, place it across a panel and generate the closings.
Each stage below works from the same deal. Nothing is re-keyed between them, and every action is on the audit trail as it happens rather than reconstructed later.
A submission arrives as a document. It is read and turned into a structured deal — cedant, insured, class and sub-class, geography, occupation, period, currency, sum insured, premium, retention and cession — for review and correction rather than retyping. What the extraction found, and how confident it was, stays on the record.
The panel sits on the deal. Each market carries its own provisional, quoted, written and signed share, moving through approached, quoted, firm order and signed — with declines recorded against a reason rather than lost in a thread. A placement queue shows the whole book at once.
Capacity is computed against the cession as lines come in, so the gap between what is written and what is signed is visible while it still matters. Over-placement and under-placement are flagged rather than discovered at closing.
The cession is allocated across the markets with ceding commission and brokerage applied per market, and the totals reconcile. Where your business needs them, deposit and minimum premium, instalment schedules, profit commission, no-claims bonus and tax lines are configured too — and stay hidden for operations that do not use them.
The slip, the debit note to the cedant and a credit note per reinsurer are generated from the deal on your own template. Where a market settles in another currency the figure stays in the deal currency and the converted table carries the rate applied. Each generated document is recorded against the deal.
A mid-term change re-runs the allocation for the delta and produces additional or return premium per market, with closings to match. A claim is checked against the deal automatically — inside the period of cover, against a bound cession — and allocated across reinsurers by signed share, with its own closings. Sanctions screening records sit against the parties.
Everything above exists to produce these. When the lines are signed, the debit note to the cedant and a credit note per reinsurer are generated from the same record the placement ran on — the cession, the ceding commission, the brokerage and the tax lines are already there, so nothing is retyped from the slip and the arithmetic is not done twice.
| Original Premium | USD 1,260,000.00 |
| Cession (75.0%) | USD 945,000.00 |
| Less: Ceding Commission | (USD 236,250.00) |
| Net Due from Cedant | USD 708,750.00 |
| VAT (5.0% on net premium, cedant) | USD 35,437.50 |
| Total Taxes | USD 35,437.50 |
| Market Premium (share of cession) | USD 259,875.00 |
| Less: Ceding Commission (25.0%) | (USD 64,968.75) |
| Less: Brokerage (10.0%) | (USD 25,987.50) |
| Net Payable to Reinsurer | USD 168,918.75 |
| Market Premium | EUR 237,785.63 |
| Less: Ceding Commission | (EUR 59,446.41) |
| Less: Brokerage | (EUR 23,778.56) |
| Net Payable to Reinsurer | EUR 154,560.66 |
1 USD = 0.9150 EUR (effective 14 Feb 2026)
The detail behind these documents — how commission and brokerage are applied per market, how taxes and instalments appear, and what happens when a market settles in another currency — is on the closings and documentation page.
Both are real deployments, and neither is the compromise. Which one fits depends on what you already own and what you are willing to keep running — not on how far along you are.
The reinsurance operation runs here end to end. Submissions arrive, deals are structured, placements are worked across the panel, premium is built, closings are generated, endorsements and claims sit against the same record, and reporting comes off it. Broking houses that have been running on a spreadsheet and a folder of Word templates usually take this route — there is no incumbent system to preserve, and the placement and the closing are the product.
This is the model where the operational gain is largest, because nothing has to be reconciled back to a second system.
Where a broker or insurer has a core system it is not replacing — a policy administration or accounting platform that holds the book of record — Regure takes the reinsurance workflow that the core does not model well: the market panel, the written and signed lines, the premium allocation across markets and the closings. The deal record is the working system for placement; the figures that matter downstream go to the core.
What that handover looks like is decided in implementation. Integrations are configured per deployment against the systems you actually run, rather than shipped as a pre-built connector list.
Both models use the same platform and the same configuration surface. See the deployment models in full for how this works beyond reinsurance, and how Regure compares to SARB if you are evaluating against a dedicated reinsurance system.
Practising reinsurance brokers have worked the chain end to end against how they actually place. Named references are available under NDA during procurement.
The reinsurance chain assessed end to end by practising reinsurance brokers, from submission intake through to closings and reporting.
Regure runs separate infrastructure per region, so data residency is a deployment choice rather than a custom build.
Each stage has its own operating detail. These pages go through them one at a time.
Market panel, approaches and responses, order, written and signed lines, capacity against cession, and closing readiness.
Slip, debit note to the cedant and a credit note per reinsurer, with commission, brokerage, taxes and multi-currency conversion.
Single-risk placement end to end, where the operational cost is turnaround and repetition rather than complexity.
Structures and participations, premium mechanics across the period, adjustments and claims against the treaty.
No lines of business, no currencies, no cedants, no markets, no commission rates and no tax rules are hardcoded. They are your configuration — which is what makes the same platform work for operations that look nothing like each other.
Quota share, surplus, excess of loss, facultative — the structure drives how premium is built, and the vocabulary is yours rather than a fixed list you have to map onto.
Deal currency, settlement currency per market and the rates applied are configuration. Commission, brokerage and tax treatment follow the way your agreements are actually written.
Slips, debit notes, credit notes and endorsement closings carry your layout and branding, not ours.
That configuration is set up with you and maintained as part of the Regure operating process, so a change to a structure, a rate or a template is an operating request rather than a development project. See how configuration works.
Facultative and treaty broking houses placing across market panels, where the placement and the closing are the product.
Firms whose lines, currencies and commission structures do not fit an off-the-shelf configuration and who have been told that means custom development.
DIFC and ADGM operations, the wider Middle East, India, Africa and London-adjacent desks — books written across several currencies with counterparties in more than one jurisdiction on the same placement.
Regional broking rarely happens in one currency or one jurisdiction. None of that is a special case here — it is the ordinary shape of a deal.
A deal is written in its own currency. Where a market settles in another, the figure stays in the deal currency and the converted table carries the rate applied — so a credit note to a European reinsurer and the cedant's position in dollars or dirhams reconcile without a spreadsheet in between. See closings and documentation.
A Gulf placement typically runs across regional capacity, London and continental Europe on a single panel, each participant carrying its own written and signed share. The panel is the record; where the participants happen to be licensed does not change how it behaves. See placement and participation.
DIFC and ADGM broking operations run the same deal, panel and closing structure as a London or European desk. Lines, currencies, cedants, markets, commission and tax rules are configuration rather than code, so a regional book does not need a bespoke build to be modelled properly.
Regure deploys on regional infrastructure, so data residency is a deployment decision rather than a custom build — which matters when the counterparties on a single placement sit under different regimes. See security and infrastructure.
Yes. The structure is part of your configuration — quota share, surplus, excess of loss and facultative all work, and the premium engine builds premium according to the structure. Treaty support covers quota share, surplus and excess of loss structures with their period, participations, premium mechanics, endorsements and adjustments — the shapes most broking books are written on.
It is read and turned into a structured deal — cedant, insured, class and sub-class, geography, period, currency, sum insured, premium, retention and cession — which you review and correct before creating the deal. Extraction improves considerably once it has seen the formats your cedants actually send.
The cession is split across the markets on the deal, with ceding commission and brokerage applied per market, and the totals reconcile. Where your business uses them, deposit and minimum premium, instalments, profit commission, no-claims bonus and tax lines are configured as well.
Yes. The figure stays in the deal currency and the converted table carries the rate applied, so a credit note to a market settling in euros shows both the deal-currency position and the conversion.
The slip, the debit note to the cedant and a credit note per reinsurer, plus closings for endorsements and claims — generated from the deal on your own template, and recorded against the deal.
Yes, and it is a common deployment. Where you have a policy administration or accounting platform holding the book of record, Regure takes the reinsurance workflow that the core does not model well — the market panel, written and signed lines, premium allocation across markets and the closings — and the figures that matter downstream go to the core. What that handover looks like is configured in implementation against the systems you actually run.
Yes. Broking houses running on spreadsheets and Word templates typically deploy it this way: submissions, deals, placement, premium, closings, endorsements, claims and reporting all live on the same record. This is the model where the operational gain is largest, because nothing has to be reconciled back to a second system.
Not structurally. The deal, the market panel and the closings behave the same way as they do for a London or European desk. What varies is configuration — the currencies you write in, the markets on your panels, the commission and tax rules — and where the deployment sits, since data residency is a deployment choice and regional infrastructure is available. Facultative energy, construction and marine business, which makes up much of the regional book, runs on the same facultative cycle as any other class.
Yes. Each part of the module is enabled per operation, so a firm can start with submissions and placement and add closings, endorsements, claims validation and sanctions records as it makes sense. Nothing needs to be turned on that you do not use.
Configured. No lines of business, currencies, cedants, markets, commission rates or tax rules are written into the platform. Today our implementation team configures it with you; we are progressively opening the same surface to customer implementation managers.
We will come back within one business day. Telling us which part of the chain hurts most means the session is spent on that rather than on a tour of everything.
A 30-minute working session on your own material. We read the submission, structure the deal, build the premium, place it across a panel and generate the closings.