PRACTICAL GUIDE
Direct bill carrier reconciliation: a practical agency guide
Direct bill carrier reconciliation connects policy activity, the carrier's commission statement, and the money the agency receives. A bank deposit records the amount received; reconciliation explains which transactions were paid and which differences need attention. The useful result is a documented answer for every statement line: matched, explained, corrected, or assigned for follow-up. Use this guide to organize the source records, work through exceptions, and carry unresolved items into the next statement period with a clear owner and next action.
What direct bill reconciliation covers
With direct billing, the insured pays premium to the carrier. With agency billing, the insured is billed by and pays the agency. [1] Keep the two workflows identifiable in a mixed book so that a customer premium balance is recorded separately from commission due from a carrier. Label the billing method in the working file before comparing amounts.
For direct bill, ask three separate questions: Does the carrier statement agree with the agency's transaction records? Does the statement explain the commission payment received? What remains unresolved after that comparison? Treat those questions as related checks. Use transaction-level details to confirm the policy, transaction date, commission amount, and producer allocation behind the payment total.
Assemble the reconciliation packet before matching
Create one packet for the carrier, agency code, and statement period being reviewed. Preserve the original statement and identify any later replacement. Record its receipt date, statement identifier, line count, commission total, and the payment reference you expect to connect. If the carrier provides both a download and a PDF, retain their relationship so a reviewer can trace an imported row to its source.
- Bring forward unresolved items from the prior period with their owners and next follow-up dates.
- Obtain the relevant agency transaction export, including policy number, writing company, effective date, transaction type, premium basis, expected commission, and producer assignment.
- Keep commission agreements and documented changes available to support disputed rates or calculation bases.
- Identify the accounting method and posting path in use before changing transactions or marking them complete.
The posting path matters. Vertafore documents several AMS360 direct-bill methods with different income timing and setup choices. Its guidance also distinguishes agency defaults from carrier-specific settings. [2] Use your agency's approved configuration and accounting policy; do not copy another team's screen sequence without confirming that the same assumptions apply.
Match the transaction, then explain the difference
Start with stable identifiers and then test the transaction details. A policy number by itself may be insufficient when the same policy has a renewal, endorsement, cancellation, or multiple payments. Preserve the original identifier alongside any normalized value. Removing spaces may help comparison; removing a meaningful suffix can join unrelated records.
AMS360's documented automatic matching checks customer, policy, writing company, effective date, line or charge, transaction type, premium or other amounts, and agency commission details. Its workflow also supports one-to-many and many-to-one matching. [3] That is a useful reminder to investigate grouped transactions rather than forcing every carrier row into a one-row assumption.
Give each unresolved item a reason, evidence reference, owner, and next action. Use specific labels such as missing policy transaction, disputed commission basis, timing under review, or unidentified payment. Avoid a single miscellaneous category that hides the work. An operator should be able to resume a colleague's investigation without repeating the original searches.
Common direct bill problems and how to solve them
- A policy does not match. Compare writing company, agency code, policy term, and the exact carrier identifier. Check whether a renewal changed the number before creating a new record. Record an approved mapping when an identifier difference is legitimate.
- The commission amount differs. Recalculate from the applicable commission basis and agreement. Separate a rate issue from a premium issue. Attach the supporting schedule or carrier explanation instead of accepting the statement merely because its arithmetic is consistent.
- The expected commission is missing. Check the carrier's payment rules, statement cutoff, transaction status, and prior statements. Set a follow-up date linked to evidence. An absent row can be a timing issue, but timing should be established rather than assumed.
- A negative amount appears. Locate the related transaction and inspect the cancellation, adjustment, or reversal documentation. Preserve the connection to the original item. Do not silently offset it against an unrelated positive commission to make the total agree.
- A line appears twice. Compare source identifiers and prior imports before deleting anything. Determine whether there are two legitimate transactions, a duplicate file, or a corrected statement. Record which version remains authoritative.
- The payment and statement totals differ. Check whether a payment covers several statements, whether an adjustment is separately documented, and whether the correct deposit was selected. Keep an unexplained difference visible until evidence supports its treatment.
Keep the carrier's commission rules beside the working file. Check how final audits, earned and paid premium, and policy changes affect the amount and timing of commission. Record the applicable rule against the item being reviewed, along with the source document and the statement period in which the adjustment is expected. [4]
Work through a statement review
Read the expected and statement columns together before assigning the next action. Expected amounts come from the agency's records at the start of the review. The difference column directs attention to the two items that need investigation, while the review action records what the operator should check next.
| Reference | Expected | Statement | Difference | Review action |
|---|---|---|---|---|
| DB-101 | $180 | $180 | $0 | Confirm identifiers and match |
| DB-102 | $240 | $225 | ($15) | Verify commission basis |
| DB-103 | $90 | $0 | ($90) | Check payment timing and missing activity |
| DB-104 | ($60) | ($60) | $0 | Confirm linked reversal |
| Total | $450 | $345 | ($105) | Resolve the two open differences |
Suppose the bank shows a $345 receipt linked to this statement. That supports the cash comparison, but DB-102 and DB-103 still need decisions. The operator should document the $15 rate or basis investigation separately from the $90 missing item. If later evidence explains one as a timing difference, retain its expected follow-up period. A reviewer can then understand both the current receipt and the outstanding work.
Review corrections before posting
Before posting, compare the working totals with the original statement and inspect every adjustment. Vertafore's reconciliation documentation treats agreement between company and agency totals as the goal before posting. [5] Your review should also establish what remains open, where it will appear next period, and who has authority to approve the proposed treatment.
Be careful with completion flags. In a documented AMS360 workflow, marking certain Customer Center transactions complete while a commission balance remains can create an adjusting journal entry. Vertafore distinguishes small rounding adjustments from discrepancies requiring invoice correction and notes that those journal adjustments do not update employee commission. [6] Confirm the consequences in your own system before closing an exception.
Retain the original statement, the final worksheet or system report, correction references, review sign-off, and the cash reference together. If an item remains unresolved, document the accounting treatment under your agency's policy and keep the operational follow-up active. Closing a period and resolving a carrier question are different decisions.
Carry open items into the next review
Finish each review by updating the open-items list. For each difference, retain the carrier and policy references, the amount, the reason being investigated, the last contact, and the next follow-up date. Separate items waiting on the carrier from those waiting on an internal correction. This gives the next operator a clear place to start.
When the next statement arrives, inspect the carry-forward list before starting a new investigation. A late adjustment may resolve a prior question, or a repeated amount may require another look at the original transaction. Link the resolution to the earlier item and record the evidence that closed it. Keep the original amount and the final treatment visible in the history.
Use a brief weekly update to keep decisions moving: what remains open, who owns the next action, who the team is waiting on, and when follow-up is due. Group related questions into one carrier inquiry with clear references. Record the reply once and apply it to the affected items so the same explanation stays attached to each decision.
EvenPenny reconciles agency-bill statements today. If direct bill is your main workflow, tell us; it is on the roadmap and the matching engine is the same.
Common questions
- Is matching the bank deposit enough to reconcile direct bill?
- A complete review connects the deposit to the statement total and the statement lines to the underlying transactions. Keep both comparisons separately reviewable. For each difference, record the reason, the evidence needed, the owner, and the next follow-up date.
- Should every commission difference be written off?
- No. First identify the cause and apply the agency's approved accounting policy. A timing difference, missing transaction, incorrect rate, and rounding difference call for different decisions. Confirm how your system treats completion and correction actions before posting an adjustment.
- What should a carrier follow-up include?
- Include the statement period, agency code, policy or bond reference, transaction date, the expected amount, the statement amount, and the question to resolve. Attach the relevant supporting record and keep the inquiry with the open item. When the reply arrives, record the decision and the next action.
Keep reading
Sources
- Agency payment guidance: billing model distinction
- Vertafore: Choose a Direct Bill Invoice Method — An Overview
- Vertafore: Processing Download Direct Bill Commission Statement Transactions
- Carrier agent FAQ: commission payment and adjustment rules
- Vertafore: Direct Bill Commission Statement (Reconciling)
- Vertafore: Adjusting Customer Center Billed Transactions in a Direct Bill Statement