Agency management systems an insurance acquirer inherits

Abe Harbid, 26 October 2026

A platform that buys independent agencies meets the same handful of agency management systems again and again: Applied Epic, AMS360, QQCatalyst, Sagitta, BenefitPoint, HawkSoft, EZLynx, NowCerts and AgencyBloc. This guide is for the platform’s integration lead. It says who owns each system and who the vendor says it is built for, how to ask an acquired agency for its data, and where each system’s own page on this site goes deeper.

The systems at a glance

Owners and audiences below come from each vendor’s own pages, as of 26 October 2026. Where a page names no owner beyond a copyright line, the table gives the name on that line.

Vertafore also lists WorkSmart, a document management product, under its agency management heading with no description [4]. We do not cover it.

Why the system matters to an acquirer

The platform has its own standard: the fields it needs for a client, a policy, a producer, a carrier and a commission. The acquired agency’s system has its own idea of each. The size of the gap depends on the audience the system was built for. An enterprise system with divisions and branch hierarchies sends several levels where the platform wants one. A system for health and group benefits sends plans and cases where the platform wants policies. A small-agency system may send everything flat and clean, with the producer in two columns. Each system page on this site starts from what is distinctive about those users and that data.

The export is rarely a single file. In the vendor help pages we read, QQCatalyst and Sagitta describe reports that export to a spreadsheet or XML file [11][12]. What the seller sends depends on which reports its staff ran and on what it was permitted to run, and a vendor’s help page cannot say what a particular agency did.

How to ask an acquired agency for its export

Ask in writing, before close if the deal terms allow it, and ask for the same things whichever system the agency uses.

1. The name of the system and the version or edition, and the person at the agency who can run reports.
2. A client list with names, addresses and any client numbers the agency uses.
3. A policy list with number, client, carrier, line of business, effective and expiration dates, premium, commission rate and producer.
4. The producer roster with codes, and the split rules for new and renewal business.
5. The agency’s carrier code list.
6. Carrier commission statements for at least the last several months, in the layouts the carriers sent them.
7. The report definitions or the names of the reports used to make each file, and the date each was run.
8. Row counts for each file, and the totals of premium and commission the agency expects, so the file can be checked against a number the seller supplied.

Ask for CSV or Excel files, not PDF. A PDF is a picture of the data. Two of the systems we cover say so in their own help pages: QQCatalyst’s report page offers PDF as a view and a spreadsheet as the data file [11], and Sagitta’s help notes that XML exports omit Grand Totals, so the totals have to be supplied separately [12].

Keep every file the seller sends, with its date. When a second export arrives, the engine compares it with the first, so a corrected file does not lose decisions already made.

What our engine does with each system’s export

The engine takes the exports an agency’s system already produces. It maps each source layout to the platform’s standard and stores that mapping, so the next agency sending the same layout starts from it. It flags duplicate clients, missing required fields, producers not on the roster and carrier codes it cannot match, with the premium behind each. It reconciles carrier statements against the mapped book and lists lines with no policy and rate differences by carrier. It puts the agency on one dashboard with the others: revenue, retention and new business by agency and producer.

The output is an import file in your layout and an error report. Your own team loads the file through your own import path. The engine does not depend on a vendor interface, and it is not a conversion vendor. For the file side, see agency data conversion. For the statement side, see commission reconciliation. The checklist for the first quarter after a deal is in the 90-day data checklist.

Questions

For the engine as a whole, see insurance acquisition onboarding. To try it on a real deal, ask for the two-week diagnostic, or watch the fictional demo.

Applied Epic, Applied Systems, AMS360, QQCatalyst, Sagitta, BenefitPoint, WorkSmart, Vertafore, HawkSoft, EZLynx, NowCerts and AgencyBloc are trademarks of their owners. Loadbearing Software is not affiliated with, endorsed by or a partner of any of them.