Brisc ingests reinsurance bordereaux in any cedent or coverholder format, maps each layout once, standardises the data to one schema, and validates every row at ingestion. Flags surface for review; originals are never overwritten.
The mapping is the hard part, so it happens once per layout.
Each partner’s column layout is fingerprinted. A known layout auto-applies the saved mapping, file after file, period after period.
An unrecognised layout stops for a one-time mapping in the UI. New formats arrive via configuration, never code.
Password-protected workbooks open. Multi-sheet files combine, with the source sheet stamped on every row it contributed.
Each row is stamped with a composite identity and a content hash, so versions, duplicates and changes are tracked from the first file onward.
Every row lands in one golden schema, whatever it looked like on arrival.
12+ date formats resolved to one.
Currency symbols and thousands separators normalised.
US state codes and Y/N flags made canonical.
Naming variants resolved to one canonical broker.
The result is one dataset, one schema, every row carrying its source file, sheet and version.
Named checks run on every row the moment a file arrives: premium, claims, and cross-version against the last file you accepted. Every check is named and explained in the validation check library.
Commission rates, taxes and levies, policy validity, currency: each row tested against the terms it should obey.
Silent premium changes, disappearing rows, duplicates: nothing changes between periods without a record.
Enforcement is off by default. Flags queue for review with the row, the check and the reason attached.
A Bermuda-based specialty reinsurer audited four years of bordereaux, more than 100,000 premium records, and found a 12% uplift in true profitability hidden in misallocated and unprocessed data.
Read the case study →Standardised, validated, versioned rows: the dataset your reporting and analytics should have been built on all along.
The work shown, exportable: what arrived, what changed, what was flagged, who reviewed it.
Processed data pushed to the systems you already run. Your system of record stays the system of record.
Looking to reconcile bordereaux against cash and contract? See bordereaux reconciliation. Receiving claims or loss bordereaux? See claims bordereaux validation.
Bordereaux at Brisc
Bordereaux ingestion is the step that turns the spreadsheets cedents, coverholders and MGAs send each period into data your systems can use. Each file is opened, its layout mapped to your schema, its fields standardised, and every row validated before anyone reports on it. Done by hand, it is rekeying and spreadsheet macros; done by bordereaux ingestion software, each layout is mapped once and every later file arrives in the same shape.
Standardisation resolves the differences between partners: date formats, currency symbols and separators, state codes, Y/N flags and broker name variants all land in one golden schema. Every row keeps its source file, sheet and version, so the standardised dataset can always be traced back to what arrived.
Whatever your cedents and coverholders already send: Excel in any layout, including password-protected and multi-sheet workbooks, CSV, and the formats that are standard nowhere but arrive anyway. No new templates, no format mandates on your partners.
The layout fingerprint no longer matches, so the file halts for a one-time human mapping instead of being forced through the old one. Nothing is mis-mapped silently, and the new layout is saved as configuration, never code.
No. Validation raises flags; your team reviews them. Originals are never overwritten, and every accepted change is versioned against the file it came from.
Ingestion and standardisation are the first half of the job: getting every bordereau into one trustworthy schema. Reconciling that data against cash and contract is the second half, covered at bordereaux reconciliation.
Typically 2 to 6 weeks. Day one needs no integration project: uploads in, standardised and validated data out, running in parallel with your current process until the numbers have earned trust.
SOC 2 Type II, GDPR and CCPA compliant. Every customer runs in a dedicated tenant on Microsoft Azure, and your data never trains our models. Documentation at trust.brisc.ai.
30 minutes, no slide deck. We ingest a real file from a real cedent, mapping, standardisation and flags included. Your book is specific; the walkthrough should be too.
Book the walkthroughNot ready for a call? Get the MGA operations report →