Reinsurance

Historical Bordereaux Loading for Reinsurers: Tie-Out Plan

On this page

Last reviewed: November 2026

"Load the old files as they are. We will clean them once they are in the new system."

Two years later, 2023 premium in the new system still differs from the ledger by USD 476,000. Nobody knows which file caused it.

Historical bordereaux loading for reinsurers is bringing back-years of cedent bordereaux into a new system.

Done properly, the loaded totals agree with what was booked in the ledger at the time.

This guide gives you a five-stage table, a layout vintage mapping example and a worked five-year tie-out with a tolerance.

Key Takeaways

  • Inventory before mapping. Know every file, gap and resubmission first.
  • Map by vintage, not by file. Layouts change; each layout gets one mapping.
  • Tie out to the ledger. Loaded totals must agree with booked accounts within a tolerance.
  • Sign off before load. Once loaded, history is hard to correct.

What Stages Does Historical Bordereaux Loading for Reinsurers Follow?

Historical bordereaux loading for reinsurers follows five stages, each with an owner and evidence kept.

StageTriggerActionOwnerEvidence kept
1. File inventoryDecision to load back-yearsList every file by cedent, period, version and receipt date; mark gaps and resubmissionsReinsurance data leadInventory with row counts and control totals
2. Vintage mappingInventory agreedGroup files by layout; map each layout's columns to target fieldsData lead with bordereaux teamSigned vintage mapping table
3. ValidationMapping approvedCheck row counts, control totals, field rules, date ranges and duplicatesBordereaux analystsValidation log per file
4. Tie-out to ledgerValidation passedCompare totals by year and cedent with booked accountsTechnical accountingTie-out schedule with explanations
5. Sign-off and loadAll years within toleranceApprove, load and freeze source filesHead of reinsurance accounting and data ownerSign-off memo

Why does a file inventory come first in historical bordereaux loading?

A file inventory comes first in historical bordereaux loading because gaps and resubmissions must be known before mapping.

Record each file's row count and control total at inventory. Later stages compare against those numbers.

Where a cedent sent a resubmitted file, record which version it replaces. Bordereau resubmission handling sets the rules.

What are layout vintages in historical bordereaux?

Layout vintages in historical bordereaux are runs of periods in which a cedent used the same file layout.

Even market standards change.

Lloyd's Coverholder Reporting Standards v5.2 added fields, such as Spanish risk postcodes from 1 June 2019. Older files lack them.

Below is an illustrative vintage map for one cedent's quota share, 60 monthly files from 2021 to 2025.

VintagePeriods (files)LayoutKey differenceMapping rule
V1Jan 2021 to Jun 2022 (18)18 columns, one sheet"Premium" is net of 25% commission; no currency column; day-first datesGross = premium ÷ 0.75; currency USD; parse day first
V2Jul 2022 to Dec 2023 (18)24 columnsGross premium and commission split; currency column addedMap directly; check commission is 25% of gross
V3Jan 2024 to Dec 2025 (24)31 columns, risk and premium tabsTabs joined by policy number; transaction type addedJoin on policy and endorsement number; use transaction type

A V1 row showing USD 7,500 premium loads as USD 10,000 gross, because 7,500 ÷ 0.75 = 10,000.

Mapping one vintage at a time is covered in bordereau template mapping.

What should validation check in historical bordereaux before tie-out?

Validation of historical bordereaux before tie-out should check each file against its inventory row count and control total.

Then test field rules: dates inside the period, no blank policy numbers, currencies on the treaty list and no duplicate rows.

Log every fix by file. A quality score per cedent, as in ceded data quality scores, shows where to look first.

How Should Historical Bordereaux Be Tied Out to the Ledger?

Historical bordereaux should be tied out to the ledger by comparing loaded premium with booked premium by year and cedent.

Here, the tolerance is 0.1% of each year's booked premium. Figures are illustrative.

YearFilesLoaded bordereaux premium (USD)Booked ledger premium (USD)Difference (USD)Tolerance (USD)Result
20211218,420,00018,420,000018,420Pass
20221221,035,40021,050,000-14,60021,050Pass
20231223,912,00024,388,000-476,00024,388Fail
20241226,104,25026,090,000+14,25026,090Pass
20251228,760,00028,760,000028,760Pass
Total60118,231,650118,708,000-476,350

The yearly differences add to the total: 0 − 14,600 − 476,000 + 14,250 + 0 = −476,350.

The 2023 gap was the original October 2023 file, loaded instead of its resubmission, which was USD 476,000 higher.

After the swap, 2023 shows zero difference. The remaining total gap of −USD 350 is rounding, within tolerance in both years.

What tolerance should a historical bordereaux tie-out use?

A historical bordereaux tie-out should use a tolerance agreed with finance before testing, so nobody moves it afterwards.

Set it tight enough that one missing monthly file fails. Here, one month is about USD 2m against a tolerance near USD 24,000.

Where Do Handoffs Break in Historical Bordereaux Loading?

Handoffs break in historical bordereaux loading where one team assumes another has already checked the totals.

  • Inventory to load. The loader picks files by name, not by the version the inventory marked.
  • Mapping to validation. A vintage rule, such as net to gross, is applied to the wrong periods.
  • Data to finance. Data signs off row counts; finance assumed it signed off money.
  • Project to operations. Source files are not frozen, so someone "fixes" one after sign-off.

Each break leaves a gap that only the tie-out finds. Keep lineage notes, as in reinsurance data lineage.

Wider system risks are covered in managing change risk during core system migration.

What Does a Dated Historical Bordereaux Loading Timeline Look Like?

A dated historical bordereaux loading timeline for 60 monthly files runs about six weeks. This one is illustrative.

DateEvent
4 Jan 2027Kick-off: one cedent, 2021 to 2025, tolerance agreed at 0.1%
8 Jan 2027Inventory: 63 files received, 3 are resubmissions, 60 periods
15 Jan 2027Vintage map for V1 to V3 signed
29 Jan 2027Validation complete; two date-range errors fixed in V2
5 Feb 2027Tie-out: 2023 fails by USD 476,000
9 Feb 2027Cause found: October 2023 original loaded; resubmission swapped in
12 Feb 2027All years pass; sign-off memo issued; files frozen

How Many Years of Bordereaux History Should a Reinsurer Load?

A reinsurer should load as many years of bordereaux history as its pricing and reserving need to see trends.

Solvency II Delegated Regulation 2015/35, Article 19 treats data as complete when it holds enough history to identify trends.

The same article expects data from different periods to be consistent. That is what vintage mapping protects.

For development data, see loss triangle data preparation.

How Does Insurnest Help Once Historical Periods Are Loaded?

Reinsurance Bordereaux Reconciliation does not load historical files, map layouts or convert formats.

Once periods are in, it calculates each reinsurer's share of premium and claims from configured participation.

It compares those values with bordereaux, master and settlement records, and flags differences for investigation.

Allocated totals tie back to the bordereaux received. The platform identifies the difference; finance teams determine the cause.

Key Terms

  • Layout vintage: A run of periods in which a cedent sent bordereaux in one layout.
  • Tie-out: A comparison of loaded totals with booked amounts, with differences explained.
  • Tolerance: The largest difference accepted without investigation, agreed before testing.

Sources

Frequently Asked Questions

What stages does historical bordereaux loading for reinsurers follow?

Historical bordereaux loading for reinsurers follows five stages: file inventory, layout vintage mapping, validation, tie-out to the booked ledger and sign-off before load.

Why does a file inventory come first in historical bordereaux loading?

A file inventory comes first in historical bordereaux loading because missing months, duplicates and resubmitted files must be known before anything is mapped or loaded.

What are layout vintages in historical bordereaux?

Layout vintages in historical bordereaux are groups of periods in which a cedent used the same file layout. Each vintage needs its own mapping to the target fields.

How should historical bordereaux be tied out to the ledger?

Historical bordereaux should be tied out to the ledger by comparing loaded totals with booked amounts by year and cedent, then explaining every difference above an agreed tolerance.

What tolerance should a historical bordereaux tie-out use?

A historical bordereaux tie-out should use a tolerance agreed with finance before testing starts, such as 0.1% of booked premium per year, so rounding passes and missing files fail.

Where do handoffs break in historical bordereaux loading?

Handoffs break in historical bordereaux loading between inventory and load, mapping and validation, and data and finance, where each team assumes the other checked the totals.

What does a dated historical bordereaux loading timeline look like?

A dated historical bordereaux loading timeline runs from kick-off through inventory, mapping, validation and tie-out to sign-off, about six weeks for 60 monthly files in the example.

How many years of bordereaux history should a reinsurer load?

A reinsurer should load as many years of bordereaux history as its pricing and reserving need to see trends, and no fewer than its triangles and treaty periods require.

Hitul Mistry

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 →
ShareLinkedInX

Read our latest blogs and research

Featured Resources

Reinsurance

Bordereau Template Mapping: Onboard New Cedent Formats Fast

Bordereau template mapping as a reusable specification: header, field map, code tables, control totals and change log, so new cedent formats onboard cleanly.

Read more
Reinsurance

Loss Triangle Data Preparation: Pricing-Ready Triangles

Loss triangle data preparation from a cedent claims listing: a field mapping table, a worked mini triangle (cumulative vs incremental) and a data error table.

Read more
Reinsurance

Reinsurance Data Lineage: From Bordereau to Capital Filing

Reinsurance data lineage traces every number from bordereau to capital filing. Learn why end-to-end traceability is now a regulatory expectation, not a data-governance luxury.

Read more

Meet Our Innovators:

We aim to revolutionize how businesses operate through digital technology driving industry growth and positioning ourselves as global leaders.

circle basecircle base
Pioneering Digital Solutions in Insurance

Insurnest

Empowering insurers, re-insurers, and brokers to excel with innovative technology.

Insurnest specializes in digital solutions for the insurance sector, helping insurers, re-insurers, and brokers enhance operations and customer experiences with cutting-edge technology. Our deep industry expertise enables us to address unique challenges and drive competitiveness in a dynamic market.

Get in Touch with us

Ready to transform your business? Contact us now!

We respond within one business day.