Insurance agency bookkeeping depends on more than recording deposits. Commission reconciliation connects carrier statements, policy records, expected commission, payments, chargebacks, adjustments and bank activity. A reliable process clearly shows what matched what did not why the difference exists and who is responsible, for fixing it.
When this work is outsourced the provider should increase visibility than become a black box. These questions help agency owners assess scope, controls, system access, review procedures, reporting and transition planning before committing.
The purpose is not simply to make statement totals agree. This record gives management a view of what the agency expected what was received, which items need attention and how open differences are progressing. That record helps with monthly reports, quicker follow-ups and better decisions, about carrier relationships and cash flow.
Why Commission Reconciliation Needs a Defined Control
Commission activity passes through several records before it becomes usable financial information. Policy transactions establish what should happen, carrier statements report what the carrier processed, deposits show what reached the bank, and the accounting system records the financial result. A difference at any handoff can create an unexplained balance, an incorrect commission entry, or an exception that remains hidden until a later close.
A controlled reconciliation links records, without assuming any one source is fully complete. It separates timing differences, from errors keeps adjustments visible and gives management a repeatable way to review unresolved items. This matters because a statement can agree with a deposit but still have a rate, a missing policy, a duplicated transaction or a chargeback not assigned to the right account.
Twelve Questions for Commission Reconciliation Providers
1. What is included in the reconciliation scope?
A strong provider defines which statements, transactions, deposits, exceptions, and reports are included. It also identifies exclusions such as historical cleanup, producer settlements, carrier disputes, accounting entries, or direct carrier follow up. Clear boundaries prevent important tasks from disappearing when an exception occurs.
A complete scope should also state the working frequency, expected turnaround, cut off dates, required inputs, materiality rules, and approval points. These details make service expectations measurable and help both parties distinguish a routine delay from a genuine control failure.
2. How do you determine expected commission?
The provider should identify the agreed source for expected commission, such as policy data, transaction records, carrier compensation schedules, or another approved record. Bank deposits show what arrived. They do not prove the agency received the correct amount.
If two sources disagree the workflow must specify which record is more important and who has the authority to approve that choice. Assumptions should be documented rather than remembered. This creates consistency across reconciliation cycles and gives reviewers evidence for understanding later corrections.
3. How are different carrier statements handled?
Ask how statement formats are received, mapped, normalized, and retained. A controlled process identifies unreadable fields, format changes, and unmapped transactions. The provider should explain which steps are automated, which require review, and who maintains each mapping.
4. How are policies, transactions, and deposits matched?
Useful matching may involve the carrier, policy number, transaction type, effective date, commission rate, customer, amount, and related deposit. A reviewer should understand why an item matched and see every item that remains unresolved.
A top level statement total can agree even when individual policies are incorrect. Transaction level matching helps reveal underpayments, duplicate activity, timing differences, and unrelated adjustments that offset one another. The goal is an explainable match, not simply a balanced total.
5. What happens when amounts do not match?
The provider should create a visible exception instead of forcing the numbers to agree. Each exception should show the expected amount, received amount, difference, likely cause, current status, supporting evidence, and next owner.
Exception categories should be consistent enough to support aging and trend analysis. Management can then see whether recurring differences come from timing, missing policies, commission rates, duplicate items, chargebacks, or incomplete source records. Materiality rules should never make unresolved differences invisible.
6. How are chargebacks and reversals handled?
Negative adjustments should remain connected to the underlying policy or transaction whenever possible. The record should explain the amount, available reason, effect on the current statement, and whether the agency or provider must take further action.
7. Who owns unresolved exceptions?
Identification, research, carrier communication, approval, and closure are separate responsibilities. A provider does not need to own every step, but ownership must be explicit. There should also be an escalation path for overdue items.
Ownership should include target response times and evidence requirements. A clear service level identifies when the provider is waiting for the agency, when carrier contact is required, and when management must approve an adjustment, closure, or decision to leave the item open.
8. How will you work with our systems?
The provider should explain how information moves between the agency management system, accounting platform, carrier files, and bank records. Ask about access levels, transferred fields, change controls, and the response when a source system changes.
9. What review occurs before completion?
A defined reviewer should examine statement completeness, unusual items, material variances, proposed adjustments, reconciliation status, and unresolved exceptions. An independent review is more reliable, than the person who prepared the work checking it themselves.
The review must show who did it when what was asked, what was fixed and what happened in the end. If the same person prepares and approves the work buyers should know which control alternative makes up for the missing separation.
10. What will management receive?
Monthly deliverables should show completed statements, expected and received commission, unmatched items, aged exceptions, chargebacks, agency actions, and anything not finalized. A simple report exposing open work is more useful than a dashboard that hides it.
Reporting should separate completed work from open work and identify items requiring a decision. Agree on thresholds, aging categories, delivery dates, and report owners before implementation. Consistent reporting helps management compare periods and recognize recurring process weaknesses.
11. How are access and continuity controlled?
How is access granted and removed how are credentials protected what activity can be. How are incidents escalated? Procedures and backup coverage should prevent dependence on one person.
12. What is included in the fee and transition?
Terms should distinguish recurring reconciliation from implementation, backlog cleanup, unusual formats, carrier follow up, reporting, and volume changes. Confirm which records, logs, mappings, and working files will be returned if the relationship ends.
What Useful Exception Reporting Should Show
An exception report should support action, not merely prove that a difference exists. Each open item should identify the carrier, policy or transaction, statement period, expected amount, received amount, variance, available explanation, supporting record, current owner, and next review date. Consistent fields make it possible to sort exceptions by age, value, carrier, cause, or responsible person.
Management also needs context around the total. The report should distinguish new items from older unresolved differences and show which exceptions were closed during the period. Repeated patterns can reveal a mapping problem, missing source data, an outdated compensation schedule, or a carrier specific process issue. The objective is not to eliminate every exception immediately. It is to keep each difference understandable, assigned, and visible until an authorized decision closes it.
What Your Agency Must Provide
Outsourcing cannot repair missing records or replace agency decisions. Success requires a named owner, timely access to statements and policy data, a defined expected commission source, deposit information, existing exception history, and prompt answers when business judgment is required. New carriers, compensation arrangements, and system changes should enter through a documented process.
Common Implementation Risks to Address Early
Transitions often fail because the provider receives incomplete access, inconsistent statement files, undocumented commission arrangements, or unclear instructions about who can approve an adjustment. Historical exceptions may also be mixed with current activity, making the first reporting cycle appear less reliable than it is. These issues must be found during planning. Added to a checklist with a person, in charge and a deadline.
Another risk is relying on a spreadsheet that one person can manage, making the process fragile and hard to maintain. Temporary working files may be needed,. The final workflow must keep source documents safe use consistent fields record mapping decisions and give an audit trail that another qualified person can follow. Agree on where files will be stored how they will be named, when they need to be reviewed what happens if issues arise and how mistakes will be fixed before any repeated work starts.
Common failure patterns include incomplete statements, delayed access, inconsistent expected commission sources, undocumented decisions, and exceptions stored only in email. Agencies should address these weaknesses during onboarding. Outsourcing a disorganized process without assigning internal ownership usually moves confusion rather than resolving it.
Use a Scoped Pilot Before Expanding
A pilot should use representative statements or one controlled reconciliation cycle. Agree on acceptance criteria before work begins. Review whether source data was identified correctly, mappings were understandable, expected and received amounts were compared, exceptions were visible, review occurred, and another qualified person could understand the handoff.
The pilot is not a test of a universal matching rate or guaranteed recovery. It tests how the provider handles missing information, uncertainty, communication, review, and documentation when the work becomes real.
Choose a sample that includes ordinary activity and realistic exceptions rather than only the cleanest statement. At the end, review open items, recurring data problems, manual steps, communication quality, and the records left behind. Expansion should occur only when the agency can understand and supervise the process.
A strong reconciliation process makes unresolved differences easier to see. The provider should show what remains open, why it remains open, and who owns the next action. That visibility allows an agency to outsource repetitive work without outsourcing management control.
Questions Buyers Ask Us
They collect statements, compare activity with agreed records, identify differences, document adjustments and chargebacks, and prepare reconciliation records for review. Exact responsibilities vary, so every included activity and exclusion should be written into the scope.
Most engagements need carrier statements, policy or transaction data, an expected commission source, deposit details, accounting records, and existing exception history. The provider should confirm required formats, access levels, and delivery deadlines during onboarding.
Expected commission is compared with the statement and amount received. Differences enter an exception process, although timing, policy changes, adjustments, or incomplete data may explain them.
They should remain traceable to the related policy or transaction, with the amount, reason, statement effect, and required follow up documented.
Potentially. The workflow may use native features, exports, controlled transfer, an API, or another documented method. Buyers should verify actual capabilities.
Evaluate scope clarity, source identification, matching logic, exception ownership, review, security, reporting, continuity, exclusions, and whether the handoff is understandable. Use written acceptance criteria and review both completed work and unresolved exceptions.
Sources and further reading
Disclosure: CrownGlobe provides outsourced accounting services. Apply this framework to every provider, including CrownGlobe. This article is general information and is not legal, tax, regulatory, cybersecurity, insurance compliance, or contractual advice.
Ready to Evaluate Commission Reconciliation Support?
CrownGlobe can review your current statement flow, define work suitable for outsourcing, and discuss whether a controlled pilot makes sense.