Commission tracking software for insurance agencies, and what an acquirer needs on top of it
Abe Harbid, 26 October 2026
Commission tracking software records what each carrier should pay an agency, posts what it did pay, and works out what each producer is owed. Inside one agency, on one management system, that is usually enough. A platform that has bought several agencies has a different problem: the same carrier pays each of them under a different code and layout, the books sit in different systems, and the platform needs one reconciled number by agency and by producer. That cross-agency layer is what this page is about.
What commission tracking does inside one agency
Most agencies handle commissions in three places. The management system holds the policies, the premium and the expected commission rate. Carriers send statements, either as files or electronically: Ivans Download, for example, delivers Direct Bill Commission Statement data from participating carriers into an agency’s management system so the agency can reconcile commissions each month [1]. Then someone posts the statement, matches lines to policies, and runs producer pay from the result.
Standalone commission tracking tools exist for agencies whose management system does not do this well, or for producers who want their own view. They differ in how they import statements, how they handle splits and overrides, and how they report. For a single agency, the right choice depends mostly on which management system it runs and how many carriers bill direct.
What changes after an acquisition
Once a platform owns several agencies, four things break the single-agency model:
- The same carrier appears under a different agency code at each agency, and sometimes under a different name in each management system.
- Statements for the acquired agency may keep arriving at the old agency’s address or mailbox for months, in the layout that agency was set up with.
- Producer splits follow the acquired agency’s comp plan until the platform’s plan takes over, so the same policy type can pay a producer differently at two agencies.
- The platform’s finance team needs commission revenue by agency, by carrier and by producer in one view, reconciled, before the agencies share a system.
None of these are failures of the agency’s commission tool. They are a level above it.
What an acquirer needs from a commission layer
| Need | Inside one agency | Across acquired agencies |
|---|---|---|
| Carrier codes | One code list | Each agency’s codes mapped to the platform’s, unknown codes flagged with the premium they cover |
| Statement layouts | The carriers the agency already set up | Every layout from every agency, read without retyping |
| Expected commission | Premium times the rate in the system | The same, computed from each agency’s mapped book in one layout |
| Variances | Posted and chased by the accounting team | Listed by agency and carrier, with lines for policies missing from the export |
| Producer view | The agency’s own splits | Each producer matched to the platform’s roster, with the split plan that applies |
| Reporting | The agency’s own reports | Commission revenue by agency and producer, next to retention and new business |
Software or a layer you own
A platform can buy a commission product and move every agency onto it, wait for each agency’s management system conversion and use the platform system’s commission features, or run a reconciliation layer over the exports and statements it already has. The first two take time per agency. The third works from day one but is only as good as its mappings and checks.
The acquisition-onboarding engine is the third kind. It reads each acquired agency’s carrier statements in their own layouts, maps carrier and producer codes to the platform’s, computes expected commission from the mapped book and lists every variance with its reason. The reconciliation side is described on commission reconciliation; producer splits across agencies are covered in producer compensation after an acquisition.
Questions to ask any commission tool before an acquisition
- Can it read a statement layout it has never seen, without a developer?
- Can it hold more than one agency’s code list and map them to one?
- Does it keep the decision when a person matches an unknown line, so the next statement uses it?
- Can it show expected and paid commission by agency and producer for agencies not yet on the platform’s management system?
- Where does the data live, and who can see each agency’s records?
Questions
What is insurance agency commission tracking software?
Software that records expected commission by policy, posts carrier statements against it, flags differences and calculates producer pay. It can be part of the agency management system or a separate tool.
Do carriers send commission statements electronically?
Many do. Ivans Download, for example, carries Direct Bill Commission Statement data from participating carriers into an agency’s management system [1]. Others send PDF or spreadsheet statements, which still have to be read and matched.
Why do commission numbers stop matching after an acquisition?
Usually because of carrier code changes, statements arriving in the old agency’s name, producer codes that do not match the new roster, or policies missing from the export. Our article on statement mismatches lists the five usual causes.
Can reconciliation run before the agency is converted to the platform’s system?
Yes, if the agency’s export and statements are mapped into the platform’s layout first. That is how the engine works: it does not need the agency to be converted.
See the full engine on insurance platforms, or test it on your own statements with a two-week diagnostic.
Ivans is a trademark of its owner. Loadbearing Software is not affiliated with, endorsed by or a partner of it or of any carrier named here.
Sources
- Ivans, "Ivans Download for Agents" (accessed 26 October 2026). ivans.com