Premium, claims and cession bordereaux in any partner layout, checked row by row against binder terms as the file lands, then generated back out in the format the receiving party requires. Exceptions queued with reasons and sources before anyone opens the spreadsheet.
| Clm Ref | Pol No | DOL | Paid | O/S Res |
|---|---|---|---|---|
| CL-8802 | HX-40219 | 3/5/26 | 4,200.00 | 12,000.00 |
| CL-8815 | HX-40221 | 11-May-2026 | 0.00 | 35,500.00 |
| CL-8820 | HX-40230 | 2026/05/19 | 18,750.00 | 0.00 |
| CL-8829 | HX-40236 | 27.5.26 | 2,310.40 | 6,000.00 |
| CL-8833 | HX-40240 | 02/06/2026 | 9,875.00 | 15,125.00 |
| CL-8841 | HX-40377 | 14/7/25 | 26,400.00 | 40,000.00 |
| Claim ref | Certificate | Date of loss | Paid in period | Outstanding |
|---|---|---|---|---|
| CL-8802 | HX-40219 | 2026-05-03 | 4,200.00 | 12,000.00 |
| CL-8815 | HX-40221 | 2026-05-11 | 0.00 | 35,500.00 |
| CL-8820 | HX-40230 | 2026-05-19 | 18,750.00 | 0.00 |
| CL-8829 | HX-40236 | 2026-05-27 | 2,310.40 | 6,000.00 |
| CL-8833 | HX-40240 | 2026-06-02 | 9,875.00 | 15,125.00 |
| CL-8841 | Held back for review, row left untouched | |||
147 of 148 claims clean and sent on in the carrier's format. 1 held with a reason; checked against May's file and the risk bordereau.
Premium records audited for one specialty reinsurer
Years of premium and claims bordereaux, reconciled end to end
Uplift in true profitability the audit found
From the file that lands to the bordereau that goes back out.
Premium and risk, claims, and cession files come in as the partner or coverholder already sends them. Per-programme templates are mapped once. Data can push into your data lake or your other systems.
See how ingestion works →Every row is checked against the programme’s own rules the moment the file lands, before anyone opens it.
See the rule library →Bordereaux checked against each other and against every prior month: written against paid, risk against premium against claims. Runs as a recurring monthly audit across every programme.
See what the audit checks →The output is a validated bordereau, generated in the format the receiving party requires, or pushed into their systems.
See the output →Works on premium and risk bordereaux and claims bordereaux. Reinsurers processing cedant statements and cash calls: see the Reinsurance Accounting Analyst.
Validation runs the moment a file lands. A sample of what runs:
Every file diffed against the last one you accepted, so nothing changes silently between periods.
Totals recomputed on every row, so the file balances before it moves anywhere.
Rates validated against the binder, row by row, not sampled.
Repeats flagged before they inflate the month.
Rows present last period and missing this one, surfaced instead of silently gone.
Every check is named and explained in the validation check library.
No bank statement required. Runs as a recurring monthly audit across every programme.
What was written checked against what was paid, without waiting on a bank statement.
The three bordereaux for a programme checked against each other, not read in isolation.
Balances that have been outstanding longer than the programme allows.
A line on the paid bordereau with no written line behind it.
An endorsement that doesn’t tie back to the policy it is meant to adjust.
Ingestion is half the job. The other half is producing the file the other end needs, in their format, on their deadline.
Normalised to one schema, then generated back out to the layout the receiving party requires: a carrier template, a syndicate layout, your own.
A partner file, a PAS extract, or a feed straight from your data warehouse. Whatever holds the written premium record.
Validated line items hand off directly to the Reconciliation Analyst as the expected side of the match. Once cash balances, the capacity bordereau and per-carrier remittance reports are generated there.
Golden-schema export, or posted to your PAS, general ledger or data lake. Your systems of record stay canonical.
The Bordereaux Analyst reads any inbound layout, validates it, and writes it back out in the format the receiving party requires. The Reconciliation Analyst tells you whether the money arrived, and generates the capacity bordereau and remittance reports once it balances. A validated bordereau hands off directly as the expected side of the match. Same rule library, same evidence trail, one exception queue.
One engine. Rules, tolerances and evidence shared across every Analyst.
Both. The Analyst reads source data in whatever form it arrives, a partner file, a PAS extract, or a feed straight from your data warehouse, normalises it to one schema, and generates the validated bordereau back out in the format the receiving party requires, whether that is a carrier template or a syndicate layout. The capacity bordereau is generated separately, by the Reconciliation Analyst, once cash is matched against the validated line items. Brisc reads bordereaux and writes them.
No. That is the work, not the prerequisite. The Analyst takes the layout each partner actually sends, maps it once with your operations team, and reuses that mapping every month. A validated file is a good input, but nothing has to be cleaned up before you start.
Whatever your partners send: Excel, CSV, PDF, any layout, market-standard and not-remotely-standard alike. The Analyst maps a partner’s layout once and the mapping persists per program, so month two isn’t month one again. No new templates, no format mandates.
At ingestion. Every row is checked as the file lands, so by the time anyone opens it the exceptions are already queued with their evidence. There’s no separate validation step to schedule, and none to forget.
No. Anything that fails a check is flagged with the reason and the source attached, queued for your team’s judgment. Nothing is silently corrected, and nothing changes without a person deciding it should.
30 minutes, no slide deck. We run your real files, any format. Your book is specific; the walkthrough should be too.
Book the walkthrough