Skip to content
For Managing General Agents

MGA software you can run the whole operation on

Submission to bind, endorsements and renewals, claims under delegated authority, commissions and bordereaux — on one record, with authority limits enforced at the point of decision rather than checked at audit. Built for US MGAs and Lloyd's coverholders.

What MGA software has to do that carrier systems never did

A managing general agent operates with delegated underwriting authority from capacity providers, binding coverage on behalf of carriers and earning commission on written premium. That model puts three things beyond negotiation: binding fast enough to win the business, staying provably inside the authority granted, and reporting back to capacity on their terms. MGA software is judged on all three at once.

Carrier systems were built for the opposite position. A carrier owns the risk, sets its own appetite and reports to itself. An MGA owns none of the risk, works inside someone else's appetite, often for several capacity providers at the same time, and has to evidence every decision to each of them. Software that treats the binder as a reference document rather than a set of enforced rules leaves that evidence to be assembled by hand.

Retained margin in the MGA model is thin, so every manual step comes straight out of it. Hours spent rebuilding bordereaux, re-keying submissions or preparing for an audit are hours not spent underwriting. Slow submission handling and slow binder issuance cost business to MGAs who simply move quicker.

A large share of the MGA market still runs core processes on email, spreadsheets, shared drives and manual document handling — not because the operators do not know better, but because the systems built for carriers never fitted the distribution model and the alternative was a bespoke build. That is the incumbent Regure is usually replacing. For a vendor-by-vendor view of the market, see our best MGA software comparison for 2026.

Run the whole MGA on it, one binder at a time

Regure is the operating platform: products, rating, binding, policy administration, claims, commissions and bordereaux on one record, with every submission, binder and endorsement held in an evidence-grade document store. You do not have to move it all at once. Binders move over one at a time, renewal-led or with their in-force book, and the legacy workflow behind each one is retired once it is accepted. See how switching works.

Automated BordereauxPremium and claims bordereaux generated from transaction data — not manual Excel compilation
Binder IssuanceBinders generated from the approved submission — not drafted by hand after the decision
Delegated Authority ComplianceAudit trails showing every bind and claim decision was within delegated authority limits
Submission-to-Quote AutomationExtract data from submissions, route to underwriters, auto-populate rating
Three insurance professionals discussing a programme around a table
For MGA founders and teams

More time with brokers and capacity, less on admin

The relationships that grow an MGA happen in meetings like this one. Regure takes the operational load off the team: authority checks, claims intake, documents and bordereaux run on one record, so the people you have can spend their time on the business.

Can you run the MGA on it?

Most MGA software pages answer a narrower question than the one being asked. This is the scope an MGA running on Regure operates across — not a roadmap, and not a list of integrations to other people's products.

01

Products, rating and quoting

Products are configured per programme with their own rate tables, and quotes are built against them rather than in a spreadsheet beside the system. Rating changes are configuration, and rate tables are versioned, so a quote can be explained months later against the rates in force when it was written.

Product configurationVersioned rate tablesQuote revisions
02

Binding, issuance and the policy year

Binding against authority terms, policy issuance, mid-term endorsements and renewals all run on the same record. The policy has one history rather than a folder of documents and a separate note about what changed.

Authority checks at bindEndorsementsRenewals
03

Claims under delegated authority

Claims handled within the scope your coverholder or binder agreement allows, with authority limits enforced at the point of decision and the evidence of that sitting on the claim rather than being assembled for an audit later.

Authority limitsClaim evidenceReferral trail
04

Money out and money in

Commissions calculated on the terms in the agreement, invoicing off the policy, and the figures reconciling to what was bound rather than being rebuilt at month end.

Commission termsInvoicingReconciliation
05

Bordereaux and capacity reporting

Premium and claims bordereaux generated from the book on each capacity provider's own template, on their own cadence, rather than compiled by hand each period.

Per-provider templatesPremium and claimsScheduled delivery
06

Brokers, policyholders and roles

Broker and policyholder portals over the same data, with what each role can see and do configured per operation. Documents are generated in the languages the operation actually works in.

Broker portalRole permissionsMulti-language documents
One policy record across one policy year — bind, endorsements, a claim and the renewal all on the same record, each carrying the authority check that allowed it.

Every stage of the MGA lifecycle, and what it leaves behind

