Carrier statements ·
Insurance Commission Net 30 vs. Net 60: When Will Agents Get Paid?
By SplitVerde editorial team · Insurance agency operations
The policy is sold. The client is covered. Then comes the question every producer knows: when am I actually getting paid?
The takeaway
Compare transactions rather than totals, preserve the original carrier evidence, and keep projected, reported, and paid amounts distinct.
The trigger matters more than the label
Net-30 and net-60 generally refer to intervals after a defined trigger. That trigger may not be the policy effective date. Carrier contracts can make eligibility depend on premium collection, transaction processing, or other conditions. Read the actual schedule instead of assuming a universal rule.
Before making a conclusion, preserve the carrier's original statement and the period it covers. Validate the number of imported transaction rows and the signed commission total against the source. If the file is a PDF, inspect a sample of extracted policy references and amounts; if it is a spreadsheet, check leading zeros and date formats. A clean-looking table can contain bad data. Keep the source file alongside the working results so the next reviewer can trace any discrepancy without reconstructing the download. When the carrier revises a statement, store the revision separately rather than overwriting the earlier evidence.
Earned, reported, and deposited are different
Keep the policy date, eligibility trigger, expected statement cycle, actual statement date, and bank deposit date in separate fields. A sold policy is not necessarily a payable commission today. A carrier statement entry is not automatically cash received. These distinctions are essential for accurate cash planning.
An expected commission is only as reliable as the assumptions behind it. Record the applicable carrier schedule, transaction type, commission basis, and eligibility conditions. A policy effective date does not automatically establish when commission becomes payable. Premium processing and statement cutoffs may matter. Mark uncertainty openly rather than assigning a confident due date that the contract does not support. Keep projected commissions, statement-reported commissions, and actual bank deposits separate. Those figures answer different questions, and collapsing them into one column creates avoidable confusion when the agency is planning cash flow.
Why sixty days can feel longer
Imagine a policy effective August 1 whose qualifying premium is processed August 20. If a hypothetical sixty-day interval runs from that processing event, the payment expectation is later than sixty days after inception. Statement cutoffs can add another reporting delay. This is an illustration, not a specific carrier promise.
Transaction-level matching matters because totals can hide offsetting errors. Suppose Policy A is expected to pay $200 and Policy B is expected to pay $200. The carrier reports $250 on A and $150 on B. Both totals are $400, but each policy has a $50 discrepancy. Review carrier, policy reference, transaction type, statement period, and signed amount. Do not force an ambiguous match merely because two names or dollar values look similar. If an adjustment arrives later, retain the original transaction and add the new event. This preserves the timeline that makes future questions answerable.
| Policy | Expected | Carrier | Variance |
|---|---|---|---|
| A | $200 | $250 | +$50 |
| B | $200 | $150 | −$50 |
| Total | $400 | $400 | Two exceptions |
Fictional values; investigate policy-level differences rather than netting them away.
Maintain carrier-specific schedules
Store payment triggers, frequency, cutoff rules, applicable products, agreement versions, and verification dates by carrier. Separate uncertain assumptions from confirmed rules. When the carrier changes its process, preserve the old schedule for historical transactions so older expected dates remain explainable.
Every unresolved difference needs an owner and a next step. An exception log should include the source row, expected and reported amounts, signed variance, likely reason, status, and follow-up date. Separate confirmed shortages from transactions not yet due, unexpected positive commissions, duplicate candidates, and chargebacks. When contacting a carrier, send a focused inquiry with the policy reference, statement period, and basis for the expected amount. Save the reply. A promise that a correction will appear next month is not a verified resolution. Keep the issue open until a later statement supports closure.
Investigate a genuine late commission
Confirm eligibility, policy status, premium conditions, and the relevant statement period. Then contact the carrier with policy reference, expected amount, schedule basis, and period checked. Record the response and follow-up date. Do not close the exception until the correction is visible and verified.
Producer compensation should be reviewed as a separate calculation. The agency's carrier commission is not automatically the amount payable to a producer. New-business and renewal rates may differ, and shared accounts may have special arrangements. Record the governing agreement version, commission basis, split rate, calculated share, and approval. A carrier chargeback does not automatically authorize a producer deduction; check the agreement and applicable law. Also distinguish calculated, approved, and actually paid amounts. A payout report is not proof that a bank transfer occurred, even when the arithmetic is correct.
Explain status to producers clearly
Show whether the carrier commission is not yet due, missing from an expected statement, received but awaiting split review, or approved for payout. Producer payment timing is governed by the producer agreement, not automatically by the carrier's payment interval. Transparent statuses reduce avoidable disputes.
At month-end, keep a compact record of source statements, import validation, matches, open exceptions, carrier correspondence, and any producer approvals. Compare carrier remittances with bank deposits separately from policy-level matching. Assign unresolved cases to the next review period without rewriting earlier history. Ask whether someone unfamiliar with a transaction could find its source, calculation, and outcome in a few minutes. If not, improve the references. A reliable process is not one that makes every status green; it is one that exposes uncertainty and shows who is responsible for resolving it.
Frequently asked questions
Does a matching monthly total prove every commission is correct?
No. Offsetting policy-level differences can hide behind a matching grand total. Review individual transactions.
Is an expected commission the same as money in the bank?
No. Expected, carrier-reported, and deposited amounts are different checkpoints.
Can a chargeback automatically reduce a producer payout?
Not necessarily. Check the producer agreement and applicable law before changing compensation.
Related guides
Continue with our commission reconciliation guide, monthly checklist, and producer payout walkthrough.