Reconciliation ·
Insurance Commission Policy Number Matching: Fixing Unmatched Carrier Payments
By SplitVerde editorial team · Insurance agency operations
Resolve unmatched carrier commissions caused by policy formatting, rewrites, and duplicate identifiers. This guide focuses on the evidence and practical steps needed to make the result trustworthy.
Identify why exact matching fails
Leading zeros disappear when identifiers are interpreted as numbers. Renewal suffixes, spaces, and punctuation may differ between carrier statements and agency records. Start by comparing the original strings. Do not immediately remove every special character: a suffix may distinguish separate policy terms, and aggressive cleanup can turn different policies into the same matching key. Preserve the raw value alongside any cleaned version.
Before treating a number as final, ask which source supports it and what period the source covers. A policy effective date, a carrier statement date, and a bank deposit date can all be different. Keep those distinctions explicit. If a carrier changes a schedule or revises a statement, retain the prior evidence and record the reason for the new interpretation. A reviewer should be able to reproduce the conclusion without relying on someone's memory or a screenshot of a summary total. This discipline matters most when an apparent discrepancy crosses month-end or affects producer compensation.
Write carrier-specific normalization rules
Normalize only what you can justify for a given carrier. Uppercasing letters or removing known separators may be appropriate, but test each rule on known matches and known nonmatches. Keep a record of the rule version used. If two different original identifiers collapse into one normalized value, do not auto-match either one. A collision is an exception requiring more evidence, not a success.
Be careful with the difference between missing information and a confirmed error. A blank field, absent statement, or uncertain matching key does not prove the carrier underpaid. It means the record needs investigation. Mark that status clearly, assign ownership, and keep a next review date. This protects the agency from wasting time on false alarms while ensuring real shortages remain visible. When asking a carrier for help, provide the policy reference, relevant period, expected amount, and the evidence behind the question.
Use other fields as supporting evidence
Compare carrier, account reference, insured, transaction type, dates, and signed amount to identify possible matches. A shared dollar amount is weak evidence because many policies pay the same commission. Similar names can refer to related businesses or different policies. Show reviewers the conflicting fields and leave uncertain candidates unresolved. Human review is preferable to a false match that hides a genuine unpaid commission.
An accurate reconciliation can still be incomplete if the input is wrong. Validate imported transaction counts and signed totals against the original statement. Inspect a sample of negative adjustments and identifiers with leading zeros. A matching grand total can hide two offsetting policy errors, and a successful upload does not guarantee correct extraction. Stop when a source validation fails; otherwise the matching engine may produce dozens of convincing but meaningless exceptions. Preserve the failed import and the reason for correction.
| Policy | Expected | Reported | Difference |
|---|---|---|---|
| A | $200 | $250 | +$50 |
| B | $200 | $150 | −$50 |
| Total | $400 | $400 | Two exceptions |
Illustrative amounts, not actual carrier transactions.
Treat rewrites as linked events
A policy rewritten with a new number may legitimately generate a reversal and new commission. Maintain an evidence-backed cross-reference between the old and new policy references, including effective dates and transaction types. Do not automatically combine all similarly numbered policies. A renewal suffix can indicate a new term rather than a duplicate. Keep the separate carrier events visible so the agency can explain both the commission and any producer adjustment.
Build the workflow around distinct transaction states. Expected is not the same as reported; reported is not the same as deposited; a calculated producer share is not the same as an approved or transferred payout. These categories may be related, but merging them hides the cause of a delay. A useful dashboard shows where the transaction sits and which evidence is missing. That makes it possible to answer a producer's question without claiming money was received before it reached the agency.
Example: a collision after cleanup
Suppose the book lists AB-00123 and AB-123, and the carrier reports AB123. Removing punctuation and leading zeros maps both book entries to the same value. The match is ambiguous even if the amount appears reasonable. Review carrier transaction IDs, insured references, and policy dates. If those do not establish a reliable link, ask the carrier or servicing team. A clearly labeled unmatched record is safer than assigning money to the wrong policy.
Negative amounts deserve the same attention as positive commissions. A chargeback may reflect cancellation, premium change, rewrite, or correction. Keep the original payment and the negative event separately with their own statement dates. Do not overwrite the original with the net result. Whether the negative event affects a producer payout depends on the governing agreement and applicable law. Record the investigation and approval rather than letting a spreadsheet formula silently decide compensation.
Measure match quality, not just volume
Track unmatched count, unmatched dollar value, false-match corrections, and the recurring causes of mismatches. Investigate sudden changes after carrier export updates. A higher automated match rate is not an improvement if it creates silent errors. Validate imported row counts and signed totals independently. Keep resolved examples in a short reference guide so future reviewers can apply the same evidence-based rules.
At the end of the period, retain the original statement, matching results, unresolved exceptions, carrier correspondence, and review decisions. Keep open items assigned to a person and a follow-up date. A promised correction is not verified until a later statement contains the relevant transaction. Bank-deposit matching should be performed separately from policy-level commission review. The objective is not to make every cell green; it is to create a reliable explanation for the money the agency expected, the carrier reported, and the agency actually received.
Frequently asked questions
Does a matching statement total mean every policy is correct?
No. Offsetting policy-level errors can produce the same grand total. Check each relevant transaction.
Should unresolved matches be automatically approved?
No. Keep uncertain matches visible until sufficient supporting evidence establishes the correct transaction.
Does a negative carrier commission automatically reduce producer pay?
Not necessarily. Review the applicable producer agreement and law before making compensation adjustments.
Related guides
Read our reconciliation overview, file format comparison, and monthly checklist.