An MGA is judged on what it can evidence, not just what it can process. Each stage below runs on Regure and produces something a capacity provider, a managing agent or a regulator can be shown.

MGA operating scope — what runs on Regure at each stage of the lifecycle, and the evidence it produces.
StageWhat runs on RegureWhat it producesConfigurable
Submission intakeSubmissions arrive by email, broker portal or API. Documents are classified on structure rather than filename and fields are extracted with a confidence score on each one.A submission record with the original documents attachedConfigured per programme
Appetite and referralChecked against the programme's appetite and the binder's authority terms. Anything outside them is referred with the reason attached rather than rejected silently.A referral carrying its reason and its decisionConfigured per programme
RatingRate tables are configured per product and versioned, so a price can be explained months later against the rates that were in force when it was written.A priced risk traceable to a specific rate versionConfigured per programme
QuotingQuotes are built against the configured product rather than in a spreadsheet beside the system. Every revision is its own record.A quote document and its full revision historyConfigured per programme
BindingBound against the terms of the binder, with authority limits enforced at the point of decision rather than checked afterwards.A binder with the authority check recorded on itConfigured per programme
IssuancePolicy documents are generated from the bound record, in the languages the operation actually works in, and signed where a signature is required.Policy schedule and wording, with the signature event loggedConfigured per programme
EndorsementsMid-term changes are made on the same policy record, so the policy carries one history instead of a folder of documents and a note about what changed.An endorsement with its before, after and effective dateConfigured per programme
RenewalsThe renewal is built from the expiring record and priced on current rates, with the prior year alongside it.A renewal quote and a like-for-like prior-year comparisonConfigured per programme
ClaimsClaims handled within the scope the coverholder or binder agreement allows, with authority enforced at the point of decision.A claim file carrying its own authority evidenceConfigured per programme
CommissionsCalculated on the terms in the agreement and taken off the policy, so the figures reconcile to what was bound instead of being rebuilt at month end.Commission entries that tie back to the bound policyConfigured per programme
Bordereaux and reportingPremium and claims bordereaux generated from the book on each capacity provider's own template and cadence.The bordereaux file, per provider, per periodPer provider
Audit and oversightEvery action is attributable, versioned and time-stamped as it happens, and what each role can see and do is configured per operation.An evidence pack assembled by the work, not after itConfigured per programme

Where the operation runs matters as much as what it does: Regure deploys on regional infrastructure, so data residency is a deployment choice rather than a custom build. See EU data sovereignty and security and infrastructure.

Binder enforcement at the point of decision, not at the audit

Capacity providers audit how you use the authority they delegate. Regure turns the binder into enforced rules, so the evidence that every bind and claim decision was within limits is created by the work itself.

A binding authority agreement sets out what an MGA may write: the classes and products, territories, maximum limits and premium, referral triggers, exclusions, the period of authority and, often, a separate claims authority. In most operations those terms live in a PDF and in underwriters' heads, and compliance is reconstructed months later by sampling files against the contract.

On Regure the binder terms are configured once and checked at quote, bind, endorsement, renewal and claims decisions. A risk inside authority proceeds. A risk outside it is referred to the capacity provider with the reason attached, and the referral, the response and the person who acted on it are recorded on the policy. Nothing is rejected silently and nothing is bound first and explained later.

When an audit request arrives, the pack is a report rather than a project: every bind for the period with the authority check that allowed it, every referral and override with its approval, and every claim decision with the authority it was made under. For Lloyd's coverholders, that is the evidence a managing agent expects during a delegated authority review. See delegated authority audits for what auditors test and what the pack contains, and oversight for carriers and managing agents for the view from the other side.

  • Every bind decision logged with the underwriter, timestamp, premium, limits and effective date
  • Authority checks run before the binder is issued, not after
  • Out-of-authority placements referred to the capacity provider with full documentation
  • Complete audit trails from submission through underwriting notes, bind decision and issuance
  • Capacity provider audit packages exported for any period
Delegated Authority — Compliance Check
Bind within premium limit ($500K cap)✓ Compliant
Coverage within authority scope (GL)✓ Compliant
Geographic restriction (US only)✓ Compliant
Claims authority (up to $100K)✓ Compliant
Illustrative limits. The checks above show the shape of a configured binder; the actual terms are whatever your binding authority agreement says. See binding authority in the glossary.

