A bordereau sits at the intersection of underwriting data and financial settlement. For managing general agents, program administrators, and the capacity providers behind them, it is one of the most consequential documents in insurance operations—and one of the most frequently inaccurate.
The mechanics of what a bordereau is are straightforward. The failure modes are not. And for organisations whose delegated authority relationships depend on accurate, timely reporting, understanding both is a precondition for managing them.
What a Bordereau Is—and Where It Sits in the Delegated Authority Chain
A bordereau is a structured report submitted by a delegated underwriting authority—most commonly an MGA or coverholder—to the capacity provider (insurer or reinsurer) that backs their book. It summarises the risks bound, premiums collected, claims paid, and claims reserved within a defined reporting period.
Two primary types exist:
Some programs require a third type—a combined or aggregate bordereau—that reconciles premium and claims activity within the same document, giving the carrier a single view of the economics of the delegated book across both income and loss.
In Lloyd’s and London Market contexts, bordereau reporting is a formal obligation under the delegated authority agreement. Coverholders submit bordereaux to syndicates and managing agents on a defined schedule, typically monthly. In US program business, requirements vary by carrier, but the underlying logic is identical: the capacity provider needs to reconstruct the economics of the book they are backing without underwriting it directly.
This structural separation—the capacity provider carries the risk but does not manage the individual risk relationships—creates the conditions for bordereau accuracy to become a financial infrastructure problem, not just an administrative one. The bordereau is not a reporting formality; it is the primary mechanism by which the economics of the delegated relationship are made visible to the party that carries the exposure.
The Four Failure Modes That Produce Inaccurate Bordereaux
Most bordereau failures are not caused by incompetence. They are caused by the architecture of delegated authority programs, which creates inherent gaps between where data originates, where it is processed, and where it needs to be reported.
Four failure modes recur across programs of every size:
Timing misalignment. A risk bound in the final days of a reporting period may not be fully processed by the submission deadline. The bordereau either misses the risk entirely or carries placeholder data that differs from the final policy record. Carriers receive one version; the MGA’s policy administration system holds another. The discrepancy surfaces at the next bordereau cycle—or later, during audit, when the divergence has compounded across several reporting periods.
Currency translation errors. International programs that bind risks in multiple currencies must translate premium and claims data to a reporting currency. When exchange rates are applied inconsistently—or at different points in the settlement cycle—the bordereau figures diverge from actual fund movements. A premium received at the rate used for accounting purposes may appear differently in the bordereau if a separate FX feed was applied at extraction time.
Policy amendment lag. Mid-term endorsements, cancellations, and reinstatements generate accounting entries that may not be captured in the bordereau for one or more reporting cycles. A claims bordereau showing a reserve of £120,000 may not reflect a reserve reduction processed three weeks prior. The carrier reserves against a position that no longer exists.
Schema fragmentation. MGAs operating multiple systems—a policy administration platform, a claims system, and a separate finance ledger—often compile bordereaux by manual extraction and reconciliation across those systems. The more manual the process, the wider the variance from source data, and the more the variance compounds as the book grows.
Each failure mode compounds the others. A premium bordereau with timing gaps creates trust deficits that make claims settlement conversations more adversarial. Both sides are managing the operational consequences of a data accuracy problem that neither can fully see from their position in the delegated chain.
How MGA and Program Business Bordereau Requirements Differ from Single-Entity Reporting
Traditional insurance reporting operates on a single-entity basis: the insurer owns the policy, the claims, the premium, and the ledger. Reporting is an internal function, reconciled against the same systems that produced the activity.
Bordereau reporting exists precisely because the policy-issuing and risk-bearing functions are separated. An MGA binds risks on behalf of a carrier but maintains the day-to-day relationship with the broker and policyholder. The carrier carries the exposure but has limited real-time visibility into the book.
This separation creates a set of requirements that have no direct equivalent in single-entity insurance reporting:
Lloyd’s coverholder agreements specify bordereau formats, field requirements, and submission deadlines in the binding authority contract. US program business is more variable, but the direction of travel—toward standardised, machine-readable formats—is consistent across both markets.
The practical implication is that MGAs operating across multiple capacity providers must maintain separate bordereau outputs that are internally consistent but formatted differently for each counterparty. Managing this without automation requires the kind of manual reconciliation work that introduces the errors described above—and that scales poorly as the number of capacity providers or the volume of risks written increases.
| Manual bordereau process | Integrated bordereau infrastructure |
|---|---|
| Bordereau compiled by extracting from 3–4 separate systems | Single source of truth: bordereau flows from the same data used for accounting |
| FX rates applied inconsistently across systems and time | Automated FX conversion applied at a single, auditable point per reporting cycle |
| Reserve figures reflect last manual update, not current position | Real-time reserve visibility integrated directly into claims bordereau output |
| Different format per carrier, assembled separately each month | Templated outputs by counterparty, produced automatically from the same underlying data |
| Audit trail reconstructed retrospectively from emails and spreadsheets | Every line item traceable to source record with timestamps and reason codes |
What Good Bordereau Infrastructure Looks Like in Practice
The standard for bordereau infrastructure has shifted. Ten years ago, a well-managed spreadsheet-based process with documented reconciliation controls was considered acceptable. Today, carriers and reinsurers are applying greater scrutiny—partly due to regulatory pressure, partly due to the growth of delegated authority programs, and partly because multi-currency, multi-jurisdiction books are structurally incompatible with manual processes at scale.
Good bordereau infrastructure has four characteristics:
Single source of truth. Premium and claims data should flow into the bordereau from the same systems used for accounting and fund management. If the bordereau is compiled from a separate extraction process, it will drift from the financial record over time. The gap between what the bordereau shows and what the ledger holds is where audit exposure originates.
Automated currency conversion. Exchange rates should be applied at a defined, auditable point in the reporting cycle, consistently across all line items. The rate used should match the rate applied in actual fund movements—not a separate FX feed pulled at a different time. This is not a technical detail; it is the difference between a bordereau that reconciles cleanly and one that requires manual adjustment at every submission.
Real-time reserve visibility. For claims bordereaux, carriers need to see current reserve positions, not reserves as of the last manual update. This requires integration between the claims system and the bordereau output—not a downstream reconciliation step after the bordereau has already been submitted.
Audit trail. Every bordereau line item should be traceable to a source record. Adjustments, amendments, and corrections should be logged with timestamps and reasons. Carriers increasingly require this not just for their own governance but for their own reporting obligations upward—to reinsurers, regulators, and in the Lloyd’s market, to the Corporation of Lloyd’s.
The financial infrastructure layer—how premiums move from policyholder to MGA to carrier, how loss fund balances are maintained and reported, how multi-currency positions are settled—is inseparable from the bordereau data layer. A bordereau that accurately reflects the financial position of a program requires that the financial movements themselves are clean, timely, and auditable from source to submission.
The Reconciliation Challenge: Connecting Bordereau Data to Actual Fund Movements
A bordereau that is technically accurate but disconnected from actual fund movements creates its own class of problems. Premium reported does not equal premium received. Reserves reported do not equal funds held. The gap between the two is where most MGA-carrier disputes originate—and where regulators focus when reviewing delegated authority arrangements.
Loss fund management is the most sensitive area. In most delegated authority arrangements, the MGA holds a loss fund—a pool of capital provided by the carrier to pay claims directly. The claims bordereau reports on what has been paid from that fund, what remains in reserve, and what has been recovered. If the bordereau figures diverge from the actual fund balance—even temporarily, due to processing timing—the reconciliation process becomes adversarial. Both parties are working from different versions of the same financial reality.
Treating the bordereau as a reporting document produced after the financial activity has occurred is the root of most MGA-carrier reconciliation disputes. When financial infrastructure is integrated, the bordereau becomes a reflection of the current state of the program—not a reconstruction assembled at month-end.
The same dynamic applies to premium trust accounts. In the UK, MGAs are required to hold policyholder premiums in a separate trust account until they are remitted to the carrier. The premium bordereau should reflect the premium due; the fund movement should reflect the premium paid. Discrepancies between the two create audit exposure and, in cases where the gap is material or persistent, raise questions about whether client money obligations are being met.
Resolving this requires treating the bordereau not as a reporting document produced after the financial activity has occurred, but as a live output of the financial infrastructure itself. When premium flows, claims payments, and reserve movements are captured in a single, integrated system, the bordereau becomes a reflection of the current financial state of the program—not a reconstruction assembled at month-end from multiple disconnected sources.
What the Shift Toward Standardised Bordereau Formats Means for MGA Operations
Lloyd’s has been the most visible driver of bordereau standardisation. Market initiatives have pushed coverholders toward structured, machine-readable formats that can be ingested directly by syndicates and managing agents without manual processing. The pressure is administrative—manual processing of inconsistent bordereau formats at Lloyd’s scale is not viable—but the effect is felt at every coverholder, regardless of size.
The US market is following a similar trajectory, driven by carriers seeking to reduce the operational overhead of processing inconsistent bordereau formats from a growing number of program partners. Market-level initiatives and carrier-specific requirements are converging on structured data standards: defined CSV schemas, API-based submission portals, and direct integration with carrier systems.
For MGAs, this creates a two-sided challenge. They must produce bordereaux that meet each carrier’s requirements—which vary by counterparty—while ensuring the underlying data is accurate, timely, and auditable. The cost of managing this manually scales poorly. Each new capacity provider relationship adds a new format requirement. Each reporting period is another round of extraction, reconciliation, and quality review.
The strategic response is to treat bordereau production as a financial infrastructure function, not an administrative one. This means building or procuring systems that produce accurate bordereau data as a by-product of normal financial operations—premium processing, claims payment, reserve management—rather than assembling it separately at reporting time. When the financial infrastructure is integrated, bordereau accuracy is a function of operational discipline, not a separate reconciliation effort.
Vitesse provides the financial infrastructure layer for insurance programs: premium flows, loss fund positions, multi-currency settlement, and real-time fund visibility managed within a single platform. For MGAs and program administrators navigating increasing bordereau obligations across multiple capacity providers, the financial infrastructure is where reporting accuracy is built—or where it breaks down.
FAQ: Insurance Bordereau Reporting
What is the difference between a premium bordereau and a claims bordereau?
A premium bordereau reports risks bound and premiums collected during a period. A claims bordereau reports claims opened, paid, reserved, and closed. Most delegated authority programs require both on the same reporting cycle, with reconciliation between the two to ensure premium flows and loss fund movements are reflected consistently.
How often does a bordereau need to be submitted?
Most delegated authority agreements require monthly submission. Lloyd's binding authorities specify the exact submission deadline in the contract—typically 30 days after month end. US program business may require quarterly or monthly reporting depending on the carrier and book size. Some high-volume programs submit weekly or more frequently to maintain real-time alignment.
What happens if a bordereau is submitted late or inaccurately?
Late or inaccurate bordereaux trigger a range of consequences: delayed premium remittance, disputed claims settlements, and in some cases, formal review of the delegated authority agreement. For Lloyd's coverholders, persistent bordereau failures can affect renewal of the binding authority. For US program business, carriers may impose remediation requirements or withhold settlement until the discrepancy is resolved.
How does bordereau reporting work in reinsurance?
In reinsurance, a bordereau serves the same function one layer up: the ceding insurer reports to the reinsurer. Facultative reinsurance may require individual risk bordereaux; treaty reinsurance typically requires aggregated reporting by class, territory, and loss period.
Can bordereau reporting be automated?
Yes, and for programs operating at scale, automation is increasingly a prerequisite rather than an optimisation. Effective automation requires integration between the policy administration system, the claims system, and the financial ledger—with output formats that match each carrier's ingestion requirements. The format challenge is non-trivial when an MGA serves multiple capacity providers with different schemas.
Where does the term "bordereau" come from?
The term derives from the French word for a schedule or memorandum. In insurance, it refers specifically to the periodic report submitted by a delegated underwriting authority to its capacity provider, summarising the risks bound or claims activity within a defined period. The term is used consistently across Lloyd's, the London Market, and international insurance and reinsurance contexts.
