Bordereaux Analyst

Bordereaux ingestion software for reinsurance. Mapped once, standardised for good.

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.

Ingestion

How does Brisc ingest a bordereau?

The mapping is the hard part, so it happens once per layout.

01 · FINGERPRINT

The layout is recognised

Each partner’s column layout is fingerprinted. A known layout auto-applies the saved mapping, file after file, period after period.

02 · MAP ONCE

New layouts halt for a human

An unrecognised layout stops for a one-time mapping in the UI. New formats arrive via configuration, never code.

03 · OPEN EVERYTHING

Real-world files open

Password-protected workbooks open. Multi-sheet files combine, with the source sheet stamped on every row it contributed.

04 · IDENTIFY

Every row gets an identity

Each row is stamped with a composite identity and a content hash, so versions, duplicates and changes are tracked from the first file onward.

Standardisation

How is the data standardised?

Every row lands in one golden schema, whatever it looked like on arrival.

Dates

12+ date formats resolved to one.

Amounts

Currency symbols and thousands separators normalised.

Codes and flags

US state codes and Y/N flags made canonical.

Broker names

Naming variants resolved to one canonical broker.

The result is one dataset, one schema, every row carrying its source file, sheet and version.

Validation

What validation runs at ingestion?

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.

Against the contract

Commission rates, taxes and levies, policy validity, currency: each row tested against the terms it should obey.

Against the last version

Silent premium changes, disappearing rows, duplicates: nothing changes between periods without a record.

Flagged for your review

Enforcement is off by default. Flags queue for review with the row, the check and the reason attached.

12%

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 →
Output

Where does the processed data go?

Golden-schema records

Standardised, validated, versioned rows: the dataset your reporting and analytics should have been built on all along.

An Excel audit pack

The work shown, exportable: what arrived, what changed, what was flagged, who reviewed it.

API and data-lake push

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

Which bordereaux page answers what

FAQ

Bordereaux ingestion, answered

What is bordereaux ingestion?

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.

What is bordereaux data standardisation?

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.

What formats can you ingest?

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.

What happens when a cedent changes their template?

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.

Do you correct our data?

No. Validation raises flags; your team reviews them. Originals are never overwritten, and every accepted change is versioned against the file it came from.

Is this the same as bordereaux reconciliation?

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.

How long does it take to go live?

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.

How is our data handled?

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.

Bring your worst bordereau.

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 walkthrough

Not ready for a call? Get the MGA operations report →