Submission-to-quote automation that eliminates manual data entry

Submissions arrive as email attachments with ACORD forms, loss runs, and exposure schedules. Regure extracts data automatically, routes to the right underwriter, and pre-populates rating — so underwriters spend time evaluating risk, not re-keying data.

ACORD Extraction
Auto-Processing
Form Type
ACORD 25
Policy Number
CA-8392-047
Effective Date
Jan 1, 2026
Premium
$2,847/yr
86%

ACORD Form Extraction

ACORD applications (ACORD 125, 126, 127, 130, 131, 140) arrive as PDFs. Regure extracts the fields — named insured, addresses, coverage requested, exposure data, loss history — each field carrying a confidence score. High-confidence fields flow directly into rating or your underwriting workbench; anything uncertain is flagged for review first.

For US MGAs processing commercial submissions at volume, see ACORD form automation for US MGAs.

Intelligent Submission Routing

Regure routes submissions by line of business, coverage type, premium size and underwriter expertise, after checking them against programme appetite — so they reach the right underwriter immediately rather than waiting in a shared inbox.

Rating and Binder Issuance

Rating runs on versioned rate tables configured per product, or data is passed by API to a rating tool you keep. Once an underwriter approves, the binder is generated from the bound record — limits, deductibles, premium, dates and insured details — routed for e-signature and delivered to the broker, with every signature logged in the audit trail.

Claims handled within the authority you hold

Some MGAs settle claims under delegated claims authority; others hand claims to the carrier or a TPA and still have to report on them. MGA software has to support both on the same policy record.

Intake that arrives as a complete file

First notice of loss from brokers and insureds is read, filed against the right policy and triaged, with missing documents requested before a handler opens the file. The claim is checked against the coverage that was actually bound, because it sits on the same record. See claims automation for the full workflow.

Claims authority enforced like underwriting authority

Reserve and payment limits from the claims agreement are configured per handler and per binder. A reserve or settlement above authority is referred to the carrier or managing agent with the file attached, and the approval is recorded on the claim rather than in an email thread.

Claims bordereaux from the live record

Reserves, payments and movements feed the claims bordereau directly, so the figures a capacity provider receives match the claim files they can inspect. There is no separate spreadsheet to reconcile.

Working with a TPA or the carrier's claims team

Where claims are handled outside the MGA, Regure records the notification, tracks status and holds the documents, so the MGA can still report on its book and see loss experience by programme. See TPA operations.

See a bordereau generated from your own data

Bring one binder and one redacted bordereau. We'll show the authority checks configured and that bordereau produced from live records.

Bordereaux and capacity-provider reporting without the monthly rebuild

Bordereaux reporting for coverholders and MGAs: premium, claims and endorsement data aggregated from processed transactions and formatted to each capacity provider's specification.

Every MGA with delegated authority reports bound premium, claims and endorsements to its capacity providers monthly or quarterly. These bordereaux show what business was written under the binding authority agreement, what claims were notified and what reserves were set.

For most MGAs, bordereaux assembly is a manual Excel exercise. An operations analyst pulls data from the policy system, formats it to the capacity provider's template, validates totals and emails the spreadsheet. With several capacity providers, each requiring a different format, that work repeats every period — and every rejection creates another version.

Regure generates bordereaux from the operating record instead:

  • Premium bordereaux: policies bound in the period with premium, exposure, dates and policy details, per capacity provider specification
  • Claims bordereaux: new claims, updates and reserve movements with incurred and paid amounts
  • Endorsement bordereaux: mid-term changes with premium adjustments and coverage changes
  • Multi-capacity support: separate templates for each Lloyd's syndicate, US carrier or reinsurer
  • Scheduled generation on each provider's cadence, delivered by email, SFTP or API
  • Validation before submission, with every figure traceable to the policy or claim it came from

For US MGAs this includes surplus lines tax and stamping fee data per state. For Lloyd's coverholders it includes delegated authority evidence formatted for managing agent review. The coverholder bordereaux page covers the Lloyd's reporting standards in detail, and our bordereaux reporting guide for Lloyd's coverholders explains what managing agents reject and why.

