Commission-Reconciliation AI Agent (Carrier Statements)
Match every carrier commission statement line to what the contract says was due, name the shortfalls, overpayments and missing statements, and package the difference — a person approves every adjustment.
Take the statement as the carrier sent it — portal export, file, spreadsheet or download — and log what arrived.
02
Read the expected side from policy admin: policy, term, premium, and the producer of record on that date.
Reason
03
Match each paid line to a policy and a term, through rewrites, mid-term changes, reinstatements and cancellations.
04
Recompute what was owed from the commission schedule and the split agreement in force on that effective date.
05
Separate a shortfall from a chargeback, a timing difference and a period that never arrived at all.
Decide
06
A clean match inside the agreed tolerance closes, logged with the schedule version it cleared against.
07
Every difference, unmatched line, missing statement and licensing flag goes to a named approver.
Out
08
Package the difference per policy and term: paid, expected, and the clause the expectation rests on.
09
Retain the statement as received, the schedule and split version used, and who approved each adjustment.
→Product statement
The agent matches, identifies and packages. Every payment, adjustment, write-off and dispute is a named approver's decision, and nothing is released to a producer whose licence and appointment for that business cannot be cleared. A clawback is a decision about someone's earnings — a person makes it, against the agreement it rests on, and it is not applied twice. This page covers commission owed on business already placed; it does not set rates, negotiate schedules or decide what a producer should be paid.
Example workflow
One statement, end to end
AgentHuman
1Statement receivedA carrier statement as it arrived — portal export, file, spreadsheet or download — with the period it covers
2Expected side assembledPolicies, terms and premium from policy admin, with the schedule and split agreement in force on each effective date
3Lines matchedEach paid line to a policy and a term, through rewrites, mid-term changes, reinstatements and cancellations
4Differences classifiedShortfall, overpayment, chargeback, timing difference or a period that never came — each named and quantified
No human action required
Stages 1 to 4 run without a person in the loop — the statement is parsed, the expected side is assembled and every difference is classified before anyone opens the file. Nothing has been paid, adjusted or written off.
5DecisionSplits on whether the match is clean and inside the agreed tolerance
Clean match, inside tolerance
Closes with the versions it cleared.
Any difference or missing line
Goes to a named approver, unresolved.
Commission or finance approver
Takes the pack with paid, expected and the clause behind the difference. Payments, adjustments, write-offs and disputes are theirs alone.
Approve · Adjust · Dispute
Approved — handed back▼
6Adjustment recordedOnly what a named approver signed — the ledger entry, the carrier dispute or the producer adjustment
7Outcome evaluatedMatch rate, discrepancy recall, false differences, licensing coverage and tolerance write-offs, by carrier and format
Approver changes
Every difference an approver reads differently is counted, in both directions.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Paying, adjusting or clawing back a producer's commission.
Writing off a difference outside the signed tolerance.
Releasing commission the licensing check cannot clear.
Applying a chargeback or reversing a paid entry.
Automation boundaryAgent acts unaided
✓Parse the statement in whatever format the carrier sends.
✓Recompute what was owed from the schedule and split in force.
✓Classify each difference and name the clause behind it.
✓Assemble the pack and route it to a named approver.
Write actions run only inside the approval boundaries agreed during implementation. The agent may open a case and stage an entry. It may not move money, post an adjustment or release a commission, on any tier or in any configuration, and writes nothing off outside the signed tolerance.
Opening or settling a dispute with a carrier.
Changing a split, a schedule or a tolerance.
Posting a commission adjustment to the ledger.
Touching money held in a fiduciary or client account.
Example output
One statement line, annotated
Everything the agent proposes is attached to the statement line and the agreement it was recomputed from.
Reconciliation output · single statement lineIllustrative example
Statement
Policy
Producer
Difference
Confidence
Adjustment
Monthly, direct bill
Rewritten mid-term
Two-way split
Paid short, one term
92%
None — approver's
As receivedThe statement in the carrier's own format and period, and the policy, term and producer as policy admin holds them.
Checks clearedMatched to the rewritten termSplit agreement in forceLicence and appointment clear
Why it is shortThe rewrite moved the term; the carrier paid on the schedule that applied before it.
ActionApproveAdjustDispute
What the score decidesWhether the match may close unattended — never whether the carrier owes it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every carrier statementFrom portals, feeds and files
03Schedules & splits
Recompute from the agreement in force
The commission schedule, the split and the override basis that applied on that effective date — not the ones filed today — read at reconciliation time and stamped with their version.
01Approved path
Close the lines that already agree
A line that matches its policy, its term and its schedule closes without anyone opening the statement, and carries the versions it cleared against.
02Human review
Send the difference up with its clause
A shortfall, a double chargeback or a period that never came reaches a named approver with paid, expected and the agreement behind the expectation — never as a number on its own.
04Build an evidence trail
Retain the statement as received, the schedule and split version used, the difference found, the approver's decision and what the carrier said back — on both paths.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
A tolerance set as a flat amount rather than a proportion writes off hardest against the smallest producers, the newest agencies and anything billed in another currency. Nobody chose that; a threshold did. Nestack reports performance by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Carriers that changed format
5.9%
3.6×
Review
Cross-border and multi-currency
4.1%
2.5×
Review
Split and sub-broker business
3.1%
1.9×
Watch
Single-producer direct bill
1.2%
0.7×
Normal
Bar: missed-difference lift vs. single-producer direct-bill baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
Carriers reject differences; the match is what failed
When a carrier sends one back, the fault is usually the term it was matched to or the schedule version it was recomputed from — not the amount.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Match rate, recall or write-off volume moves on one carrier.
02Diagnose
Traced to the format, the match, the version pinned or the tolerance.
03Improve
The parser, the matching rule or the tolerance is changed, re-signed by finance and version-linked.
04Verify
Re-run against held-out statements, including every rejected difference.
05Learn
The rejected difference becomes a regression case with its clause attached.
Learn → DetectThe return edge. Every cycle re-reads the tolerance itself — a threshold that quietly widened, or a write-off nobody put their name to, goes to finance before anything else ships.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, statement and agreement sourcing, matching and recomputation, evaluation, ledger integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Workflow discovery and automation-boundary definition.
02Carrier and statement-format inventory.
03Policy-admin and agency-management APIs.
04Statement parsing and change detection.
05Schedule, split and override modelling, pinned by date.
06Policy, term and producer matching rules.
07Chargeback, reversal and timing logic.
08Licensing and appointment validation.
09Tolerance policy, register and approval routing.
10Match-rate and discrepancy-recall testing.
11Ledger, payment and dispute-pack integration.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne carrier, one formatProductionLive reconciliationAdvancedMulti-carrier / multi-entity
Introduced at Pilot
Statement parsing and normalisation✓✓✓
Policy, term and producer matching✓✓✓
Difference classification and pack✓✓✓
Draft mode — nothing is adjusted✓✓✓
Baseline evaluation✓✓✓
Introduced at Production
Schedule and split modelling by date—✓✓
Licensing and appointment validation—✓✓
Tolerance register and approval routing—✓✓
Ledger and payment integration—✓✓
Introduced at Advanced
Overrides, contingents and bonus tiers——✓
Multi-currency and enterprise controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on the carriers and statement formats in scope, the policy-admin and ledger systems involved, schedule and split complexity, statement volume, the tolerance and approval controls agreed, and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01The carriers, statements and periods in scope→Workflow discovery and automation-boundary definitionWeek 1
02Real statements in every format they arrive in→Statement parsing and format-change detectionWeek 2
03Access to policy admin or the agency system→Policy, term and producer matching rulesWeek 2
04Commission schedules, split and override agreements→Schedule, split and override modelling, pinned by dateWeek 3
05Your licensing and appointment source of record→Licence and appointment validation before any releaseWeek 3
06A period you reconciled by hand, differences and all→Evaluation suite, discrepancy recall and regression casesWeek 4
07The named approver, and the tolerance they will sign→Tolerance register, approval routing and the audit trailWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. Nothing is paid or adjusted before week 6; reconciliation runs on a period you have already closed.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Carriers, formats and who may approve an adjustmentW2Statement parsing, policy-admin access and the expected sideW3Schedules, splits, chargebacks and licensing validationW4Evaluation suite, recall testing and the tolerance policyW5Ledger and payment integration, in draft — nothing postsW6First approved adjustments inside the signed tolerance, then handover
Reading the bandBars span only the weeks their work is named in. Draft running in week 5 is real — the agent proposes adjustments and posts none.
At the end of W6Adjustments have been posted only where a named approver signed them, and every release cleared the licensing check.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Insurance AI agent
Reconcile the statement before you argue about the money.
Show us a month of carrier statements in the formats they actually arrive in, the schedules and splits behind them, and who may approve an adjustment. We'll reconcile that month beside your own numbers and show you every line where the two of us disagree.
