Insights

Bordereaux automation: how automated bordereaux work

Bordereaux automation explained: why spreadsheets break, how automated bordereaux are generated per binder from the live book, and what makes them reconcile.

Updated 16 November 2026 · Written and reviewed by the Soldek team

Bordereaux automation means the premium, risk and claims reports an MGA or coverholder owes each capacity provider are produced by the system that holds the book, on schedule, from the same rows that produced the policies and claims, instead of being assembled by hand at month-end. Automated bordereaux are not a formatting feature; they are a consequence of keeping the book structured.

Why the spreadsheet bordereau breaks

A bordereau built by hand copies figures out of a policy system, a finance file and a claims list into the template each carrier wants. Every copy is a place where a figure can go stale: a cancellation booked after the extract, an endorsement that changed the premium, a claim closed in the previous month. The carrier reconciles against its own records and the questions come back weeks later.

What an automated bordereau is built from

Transactions, not policies
A premium bordereau reports what happened in the period: new business and renewals at inception, endorsements with a premium change on their effective date, cancellations with the return premium on the cancellation date, each with its sign.
The binder and its sections
Every row carries the agreement it is written under: UMR or agreement reference, section, class of business and risk code, so the carrier can match it to the slip.
The full record
Insured and address, broker and channel, premium split between broker, MGA and carrier, fee and tax as invoiced, payment status, underwriter and the engine's rating snapshot, open bind conditions, and schedule detail for schedule products.
Claims that moved
Every claim open or reported in the period, and a closed claim once more in the month it closed, with reserve and paid amounts linked to the policy and binder.
A data dictionary
The column list with a definition per column, shipped with the file, so there is one meaning for every header.

The checks that make it reconcile

  • One selection rule per report, used by the screen and the scheduler alike, so a bordereau run by hand and one run by the cron contain the same rows.
  • A snapshot of every row at generation time, so a bordereau can be re-opened later exactly as it was sent even if the policy has changed since.
  • Subtotals per section and per binder that are computed from the rows, never typed.
  • Payment status read from the invoices and the bank reconciliation, so premium reported as paid is premium that arrived.
  • Submission as a recorded step: file stored, e-mailed to the lead underwriter, status set to submitted, with the date in the audit trail.

What this means for the MGA

The month-end scramble disappears, but the larger change is upstream: because bordereaux management software can only report what the book contains, the book has to be complete at the moment of binding. Binder, section, broker, commission and tax are captured at quote and bind, not reconstructed at month-end. That is also why bordereaux reporting software bolted onto a system that does not hold those fields never fully reconciles.

See it running.

Book a demo and we show you the complete platform live. Still stuck? Write to hello@soldek.io.