Bordereaux Queue — Example period
Premium Bordereau — Syndicate 1234Sent
Claims Bordereau — ABC Insurance Co.Sent
Endorsement Bordereau — XYZ ReinsuranceGenerating
Surplus Lines Tax — All StatesReview req'd
Reporting to reinsurers too: where capacity sits behind a reinsurance arrangement, the same records feed reinsurer reporting. See reinsurance for MGAs.

Launching a new programme is configuration, not a development project

An MGA grows by adding programmes and capacity. If every new product waits on a vendor change request, the capacity sits unused while the build is scheduled.

Products and rating

Product structure, coverages, questions and rate tables are configured per programme and versioned, so a rate change takes effect on a date and earlier quotes still explain themselves. See configurable rating.

Authority and referrals

The new binder's limits, territories, referral triggers and claims authority are loaded as rules, so the programme writes within control from its first quote rather than after a retrospective review.

Documents and reporting

Policy wordings, schedules and certificates are templated per programme, in the languages the operation works in, and the capacity provider's bordereaux template is set up alongside the product rather than after the first reporting deadline.

What US MGA software has to handle

US MGAs writing excess and surplus lines carry obligations that a Lloyd's or European operation does not. The US MGA software page covers them in depth; the essentials are below.

Surplus lines compliance

Each state sets its own surplus lines premium tax, stamping fees, filing deadlines and diligent search rules. Multi-state placements allocate premium across states from the exposure data on the submission, and filing deadlines are tracked. See US surplus lines compliance by state.

ACORD automation

US commercial submissions arrive as ACORD applications and supplements. Extraction with confidence scoring removes re-keying while keeping a human on anything uncertain. See ACORD form automation.

FNOL automation

Loss notices from retail agents, wholesalers and insureds arrive by email, portal and phone. Intake creates the claim against the bound policy and routes it within claims authority. See FNOL automation for US MGAs.

MGA software for Lloyd's coverholders and delegated authority

A Lloyd's coverholder works under a binding authority contract with one or more managing agents, and the managing agent is accountable to Lloyd's for how that authority is used. That puts two requirements on the coverholder's systems: bordereaux in the format the market expects, delivered on time and accurate the first time, and evidence that binding and claims handling stayed within the contract.

Regure produces both from the operating record. Risk, premium and claims bordereaux are mapped to each managing agent's requirements, and the delegated authority audit pack — binds within contract terms, referrals with their approvals, claims within the coverholder's authority — is exported for any period. For the FCA side of operating in the UK, including Consumer Duty, see UK and Ireland insurance compliance.

Many coverholders also write US business, or are US MGAs that have added Lloyd's capacity. Both models run in the same Regure instance: surplus lines and state filings on one programme, Lloyd's bordereaux and managing agent reporting on another, with each binder's terms enforced on its own business.

MGA software for a start-up MGA and for a scaling one

Start-up MGAs

A new MGA usually has one binder, one capacity provider, a small team and a carrier that wants to see control before it extends more capacity. The risk is building the operation on spreadsheets and email, then having to re-platform at exactly the moment the book starts to grow.

On Regure a start-up configures only what it uses — typically quoting and binding against the binder, claims intake and bordereaux — and adds policy administration scope, products and capacity providers later on the same record. The small team handles the decisions; the system carries the routine work and the evidence.

Scaling MGAs

An established MGA has the opposite problem: several programmes, several capacity providers, possibly several jurisdictions, and a stack that has grown by accretion. Each new programme adds another reporting format and another place where the authority terms are tracked by hand.

Here Regure replaces the stack in phases, by product or binder. Each phase defines when Regure becomes authoritative for that scope and which legacy workflow is retired, until the whole operation runs on one record. See the policy administration platform and how switching works.

What an MGA deployment has actually covered

One coverholder operation, three products, configured end to end. Named references are available under NDA during procurement.

Live in production

Swiss Lloyd's coverholder

Specialist medical insurance

Three insurance products configured on Regure, covering the operation end to end — from quoting through to Lloyd’s reporting — on Swiss data residency.

  • Quoting
  • Configurable rating
  • Policy administration
  • Claims
  • Commissions
  • Invoicing
  • Lloyd's bordereaux
  • Broker portal
  • Policyholder portal
  • Multilingual documents
  • Swiss data residency
Operating today

Multi-region deployment

United States and Switzerland / Europe

