The bordereaux you stop assembling by hand,
with a record the carrier can audit.
Every month the premium and claims bordereaux get built from policy admin exports, a spreadsheet or three, and email, in a different format for each carrier, by someone who has a real job. Late files strain the fronting relationship. Errors get found by the carrier. Haltere builds the line that generates each bordereau from governed data on schedule, holds the rows that don’t reconcile for a person, and releases the file under a named human with a receipt per row.
The carrier finds the error.
You find out at the audit.
A bordereau is only as trustworthy as the record behind each row. Assembled by hand, there is no record: a premium figure that doesn’t tie to cash, an endorsement that never made it into the file, a column mapped differently than last month. The delegated-authority agreement gives the carrier audit rights over all of it. The audit is a project every time, because the file was never produced by a system.
Generated from governed data.
Validated. Released by a person.
Policy admin, cash, and claims, reconciled.
The line reads the systems you already run and reconciles them before anything is mapped: premium ties to cash, endorsements tie to transactions, claims tie to policies. What doesn’t reconcile is held, with the reason.
Mapped once, versioned forever.
Every carrier and fronting partner gets the file in their schema. The mapping is versioned; when a carrier changes a column, the change carries a name and a date, and last month’s file still reproduces.
A person releases. The record says so.
The file is generated on schedule and waits for release by a named person, with the held rows in front of them. The release carries the file hash, so the version the carrier received is the version you can reproduce.
A receipt per row. A release per file. An audit that is a query.
One premium bordereau,
generated, checked, released.
Fixture data; the shape is the point. Thirteen rows held, one person released, one hash the carrier can match.
Fixture data. The nine unpaid rows roll to September automatically; the four mismatches are someone’s job today, not at the audit. The receipt format is public
What the delegated-authority agreement
actually entitles the carrier to.
The governed first build.
One backlog item. Fully governed. Evidence included.
One bordereau line for one carrier or fronting partner to start: reconciliation, mapping, validation, scheduled generation, named release. The other carriers and the claims bordereau run on the same line.
Scoped to the project and quoted in the first conversation. Agreed before anything starts. No time-and-materials meter running.
From scoping to production-acceptable delivery, live in your environment.
Two deliverables, always paired: the working software, and the evidence pack. Show the board AI progress; show the examiners the receipts.
The process guarantee: your team reviews and approves every change. Nothing merges ungoverned. Nothing leaves for a broker or a carrier without a named human release.
Two ways to run it afterward: we operate the line for teams with no engineering bench, or your team operates it and we train your operator. The software, the map, and the receipts are yours in either mode. You walk at renewal with everything. The first cohort of five is filling now
What you’ll want to know.
Which bordereaux?
Premium, claims, and risk bordereaux, in each carrier’s or fronting partner’s format. The first build takes the one that costs you the most hours or the most goodwill; the others run on the same line.
Our policy admin data isn’t clean enough.
It rarely is, and the line is built for that. Rows that fail validation (premium that doesn’t tie to cash, endorsements without a matching transaction) are held and shown to a person, with the reason. The released file contains only rows that passed, and the record says which were held and why.
Does anything go to the carrier automatically?
No. The file is generated on schedule and released by a named person. The release is on the record with the file hash, so the version the carrier received is the version you can reproduce.
Is this a London-market product?
It is built for the US MGA-to-carrier and fronting relationship first: the formats your carriers actually ask for. If you also report into Lloyd’s coverholder standards, the same line produces that format.
How long, and what does it cost?
Four to eight weeks for the first bordereau line, fixed fee agreed before anything starts and quoted in the first conversation.
Bring us the bordereau that costs the most.
Tell us the carrier, the format, and who builds it today. Scoping is a conversation, the fee is fixed before anything starts, and the first review is on your calendar before we write a line.
No newsletter. No drip sequence. Every request gets a real reply within one business day, from someone who can answer it.
