Skip to main content
Module · Broker Comp

Stop flying blind on carrier statements.

Carrier statements are hundreds of line items, dozens of formats, reissued every month. No agency audits them by hand and most don't audit at all. Atlas ingests every statement with our AI vision engine, extracts every row at 99.1% accuracy, matches each to your book, computes expected commission from the schedule engine, and surfaces variance — with chargebacks, GA-override hierarchy, splits, 1099-NEC, bonus attainment, persistency, projection, and aging all in production.

Velora-native module
Velora productAtlas Broker Comp (in-product)

Commission reconciliation runs inside Atlas — not a separate Velora sister-product and not a third-party plug-in. The statement-ingest engine, match layer, and variance math share Atlas's database and audit log directly.

Ingest, match, compute expected, surface variance, settle.

Ingest + match

Upload a carrier statement PDF. Our AI vision engine extracts every row — account, policy, period, premium, commission — into structured CommissionEntry records, then matches each row to your book (exact first, fuzzy-contains fallback). 99.1% field-level extraction accuracy across 60+ format variants, audited against 4,200 statements.

Compute expected

The schedule engine resolves the contractual rate per carrier / product / effective date and computes expected commission per entry. Tiered, graded, heaped, and PEPM rate shapes are all modeled. GA overrides and downline / sub-producer splits resolve through the hierarchy resolver as first-class structured data on each entry.

Surface, settle, file

Variance is computed (actual − expected) and flagged with reason. Chargebacks reverse on cancel-window cancels. Producer statements, persistency, projection, bonus attainment, aging, and 1099-NEC PDFs export from the same data. The reconciliation IS the dispute trail.

What's shipped — full schedule, splits, chargebacks, 1099.

01

AI vision on every statement

60+ carrier statement formats supported. Tables that span multiple pages, carriers that redesign layouts annually, scans of mailed statements — all extracted to structured rows.

99.1% row-extraction accuracy · audited against 4,200 statements
02

Schedule engine — tiered, graded, heaped, PEPM

Per carrier × product × effective-date schedule resolver computes expected commission for every entry. Rate shapes (tiered, graded, heaped, PEPM) all modeled in the schema. Variance is automatic, not a manual data entry step.

03

GA overrides, downline + producer splits

First-class hierarchy resolver and split engine. GA overrides, downline / sub-producer chains, and direct-write multi-producer splits all resolve to structured rows on each CommissionEntry — producer ID, percentage, amount, override level.

04

Chargebacks + dispute trail

Cancel-window chargebacks reverse against the originating entry through the chargeback engine. Every reconciled entry keeps the source statement page, match method + confidence, and the variance calculation, so the reconciliation is the dispute packet.

05

1099-NEC, bonus, persistency, projection, aging

PDF exports for all of it: 1099-NEC summary, producer statements, bonus attainment, persistency, projection, aging. Same source-of-truth ledger; same audit log on every line. No spreadsheet stage in between.

All shipped, all PDF-exportable
06

Auto-drafted dispute emails

POST /api/v1/commissions/disputes/:id/draft returns a carrier-ready email. Deterministic template populates account name, policy, period, expected vs actual, variance, producer of record, and the match-basis evidence. When AI is enabled, our AI engine refines the body for tone — guarded against drift (response must still reference org name + a dollar amount or the deterministic body is returned). The route does not auto-send; the operator pastes into their carrier-relations email.

Broker Comp feeds the rest of the agency.

Commission reconciliation isn’t an isolated function. Broker Comp reads lives-under-management from HRIS, reads policy effective dates from the CRM, and writes the settled commission back to the producer’s book record. When you fix a rate-tier bug here, it back-fills every affected account in one pass.
  • HRISLives-under-management, per book
  • Billing ReconPairs with invoice reconciliation
  • Ben AdminEffective-date source of truth
  • NetworkRenewal network disruption triggers schedule review
99.1%
carrier-statement row extraction accuracy

Field-level extraction accuracy of Atlas's AI vision pipeline on 4,200 carrier commission statements across 60+ format variants, audited line-by-line against ground truth. The extraction is one layer; the rest of the engine — schedule resolution, splits, GA overrides, chargebacks, 1099-NEC, bonus, persistency, projection, aging — runs on the same ledger.

Pilot-phase benchmark· Reference customers launching Q2 2026 · ask for a reference call

Questions brokers actually ask.

Which carrier statement formats are supported?
60+ out of the box including Aetna, BCBS (most states), Cigna, UHC, Humana, Kaiser, Guardian, Principal, Mutual of Omaha, Sun Life, Lincoln, MetLife, Anthem. If your carrier isn’t on the list, upload 3 recent statements — we add the format in under 48 hours.
Does it handle splits between producers?
Yes — direct-write multi-producer splits, GA overrides, and downline / sub-producer hierarchies all resolve through the hierarchy resolver and split engine to first-class structured rows on each CommissionEntry (producer ID, percentage, amount, override level).
What about commission advances and chargebacks?
Chargebacks ship today via the chargeback engine — cancel-window cancels reverse against the originating entry, with the recoupment tracked on the producer ledger. Commission advances (carrier-paid advances against future earnings) are on the roadmap.
Can we pull directly from carrier portals instead of uploading?
Not today — direct carrier-portal scraping is on the roadmap. The ingest path today is statement upload (drag-drop or email-in) into the AI vision parser. For carriers that publish a structured download, a CSV import path is also live.
Is this just PDF parsing, or is there actual reconciliation logic?
Parsing is step 1 of 5 and the only one that’s commoditized. Steps 2–5 — schedule modeling per carrier/product/effective-date, account- period matching with proration, variance detection with confidence scoring, and chargeback recoupment on cancel-window cancels — all ship today. Auto-drafted dispute emails (deterministic template + optional AI tone refinement) close the loop: POST /api/v1/commissions/disputes/:id/draft returns a carrier-ready subject + body off the variance trail.
How long to get set up?
Most agencies are running reconciliations within 2 weeks: week 1 is modeling the expected schedules (your team + ours), week 2 is ingesting 6 months of historical statements for back-reconciliation. First real recovery usually lands mid-week-2.

Upload a statement. See the full reconciliation.

Send a recent carrier PDF. Inside 24 hours we'll parse it, match it to a sample book, resolve the schedule + splits + GA hierarchy, compute expected vs actual, and show you a live producer statement / 1099 / aging export from the same ledger.