Regure runs separate infrastructure per region, so data residency is a deployment choice rather than a custom build.

  • US deployment
  • Swiss / EU deployment
  • Regional data residency
  • Per-region infrastructure

How to evaluate MGA software: a checklist

Whichever vendor you shortlist, these are the questions that separate MGA software from a carrier policy system with a binder field added. Ask each vendor to demonstrate them on your own binder terms and a real bordereau, not on a prepared demo dataset.

  • Are binder limits, territories and referral triggers enforced at quote, bind and endorsement, or only reported on afterwards?
  • Is claims authority enforced on reserves and payments in the same way as underwriting authority?
  • Can each capacity provider have its own bordereaux template and cadence without custom development?
  • Does every bordereau figure trace back to a specific policy, endorsement or claim?
  • Can a new programme — product, rating, documents, authority — be launched by configuration?
  • Are rate tables versioned so an old quote can be explained against the rates in force at the time?
  • Does it support both US surplus lines obligations and Lloyd's coverholder reporting if you need both?
  • Can it take over one binder at a time and retire your current system behind it, without a big-bang cutover?
  • Where is the data hosted, and can residency be chosen per region?
  • Can the vendor show what a deployment has actually covered, with references under NDA?

Two things tend to decide the outcome. The first is whether authority is a rule or a report: a system that only tells you afterwards that a bind was out of authority has not reduced your exposure, only documented it. The second is whether bordereaux come from the operating record or from an export that someone reshapes; only the first stays accurate as the book grows.

For a comparison of how the main vendors answer these questions, see best MGA software in 2026. If you are still defining the operating model, the MGA glossary entry and delegated authority explain the structure the software has to support. When you are ready, book a demo and bring a binder.

MGA software questions

What is MGA software?

MGA software is the operating system for a managing general agent: it quotes and binds within the authority a capacity provider has delegated, administers the policy through endorsements and renewals, handles claims within the agreed claims authority, calculates commissions, and reports premium and claims back to each capacity provider as bordereaux. The defining requirement is that the authority terms of the binder are enforced by the system, not checked afterwards.

What's the difference between an MGA platform and a policy administration system?

A traditional PAS focuses on policy, rating and financial transactions. An MGA platform must also control submission intake, binding authority, capacity reporting, bordereaux and delegated-authority evidence. Regure does both jobs, allowing an MGA to migrate the binder lifecycle onto one operating platform and retire the fragmented systems and manual processes it replaces.

Can Regure replace my existing MGA management system?

Yes. Products and rating, quoting, issuance, endorsements, renewals, claims, commissions, invoicing and bordereaux can all run on Regure, with broker and policyholder portals over the same record. Migration is phased by product or binder, with integrations supporting the transition until the incumbent workflows and systems for that scope are retired.

Do you support both US MGAs and UK coverholders?

Yes. Regure supports the US MGA model (surplus lines, state-by-state stamping office requirements, ACORD submissions, US carrier bordereaux formats) and the Lloyd's coverholder model (binding authority contracts, delegated authority compliance, coverholder bordereaux, managing agent audit packages) — in the same instance for MGAs operating on both sides of the Atlantic.

Does Regure automate bordereaux for all capacity providers?

Yes. Each capacity provider — a Lloyd's syndicate, a US carrier, a reinsurer or a European insurer — gets its own template, field mapping and cadence. Bordereaux are generated from the operating record, validated before they are sent, and delivered by email, SFTP or API.

Can Regure validate delegated authority limits automatically?

Yes. Binder terms — premium and limit caps, classes, territories, referral triggers and claims authority — are configured once, and every quote, bind, endorsement and claim decision is checked against them. Anything outside authority is referred with the reason attached before the commitment is made.

We are a start-up MGA. Is this too much system for us?

No. You configure only what you use. A new MGA can start with one binder — quoting, binding, claims intake and bordereaux — and add products, capacity providers and policy administration scope as the book grows, without re-platforming later.

How much does MGA software cost?

Regure pricing for MGAs is scoped rather than listed per seat: a platform fee set by the modules you run, the number of products and the workload, plus a one-time configuration scope. A focused starting point costs materially less than a full deployment. Contact us for a scoped quote based on your book, products and team size.

Walk us through your MGA

Bring one binder and one real bordereau. We'll show your authority terms checked at the point of decision and that bordereau produced from live records.

Book a working session