6 min read

Does your AMS reconcile commissions? What it checks and what it misses

Systems differ, and so does setup. Here is what a commission reconciliation involves, which parts software can plausibly cover, and what to confirm with your vendor.

By Lapidar, the team building it · October 7, 2026

In short

An agency management system (AMS) records what your book says you should earn and, depending on setup, what carriers reported. Whether it checks that against the money that actually arrived varies by product, version and how it is configured.
Where a system does reconcile, it usually does so for transactions it received or entered. A commission that never produced a transaction leaves nothing to compare.
The gaps that cost agencies money tend to sit in the same places: missing lines, wrong rates, duplicates, late chargebacks, and policies that are on a statement but not in the book.
We don’t describe any specific product here. Ask your vendor the questions at the end of this page.

“Does my AMS reconcile commissions?” has no single answer, because agency management systems differ in how much they do and how much depends on setup. Many have a commission or accounting module. Some let you download carrier transactions, some accept statement files, and some leave statement entry to your staff. This page describes what a reconciliation of that kind generally involves, which parts a system can plausibly cover, and which parts tend to stay with a person. It makes no claims about any named product. Features change, so check each point with your own vendor.

What “reconcile” has to mean

A commission reconciliation compares three things for every policy and every statement period: what you should have earned, what the carrier says it paid, and what actually reached your bank account. Differences between any two of them are the work. A check that compares only two of the three is useful, but it will not find everything.

The “should have earned” side depends on your own records: the policy’s premium, effective date and status, plus the commission schedule that applies to that carrier, line and term. Our guide to reconciling carrier statements goes through the checks in order.

What an AMS may check

Depending on the system and how it is set up, some of the following can be automated. None of it should be assumed.

Matching statement lines to policies. Where statement data arrives as a download or an import, a system can match on policy number and carrier. This works best when the number in the system is the number on the statement.
Applying a stored commission rate. If a schedule is stored, some systems compute an expected amount and show the difference. That is only as good as the schedule: renewal rates, splits, tiers and carve-outs have to be entered and kept current.
Posting and balancing. Accounting modules can post commission receipts and show whether a statement total ties to a deposit.
Flagging unmatched items. Some systems list statement lines they could not match to a policy, so someone can look at them.

What tends to be missed

These are not criticisms of any product. They are places where the structure of the problem makes automation hard, whatever the software.

Commission that never arrived. A missing renewal produces no statement line, so there is nothing for the system to match. Finding it means starting from the book and asking, for each policy, where the payment is. See missing renewal commissions.
Statements that don’t arrive as clean data. Many carriers send PDFs, and layouts differ from carrier to carrier and sometimes change without notice. Someone, or something, has to turn each into rows.
Policy numbers that don’t match. Carriers add suffixes, change numbers at renewal, or print them with different formatting. A near miss is treated as no match, or matched to the wrong policy.
Chargebacks that arrive late. A cancellation can be reported months after the original commission was paid. The chargeback line may carry little to tie it to the original payment. Chargebacks explained covers why.
Policies on the statement and not in the book. A line for a policy your records don’t contain may be a data-entry gap, a policy written under another code, or a payment that belongs to someone else.
Duplicates across periods. The same commission can appear twice, in one statement or across two. Spotting it needs a view across periods, not a single statement.
Rates that are wrong but plausible. A stored rate that is out of date makes every comparison agree with the wrong number.

The reasons a statement and a system disagree are often ordinary. Our guide on statements that don’t match the AMS separates those from money owed.

Reconciliation depends on the data you give it

Even a well-built check has limits. If premium or status is stale in the system, the expected amount is wrong. If a carrier’s statement is incomplete, the paid side is wrong. An agency that downloads transactions from a carrier is reconciling against what that carrier reported, which is not the same as what was deposited. Know which one your process compares.

Questions to ask your AMS vendor

Does the system compare commission paid against an expected amount from my schedule, or only against what was entered or downloaded?
Which carriers can I receive statements from as data, and which need manual entry or import?
What happens to a policy that should have paid and produced no line at all? Is there a report for expected-but-missing commission?
How are renewal rates, splits and producer shares stored, and who maintains them?
How does it handle a policy number that differs from the one in the system?
Does it match a chargeback to the original commission, and how long afterwards?
Does it flag a commission paid twice?
Can I see, per statement, what was matched, what was not and why?

The answers will tell you where your own process needs to pick up. Many agencies find that their system records commission well and leaves the audit to a person with time to do it.

Where Lapidar fits

Lapidar is in development and has not launched. It is being built to sit beside your existing system, not replace it: you give it carrier statements and your book, and it checks each line and reports what is missing, underpaid, paid twice or not in your book. We can’t yet show results, and we won’t claim any until agencies have used it. It is also not a small job. Statement formats, policy-number quirks and chargeback timing are what make the work slow, and they are the part we are building for. Join the early-access list below and we’ll write once, when the first agencies can upload statements.