Conversion vendor vs reconciliation layer: which one an acquirer needs

Abe Harbid, 26 October 2026

A conversion vendor moves an acquired agency’s book from its old management system into the platform’s system. A reconciliation layer does not move the book. It maps the agency’s data to the platform’s standard, checks it, matches carrier commission statements against the book, and shows every agency side by side. A platform that wants the agency on its own system needs a conversion. A platform that wants to know whether the numbers are right, in any system, needs reconciliation. Many need both, at different points in the deal.

What each one does

We are not a conversion vendor and do not name any here. A platform that wants a list should ask its management system vendor, its peers or its carriers, and check each vendor’s own pages for what it covers.

When you need a conversion

• The platform has decided to put every acquired agency on one management system and the agency’s staff will work in it.
• The old system will be switched off, and its contract is ending.
• The agency’s policy history, documents and notes must live in the target system.

Services firms list this kind of work among their offerings. ReSource Pro’s April 2026 press release, for one, names "agency management system transition project management" and "data cleanup and migration" as components of its M&A Integration Suite [1]. In these cases someone has to load the data into the target system, whether a vendor or the platform’s own team using the target system’s import path. A reconciliation layer does not replace this step.

When you need a reconciliation layer

• The platform wants commission revenue by agency and producer that ties to the carrier statements.
• Acquired agencies stay on their own systems for a year or more, and leadership needs one set of numbers sooner.
• Carrier statements stop matching after the acquisition, because policy numbers, producer codes or carrier codes changed.
• The platform expects to buy many agencies on the same few systems and wants the mapping saved.

Moving every agency onto one system takes time, and leadership usually wants reliable numbers before it finishes. The gap between the close date and the last conversion is where a reconciliation layer sits.

When you need both

A platform that converts each agency onto its management system still has commission statements to reconcile, and still has to find out what did not convert correctly. A sensible order is:

1. Before conversion, map and check the agency’s export. Fix duplicates, missing fields, unmatched producers and unknown carrier codes in the source file, so the vendor or your team loads cleaner data.
2. Convert, using the vendor or the target system’s own import.
3. After conversion, reconcile carrier statements against the book in the target system, and compare record counts and premium totals with the pre-conversion file.
4. Keep the cross-agency dashboard running for the agencies still waiting their turn.

The error report from step 1 is useful to a conversion vendor too, since it lists the rows that would otherwise fail on load.

What goes wrong when the two are confused

Platforms sometimes buy a conversion and expect it to answer the question of whether commission is right. It does not, because the conversion’s job is to move records. Others buy reconciliation and expect the agency to be on the new system when it is done. Neither is a flaw in the product, only a mismatch with the purchase. Writing down which of the two outcomes you want, "the agency is in our system" or "the numbers tie out", settles most of the choice.

How we price our side

Our diagnostic takes two weeks on one recent acquisition or a de-identified sample. Then comes one bounded build, a fee for each later acquisition by the acquired agency’s size, and a care plan. Fixed price, set by your acquisition volume and the systems involved, agreed in writing before work starts. The diagnostic fee is credited toward the build if you sign within 14 days of the readout.

Questions

Read about commission reconciliation and agency data conversion, return to the insurance overview, or book a diagnostic.

ReSource Pro is a trademark of its owner. Loadbearing Software is not affiliated with, endorsed by or a partner of ReSource Pro.