AgencyBloc data after an acquisition: health, life and group benefits

Abe Harbid, 26 October 2026

AgencyBloc’s own pages describe a suite built for health, life and group benefits agencies, with AMS+ as the management system and Commissions+ for commission processing [1][2]. An acquirer buying an agency on it is buying a book of individual, Medicare and group business with commission hierarchies, not a property and casualty book. The mapping problems follow from that.

What is distinctive about AgencyBloc agencies

The home page calls the suite "built for health and benefits professionals" and names Medicare, group benefits and individual and ACA lines of business [1]. The people it serves are independent agents and agencies and insurance uplines (IMOs, FMOs and GAs), in roles from sales producer to commissions manager [1]. The pricing page describes AMS+ as covering customer and policy management, lead management, marketing and reporting for independent agencies, GAs, IMO/FMOs and call centers [2]. Quote+ is described as a group health quoting and enrollment product for small group brokers, agencies and GAs [2].

Another AgencyBloc page lists what AMS+ tracks: clients, policies, tasks and communication, with prospects, carriers and agents, and says agencies track individual and group clients [1][3]. Policy records are described as including policy numbers, carrier details and coverage types [3].

Those lines produce different data. An individual or Medicare policy belongs to one person. A group case has an employer and, in a typical group record, members and a plan year. The agency that sells both has two shapes of record in one system.

What the agency can export

The AgencyBloc pages we read do not describe an export function. The page on choosing an AMS says data migration is part of implementation but gives no format detail and does not describe exports [3]. The commissions page does not say whether commission reports leave the system as spreadsheets or PDFs [4]. So we cannot state the format, and the exact export depends on how the agency set up its reports.

What an acquirer can ask for is generic. Clients and prospects with their types, policies with carrier, plan or product, effective date, premium and status, the agent list and any hierarchy above each agent, and the carrier commission statements as the carriers sent them. Ask separately for the group cases, since the employer and the members are not one record. Also ask which fields the agency uses for Medicare, because the pages we read do not say what the system stores for it [3].

What breaks when you map it to your standard

• Persons and groups in one list. A platform standard written for property and casualty has a client and a policy. A group case adds an employer and members, and the policy premium belongs to the group. The engine keeps cases apart from individual policies and flags a row it cannot place.
• Renewal logic. Individual and Medicare policies may renew on terms that differ from a P&C policy’s annual term. A mapped policy can look expired when it is not, so retention on the dashboard depends on how status is decided first.
• Agents above agents. Commissions+ is built around agent payment hierarchies, with downlines, overrides and bonuses [4][5]. A producer in your roster may sit beneath an upline in the agency’s records. The mapping has to say which level is the producer of record and which is a payee.
• Prospects as records. AMS+ holds leads and prospects beside clients [1][2]. Mapped as clients, they inflate the book.
• Carriers by product. The carrier codes in a file may identify a product or a company. The engine flags unknown codes with the premium behind them and does not guess which.

Commission statements next to the export

This is where AgencyBloc is documented best. The Commissions+ page says it uses built-in mapping software that interprets and itemizes carrier statement data, including statements of 20,000 or more lines, with carrier-specific maps [4]. A red edit tool flags lines needing attention and shows where commissions may be missing by comparing statement data against the AMS+ records [4]. Agents’ payment hierarchies, splits, overrides and bonuses are set up once and calculated from the stored rate tables [4]. The six-step process another AgencyBloc page gives is: set up policies, set up rate tables, tie payees to policies, import carrier files, reconcile commissions and generate agent statements [5]. The home page also names a "Commissions Not Received" report [1].

For an acquirer, the point is that the commission the agency records is calculated per payee [4]. The file you receive may show amounts per level of the hierarchy, not one rate per policy.

What our engine builds for an AgencyBloc agency

The engine keeps a mapping per source layout, as it does for every system, and for this one it handles cases and hierarchies explicitly. Individual policies and group cases are mapped to different parts of your standard. For each agent it records the upline chain given in the export and asks once which level is the producer. That answer is stored with the layout.

It then reads the carrier statements, and matches lines to the mapped book. It lists unmatched lines, rate differences and carriers that sent no statement. The agency goes on the dashboard by producer and agency, beside the P&C agencies you own. Your team receives an import file in your layout and an error report, and runs the import. The engine does not replace Commissions+ for paying agents; it reconciles what the carriers paid to the book you now hold. More on commission reconciliation.

Questions

Return to the systems list or the engine overview, and book a diagnostic to test a sample.

AgencyBloc, AMS+, Commissions+, Quote+ and Engage+ are trademarks of their owners. Loadbearing Software is not affiliated with, endorsed by or a partner of any of them.