Multi-Treaty Reinsurance Bordereaux Files: Routing Rules
On this page
- Key Takeaways
- What Are Multi-Treaty Reinsurance Bordereaux Files?
- Which Fields Decide the Treaty for Each Bordereau Row?
- What Routing Rules Send Each Row to the Right Treaty and Year?
- How Do You Route a Ten-Row Bordereau Across Three Treaties?
- How Do You Prove Control Totals Per Treaty After Splitting a Bordereau?
- How Does Insurnest Reconcile Multi-Treaty Bordereaux Once Rows Are Routed?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
The cedent's Q3 file had 4,200 rows and one tab. It covered two property years, an engineering treaty and some marine rows nobody had reinsured.
The team booked it all to the 2026 property quota share because that was the treaty named in the email.
Multi-treaty reinsurance bordereaux files are single cedent files whose rows must be routed to several treaties, years or sections before booking.
It matters because a row in the wrong treaty year moves premium, claims and commission between reinsurer panels.
This guide gives you an if-then routing table, a worked ten-row split, control totals per treaty and rules for the hold queue.
Key Takeaways
- Route before you calculate. Shares are meaningless on the wrong treaty.
- Attachment basis decides the year. Risks attaching uses inception; losses occurring uses loss date.
- Never default a row. Missing keys go to a hold queue.
- Totals must close. Routed plus held plus excluded equals the file.
What Are Multi-Treaty Reinsurance Bordereaux Files?
Multi-treaty reinsurance bordereaux files are cedent files that mix rows for more than one treaty, underwriting year, class or section.
They appear when cedents report from one system extract, at renewal, and for off-anniversary treaties.
They differ from one treaty with many classes, which is covered in multi-class treaty premium allocation.
Which Fields Decide the Treaty for Each Bordereau Row?
The fields that decide the treaty for each bordereau row are the ones the treaty wordings use to define business covered.
- Class or line code: decides which treaty family can accept the row.
- Policy inception or renewal date: decides the year under risks attaching.
- Loss date: decides the year for claims under losses occurring.
- Original policy reference: links endorsements, cancellations and claims to their policy.
- Currency: decides whether conversion is needed.
- Treaty or section reference: a cedent-supplied check, never the only key.
The RAA glossary defines the basis of attachment as the method that decides which original losses a treaty covers.
It ties underwriting year to the original policy's effective date, and accident year to the loss date.
What Routing Rules Send Each Row to the Right Treaty and Year?
Routing rules send each row to the right treaty and year when applied in a fixed order, with the rule recorded on the row.
| Rule | If | Then |
|---|---|---|
| R1 | Class has no matching treaty | Exclude from cessions; query the cedent |
| R2 | Treaty is risks attaching | Treaty year = year containing policy inception or renewal date |
| R3 | Treaty is losses occurring | Claims: treaty year = year containing loss date; premium per the wording's basis |
| R4 | Row is an endorsement or cancellation | Follow the original policy's treaty and year, not the transaction date |
| R5 | Row currency differs from treaty currency | Convert at the treaty's stated rate source and date |
| R6 | Cedent's treaty reference disagrees with R1 to R4 | Rule result wins for routing; raise a query |
| R7 | Any routing key missing or invalid | Hold queue; do not route |
Treaty periods that do not start on 1 January need R2 applied against their own dates; see off-anniversary treaty renewals.
Mapping cedent policy numbers for R4 is covered in policy number mapping between cedent and reinsurer.
Where should bordereau rows with missing routing keys go?
Bordereau rows with missing routing keys should go to a hold queue that names the missing field and the query sent.
Defaulting them to the current treaty is the most common silent error. Clear the queue before the next cut-off.
Lloyd's coverholder standards make a section reference mandatory for multi-section binders.
Asking cedents for a treaty reference column follows the same logic, as a check on R1 to R4.
How should currency be converted when one bordereau feeds several treaties?
Currency conversion when one bordereau feeds several treaties should follow each treaty's wording, row by row.
If a wording names a source such as ECB euro reference rates, note the ECB publishes them "for information purposes only".
They are usually updated around 16:00 CET each working day. Record the rate, its date and its source on the row.
How Do You Route a Ten-Row Bordereau Across Three Treaties?
To route a ten-row bordereau across three treaties, apply the rule table to each row and write the rule number beside the result.
Illustrative treaties, all risks attaching and in EUR:
- T1 Property QS 2025: policies incepting in calendar 2025.
- T2 Property QS 2026: policies incepting in calendar 2026.
- T3 Engineering QS: policies incepting in the 12 months from 1 April 2026.
| Row | Class | Type | Policy inception | Loss date | Amount (EUR) | Rule | Routed to |
|---|---|---|---|---|---|---|---|
| 1 | Property | AP endorsement | 15 Nov 2025 | None | 2,400 | R4, R2 | T1 |
| 2 | Property | Premium | 1 Jul 2026 | None | 18,000 | R2 | T2 |
| 3 | Property | Premium | 20 Mar 2026 | None | 9,200 (USD 10,000 at treaty rate 0.92) | R5, R2 | T2 |
| 4 | Engineering | Premium | 10 Feb 2026 | None | 6,500 | R7 | Hold: before T3 start, no matching year supplied |
| 5 | Engineering | Premium | 5 May 2026 | None | 12,000 | R2 | T3 |
| 6 | Property | Paid claim | 1 Dec 2025 | 3 Aug 2026 | 40,000 | R2 | T1 |
| 7 | Property | Paid claim | 2 Feb 2026 | 14 Sep 2026 | 15,500 | R2 | T2 |
| 8 | Marine cargo | Premium | 1 Aug 2026 | None | 3,000 | R1 | Excluded: no treaty |
| 9 | Property | Premium | Blank | None | 4,100 | R7 | Hold: inception missing |
| 10 | Property | Cancellation RP | 1 Oct 2025 | None | -1,800 | R4, R2 | T1 |
Row 4 is the trap: it is engineering, but it incepted before T3. It belongs to the prior engineering year, if one exists.
How Do You Prove Control Totals Per Treaty After Splitting a Bordereau?
To prove control totals per treaty after splitting a bordereau, the routed, held and excluded buckets must add back to the file.
| Bucket | Rows | Premium (EUR) | Paid claims (EUR) |
|---|---|---|---|
| T1 Property QS 2025 | 3 (1, 6, 10) | 600 | 40,000 |
| T2 Property QS 2026 | 3 (2, 3, 7) | 27,200 | 15,500 |
| T3 Engineering QS | 1 (5) | 12,000 | 0 |
| Hold queue | 2 (4, 9) | 10,600 | 0 |
| Excluded | 1 (8) | 3,000 | 0 |
| File total | 10 | 53,400 | 55,500 |
Run this check on every file, on rows and on each amount column. A one-row difference means a row was duplicated or dropped.
What happens when a multi-treaty file is routed by loss date instead of policy inception?
When a multi-treaty file is routed by loss date instead of policy inception, row 6 moves from T1 to T2.
The 2026 year then shows EUR 55,500 of paid claims instead of 15,500. The 2025 year shows nil instead of 40,000.
Different panels, or different shares on the same panel, now carry the wrong loss. The error also distorts each year's loss ratio at renewal.
How Does Insurnest Reconcile Multi-Treaty Bordereaux Once Rows Are Routed?
Reinsurance Bordereaux Reconciliation does not route bordereau rows to treaties or validate routing keys.
Once your team has split the file, it calculates each reinsurer's premium share and claim liability from configured participation.
It compares those values with bordereaux, master, premium, claim and settlement records, and surfaces the variances.
It shows which positions are matched and which need review. Your team investigates the cause, including a mis-routed row.
Treaties running over several years need their periods set up correctly first; see multi-year reinsurance treaty.
Key Terms
- Risks attaching: A basis where the original policy's inception decides the treaty year.
- Losses occurring: A basis where the loss date decides the treaty year.
- Hold queue: Rows kept out of all treaties until a missing or conflicting key is resolved.
Sources
- Reinsurance Association of America: Glossary of reinsurance terms
- European Central Bank: Euro foreign exchange reference rates
- Lloyd's: Coverholder Reporting Standards user guide v5.2
- Insurnest: Reinsurance Bordereaux Reconciliation
Frequently Asked Questions
What are multi-treaty reinsurance bordereaux files?
Multi-treaty reinsurance bordereaux files are single cedent files whose rows belong to several treaties, years, classes or sections, and must be split before any share is calculated or booked.
Which fields decide the treaty for each bordereau row?
The fields that decide the treaty for each bordereau row are class, policy inception date, loss date for claims, original policy reference for adjustments, currency and any treaty section reference.
What routing rules send each row to the right treaty and year?
Routing rules send each row by class first, then by the treaty's attachment basis: policy inception date for risks attaching, loss date for losses occurring, with exceptions held rather than defaulted.
How do you route a ten-row bordereau across three treaties?
To route a ten-row bordereau across three treaties, apply the rule table row by row, record the rule used, then prove routed, held and excluded totals equal the file total.
How do you prove control totals per treaty after splitting a bordereau?
To prove control totals per treaty after splitting a bordereau, check that rows and amounts routed to treaties, plus the hold queue and exclusions, equal the file's own totals exactly.
What happens when a multi-treaty file is routed by loss date instead of policy inception?
When a multi-treaty file is routed by loss date instead of policy inception on a risks-attaching treaty, claims move to the wrong underwriting year, overstating one year and understating another.
Where should bordereau rows with missing routing keys go?
Bordereau rows with missing routing keys should go to a hold queue with the missing field named, never to a default treaty, and be queried with the cedent before the next cut-off.
How should currency be converted when one bordereau feeds several treaties?
Currency conversion when one bordereau feeds several treaties should use the rate source and date each treaty's wording specifies, recorded per row, with silent wordings queried rather than assumed.

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 →