Expected versus received: a practical commission reconciliation workflow
A commission total is useful only when you can explain where it came from. Reconciliation connects what the agency expected with what a statement reports, and makes the remaining exceptions visible.
Keep expected and received amounts separate
An expected commission is a forecast tied to the relevant policy, carrier, agent and period. A received statement entry is an observed payment record. Keep the two distinct so the dashboard does not turn forecasts into collected revenue.
Record the source and period for each amount. Preserve exact cents through imports, calculations and exports. Define how negative entries, reversals and chargebacks are represented before adding them to totals.
Retain the original statement and map it explicitly
Keep the original statement in an authorized location and record the carrier, statement period and import date. Map the source columns to known fields and validate amounts before importing.
Identify duplicate statement entries or repeated files. Re-importing a statement should not double the received amount. Use a stable source identity or a reviewed duplicate rule rather than assuming each uploaded row is new.
Match entries with enough context
Use the carrier, policy reference, agent, period and transaction context available in the statement. A shared client name alone is not a reliable match. Ambiguous entries should stay in a review queue.
Show why an entry matched and let an authorized person review corrections. Keep the audit trail when a match changes. A dashboard can summarize the result, but users still need a route back to the source records.
Work the exceptions
Separate missing expected payments, unexpected received entries, amount differences, duplicate entries and chargebacks. Give each exception an owner and a next action.
Reconcile splits and reversals before treating an agent balance as payable. A recorded payout status is not evidence that funds were sent to a bank. Bank transmission and settlement require their own verified provider records.
Close the period with an explainable export
Compare source totals, imported totals, matched amounts and unresolved exceptions. Export the reconciled result and preserve the period’s review evidence.
Test a duplicate statement, a missing entry, a chargeback, a fractional split and a failed import. Measure reconciliation time and unresolved amounts before claiming an improvement over the agency’s current process.
Acceptance checklist
- Expected and received amounts are distinct
- Source statement retained securely
- Repeated statements do not double count
- Ambiguous matches require review
- Splits and chargebacks preserve exact cents
- Recorded payouts are distinct from bank settlement
Lunaro is being built around insurance records and commission visibility. Statement compatibility, matching, splits and reconciliation must be accepted in the actual workflow; a ledger preview does not prove settlement or financial completeness.