Oversee every MGA you give authority to, from one record
Delegated authority oversight for carriers, capacity providers and Lloyd's managing agents: every MGA's bordereaux taken in and validated against its binder, authority breaches flagged in the period they happen, and audits and remediation tracked per MGA.
You carry the risk. The MGA holds the pen.
Delegating authority to an MGA or coverholder is how a carrier reaches business it could not write itself. It also means the decisions that put risk on your balance sheet are made in someone else's office, on someone else's systems, and reported back to you weeks later in a spreadsheet you did not design.
For most delegated authority teams, oversight is the work of checking those spreadsheets. Every MGA sends its premium and claims bordereaux in its own layout, on its own schedule, with its own interpretation of the fields. Someone reshapes each one, checks the totals, looks for risks outside the binder, chases the queries, and repeats it next month for every MGA in the portfolio. The annual audit then samples files to find out what the bordereaux did not show.
Regure turns that into a system. Each MGA's bordereaux are taken in and mapped to one model. Each line is validated against the binder that MGA writes under. Breaches surface in the period they happen, queries go back to the MGA with the line attached, and audits, findings and remediation are tracked per MGA on the same record. The portfolio view is the sum of validated data, not a consolidation of unchecked spreadsheets.
From an MGA's spreadsheet to a validated portfolio view
The same four steps run for every MGA and every reporting period, configured per MGA and per binder.
Take it in
Premium, claims and endorsement bordereaux arrive by email, SFTP or upload in the MGA's own layout. Document processing extracts each line and maps it to a common model, with the mapping set up once per MGA.
Check it against the binder
Every line is validated against that MGA's binder: limits and premium caps, classes, territories, period of authority, dates and premium arithmetic. Missing or inconsistent fields are caught on arrival.
Query the exceptions
Out-of-authority risks and data errors are flagged and queried back to the MGA with the line attached. The query, the response and the resolution stay on the record.
See the portfolio
Validated premium, claims and exposure roll up per binder, per MGA and across the portfolio, so capacity and performance decisions are made on checked data.
Spend the meeting on the MGA, not on the spreadsheet
When the bordereaux are already validated, a portfolio review is about underwriting performance, capacity and the relationship, not about whether the numbers can be trusted.
Oversight across the delegated authority lifecycle
Binders and authority
Each binder's terms are held as rules: classes, territories, limits, premium caps, referral triggers, claims authority and the period of authority. They drive bordereaux validation and give one place to see what each MGA is allowed to write.
Bordereaux and data quality
Premium, claims and endorsement bordereaux validated per period, with data quality tracked per MGA over time, so a deteriorating reporter is visible before it becomes an audit finding. See bordereaux.
Referrals
Where an MGA refers a risk or claim above its authority, the referral, the file and your decision are recorded against the binder, rather than scattered across inboxes.
Audits
Audits scheduled per MGA, evidence requested and held against the binder, and the history of every previous audit one click away when the next one is planned.
Findings and remediation
Findings recorded with owners, actions and due dates, and tracked to closure through the workflow engine, so a repeat finding is obvious.
Evidence for your own regulator
Everything above sits on an immutable audit trail, which is how a carrier or managing agent evidences that its own oversight duty was discharged.
Bring one MGA's bordereau
Send us one binder and one redacted bordereau from an MGA you oversee. We'll show it taken in, validated against the binder and the exceptions flagged.
Oversight of any MGA, and control at source for MGAs on Regure
Most delegated portfolios mix MGAs on very different systems. Regure oversees all of them; for MGAs that run their operation on Regure, the control moves to the point of decision.
| Dimension | MGA on its own systems | MGA running on Regure |
|---|---|---|
| Bordereaux | Taken in, mapped and validated against the binder on arrival | Generated from the MGA's operating record, each figure traceable to its policy or claim |
| Authority breaches | Flagged when the bordereau is reported | Prevented before bind; out-of-authority risks referred to you with the file |
| Claims authority | Checked against reported reserves and payments | Enforced on reserves and payments as they are made |
| Audit evidence | Requested and tracked per MGA | Delegated authority audit pack exported for any period |
| Your workload | Exceptions, not every line | Decisions on referrals, and review of data you can trust |
For an MGA's view of the same audit, see delegated authority audits for MGAs, and for what the MGA operating platform covers, see MGA software.
For whoever is accountable for business written under someone else's pen
Carriers and capacity providers
Delegated authority and programme teams overseeing a portfolio of MGAs across classes and territories, including US carriers fronting surplus lines programmes. See carrier solutions.
Lloyd's managing agents
Oversight of coverholders under binding authority contracts, with the evidence a managing agent needs to show Lloyd's its supervisory duty is discharged. See what managing agents look for.
Reinsurers with delegated programmes
Programme business written through MGAs and reported up through bordereaux, checked against the terms of the arrangement. See reinsurance operations.
Start with the MGAs that cost you the most time
Oversight is set up MGA by MGA. A sensible first scope is the handful of MGAs whose bordereaux take the longest to check or produce the most queries. Each one needs its binder terms configured as rules and its bordereaux layout mapped once; after that, every period runs through the same validation. Further MGAs are added by configuration, not development.
Regure runs on separate infrastructure for the United States and for Switzerland / Europe, holds ISO/IEC 27001:2022 certified security controls, and writes every action to an immutable audit trail. Pricing follows the same model as the rest of the platform: a platform fee, a one-time configuration scope and infrastructure where residency requires it. See how implementation works and security.
Delegated authority oversight questions
What software helps carriers oversee many MGAs?
Oversight software has to do three things a policy system does not: take in each MGA’s bordereaux in whatever format it arrives, check every line against the binder that MGA writes under, and keep the audit and remediation history per MGA. Regure does all three on one record, configured per MGA and per binder, so a delegated authority team sees exceptions across its whole distribution rather than one spreadsheet at a time.
Can Regure validate bordereaux from MGAs that do not use Regure?
Yes. Bordereaux arrive by email, SFTP or upload as spreadsheets or documents, are extracted and mapped to a common model per MGA, and are validated against that MGA’s binder: limits, classes, territories, dates and premium arithmetic. Exceptions are flagged and queried back to the MGA, with the query and its resolution kept on the record.
How does Regure detect authority breaches?
Each binder’s terms are configured as rules. Every bordereau line is checked against them as it comes in, so a risk bound outside limits, in an excluded class or territory, or after the period of authority is flagged in the period it was written rather than discovered at the annual audit.
Can we run delegated authority audits in Regure?
Yes. Audits are scheduled per MGA, evidence requests are issued and tracked, the evidence is held against the MGA and binder, and findings are recorded with owners and due dates and tracked to closure. The next audit starts from the last one’s history rather than from a blank spreadsheet.
What changes when our MGAs run on Regure themselves?
Oversight moves upstream. The MGA’s binder terms are enforced before bind, out-of-authority risks are referred to you with the file attached, bordereaux are generated from the MGA’s operating record, and the delegated authority audit pack is exported for any period. You receive data you can trust rather than data you have to check.
Who is this for?
Carriers and capacity providers writing through MGAs, Lloyd’s managing agents overseeing coverholders, and reinsurers with delegated programmes: any team accountable for business written under someone else’s pen.
See one MGA's bordereau validated against its binder
Bring one binder and one redacted bordereau from an MGA you oversee. We'll take it in, check it against the binder and show you the exceptions.