Cyber Bordereaux for Reinsurers: Field Template & Checks
On this page
- Key Takeaways
- Which Fields Should a Cyber Bordereau Carry?
- What Does Each Part of the Cyber Bordereau Template Check?
- What Does a Filled Cyber Bordereau Row Look Like for a Trucking Company?
- Who Should Own the Cyber Bordereau Template?
- How Does Insurnest Help With Cyber Bordereaux for Reinsurers?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
Since 31 March 2023, Lloyd's standalone cyber-attack policies need a state backed cyber-attack exclusion on inception or renewal.
Three years on, can your cyber bordereau show which clause each ceded policy carries?
Cyber bordereaux for reinsurers are the policy-level returns a cedent sends under a cyber treaty.
Most report premium and limit. Few report the sector, sub-limits and exclusions that decide how a cyber event hits the treaty.
This guide gives you a copy-ready field template with checks, a filled example row and ownership rules.
Key Takeaways
- Code the sector. Free-text industry descriptions cannot be accumulated.
- Band revenue, but keep the number. The band drives checks; the figure proves the band.
- Check sub-limits against their parents. Dependent BI should never exceed BI.
- Record the exclusion clause used. A yes or no flag is not enough.
Which Fields Should a Cyber Bordereau Carry?
A cyber bordereau should carry sixteen fields per policy transaction, each with a format and a check.
Copy the template below into your specification for cyber bordereaux for reinsurers.
Bands, minimums and the clause list are illustrative. Set your own per treaty.
CYBER BORDEREAU FIELD TEMPLATE (one row per policy transaction)
# Field Format Check
1 Policy / certificate ref text unique per transaction
2 Insured name text not blank
3 Insured country ISO 3166 alpha-2 inside treaty territory
4 Sector scheme and code NAICS 2022, 3-6 dig not on excluded list
5 Annual revenue + currency number, ISO 4217 > 0; currency given
6 Revenue band A-E agrees with field 5
7 Aggregate limit number <= treaty max line
8 Ransomware / extortion sub number <= field 7
9 Business interruption sub number <= field 7
10 Dependent BI sub-limit number <= field 9
11 Retention number >= band minimum
12 BI waiting period hours >= treaty minimum
13 State-backed exclusion clause reference on approved list
14 Prior incidents (3 years) count + paid value > 0 needs referral ref
15 Gross premium number > 0, or reason code
16 Inception / expiry dates inside treaty period
Illustrative bands: A < USD 10m B 10m-50m C 50m-250m
D 250m-1bn E > 1bn
Illustrative minimum retention: A 10k B 25k C 100k D 250k E 1m
Illustrative minimum waiting period: 8 hours. Max line: USD 10m.
Mapping a cedent's own layout onto these fields is covered in bordereau template mapping.
What Does Each Part of the Cyber Bordereau Template Check?
Each part of the cyber bordereau template checks one thing a treaty underwriter would otherwise ask by email.
How should a cyber bordereau identify the insured's sector and size?
A cyber bordereau should identify the insured's sector with a coded scheme and its size with annual revenue.
The open OED exposure standard marks industry scheme, industry code and annual revenue as required for cyber.
OED defines annual revenue as total gross income, not profit. Its code list includes NAICS 2022.
A sector code without its scheme is ambiguous. A revenue band without the figure cannot be tested.
A revenue figure without its currency cannot be banded at all.
Which limit and sub-limit checks belong on a cyber bordereau?
Limit and sub-limit checks on a cyber bordereau confirm that each limit sits inside the one above it.
The aggregate limit must sit within the treaty's maximum line. Ransomware and BI sub-limits sit within the aggregate.
Dependent business interruption sits within BI. A row that breaks the chain usually means columns were shifted.
How should retention and waiting period be recorded on a cyber bordereau?
Retention and waiting period on a cyber bordereau should be recorded per policy, as an amount and as hours.
A retention below the band minimum, or a waiting period shorter than the treaty allows, sends the row to query.
Structures vary by insured. See cyber insurance deductible retention structures.
Why does a cyber bordereau need a state backed cyber-attack exclusion field?
A cyber bordereau needs a state backed cyber-attack exclusion field because a yes or no flag cannot show which wording applies.
Lloyd's Market Bulletin Y5381 set this requirement for risk codes CY and CZ.
The bulletin also asked managing agents to have regard to their reinsurance, so cover stays back to back.
A clause reference per row makes that checkable.
The same logic sits behind treaty exclusion checks at cession.
What should a cyber bordereau record about prior incidents?
A cyber bordereau should record the count and paid value of the insured's incidents over three years.
Any count above zero needs a referral reference, so the reinsurer can see that the cedent's authority holder reviewed it.
What Does a Filled Cyber Bordereau Row Look Like for a Trucking Company?
A filled cyber bordereau row for a trucking company shows how each check passes, fails or refers. The insured is illustrative.
| Field | Value | Check result |
|---|---|---|
| Sector scheme and code | NAICS 2022, 484 Truck Transportation | Pass: not excluded |
| Annual revenue | USD 180,000,000 | Pass: greater than zero |
| Revenue band | C | Pass: USD 180m sits in 50m to 250m |
| Aggregate limit | USD 5,000,000 | Pass: within USD 10m max line |
| Ransomware sub-limit | USD 2,500,000 | Pass: within aggregate |
| BI sub-limit | USD 5,000,000 | Pass: equals aggregate |
| Dependent BI sub-limit | USD 1,000,000 | Pass: within BI |
| Retention | USD 100,000 | Pass: meets band C minimum |
| BI waiting period | 12 hours | Pass: above 8 hours |
| State-backed exclusion | Clause ref CW-2 | Pass: on approved list |
| Prior incidents | 1 in 2024, USD 60,000 paid | Refer: reference R-1187 given |
| Gross premium | USD 62,000 | Pass: rate on line 1.24% |
The rate on line is 62,000 ÷ 5,000,000 = 1.24%.
Had revenue been entered in thousands as 180,000, band C would fail at once. USD 180,000 belongs in band A.
Who Should Own the Cyber Bordereau Template?
The cyber bordereau template should be owned by the reinsurer's cyber treaty underwriter, with clear maintenance rules.
| Item | Owner | Rule |
|---|---|---|
| Revenue bands and minimums | Cyber treaty underwriter | Reviewed at each renewal |
| Excluded sector list | Cyber treaty underwriter | Changes dated and sent to cedent |
| Approved exclusion clauses | Underwriter with wordings team | New clause added only after review |
| Template versions | Bordereaux lead | Version number on every file |
| Field sign-off | Cedent's bordereaux contact | Confirmed before first use |
Systemic scenarios behind these rules are covered in cyber reinsurance systemic peril and silent cyber across LOB reinsurance.
UK insurers will also know the PRA's Supervisory Statement 4/17 on cyber underwriting risk.
How Does Insurnest Help With Cyber Bordereaux for Reinsurers?
Reinsurance Bordereaux Reconciliation does not run the class checks in this template.
Revenue bands, sub-limits and exclusion clauses stay with your underwriting and bordereaux teams.
It calculates each reinsurer's share of cyber premium and claims from configured participation.
It then compares those values with bordereaux and settlement records.
Mismatches are flagged with status by reinsurer. The platform identifies the difference; your teams determine the cause.
For the wider picture, see AI in cyber insurance for reinsurers.
Key Terms
- Revenue band: A size bracket set in the treaty, used to apply limits and minimum retentions.
- Waiting period: Hours of interruption before business interruption cover responds.
- Dependent business interruption: Cover for loss caused by an outage at a supplier the insured relies on.
Sources
- Lloyd's: Market Bulletin Y5381, State backed cyber-attack exclusions (17 August 2022)
- Prudential Regulation Authority: Cyber insurance underwriting risk, SS4/17
- Oasis LMF: Open Exposure Data (OED) (cyber field status and industry codes)
- Insurnest: Reinsurance Bordereaux Reconciliation
Frequently Asked Questions
Which fields should a cyber bordereau carry?
A cyber bordereau should carry policy reference, country, sector code, annual revenue and band, aggregate limit, ransomware, BI and dependent BI sub-limits, retention, waiting period, exclusion clause and prior incidents.
How should a cyber bordereau identify the insured's sector and size?
A cyber bordereau should identify the insured's sector with a coded scheme such as NAICS and its size with annual revenue, currency and the treaty's revenue band.
Which limit and sub-limit checks belong on a cyber bordereau?
Limit and sub-limit checks on a cyber bordereau confirm the aggregate limit sits within the treaty line and each sub-limit sits within the limit above it.
How should retention and waiting period be recorded on a cyber bordereau?
Retention and waiting period on a cyber bordereau should be recorded as amounts and hours per policy, then checked against the minimum the treaty sets for each revenue band.
Why does a cyber bordereau need a state backed cyber-attack exclusion field?
A cyber bordereau needs a state backed cyber-attack exclusion field so the reinsurer can see which clause each ceded policy carries and whether it matches the treaty.
What should a cyber bordereau record about prior incidents?
A cyber bordereau should record the count and paid value of the insured's incidents in the last three years, with a referral reference where treaty rules require one.
What does a filled cyber bordereau row look like for a trucking company?
A filled cyber bordereau row for a trucking company shows NAICS 484, USD 180m revenue in band C, a USD 5m limit, a USD 100,000 retention and a referred prior incident.
Who should own the cyber bordereau template?
The cyber bordereau template should be owned by the reinsurer's cyber treaty underwriter, with the bordereaux lead keeping versions and the cedent signing off any change.

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 →