At a glance
- Agencies reconcile carrier commission statements against policy and transaction records in the agency management system (AMS), then investigate whatever doesn't match before commission revenue is recorded.
- Three options automate that match — an AMS-native module, a point tool, or a custom agent — keyed to AMS instance count, carrier count, statement formats, and split complexity.
- Applied Recon is embedded in Applied Epic; Vertafore names no AMS. Neither vendor's own material describes reconciling across more than one AMS instance or complex producer splits, so confirm both points with the vendor.
- Roll-ups running more than one AMS instance after an acquisition need a plan for consolidating commission data across systems, not just within one of them.
- Not every discrepancy belongs on the same desk: a routing table sorts common discrepancy types by what they look like and who resolves them.
How do agencies reconcile carrier commission statements?
A carrier sends a commission statement — a report of the premiums it processed and the commission it owes on them — by mail, email, or a carrier portal, in whatever format that carrier uses. An agency's accounting team reconciles that statement against what the agency management system (AMS) expected for the same policies, then explains and resolves whatever doesn't agree before recording the revenue.
- Ingest the statement
Load the carrier's statement, whatever its format, and extract one line per policy or transaction.
- Match each line to the AMS
Confirm the policy is in force, and align the statement's reference to its AMS policy and transaction record.
- Check the expected commission
Compare the statement's rate and amount against the agency's agreement with that carrier, including contingent or override terms.
- Apply producer splits
Allocate the matched commission across producers per the agency's compensation plan, including any split or override percentages.
- Flag and route what doesn't match
Send differences in rate, amount, timing, or allocation to the preparer or accounting lead before the revenue posts.
Direct bill and agency bill business reconcile differently, even from the same statement. On direct bill, the carrier bills and collects premium from the insured and remits commission to the agency, so the agency reconciles what it's owed. On agency bill, the agency bills and collects premium itself, then owes the carrier the net premium after commission, so the agency reconciles what it owes as well as what it's paid.
The AMS module vs. point tool vs. custom agent comparison
Three kinds of system can run the match above: a reconciliation module built into the AMS, a dedicated point tool layered on one or more AMS platforms, or a custom agent built to the agency's own data model. The matrix below is our own recommended framework for choosing among them, not a market survey. It keys the choice to four things that make reconciliation harder as they grow.
| Option | AMS instances | Carrier count | Statement formats | Producer split complexity |
|---|---|---|---|---|
| AMS-native module (a reconciliation feature built into the AMS) | One | Within what your AMS module already supports | Formats your AMS module already parses | Simple: flat rates or a few standard splits |
| Point tool (dedicated reconciliation software layered on the AMS) | One, sometimes two | High | Wide variety, including formats your AMS module can't parse | Tiered, contingent, or override commissions your AMS module doesn't model |
| Custom agent (built to the agency's own data model) | Three or more, for example, after acquisitions | High | Inconsistent across the carriers each acquired agency brought with it | Complex and inconsistent across entities, including compensation plans acquired with each agency |
Read the matrix for your own agency, not as a ranking of one option over another: compare licensing, support terms, and build cost across options before choosing, and treat a custom agent's build cost as worthwhile only when a roll-up's AMS instances, carriers, and split rules don't fit inside one vendor's module or a point tool. This agency-specific match is one case of the account-matching work our page on financial reconciliation automation covers in general.
Is Applied Recon or Vertafore's Reconciliation Agent enough?
Applied Recon is a reconciliation feature embedded in Applied Epic, per Applied's description below. Vertafore's post doesn't say which AMS platforms or instance count its Reconciliation Agent supports — ask the vendor. Judge whichever module your AMS includes against the matrix's criteria for carrier count, formats, and split complexity, not against the other vendor's or a ranking of the two.
Whether either module is enough depends on the matrix above, not on which vendor you ask. Neither vendor's post describes reconciling across more than one AMS instance; confirm multi-instance support with the vendor before planning a roll-up around it. Neither vendor's material above describes producer-split logic, so an agency with tiered or override splits should confirm its module models them the way its compensation plan does.
How do roll-ups reconcile commissions across multiple AMS instances?
A roll-up with more than one AMS instance — for example, after acquiring agencies that each ran their own system — has to choose where commission data gets unified: inside one AMS, in a layer above all of them, or somewhere in between. Confirm with your AMS vendor whether its module reconciles across more than one instance before assuming it does.
- Migrate onto one AMS first
If consolidation onto a single AMS is already planned, sequence it ahead of reconciliation automation so the module can cover the combined book without a bridge.
- Keep AMS instances separate, consolidate at the ledger
Reconcile each instance with its own module or point tool, then bring the totals together only at the general ledger, where each entity's numbers already match.
- Normalize statement data above the AMS layer
A point tool or custom agent reads each AMS's export and the carrier statements directly, applying one set of rules across entities instead of each AMS's own logic.
- Treat legacy AMS instances as integration targets, not replacements
Where an acquired agency's AMS isn't being retired soon, connect to it through its own export or API rather than forcing its data into the acquiring AMS early.
That last pattern — reconciling against a system you aren't migrating yet — is the same problem a legacy AMS instance poses as any other older finance system; see legacy finance workflow automation for integration patterns that don't require a migration first.
What commission discrepancies should go to a human?
The table below is our own framework for routing discrepancies, not a survey of practice. Every type needs a person to resolve it; the question is who, and how fast. None should auto-resolve by overwriting the AMS's expected amount, since each can also signal a bigger problem.
| Discrepancy type | What it looks like | Who resolves it |
|---|---|---|
| Rate mismatch | The statement's commission rate differs from the agency's rate agreement with that carrier | Accounting preparer confirms the current agreement, then accounting lead approves any resulting adjustment |
| Short or missing payment | A policy the AMS expects commission on doesn't appear on the statement, or pays less than expected | Accounting preparer, escalating to the carrier relationship owner if the carrier can't confirm the cause |
| Timing difference | The statement posts in a different period than the AMS expects, for example around a renewal or endorsement | Preparer confirms it will reconcile next period before treating it as a real difference |
| Producer split discrepancy | The allocation across producers doesn't match the agency's compensation plan for that policy | Accounting lead, since this affects individual producer pay |
| Contingent or override true-up | A periodic or year-end contingent commission doesn't match the agency's own calculation | Accounting lead, often with the carrier relationship owner, since the carrier's contingent formula may differ from the agency's estimate |
| Statement parsing exception | The system can't extract or match a line because of an unusual statement layout | Preparer reviews the source statement directly rather than accepting a partial or guessed match |
Commission disputes and write-offs are approved by agency accounting in every row above, as the agency's own operating practice — not something this table or any automation decides.
Where to start: a first scoped workflow
Start with the carrier pattern that costs the most preparer time today, not the hardest case in the matrix. A scoped pilot proves the match logic on real statements before it touches commission revenue.
- Pick one carrier relationship
Choose a carrier with enough volume to be a real time cost, and simple enough — one AMS instance, standard splits — to prove the approach quickly.
- Replay two or three closed periods
Run the proposed matching logic against statements you've already reconciled by hand, and compare its matches and exceptions against what your preparer found.
- Set the routing rules before go-live
Agree which discrepancy types from the table above route where, and who approves an adjustment, before any match posts on its own.
- Expand by carrier, not by AMS instance
Add carriers one at a time within the same AMS instance before taking on a second instance or a more complex split structure.
Once reconciliation runs reliably for that carrier, its output becomes one input to the wider close process rather than a side spreadsheet; see financial close automation for how commission data fits into close coordination, accrual support, and sign-off.
When this doesn't apply
- A single AMS, a handful of carriers, and simple flat-rate commissions with no splits. The AMS's existing reconciliation feature likely already covers this without a new build.
- Most of your reconciliation differences trace back to how producer splits or carrier agreements are recorded, not to matching logic. Fix the underlying data first.
- You're mid-acquisition and still deciding whether to retire an acquired AMS. Settle that migration plan first; it changes which option in the matrix fits.
- Volume on a given carrier is too low to justify building or configuring anything beyond what your AMS already does.
Frequently asked questions
How much commission revenue is lost to reconciliation errors?
There's no verified, agency-wide figure to cite here, and a vendor's demo numbers aren't a substitute for your own data. Measure it directly: track short payments, missed statements, and write-offs you can't collect over several periods, and treat that total as your baseline rather than an industry number nobody checked against your book.
Can a single AMS module reconcile commissions across two AMS instances?
Neither Applied Recon's nor Vertafore's Reconciliation Agent's own documentation describes reconciling across more than one AMS instance; confirm with the vendor before assuming either one does. Unless the vendor confirms it, plan for a migration, a point tool, or a custom agent that reads across both systems.
What's the difference between a point tool and a custom agent for commission reconciliation?
A point tool is purchased software built to reconcile commissions across carriers and statement formats, configured to your rules. A custom agent is built to your own data model and compensation plan. Point tools fit high carrier or format variety within one or two AMS instances; custom agents fit roll-ups no vendor product already unifies.
Should AI-matched commission lines auto-post to the ledger?
No. Treat an AI-suggested match as a proposal a preparer confirms, not a posting that happens on its own. Reserve auto-posting for lines that match exactly against a known policy and rate, and route everything else, including every AI-suggested match, to a person before it affects recorded revenue.
How do producer splits complicate commission reconciliation?
A split or override means the statement's single commission amount has to be divided correctly before reconciliation is complete. Where the carrier's statement shows only a policy-level commission, the agency's compensation plan has to drive the split. If your AMS module can't model your tiered or override splits, that's a reason to look at a point tool or custom agent.
Related reading
- Financial reconciliation automation covers the account-matching workflow this agency-specific problem is a case of.
- Legacy finance workflow automation covers integrating with an older AMS or accounting system you aren't ready to retire.
- Financial close automation covers how commission reconciliation output feeds the wider month-end close.
- Reconciliation match rules and exceptions gives the general match-type and exception framework behind the routing table above.
More in Insurance operations
What AI Claims Automation Costs: A Cost and ROI Model for Carriers, TPAs and MGAs
AI claims automation cost depends on scope, not a price list. Get the cost drivers, an LAE baseline worksheet, and a payback method for carriers, TPAs and MGAs.
Insurance CompaniesBordereaux Automation for MGAs and Carriers: Ingestion, Validation and Reconciliation Checks
Bordereaux automation for MGAs and carriers: a validation-and-reconciliation check matrix with data source, rule, tolerance, owner and action for every check.
Insurance CompaniesLoss Run Extraction Automation: A Field Schema and Accuracy Test for Agencies and Underwriters
Loss run extraction automation needs a shared field schema and a tie-out test across carrier formats: the minimum fields to pull and five checks to trust it.
Insurance Companies