Use caseDocument AIWorkflow automation
Carrier commission statements matched to the policies in your agency system, shortfalls listed for finance
Commission statements from many carriers, in PDF, Excel and portal formats, matched to policies in Applied Epic or AMS360, with every shortfall listed.
A blueprint, not a client story. The business described is illustrative; the architecture, integrations and trade-offs are real, and this is how I would build it. By Ergini, .
The short version
A reconciliation workflow for independent insurance agencies and brokers placing business with many carriers. Each carrier's commission statement is read in whatever layout it arrives. Every line is matched to a policy in the agency management system on policy number, term dates, insured and line of business. Code computes the commission each line should have paid from the agency's schedule, and lists the differences. Finance approves every posting and every dispute.
- Best for
- Independent agencies with a dozen or more carriers, reconciling monthly statements by hand in Applied Epic, AMS360 or a similar system.
- The AI does
- Reads statements in PDF, Excel or CSV form, extracts each line with its source, and proposes the policy each line belongs to with a match confidence.
- People do
- Approve postings into the agency system, decide each disputed or unmatched line, and raise queries with carriers about rates and cancelled policies.
- Built as
- AI Workflow Automation, usually $15K - $30K
Forty layouts, one monthly deadline
Take an independent agency placing commercial and personal lines with about twenty carriers. Each carrier sends a commission statement once a month, and each one arranges it differently: one as an Excel sheet with policy numbers in the first column, one as a PDF with the insured's name and a term date, one through a portal that only exports a CSV with a different delimiter every quarter. Some carriers pay on premiums the agency billed. Others bill the client directly and pay the agency's commission on their own schedule.
A finance assistant opens each statement, finds every policy in Applied Epic, confirms that the commission is the amount the agency should have received, and writes the matched lines into the reconciliation. It takes most of two days each month, and the work that matters is the last few percent: a policy that carries the wrong commission rate, a cancelled policy the carrier still paid on, a renewal missing from the statement altogether.
Those are the lines that cost money. An overpayment that is not returned is a liability the agency will eventually answer for. An underpayment that nobody chases is income that never arrives. A statement reconciled against the wrong policy number carries a wrong figure into the books. None of these needs judgment about insurance. They need every line checked against the policy record, and the differences listed clearly enough that someone can act on them the same day.
One carrier statement, matched line by line
The finance team's first view is not a blank reconciliation. It is the statement with its matches and differences already sorted.
Finance mailbox, 1st of the month
Carrier commission accounting · Email, with PDF
Attached is the November commission statement for agency code 4471. Please confirm receipt.
- extract_statement(document: "carrier_statement_nov.pdf")38 lines / columns: policy number, insured, transaction type, premium, commission rate, commission amount / statement total EUR 21,406.12 matches the sum of its lines
- match_policy(lines: 1 to 38, keys: ["policy number", "term dates", "insured"])35 exact matches / line 14: policy suffix differs, insured and term dates match, confidence 0.91 / line 22: no open policy found
- expected_commission(lines: 35, schedule: "carrier schedule, valid from 1 Oct")33 lines agree with the schedule / line 9: statement rate 12.5 percent, schedule rate 15 percent for this line of business / line 31: commission paid on a policy cancelled in February
Reconciliation queue · Finance screen
Statement drafted, not posted. 33 lines agree. Four need you: line 9 rate difference, line 14 policy suffix to confirm, line 22 unmatched, line 31 paid on a cancelled policy.
- Finance confirms line 14, raises a query with the carrier on lines 9 and 31, and holds line 22 for the account handler. The posting batch for the 33 agreed lines is approved and imported.
How a statement becomes a reconciled batch
The reader proposes matches. The schedule and the policy record decide what the expected amount is. Finance decides what gets posted.
01 Trigger · Microsoft Graph, file share
A statement arrives
An email from a carrier or wholesaler, a portal export, or a file dropped into the finance share. Statements are linked to the carrier and the period, and a re-sent statement updates the same reconciliation instead of starting another.
02 AI model · Vision model, strict schema
Read every line
Each statement is read into lines with the same fields, whatever its layout, and every value keeps the row or page it came from. The statement's own totals are checked against the sum of its lines before anything else happens.
03 Plain code
Match each line to a policy
Policy number first, then term dates, insured name and line of business. A suffix or formatting difference is allowed to match, but only with a confidence score that finance can see, and only when the other keys agree.
04 Plain code
Compute the expected commission
The expected amount comes from the agency's commission schedule for that carrier and line of business, on the premium in the policy record, with the schedule version valid on the transaction date. The model never supplies a rate.
05 Decision
What kind of difference is it?
Each line lands in one category, and the category decides who sees it.
- Matched, and the amount agrees with the schedule then the line goes into the batch for approval
- Matched, but the amount or rate differs then a query is drafted to the carrier, and the line is held
- No policy found, or commission paid on a cancelled policy then the line goes to the account handler with the policy history attached
06 Person
Finance approves and disputes
The queue shows held lines first, with the statement row beside the policy record. Finance accepts the carrier's figure, sends the query or corrects the agency record. Nothing is posted without an approval.
07 Result · Applied Epic import, AMS360 import
Posted through the agency system's import
Approved lines are imported as a reconciliation batch through the agency system's own import route, which keeps its audit trail. Each approved line keeps the statement it came from, so a later question has an answer.
How each kind of difference is handled
Each difference has a usual cause and a fixed next step. The categories are the same whichever carrier sends the statement.
| Difference | Usual cause | Handling |
|---|---|---|
| Policy not found | A new policy not yet entered, a changed policy number, or a carrier error | Account handler checks the policy record and the carrier's schedule; line stays held until then |
| Amount short | A rate lower than schedule, a missing endorsement, or a commission not yet earned | Query drafted to the carrier with the expected figure and the policy reference |
| Amount over | A wrong rate, a duplicate line or a commission on a cancelled policy | Held for finance to decide on repayment; never netted off silently |
| Rate differs from schedule | A schedule change not yet loaded, or a carrier using an old rate | Finance confirms the effective date in the schedule, then accepts or queries the rate |
| Statement line repeats an earlier month | A re-sent statement or a carrier restating adjustments | Matched to the earlier batch and shown as a restatement, not counted twice |
Lines that finance should not automate away
These are the cases where a reconciliation tool is trusted only if a person still makes the call.
Repaying an overpayment
A commission paid on a cancelled policy is a debt the agency may owe back. The workflow lists it with the policy history and the cancellation date. Whether, when and how to repay is finance's decision.
Direct bill and agency bill side by side
Direct-bill commissions come from carriers that bill the client; agency-bill commissions follow premium the agency collected. The two are reconciled on different timing, so they are shown in separate sections rather than one total.
Schedules that change mid-year
A new schedule valid from an effective date changes the expected amount only for transactions on or after that date. Expected values are stored with the schedule version they used, so the calculation can be reproduced when a carrier asks.
Contingent and profit-share payments
Bonuses and profit-share statements are often calculated on volume or loss ratios the agency system does not hold. They are read and listed, but the expected amount is entered by finance, not inferred.
The agency system's own reconciliation, a vendor layer, or a custom one?
Check the agency system first. Applied Epic has a classic reconciliation import: finance adds a batch, selects a mapping file for the carrier, and imports the transactions in a second step after reviewing them. Applied also sells Applied Recon, which uploads PDF, XLSX and CSV statements and uses AI to match them on policy number, term dates and line of business. If Recon supports your carriers and your system, buy it. Coverage has been described differently across Applied's own pages, so confirm your carriers in writing before you commit.
A custom layer fits an agency whose carriers and schedules are not all supported by a vendor module, whose commission schedules need their own version history, or whose statements arrive in layouts a vendor has not seen. It reads the statements, computes the expected amounts from the agency's own schedules, and hands the batch to the agency system's import, so the system stays the record.
Either way, the posting decision stays with finance. A vendor module or a custom layer that posts without approval is the setup to avoid, because a wrong batch is hard to unwind once it is in the books.
How you would know it is working
A blueprint has no results to report, so here is what I would measure from the first week instead, on your own data.
- Lines matched without a change
- The share of lines matched automatically and approved unchanged, by carrier. Low numbers for one carrier usually point to a layout or a policy-number format problem.
- Days from statement to posted batch
- Working days between the statement's arrival and the approved import, compared with the month before the workflow went live.
- Commission found short or over
- Euro value of shortfalls recovered and overpayments repaid each quarter, as a check that the expected-amount logic is working.
- Queries raised with carriers
- Number of queries sent and how many were resolved in the carrier's favour, to show where schedules or statements need correcting.
What a build like this costs
This is built as AI Workflow Automation, which runs $3.5K - $60K overall. A build like this one usually lands in the multi-step workflow tier: $15K - $30K, 3-5 weeks. The first working version runs on your real data well before the end of that window.
What it costs to run
A statement of a few dozen lines costs a few cents in model usage to read and match. The larger recurring cost is finance's review time on held lines, which falls as schedules are kept current and carriers' layouts are learned.
What moves the price
- How many carriers and statement layouts are in scope, and how many arrive as PDF only
- How the agency system accepts reconciliation batches: a documented import route, a file format, or neither
- How complete the commission schedules are, and how many versions they have had
- Whether direct-bill and agency-bill statements both need reconciling
- How much history needs loading so that matches to older policies work
Who this is for
- Independent agencies with a dozen or more carriers, where finance reconciles statements by hand each month
- Brokers paid on both direct-bill and agency-bill business who need the two kept apart
- Agencies that have grown through acquisitions and inherited several commission schedules
- Finance teams in agencies that have been asked by an auditor or a carrier to show how an expected commission was calculated
Questions people ask about this
What does insurance commission reconciliation automate?
Reading each carrier's statement, matching its lines to policies, computing the commission each line should have paid from the agency's schedule, and listing the differences. Finance still approves every posting, decides on every repayment and sends every query to a carrier.
Which agency systems can take the result?
Applied Epic imports reconciliation statements through a mapping file and a two-step batch import, so the output has to match that route. AMS360 and other systems have their own import formats. Confirm the import route for your system before you scope the work, since it decides how much of the posting is automatic.
Can Applied Recon replace a custom reconciliation layer?
If your carriers and your system are supported, probably yes for matching. Applied Recon reads PDF, XLSX and CSV statements and matches on policy number, term dates and line of business. Its carrier coverage is described differently across Applied's pages and brochure, so confirm your carriers in writing first.
Does it work for carriers that only send PDFs?
Yes, provided the columns can be read. A PDF statement is extracted into the same fields as a spreadsheet, its printed totals are checked against the sum of its lines, and every amount keeps the page it came from so finance can check it in seconds.
How are commission disputes handled?
Each exception is listed with the statement line, the expected amount from the schedule and the policy record. Finance either accepts the carrier's figure, sends a query with the expected amount, or corrects the agency's own record. Nothing is posted until a person approves it.
Sources