Bordereau Resubmission Handling Without Double-Counting
On this page
- Key Takeaways
- What Types of Bordereau Resubmission Do Cedents Send?
- What Versioning Rules Should Bordereau Resubmissions Follow?
- How Does a Corrected Bordereau Get Double-Counted?
- Which Tests Catch a Double-Counted Bordereau Resubmission?
- How Should a Resubmission Be Handled After Settlement?
- Who Should Approve a Bordereau Resubmission?
- How Does Insurnest Support Bordereau Resubmission Handling?
- What Should a Head of Bordereaux Operations Change First?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
The cedent's corrected March bordereau arrives with a short email: "Please use this version instead."
Two weeks later, the reinsurer's ceded premium for March is almost double the cedent's figure, and both versions are sitting in the system.
Bordereau resubmission handling is the process for applying a corrected premium or claims bordereau so it replaces or adjusts the earlier version exactly once.
Getting it right means versioning rules that every sender follows, a declared correction type, and tests that compare each new version with the last.
Key Takeaways
- "Use this version instead" is not a processing rule. Every resubmission needs a declared type and version number.
- Supersede, never add. A corrected file replaces or adjusts; it is never new business.
- A delta loaded as a replacement is just as dangerous. It can wipe out a period's premium.
- Row-level keys make corrections safe. Transaction numbers link each corrected row to its original.
- Settled periods need adjustments, not reopening. Corrections flow through the next account.
What Types of Bordereau Resubmission Do Cedents Send?
Cedents send three types of bordereau resubmission, and each must be processed differently.
| Type | What the sender means | How to process | Risk if mishandled |
|---|---|---|---|
| Full replacement | Every row for the period, restated | Retire the earlier version; load this one | Loaded as additional: everything counted twice |
| Delta | Only the rows that changed | Apply rows against the matching originals | Loaded as replacement: all unchanged rows lost |
| Reversal and rebook | Negative rows cancelling errors, plus corrected rows | Load as additional, check reversals match originals | Reversal without a match: premium cut twice |
The sender often does not say which type it is. An email saying "updated file" can mean any of the three.
How should a reversal-and-rebook resubmission be checked?
A reversal-and-rebook resubmission should be checked by matching every negative row to an original row with the same transaction number and amount.
If a cedent reverses 40 duplicate rows at -80,000, those 40 reversals must point to 40 rows in the original file that total 80,000.
A reversal that matches nothing is itself an error. It removes premium that was never duplicated, so the period ends up understated.
What Versioning Rules Should Bordereau Resubmissions Follow?
Bordereau resubmissions should follow rules that make each file's identity, type and relationship to earlier versions explicit.
| Rule | Why it matters | Example |
|---|---|---|
| Identify contract, period, bordereau type and version | Stops a March file replacing April | UMR, 2026-03, premium, v2 |
| Declare the correction type on the file | Decides replace, apply or add | "Full replacement" in the header or submission note |
| Give every row a stable transaction number | Links corrected rows to originals | Same number in v1 and v2 for an unchanged policy |
| Keep the original read-only | Preserves the audit trail and the reason for change | v1 retained and marked superseded |
| Record a reason code | Separates data errors from late business | Duplicate rows, missing policies, wrong premium |
| Check settlement status first | Settled periods need an adjustment route | v1 settled: correction goes through the next account |
| Set a correction deadline | Stops versions arriving months later | Before the next bordereau is due |
Lloyd's reporting standard v5.2 has a mandatory Transaction Number field (CR0230M), per Lloyd's premium bordereaux procedure.
Lloyd's market bulletin Y5311 on Conditions of Trade proposed that corrections be made no later than the next bordereau, once market prerequisites were in place.
Both apply to Lloyd's delegated authority data. Treaty bordereaux elsewhere follow their own contract terms, but the same logic travels well.
Mapping each sender's file layout comes before any of this. See bordereau template mapping.
How Does a Corrected Bordereau Get Double-Counted?
A corrected bordereau gets double-counted when the processing route does not match the correction type. This example is illustrative.
A quota share cedes 60% of premium. Reinsurer A holds a 30% share of the ceded portion.
| Version | Rows | Gross premium |
|---|---|---|
| v1, original March bordereau | 1,240 | 2,480,000 |
| Errors found | 40 duplicate rows, 12 missing policies, 5 rows understated | -80,000, +36,000, +9,000 |
| v2, full replacement | 1,212 | 2,445,000 |
The rows reconcile: 1,240 - 40 + 12 = 1,212. The premium reconciles: 2,480,000 - 80,000 + 36,000 + 9,000 = 2,445,000.
What does each processing outcome do to the reinsurer's share?
Each processing outcome changes reinsurer A's share, and only one is right.
| Processing outcome | Gross premium | Ceded at 60% | Reinsurer A at 30% |
|---|---|---|---|
| Correct: v2 replaces v1 | 2,445,000 | 1,467,000 | 440,100 |
| Correction ignored: v1 stays | 2,480,000 | 1,488,000 | 446,400 |
| Double-counted: v2 added to v1 | 4,925,000 | 2,955,000 | 886,500 |
| Delta of 57 rows loaded as replacement | -35,000 | -21,000 | -6,300 |
The double-count overstates reinsurer A by 446,400, which is exactly v1's share: 2,480,000 × 60% × 30%.
The last row shows the opposite failure. Had the cedent sent only the 57 changed rows, net -35,000, as a delta, loading it as a replacement leaves March negative.
Do claims bordereaux double-count the same way?
Claims bordereaux double-count the same way, and the damage is usually larger because cash moves.
A paid claim of 150,000 in both v1 and v2 is collected twice. Reinsurer A pays 150,000 × 60% × 30% = 27,000 too much.
Recovering an overpaid claim is slower than reversing a premium entry, so claims resubmissions deserve a second check.
Which Tests Catch a Double-Counted Bordereau Resubmission?
The tests that catch a double-counted bordereau resubmission compare the new version with the previous one before anything is booked.
| Test | What it catches |
|---|---|
| Period total vs prior version | A jump near 100% signals a version added, not replaced |
| Transaction numbers across versions | The same number active twice |
| Policy count vs prior version | Counts far above the correction's stated change |
| Premium or claim register comparison | Booked totals above what the registers support |
| Settlement status of the period | A correction aimed at an account already settled |
Set a tolerance for each test. A replacement that moves the period total by more than its stated corrections needs a second look.
Run the tests on premium and claims bordereaux separately. A claims version can change while the premium file for the same period stays the same.
Cut-off rules decide which period a late row belongs to. See bordereaux cut-off dates.
How Should a Resubmission Be Handled After Settlement?
A resubmission after settlement should usually be handled as an adjustment in the next account, linked back to the original period.
Reopening a settled account changes figures that both parties have agreed and paid. The treaty terms and accounting policy decide the exact route.
Keep the link between the adjustment and the superseded version. Our guide to reinsurance data lineage explains why that trail matters.
Settled cash should then be checked in reinsurance settlement reconciliation.
Who Should Approve a Bordereau Resubmission?
A bordereau resubmission should be approved at a level that rises with its size and with how far the period has progressed.
| Situation | Approver | Evidence |
|---|---|---|
| Before booking, change within tolerance | Bordereaux analyst | Version comparison results |
| Before booking, change above tolerance | Bordereaux team lead | Reason codes and row-level differences |
| Period already settled | Finance, with the bordereaux lead | Adjustment entry linked to the original period |
| Claims bordereau with paid claims changed | Claims and finance | Claim-level list of changed payments |
Tolerances should be set per contract. A small binder and a large quota share should not share one threshold.
How Does Insurnest Support Bordereau Resubmission Handling?
Insurnest does not manage bordereau versions. Version control, correction types and the replace-or-adjust decision stay with your team.
Insurnest Bordereaux Calculation and Reconciliation maintains participation percentages and allocates premium and claims by reinsurer share.
It compares calculated values with bordereaux, master data, premium and claim registers and settlement records, and shows reinsurer-wise status.
A version loaded twice can then appear as a variance against the registers. Finding why it happened stays with your team.
What Should a Head of Bordereaux Operations Change First?
A head of bordereaux operations should change the intake rule first: no resubmission is processed without a declared type and version.
- Publish a resubmission note template. Contract, period, type, version, reason code and row count.
- Require transaction numbers. Agree a stable row key with each cedent or coverholder.
- Run the version comparison before booking. Period total, row count and duplicate keys.
- Route settled periods to adjustment. Never reopen without finance sign-off.
Key Terms
- Full replacement: A resubmitted bordereau that restates every row for the period.
- Delta bordereau: A resubmission containing only the rows that changed.
- Reversal and rebook: Negative rows that cancel errors, followed by corrected rows.
- Transaction number: A row-level reference used to match each row across versions.
- Superseded version: An earlier bordereau kept read-only after a replacement.
Sources
Frequently Asked Questions
What is bordereau resubmission handling?
Bordereau resubmission handling is the process for receiving a corrected premium or claims bordereau and processing it so it replaces or adjusts the earlier version exactly once. It covers version identification, the type of correction, row-level matching and accounting for periods already settled.
Why do resubmitted bordereaux cause double-counting?
Resubmitted bordereaux cause double-counting when the corrected file is loaded as new business instead of replacing the original. Every row then appears twice, so premium and claims for the period are roughly doubled, and each reinsurer's share is overstated by the full original amount.
What is the difference between a full replacement and a delta bordereau?
The difference between a full replacement and a delta bordereau is what the file contains. A full replacement restates every row for the period, while a delta contains only corrections. Processing a delta as a full replacement can wipe out the period's premium entirely.
How do you process a corrected bordereau without double-counting?
To process a corrected bordereau without double-counting, identify the contract, period, type and version, confirm whether it is a full replacement or delta, match rows on transaction number, supersede the earlier version rather than adding to it, and compare the new period total with the prior version.
What should happen if the original bordereau was already settled?
If the original bordereau was already settled, the correction should usually go through the next account as an adjustment linked to the original period, rather than reopening a closed settlement. The treaty or binder terms and the accounting policy decide the exact treatment.
What does Lloyd's say about bordereau corrections?
Lloyd's market bulletin Y5311 on Conditions of Trade for delegated authority data proposed that corrections be made no later than the next bordereau, once market prerequisites were met. That applies to Lloyd's coverholder data; other markets and treaty bordereaux follow their own contract terms.
Why is a row-level transaction number important for resubmissions?
A row-level transaction number is important for resubmissions because it lets each corrected row be matched to the row it replaces. Without a stable key, a policy that appears in both versions cannot be told apart from two different policies, and duplicates go unnoticed.
Does Insurnest handle bordereau resubmission versions?
Insurnest does not handle bordereau resubmission versions. Insurnest Bordereaux Calculation and Reconciliation allocates premium and claims by reinsurer share and compares calculated values with bordereaux, registers and settlement records, so teams still own version control and the replace-or-adjust decision.

Hitul Mistry
CEO, Insurnest
An InsurTech leader with more than a decade of experience across insurance and technology, focused on solving business problems with the help of technology. Has worked with brokers, insurance carriers, and reinsurance firms across the India, UAE, and US markets.
View LinkedIn profile →