How does a configurable policy administration system make an MGA more efficient?

A configurable policy administration system makes a managing general agent (MGA) more efficient by holding each capacity provider’s rates, limits, referral rules, documents and reporting requirements as settings rather than as code or spreadsheets. Staff quote inside their authority without checking a rate sheet, risks outside it are referred automatically with the reason shown, and bordereaux are produced from data that was entered once. Launching a product or moving a scheme to new capacity becomes set-up work rather than a development project.

The rest of this article explains where that time is actually saved, and what to check when you compare systems.

Why do MGAs have more admin than most insurance businesses?

An MGA writes business on someone else’s capacity, under a delegated authority agreement. That brings a layer of work a broker or a direct insurer does not carry in the same way.

Each capacity provider has its own rates, excesses, limits and referral points. Each one wants its premium and claims bordereaux in its own format, on its own timetable. Each one audits the book and expects every decision to be traceable. Many MGAs also write several specialist classes, sometimes with different insurers behind each scheme.

When that is run from spreadsheets, email and a system that was never designed for delegated authority, the same data gets typed in several times and checked by hand at every step. That is where the cost sits.

Where does a configurable system save time?

Quoting inside your authority

When rating tables and authority limits are settings in the system, a quote is produced from the answers on the screen. Nobody has to open the right version of the right insurer’s rate sheet, and nobody has to remember which excess applies to which risk. Optional covers such as legal expenses or terrorism can be added at quote and priced at the same time.

Referrals that route themselves

The points where a risk has to go to an underwriter, or back to the insurer, are configured once. Everything inside them quotes straight away. Everything outside them is referred with the reason recorded, so the underwriter sees why it stopped and nothing gets bound that should not be.

One record from enquiry to renewal

Enquiry, quote, referral, policy issue, mid-term changes, renewal and cancellation all work from the same policy record. Documents are produced from that record rather than retyped into a template. Renewals pick up the current terms and rates without anyone rebuilding the policy.

Bordereaux without rebuilding the figures

Because each policy already knows which insurer it belongs to and which rules applied, premium and claims bordereaux can be produced per insurer from the data the team has already entered. Agent statements come from the same records. Month end stops being a spreadsheet exercise.

Brokers submitting online

A broker portal that sits on the same rules lets brokers complete the application themselves, see a price where your rules allow it, and submit business that lands directly in the system. Anything outside the rules becomes a referral rather than a quote, so the portal cannot write business your authority does not allow.

Answering audits from the system

When every change to a record is logged with who made it and when, a capacity provider’s audit question is answered by looking at the record, not by searching inboxes.

How does configuration help with new products and capacity?

This is where the difference between a configurable system and a hard-coded one shows most.

If questions, rating tables, referral points and document wording are configuration, adding a product, changing a rate or moving a scheme to a new insurer is a set-up change. If they are written into the software, every one of those changes waits for a developer, a test cycle and a release.

It is worth being clear about who does the configuring. In some systems your own staff change the rules through an admin screen. In others, including ours, the supplier sets products up with you. Either can work well. What matters is that a change is measured in days of set-up rather than months of development, and that you know before you sign who makes changes and how they are charged.

What should an MGA check when comparing systems?

Ask each supplier to show you, using one of your own products rather than a generic demo:

  • Several capacity providers at once. Can each insurer have its own rates, excesses, referral rules and bordereaux on the same system?
  • Authority enforced, not just recorded. Does a risk outside your authority stop and refer, with the reason captured?
  • Bordereaux per insurer. Are they produced from the policy data, in the format each insurer asks for?
  • A field-level audit trail. Can you see who changed what, and when, on any record?
  • A broker portal on the same rules. Does online business follow the same rating and referral logic as your own team?
  • A realistic data move. How will your existing book be converted, and how many trial runs happen before the switch?
  • Where your data is held, and who looks after hosting, backups and updates.
  • How changes are charged. A clear set-up fee and monthly fee, with any development quoted and approved before work starts, avoids surprises.

A supplier that cannot walk through these with an example close to your own business is unlikely to save you the time you are looking for.

How MPACS approaches this

MPACS is the policy administration system we build at Mandon, and it is used by MGAs writing specialist classes on third-party capacity, including commercial combined, commercial property, private medical and structural warranty. Each insurer’s rates, limits and referral rules sit in MPACS as settings, bordereaux are produced per insurer, MPORT gives brokers online submission on the same rules, and every change is logged down to the individual field. MPACS is hosted in a UK data centre and supported by the team that builds it.

We have built software for the insurance market, and only the insurance market, since 1999. If you would like to see how MPACS would handle one of your own schemes, book a demo and tell us what you write today.

All articles

See it with your own products

Tell us what you write and how you work today. We'll show you how MPACS would handle it, using examples that look like your business rather than a generic demo.

Book a demo