Payment gaps
The chargeback proof-out answers “was I paid before they took it back?” Payment gaps answer the opposite question: which months did the carrier simply not pay at all? For every policy in your loaded history, the report finds months with no record whatsoever — no payment, no chargeback — sitting between two months the carrier did pay. It’s an enterprise feature, turned on per account.
The three find-money questions
CommissionSight answers “am I getting all my money?” with three reports, each built on different evidence and each catching a failure the others can’t. This page is the second.
| Report | Question it answers | Evidence it uses | What it catches |
|---|---|---|---|
| Chargeback proof-out | Was the money they took back legitimate? | Statements vs. statements | Clawbacks with no prior payment; multi-month over-reversals |
| Payment gaps (this page) | Which months did they skip mid-stream? | A member’s own payment timeline | Months with no record between two paid months |
| Unpaid members | Who did they never pay at all? | Your roster vs. statements | Members missing from the statements entirely |
Payment gaps need no input at all — a member’s own timeline is the evidence (paid before, paid after, silent in between). That self-evidencing design has two deliberate blind spots: a member who never appears on any statement produces no timeline to find a hole in, and a member whose payments stop and never resume reads as churn, not a gap. Unpaid members covers exactly those two cases — it diffs your active-member roster against the statements, which is why it’s the one report that asks you to upload something.
What it finds
A gap is a month (or a run of consecutive months) where a policy that was being paid before and after went silent. That’s the strongest unpaid-commission shape there is: the member was on the books on both sides of the gap, and nothing in the statements explains the missing months.
Each gap run is judged by the payment that ends it, because carriers that fix a missed month usually pay it as a lump when the policy resumes:
- Unpaid — the policy resumed at (or below) its old monthly rate. Nothing suggests the missing months were ever paid. These are the lines to take to the carrier.
- Partial catch-up — the resuming payment was elevated above the old rate, but not by enough to cover every missing month. The shortfall is reported after crediting the excess.
- Caught up — the resuming payment covers the missing months in one lump. Counted and shown, but estimated at $0 — the carrier already made it right.
How the estimate stays honest
The dollar estimate is deliberately conservative:
- Missing months are priced at the lower of the rate before the gap and the rate after it — so a household that shrank during the gap (say, a $68 two-person policy resuming at $34) never inflates the claim.
- Any catch-up excess in the resuming payment is credited against the estimate.
- The upper bound (every missing month at the prior rate, no credits) is reported alongside, so you always see both ends of the range.
- A month containing only a chargeback counts as present, not missing — that story belongs to the chargeback proof-out.
In the app
When enabled, a Payment gaps tab appears in the Chargebacks section, beside Proof-out. Summary tiles give the headline — missing months, the conservative estimate, how many runs were never caught up vs. trued up by the carrier, and the upper bound — with the line-by-line table below: the missing months, the member and policy, the monthly rate, when the policy was last paid and when it resumed, and the per-run estimate. Filter by carrier, workspace, or a from/to month range.
Export CSV downloads the whole report as one file — every gap with its months, rates, catch-up status, and estimate — ready to check against the carrier’s own enrollment records or attach to a dispute.
The page opens on gaps that began in the last 60 days. One click scans your full history — that walks every policy’s entire payment timeline, so on a large book expect it to take several seconds. The CSV export always covers whatever range is selected.
You can also just ask: with payment gaps enabled, Ask AI answers questions like “which months did the carrier never pay me?” or “show the gaps that were never caught up” conversationally — computed by this same report, with the matching rows and a link back to it.
Reading the results honestly
- A gap is evidence of a missing payment in your loaded statements — before disputing, rule out the two innocent explanations: the member lapsed and re-enrolled (the carrier owes nothing for lapsed months), or your copy of that month’s statement was incomplete (re-upload it and the report recomputes automatically).
- Gaps that cluster on the same calendar months across many members usually mean a statement problem — one month’s file was partial — rather than many individual coincidences. Check those months’ files first.
- Short gaps (one or two months) surrounded by payments at the same rate are the hardest to explain away — start there.
- Pair it with the dispute & recovery workflow once a gap survives those checks.
Payment gaps are an app-only capability — not part of the public API or SDKs. For single-period chargeback data over the API, see Chargebacks.
Turning it on
It’s off by default — contact CommissionSight to enable payment gaps for your account.