Inception Date Checks on Reinsurance Bordereaux: Rule Table
On this page
- Key Takeaways
- What Are Inception Date Checks on Reinsurance Bordereaux?
- Which Date Decides the Treaty Year on a Risks Attaching or Losses Occurring Treaty?
- What Decision Table Assigns a Bordereau Policy to the Right Treaty Year?
- Which Excel Formulas Test Inception Dates on a Bordereau?
- How Do Six Illustrative Policies Route Under the Inception Date Rules?
- How Does Insurnest Support Inception Date Checks on Reinsurance Bordereaux?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
The 1 January renewal looked clean. Then the cedent's system copied each policy's first-ever inception date onto the renewal rows.
Dozens of renewals landed in an old treaty year. That year had a different panel, a different rate and little limit left.
Inception date checks on reinsurance bordereaux test each row's dates against the treaty's attachment basis to fix its treaty year.
The treaty year decides which reinsurers, rates, commission terms and limits apply to the row.
This guide gives you a treaty-year rule table, copy-ready Excel date tests and six illustrative policies routed by the rules.
Key Takeaways
- The basis picks the date. Risks attaching uses inception; losses occurring uses the loss date and earning.
- Renewals are new attachments. A renewal attaches on its own renewal date, not the first-ever inception.
- Backdating moves rows across years. A policy booked in January can still belong to December's year.
- Test dates before shares. Wrong-year rows produce correct maths on the wrong panel.
What Are Inception Date Checks on Reinsurance Bordereaux?
Inception date checks on reinsurance bordereaux are tests that each row's inception, expiry and booking dates are valid and point to one treaty year.
They run before premium shares are calculated, because every later figure depends on the year.
What happens when a bordereau policy is ceded to the wrong treaty year?
A bordereau policy ceded to the wrong treaty year is shared among the wrong reinsurers, at the wrong rate and commission.
- Panel. Signed lines often change at renewal, so each reinsurer's share is misstated.
- Limits. Losses erode a year that may be exhausted, or miss a year with capacity.
- Commission. Sliding scales and profit commissions are computed on the wrong year's results.
- Closing. Errors found later force reopening; see closing old underwriting years.
Which Date Decides the Treaty Year on a Risks Attaching or Losses Occurring Treaty?
The date that decides the treaty year on a risks attaching or losses occurring treaty depends on the basis of cover in the wording.
The Bank of England's IR.30.03 reporting instructions define both bases for outwards reinsurance returns.
- Losses occurring: covers losses "occurring during the period of the contract". The loss date decides.
- Risks attaching: covers losses to policies "considered to be attached" in the contract period. Inception decides.
On a losses occurring treaty, premium is normally ceded as it is earned; see earned premium calculation in reinsurance.
The Munich Re glossary defines a cutoff: no liability for occurrences after the termination date.
Year labels matter too; underwriting year vs accident year reporting explains both.
What Decision Table Assigns a Bordereau Policy to the Right Treaty Year?
The decision table that assigns a bordereau policy to the right treaty year tests the basis first, then the event that created the row.
| If the row is… | Basis | Date to test | Do this |
|---|---|---|---|
| New policy | Risks attaching | Inception | Year containing inception |
| Renewal | Risks attaching | Renewal date | Year containing renewal date; reject first-ever inception |
| Backdated | Risks attaching | Inception, not booking | Year containing inception; flag if booked over 30 days late |
| Mid-term endorsement | Risks attaching | Parent inception | Parent's year, unless wording treats increases as new risks |
| Cancellation or reinstatement | Either | Parent dates | Reverse in the parent's year, never a new year |
| Policy over 12 months | Risks attaching | Inception and term | Inception year; check the maximum period clause |
| Premium row | Losses occurring | Inception and expiry | Split by days earned in each treaty year |
| Claim row | Risks attaching | Parent inception | Year the policy attached to |
| Claim row | Losses occurring | Date of loss | Year containing the loss date |
| Expiry on or before inception | Either | Both dates | Reject to cedent |
| Inception after period end | Either | Inception vs bordereau period | Hold and query the future-dated row |
The 30-day tolerance is illustrative. Set your own and write it into the bordereau agreement.
How should backdated policies be treated on a risks attaching treaty?
Backdated policies on a risks attaching treaty belong to the year containing their inception date, even when booked in the next period.
Add a known-loss check: a loss dated before the booking date on a backdated policy needs a query before it is accepted.
Does a bordereau cut-off date change a policy's treaty year?
A bordereau cut-off date does not change a policy's treaty year. It only decides which bordereau reports the row.
Keep the two rules apart, as set out in bordereaux cut-off dates.
Which date applies to a mid-term endorsement on a bordereau?
The date that applies to a mid-term endorsement on a bordereau is, by default, the parent policy's inception on risks attaching business.
Check the wording first: some treaties treat a mid-term increase in sum insured as a new attachment.
On a losses occurring treaty, the endorsement's premium is earned from its effective date to expiry.
Which Excel Formulas Test Inception Dates on a Bordereau?
Excel formulas that test inception dates on a bordereau need six columns: basis, inception, expiry, booked date, treaty start and treaty end.
Assume row 2 holds B basis, C inception, D expiry, E booked date, F treaty start and G treaty end.
Treaty year, 1 January anniversary =YEAR(C2)
Treaty year, 1 April anniversary =YEAR(EDATE(C2,-3))
Inception outside treaty period =OR(C2<F2, C2>G2)
Expiry not after inception =D2<=C2
Backdated over 30 days =E2-C2>30
Term over 18 months =D2>EDATE(C2,18)
Losses occurring share in period =MAX(0,MIN(D2,G2+1)-MAX(C2,F2))/(D2-C2)
Text date, not a real date =NOT(ISNUMBER(C2))
Microsoft's EDATE function returns a date a set number of months from a start date.
Run the text date test first. A text date such as 03/04/2026 can be read as March or April, depending on locale.
How Do Six Illustrative Policies Route Under the Inception Date Rules?
Six illustrative policies on one Q1 2026 bordereau show how the inception date rules change the treaty year.
Treaty A is a risks attaching quota share renewing each 1 January. Treaty B is losses occurring from 1 January; Treaty C renews each 1 April.
| Policy | Row | Dates on bordereau | Cedent's year | Rule outcome |
|---|---|---|---|---|
| P1 | New, Treaty A | Inception 10 Feb 2026, booked 12 Feb 2026 | 2026 | 2026, pass |
| P2 | Renewal, Treaty A | Inception field 1 Jan 2024; renewed 1 Jan 2026 | 2024 | 2026; fix the field |
| P3 | Backdated, Treaty A | Inception 15 Dec 2025, booked 20 Jan 2026 | 2026 | 2025; 36 days late, no loss before 20 Jan |
| P4 | Endorsement, Treaty A | Parent incepted 1 Jul 2025; extra premium from 1 Mar 2026 | 2026 | 2025 by default; check wording |
| P5 | New, Treaty B | 1 Oct 2025 to 1 Oct 2026; loss 5 Feb 2026 | 2025 | Premium 92/365 = 25.2% to 2025, 74.8% to 2026; loss to 2026 |
| P6 | New, Treaty C | Text "03/04/2026" | 2025 (read as 4 March) | 2026 if 3 April; confirm format |
Only P1 passed untouched. Every other row needed a year change, a premium split or a query to the cedent.
Run rate checks on reinsurance bordereaux after the years are fixed, not before.
Then use reinsurance bordereaux period comparison to spot rows that jumped between years.
How Does Insurnest Support Inception Date Checks on Reinsurance Bordereaux?
Reinsurance Bordereaux Reconciliation does not validate dates on the bordereau file. The checks above stay with your team.
Once rows sit in the right year, it calculates each reinsurer's premium share from that year's configured participation.
It compares calculated values with bordereaux, premium and settlement records, and shows which positions match and which need review.
The platform identifies the difference; your team investigates whether a date caused it.
Key Terms
- Risks attaching: A basis covering losses on policies that attach during the treaty period, whenever the loss occurs.
- Losses occurring: A basis covering losses that occur in the treaty period, whatever the policy's inception date.
- Backdated policy: A policy booked after its stated inception date.
Sources
- Bank of England: IR.30.03 Non-life outwards reinsurance contract information, instructions
- Munich Re: Reinsurance Glossary
- Microsoft Support: EDATE function
- Insurnest: Reinsurance Bordereaux Reconciliation
Frequently Asked Questions
What are inception date checks on reinsurance bordereaux?
Inception date checks on reinsurance bordereaux test each row's inception, expiry and booking dates against the treaty's attachment basis, so every policy lands in one correct treaty year.
What happens when a bordereau policy is ceded to the wrong treaty year?
A bordereau policy ceded to the wrong treaty year is shared among the wrong panel, at the wrong rate and commission, and its losses erode the wrong year's limits.
Which date decides the treaty year on a risks attaching or losses occurring treaty?
On a risks attaching treaty, the policy's inception date decides the treaty year. On a losses occurring treaty, the loss date decides claims and premium is split by days earned.
What decision table assigns a bordereau policy to the right treaty year?
A decision table assigning a bordereau policy to the right treaty year tests the basis first, then the row type: new, renewal, backdated, endorsement, cancellation or claim.
How should backdated policies be treated on a risks attaching treaty?
Backdated policies on a risks attaching treaty belong to the year containing their inception date. Flag rows booked over 30 days late and check for losses before booking.
Does a bordereau cut-off date change a policy's treaty year?
A bordereau cut-off date does not change a policy's treaty year. Cut-off decides which bordereau reports the row; the attachment basis and policy dates decide the year.
Which date applies to a mid-term endorsement on a bordereau?
On risks attaching business, a mid-term endorsement on a bordereau follows the parent policy's inception year by default, unless the treaty wording treats increases as new risks.
Which Excel formulas test inception dates on a bordereau?
Excel formulas that test inception dates on a bordereau include YEAR, EDATE for non-January anniversaries, period range tests, a 30-day backdating flag and ISNUMBER for text dates.

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 →