Both pull in carrier commission statements — then take them in different directions.
Different jobs. Comtrack is built to pay your downline — uplines, splits, overrides, payroll, and agent portals. CommissionSight is built to find the money the carrier owes you and audit the health of your book. Many agencies will want both — but only one of them computes Medicare commission owed against CMS rate tables.
Credit where it’s due — these are real strengths. The question is which job you’re solving.
| Capability | CommissionSight | Comtrack |
|---|---|---|
| Member-level book health | Every member scored green / yellow / red each period — attrition (MoM/QoQ/YoY), drops, and reappearances | Detects clients “fallen off the books” |
| Carrier-agnostic by config | Any carrier from a single sample statement — a JSON mapping, no code, no waiting on a vendor | Automatic carrier detection |
| Commission owed (expected vs. actual) | To the member, with an honest coverage % of the book — and graded health schedules (premium-banded tiers, PMPM, first-year vs. renewal, production bonuses), not just a flat percentage | Reconcile underpayments |
| Medicare CMS owed engine | CMS rate tables by region × initial/renewal, with RDE clawbacks, vesting, and per-state caps — owed works day-one from the published CMS maximums, and over-the-cap pay is flagged as a compliance exposure | Not advertised |
| Chargeback tracing | Each clawback traced to the original payout it reverses — period, amount, and source file | Chargeback accounting (within payroll) |
| Developer surface | REST API + typed SDKs (TypeScript, Python, C#) + native CLI + signed webhooks | REST API (read); no public SDK or CLI advertised |
| Data isolation | Each account’s data in its own isolated, encrypted database — never co-mingled | Not stated publicly |
| Agent hierarchy / splits / payroll | On the roadmap (Exploring) — and only ever as a layer on top of reconciled, owed-aware numbers | Yes — uplines, downlines, LOA & override splits, payroll |
“Not advertised / not stated publicly” means we couldn’t confirm it on Comtrack’s public site — not that it can’t be done. Comparison reflects each product’s public website as of June 2026, and our reading of what it does. Products change — found something out of date? Email hello@commissionsight.com and we’ll fix it.
Expected vs. actual to the member with an honest coverage figure, plus a Medicare CMS owed engine — the recoverable shortfall you take back to the carrier.
Every member graded green / yellow / red each period, with attrition and reappearance — a health check on the book itself, not a payroll run.
Each agency’s statement data lives in its own isolated, encrypted database — never co-mingled in a shared store.
A REST API plus typed SDKs (TypeScript, Python, C#), a native CLI, and signed webhooks — built to automate and embed.
They solve different problems. Comtrack is agent-hierarchy commission management and payroll — paying uplines, downlines, and overrides. CommissionSight is reconciliation and book-health auditing — finding the commission a carrier owes you and scoring the health of your book. Some agencies use one, some will use both.
Not today. Agent hierarchy and splits are on our roadmap (Exploring), and we’d build them as a layer on top of reconciled, owed-aware numbers — not as a standalone payroll product.
A Medicare CMS rate-table owed engine (region × initial/renewal, RDE clawbacks, vesting, state caps), member-level green/yellow/red book-health scoring, per-account data isolation, and a full API + typed SDKs + CLI + signed webhooks.
Upload a few carrier statements and watch CommissionSight score every member and surface what you’re owed — in minutes, nothing stored.