Property Bordereaux for Reinsurers: Error Catalogue & Fixes
On this page
- Key Takeaways
- Which Errors Should a Property Bordereau Check Catch?
- Which Property Bordereau Errors Should Be Fixed First?
- How Does a Store With 10 Times Its Peers' Value Get Resolved?
- How Can a Reinsurer Test Last Year's Property Bordereaux?
- How Does Insurnest Help With Property Bordereaux for Reinsurers?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
"It's just another store," the cedent said.
The property bordereau said otherwise: USD 11.8m on one row, against a chain median of USD 1.15m.
Property bordereaux for reinsurers are location-level returns from cedents, listing each risk, its value and its building details.
Errors in property bordereaux for reinsurers flow into pricing, accumulation and the cat exposure returns to reinsurers.
This guide gives you an error catalogue with detection rules and fixes, a triage order and a worked outlier case.
Key Takeaways
- Test values before locations. A currency or units error moves every row at once.
- Unknown is a value, not a gap. OED codes 5000 and 1000 mean construction and occupancy are unknown.
- Compare each row with its peers. A sum insured 10 times the median needs an explanation, not a delete.
- Rank by value affected. Fix the errors that move the most insured value first.
Which Errors Should a Property Bordereau Check Catch?
A property bordereau check should catch nine errors in four families: location, value, building data, and duplicates or currency.
Field names follow Open Exposure Data (OED), the open exposure format published by Oasis LMF.
| Error | How it shows up | Detection rule | Fix |
|---|---|---|---|
| Missing geocode | Latitude and Longitude blank or 0,0 | Blank, or both values zero | Geocode from address; record Geocoder and AddressMatch |
| Coarse geocode | Coordinates with one or two decimals | Fewer than four decimals, or postcode-level match | Re-geocode to street or building level |
| Wrong-country point | Point falls outside the stated country | Coordinates outside the country's bounds | Check for swapped latitude and longitude |
| Zero sum insured | BuildingTIV of 0 beside a premium | TIV = 0 and premium > 0 | Request the value; hold the row |
| Outlier sum insured | One value far above its peers | TIV > 5 times the median for the same occupancy | Query; do not cap or delete |
| Unmapped codes | ConstructionCode 5000 or OccupancyCode 1000 | Share of unknown codes above an agreed limit | Map OrgConstructionCode and OrgOccupancyCode to OED |
| Year built gap | YearBuilt 0, blank, 1900 or a future year | Outside 1800 to the current year | Request it, or band by survey |
| Duplicate locations | Same address or coordinates twice on a policy | Repeated address plus postcode, or identical coordinates | Merge, or confirm separate buildings |
| Location currency error | LocCurrency missing, or local values marked USD | Currency blank, or value out of line for the country | Restate with the stated exchange rate |
The five-times threshold is illustrative. Set it per occupancy with the treaty underwriter.
How do location errors show up on a property bordereau?
Location errors on a property bordereau show up as blank coordinates, coarse coordinates and points in the wrong place.
Precision matters. One degree of latitude is about 111 km, so two decimals place a risk within about 1.1 km.
Four decimals narrow that to about 11 m. OED's GeocodeQuality and AddressMatch fields record how good the match was.
How do sum insured errors show up on a property bordereau?
Sum insured errors on a property bordereau show up as zeros beside premium, values far above peers and whole schedules on one row.
OED splits value into BuildingTIV, ContentsTIV and BITIV.
A cedent putting total insured value in the building field alone distorts every peer test.
Check the total against the policy's declared value, as in exposure to premium reconciliation.
Which building attribute errors weaken a property bordereau?
Building attribute errors that weaken a property bordereau are unmapped codes, unknown defaults and impossible build years.
In the OED construction values, code 5000 means the class is not known. Occupancy 1000 means the same.
Lloyd's Coverholder Reporting Standards include wall and roof construction fields for some property business.
Keep the cedent's original construction code beside the mapped one. That way a wrong mapping can be traced back.
How should duplicate locations and currency be checked on a property bordereau?
Duplicate locations and currency should be checked on a property bordereau before any totals are reported to underwriters.
A duplicate doubles value at one address. Two buildings on one site are not duplicates, so confirm before merging.
LocCurrency is a required OED field. A row without it cannot be converted safely.
Which Property Bordereau Errors Should Be Fixed First?
Property bordereau errors should be fixed in order of the insured value they move.
- Currency and units. One wrong currency or a missing "000" changes every row.
- Zero and outlier sums insured. These change the amount at risk directly.
- Duplicate locations. These double value at one address.
- Missing and coarse geocodes. These move accumulation between zones.
- Unknown construction and occupancy. These widen the range of modelled loss.
- Year built. Useful, but the last to hold up a bordereau.
How Does a Store With 10 Times Its Peers' Value Get Resolved?
A store with 10 times its peers' value gets resolved by querying the row, not by capping or deleting it.
Take an illustrative retail chain of 38 stores ceded on a property quota share.
What did the outlier test show on a store valued at 10 times the chain median?
The outlier test on a store valued at 10 times the chain median flagged store 27: USD 11.8m against a median of USD 1.15m.
That is about 10.3 times the median (11.8 ÷ 1.15). It is well past the five-times threshold.
The other 37 stores total USD 44.4m, so the schedule is USD 56.2m. Store 27 alone is 21.0% of it (11.8 ÷ 56.2).
What did the cedent's reply reveal about the outlier store on the property bordereau?
The cedent's reply revealed that the outlier store was the chain's regional distribution warehouse, coded as a retail shop.
The value was right; the occupancy code was wrong. The cedent corrected it on a resubmitted bordereau.
Had it been a typing error for USD 1.18m, the same test would have caught it. The rule finds the row; the cedent explains it.
How Can a Reinsurer Test Last Year's Property Bordereaux?
A reinsurer can test last year's property bordereaux in six steps, using the catalogue above as the rule set.
- Collect four quarters. Use the files as received, not the cleaned copies.
- Put them in one layout. Map columns to OED-style names, as in bordereau template mapping.
- Run each detection rule. Count rows and total insured value affected per error.
- Rank by value. Sort errors by insured value affected, not by row count.
- Send the top items. Give the cedent row references and the rule each row failed.
- Repeat next quarter. Compare counts to see whether the cedent's data is improving.
Files that feed modelling then need the steps in cat model input preparation.
Resubmitted files go through bordereau resubmission handling.
How Does Insurnest Help With Property Bordereaux for Reinsurers?
Reinsurance Bordereaux Reconciliation does not geocode, map codes or run the location checks above.
It splits premium and claims between reinsurers using the configured participation.
It compares those values with bordereaux, master and settlement records.
It also checks that allocated totals tie back to the bordereaux received.
Mismatches carry a status per reinsurer. Your team decides whether a TIV outlier is a data error.
Key Terms
- Total insured value (TIV): Building, contents and business interruption value at a location.
- Geocode precision: How closely coordinates place a risk, often shown by decimal places.
- OED: Open Exposure Data, an open, model-agnostic exposure format from Oasis LMF.
Sources
- Oasis LMF: Open Exposure Data (OED) (input fields and construction and occupancy code lists)
- Lloyd's: Coverholder Reporting Standards User Guide (Version 5.2, August 2019)
- Insurnest: Reinsurance Bordereaux Reconciliation
Frequently Asked Questions
Which errors should a property bordereau check catch?
A property bordereau check should catch missing or coarse geocodes, zero or outlier sums insured, unknown construction and occupancy codes, year built gaps, duplicate locations and currency errors.
How do location errors show up on a property bordereau?
Location errors on a property bordereau show up as blank or zero coordinates, coordinates with one or two decimals, points in the wrong country and postcode-only addresses.
How do sum insured errors show up on a property bordereau?
Sum insured errors on a property bordereau show up as zero values beside a premium, values ten times their peers, or a whole schedule's value placed on one row.
Which building attribute errors weaken a property bordereau?
Building attribute errors that weaken a property bordereau are cedent codes left unmapped, codes defaulted to unknown, and year built entered as zero, blank or a future year.
Which property bordereau errors should be fixed first?
Property bordereau errors should be fixed in order of value affected: currency and units first, then zero and outlier sums insured, duplicates, geocodes, building codes and year built.
What did the outlier test show on a store valued at 10 times the chain median?
The outlier test on a store valued at 10 times the chain median showed store 27 at USD 11.8m against a chain median of USD 1.15m, about 10.3 times its peers and 21% of the schedule's value.
What did the cedent's reply reveal about the outlier store on the property bordereau?
The cedent's reply revealed that the outlier store was the chain's distribution warehouse, coded as a retail shop. The value was right; the occupancy code was wrong and was corrected on the resubmitted bordereau.
How can a reinsurer test last year's property bordereaux?
A reinsurer can test last year's property bordereaux by putting four quarters in one layout, running each detection rule, ranking errors by value affected and sending the cedent the top items.

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 →