Carrier statements ·
Insurance Carrier Commission Statement Codes: A Practical Interpretation Guide
By SplitVerde editorial team · Insurance agency operations
Carrier commission statements often contain abbreviated transaction codes. Misreading one code can turn a normal adjustment into a false missing-payment claim.
Start with the carrier's own code definitions
There is no universal set of transaction codes shared by every insurance carrier. A letter that represents renewal on one statement might mean something else on another. Download the carrier's legend, statement guide, or compensation documentation when available. Store the source and its effective date with your import mapping. If a code is not documented, ask the carrier rather than guessing. This matters especially when the statement contains negative amounts or multiple transactions for the same policy.
Common transaction categories to recognize
Most reconciliation workflows need to distinguish new business, renewal, endorsement, cancellation, reversal, correction, installment, and supplemental compensation. These are categories, not guaranteed carrier code values. A new-business transaction may represent the initial eligible commission, while an endorsement reflects a change to an existing policy. A cancellation may trigger a negative adjustment. A correction can reverse and replace an earlier entry. Mapping these categories helps reviewers compare like with like, but the carrier's actual definition controls.
Preserve the raw code and the mapped label
Keep both the exact source code and your agency's readable category. If a carrier uses an unfamiliar code, store it as unknown until verified. Do not silently force it into the nearest category. Record who approved the mapping and when. A later carrier format change should not rewrite the interpretation of historical statements. Keeping raw values also makes it easier to send a carrier inquiry with the exact code shown on the source row.
Use amount signs as clues, not conclusions
A negative row may indicate cancellation, premium reduction, reversal, or another adjustment. The sign alone does not establish the cause. Similarly, a positive row could be a new commission or a correction of an earlier negative transaction. Review the code, policy history, effective date, and nearby statement rows. If the carrier provides separate debit and credit columns, normalize the sign carefully and verify the signed statement total. A mistaken sign can make a valid chargeback look like extra commission.
Example: a correction sequence
Suppose a carrier originally reports +$180 for a policy. In a later statement, it reports −$180 with a reversal code and +$195 with a correction code. The net across the sequence is $195, but the agency should retain all three events. If the two later rows are interpreted as an unexplained chargeback and a duplicate payment, staff may chase two false exceptions. The exact codes are carrier-specific; the example demonstrates why linking related transactions matters.
Handle new or ambiguous codes
When a new code appears, compare it with carrier release notes or ask the commission support team for a definition. Record the response, affected statement periods, and whether prior mappings need review. Check a few source rows before applying a new rule to an entire file. If the code indicates a special transaction that does not belong in ordinary policy commission, preserve it in a separate category. Avoid dropping unfamiliar rows just because the matching engine cannot immediately classify them.
Build a small mapping reference
Maintain a carrier-specific table containing raw code, readable label, sign convention, calculation notes, effective date, and documentation source. Review it when carrier exports change. At month-end, report unknown codes and unmapped transaction totals so they do not disappear from reconciliation. This modest control reduces false discrepancies, makes carrier questions more precise, and lets another employee interpret the statement without relying on one person's memory.
A sample carrier mapping workflow
Begin by collecting one statement that contains several transaction types. Identify the raw code column and compare each code against the carrier's published legend. Create a small table with source code, description, signed amount convention, and a plain-language category. Do not assume a code means the same thing on every carrier. Preserve the source statement and any email from the carrier that clarifies an ambiguous code.
Next, test the mapping against policy histories. If a row labeled renewal appears on a policy with an endorsement during the same period, check whether the carrier's definition differs from the agency's expectations. If the mapped code produces unexpected negative values, inspect the carrier's debit-credit convention. Confirm that the total of the normalized signed transactions equals the source statement total before using the data for reconciliation.
Finally, give unknown codes a visible review status. Count the rows and dollars affected rather than dropping them from the report. When the carrier supplies a new definition, update the mapping with an effective date and retain the earlier version. This helps the agency explain why historical statements were categorized differently and prevents a later mapping change from silently altering past reports.
Practical checklist
- Keep original carrier statements and verify imported transaction totals.
- Document the calculation and timing basis behind expected amounts.
- Separate policy-level discrepancies from bank deposit differences.
- Assign unresolved issues to an owner with a follow-up date.
- Retain the original transaction when a later correction appears.
Frequently asked questions
Does a matching bank deposit prove every commission was correct?
No. Matching the remittance to the deposit is a cash control. Policy-level reconciliation is a separate review.
Should I overwrite a transaction after a carrier correction?
No. Preserve the original event and link the later correction to maintain a usable audit trail.
Can a negative carrier adjustment automatically reduce producer pay?
Not necessarily. Check the producer agreement and applicable law before changing compensation.
Related guides
Read the agency reconciliation checklist, commission KPIs guide, and producer payout overview.
The 7-day trial requires a payment card and renews unless canceled. No direct carrier integrations or scanned-image PDF OCR.