The bordereau is what the carrier sees

A broker’s view of a client relationship is built from conversations, renewals, claims handled well and the occasional favour. A capacity provider’s view of the same relationship is built from a spreadsheet that arrives once a month.

That asymmetry gets underestimated. The bordereau is, for many carriers, the entire operational impression of your book. If it is late, inconsistent or hard to reconcile, that becomes what your firm is like to deal with, regardless of how the relationship feels at the underwriting table.

What has changed on the carrier side

Reporting expectations have tightened across the market. Data quality initiatives, delegated authority oversight and internal exposure management have all pushed in the same direction: capacity providers want more fields, more consistently, more often.

The requests are reasonable individually. Cumulatively they create a problem for brokers, because each carrier wants a slightly different format, and the data needed to fill any of them lives in declarations that were never captured with reporting in mind.

So the month-end bordereau becomes an assembly exercise. Someone pulls from the system, fills gaps from email, reformats per carrier, checks the totals against the ledger, and sends. It takes days. It is the kind of work that is invisible when it goes well and highly visible when it does not.

Where the errors actually come from

Rarely from carelessness. Almost always from the same three places.

Fields that were never captured. If the declaration arrived as an attachment and only the premium and the insured were keyed, everything else has to be recovered manually, every month, forever.

Reconstruction rather than derivation. If the bordereau is built by exporting and reformatting rather than generated from the underlying records, then the bordereau and the ledger are two independent versions of the truth, and they will diverge.

And adjustments. A mid-term change that is reflected in the policy record but not propagated into the reporting is the single most common source of a carrier query, because it surfaces months later when nobody remembers the change.

A test worth running this month

Take last month’s bordereau for your largest cover and compare it to the ledger, line by line, for one client.

Two questions. Do they agree? And if they do, did they agree because the system produced both from the same data, or because a person reconciled them?

The second answer is the one that matters. A book that reconciles because someone reconciles it is a book with a single point of failure who will eventually take a holiday.

Where we sit

In tigerlab BMS, declarations are structured records against the open cover, and bordereaux are produced from those records rather than assembled alongside them. The same data carries the four ledgers, so the reporting and the money come from one place by construction rather than by reconciliation.

Built with a global cargo brokerage, in co-creation with the brokers who send these files every month.

How long does your month-end reporting take? Download The bordereau health check: eight questions on formats, fields, adjustments and what happens when the person who does it is away.