Broker commission reconciliation system map: the five keys that join placement, statement, producer and ledger

Short answer

Following one commission case across a brokerage's software takes five identifiers: the policy number with its term, the carrier's sheet and line number, the internal item ID assigned when lines are matched, the producer code, and the journal reference in the ledger. The dispute trail, where arguments about the case live, has no system key at all. When every identifier is carried forward, a reversal can be walked back to the policy it undoes; when one is dropped, it reads as a stray negative number.

Visual briefFull-size diagram
Five system nodes in a ring, broker management system, carrier statements, producer compensation, general ledger and dispute log, with keys (policy and term, statement line, item ID, producer code, journal reference) travelling between them to join one return commission case.
Illustrative system map. Field names and keys differ by broker management system, version and carrier.

This map is part of the broker commission reconciliation guide, which covers what to inventory before an acquisition. The worked hard case tells one cancellation as a story; this page is the wiring diagram underneath it: nodes, keys, owners and the places where keys get lost.

Five nodes, one ring of identifiers

Think of the brokerage's records as five nodes joined by identifiers. Each node answers one question about a case, and each identifier is a foreign key that lets you step to the next node. None of the nodes tells the whole story alone.

Broker management system: what was bound. The policy record and the matched item. Its key out is the policy number with its term dates, and an internal item or transaction ID once matching is done.

Carrier paperwork: what the insurer said it paid. Line by line, in the carrier's numbering. Often downloaded from carrier portals and filed as PDFs or spreadsheets on a shared drive, apart from the brokerage's own matched version. Its key out is a sheet number and line number.

Producer pay: who got credited. Splits and clawbacks, keyed by a producer code. Sometimes calculated inside the broker management system, sometimes in a payroll tool or a workbook.

Ledger: how it was booked. Income, reversals and corrections, keyed by a journal reference. Whether the memo field carries an item or sheet number decides whether the ledger can be walked back.

Dispute trail: why anyone argued. Email threads, a tracker or notes on the item. It has no system key at all, only whatever a person typed into the subject or body. It is the most informative node and the least structured.

System map: record, linking key and owner

Read across a row to see what each system holds, which key leaves it and where that key lands.

SystemRecordLinking keyPoints toOwner
Broker management systemPlacementPolicy number and effective dateCarrier statement lineAccount management
Carrier statementsCommission or return lineStatement number and line, plus policy numberReconciled itemAccounting team
Broker management systemReconciled item and statusItem or transaction IDProducer statement; ledger postingAccounting team
Producer compensationSplit or chargebackProducer code plus item ID or policy numberOriginal placementFinance director
General ledger or ERPPosting or adjustmentJournal reference with statement or item numberReconciled itemController or finance director
Dispute logQuery, argument, decisionPolicy number or item ID typed into the threadItem and producer statementFinance director

Two keys are typed by people: the item reference in a ledger memo and the policy number in a dispute email. Those break first. Ask about them before anything else.

One fully joined case (Illustrative)

Illustrative and invented for this page. A fictional 150-person commercial lines brokerage; a general liability policy cancels mid-term and the carrier returns part of the commission. Here is the case when every key holds.

KeyIllustrative valueHeld inJoins
Policy number and termGL-55210, Mar 1 termPlacement; both carrier statementsPlacement to original and return statement lines
Statement and lineApril statement line 14; August statement line 9Carrier statement PDFsCarrier lines to the reconciled item
Item IDItem 88413, reopened for the returnBroker management systemItem to producer chargeback and ledger posting
Producer codeP-117Producer statement, with item 88413Chargeback to original split
Journal referenceJE-2291, memo cites August line 9 and item 88413General ledgerAdjustment to the reconciliation
Dispute threadSubject line cites GL-55210Finance mailboxProducer's challenge and finance director's decision

Top to bottom, the chain says: this placement was paid in April, part of it was returned in August, the same item was reopened rather than duplicated, the producer's chargeback names that item, the ledger adjustment cites the statement line, and the dispute about it names the policy. That is a complete case.

Where the joins break

Each link has a typical failure. Knowing them lets a partner ask the right question in one sentence.

Reconciliation logic differs by product, which changes where each break shows up. In AMS360, a statement is built from eligible uncleared transactions and compared with the carrier's, and company totals should match agency totals before posting. In Applied Epic, a direct bill commission statement moves through statuses such as Suspended, Finalized and Approved, and can be associated with a receipt, disbursement or journal entry.

  1. Renewals and rewrites. Carriers sometimes reissue policy numbers at renewal or rewrite, so the policy number alone may not distinguish terms. Ask: "How are renewals keyed: same number with a new term, or a new number?"
  2. Closed items and late returns. Applied's training documentation describes a final-payment checkbox that removes an item from future reconciliations. When a return arrives after that, ask: "Do you reopen the original item, or book a separate line with no link back?"
  3. Reopened statements. Applied Epic notes that reopening a finalized statement reopens others sharing the same master statement number. Ask whether the team avoids reopening and books corrections elsewhere instead, which breaks the trail.
  4. Chargebacks outside the system. Ask: "Are chargebacks calculated in the system or a spreadsheet, and does each one name the original policy or item?"
  5. Ledger memos. Ask: "Do adjustments carry a statement or item reference, or only free-text memos?" The general ledger reconciliation page covers the ledger side in more depth.
  6. Disputes in email. Ask: "Do dispute threads name the policy or item, and are those mailboxes kept?"

Export capability varies by system, version and contract. Do not assume any export exists; the company should confirm with its own administrators what history each system can produce.

What to note, and what stays unknown

Write one line per key: holds, partly holds, or does not hold, with years and rough volume. For example: "Return commissions matched to reopened items since 2018; chargebacks in a spreadsheet citing policy numbers; disputes in the finance mailbox." Never collect statements, producer names, client names or system access. Exception handling records of this kind are described more generally in exception handling data for AI agents. If the brokerage already works with an M&A broker, referral fee if a company already has a broker explains how that interacts with an introduction.

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Who can authorize the discussion is set out on who can license broker commission reconciliation records. Whether carrier agency agreements allow licensing, what de-identification is needed and whether there is buyer interest stay unknown until SourceX reviews it.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the finance director can confirm that most of the five keys hold across the brokerage's systems, register as a partner, check the company against who qualifies and read the program terms before you introduce them.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Which key breaks most often?

The link from a late return commission back to its original item. If the item was closed with a final-payment flag, the return is often booked as a new line with no reference to the policy term it reverses.

Do carrier statements count as a separate system if they are only PDFs?

Yes, for mapping purposes. Statement PDFs in a shared drive hold the carrier's own line numbers, which are the only way to prove the agency's reconciliation matched what the carrier reported.

Can a partner check the joins without seeing the data?

Yes. The finance director can answer one yes-or-no question per key. Partners never ask for statements, exports or system access.

Sources

  1. help.vertafore.com/ams360/content/contextsensitive/company/csdb…
  2. help.appliedsystems.com/Help/Epic/2023.2en-US/General_Ledger/Reconci…
  3. appliedsystems.com/DOC_CENTRAL/TR-TRAINING/RECONCILINGOFAGENCYO…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment