# Brokerage statement to reconciliation chain | SourceX

Canonical: https://refer.sourcex.si/guides/brokerage-statement-to-reconciliation-record-linkage
Last updated: 2026-11-04

An agency connects its statement-to-reconciliation records by mapping which field each system uses for the same thing. The policy number is the natural key from placement to statement line. The statement number bridges the agency system and the reconciliation tracker, and the journal entry number bridges the tracker and the ERP. Most chains hold until a cancellation lands on a later statement, because the ERP rarely carries the policy number and the first reconciliation is already closed.

This key map is part of the [statement-to-reconciliation guide for insurance agencies](/guides/chain-brokerage-statement-to-reconciliation), which sets out the metadata packet for the whole workflow. Here the only job is to name the key on every link and show where links give way.

## The chain from placement to ledger, link by link

The example is Illustrative: a fictional 160-person commercial agency using Applied Epic, a monthly spreadsheet tracker and an ERP. One direct bill liability policy is placed in January, its $5,400 commission is paid on the February statement, and it cancels mid-term, so a $3,825 return commission appears on the June statement.

| Step | Record | Key that carries the link | System |
|---|---|---|---|
| 1. Placement | Policy and expected commission | Policy number | Applied Epic |
| 2. Carrier pays | Commission statement line | Policy number on the line, if the carrier prints it | Carrier statement, loaded to Epic |
| 3. Line matched | Statement closed | Statement number | Applied Epic |
| 4. Month tracked | Tracker row marked matched | Statement number typed per row; policy number if someone keeps a column | Spreadsheet |
| 5. Month posted | Commission journal | Journal entry number, associated with the statement in Epic | ERP |
| 6. Cancellation | Cancellation on the policy | Policy number | Applied Epic |
| 7. Money taken back | Return commission on a later statement | Policy number on the line, if printed | Carrier statement |
| 8. Debit posted | Negative journal in a later month | Journal entry number only | ERP |

Read down the key column. The policy number runs through steps 1, 2, 6 and 7. The ERP, at steps 5 and 8, carries only its own journal number. The tracker is the only place a person can tie the two together.

## The three keys and what each one joins

**Policy number.** Joins the policy, its cancellation and every statement line about it, as long as the carrier prints it. Some carriers list only the insured's name, which turns a recorded join into a manual match.

**Statement number.** Joins a statement in Epic to the tracker sheet where it was matched. Applied documents that each statement carries a status, and that reopening a closed one also reopens others sharing its master statement number. That master number is itself a link worth noting.

**Journal entry number.** Joins Epic to the ledger. Applied's documentation says a statement that is not yet approved can be tied to an existing receipt or journal entry. If the agency used that association, the February journal traces back to the February statement inside Epic. If it did not, the only bridge is a journal number pasted into the tracker, when someone remembered.

## Field map: one concept, three systems

| Concept | Applied Epic | Tracker | ERP |
|---|---|---|---|
| Policy | Policy number on the policy and its transactions | Policy number column, if kept | Usually absent; revenue posted by carrier |
| Carrier statement | Statement with a status | One sheet per carrier per month | Not held |
| Matching state | Statement status | "Matched", "unmatched" or a cell color | Not held |
| Ledger link | Statement associated with a receipt, disbursement or journal entry | A pasted journal number, sometimes | Journal entry number |
| Adjustment | Cancellation on the policy; return line on a later statement | A new row on a later sheet | A negative entry in a later month |

Illustrative. Field names describe the example, not a tested export.

## Where links commonly break

Five breaks explain most incomplete chains:

1. **Statement lines without policy numbers.** The join from statement to policy depends on name matching for those carriers.
2. **The item closed for good.** Applied's training material describes a final-payment checkbox that excludes an item from future reconciliations so no more payments can be applied to it. A return commission that arrives after that has nowhere to land, and is often posted to suspense or an "unmatched" tab.
3. **Lump-sum journals.** If the ERP posts one commission entry per carrier per month, no ledger line points to a policy.
4. **A tracker without a policy column.** The tracker then joins statements to journals but not to policies, so the cancellation link runs only through Epic.
5. **Overwritten workbooks.** Microsoft documents that version history works only for files stored in OneDrive or SharePoint. A tracker saved over each month on a local drive keeps only its latest state, so earlier months' matching decisions are gone.

In the example, the June return commission of $3,825 against the February payment of $5,400 is the weak link. It reconnects only through the policy number on both statement lines, read in Epic. That is common, and fine to say in an introduction. What the same trail looks like with each system read on its own is in [what an Epic-only export leaves out](/guides/brokerage-statement-to-reconciliation-missing-context); the pass, partial or fail version is the [completeness checklist](/resources/brokerage-statement-to-reconciliation-completeness-checklist).

## Who can confirm the keys and who can authorize

The accounting manager can say which keys exist and since when. The CEO, usually the agency principal in an owner-run agency, can authorize a licensing discussion; the CFO, or the platform CFO in a private-equity-backed group, often sponsors it. Commission records reveal carrier relationships and client premiums, so the decision sits at that level.

Before introducing, confirm 50+ full-time employees at peak (contractors excluded), 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.

Unknown until SourceX reviews it: what carrier agreements permit, how client details would be de-identified, which export fields exist and any offer. Partners never ask for or handle statements, workbooks or ledger exports. This page names Applied Epic only because its documentation is public; it does not imply a SourceX connector. Related: [Applied Epic agency histories](/systems/applied-epic-data-export), [general ledger reconciliation records](/resources/mcp/mcp-general-ledger-reconciliation), [who owns agency management system data](/systems/agency-management-system-data-ownership) and the [systems hub](/systems).

## 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 an agency can say which carriers print policy numbers and whether its statements were associated with journal entries, [register as a partner](/register), check it against [who qualifies](/who-qualifies), and introduce its principal under the [program terms](/terms).

## Sources

- https://help.appliedsystems.com/Help/Epic/2023.2en-US/General_Ledger/Reconciliations/Recs_Associate_GL_Item.htm
- https://www.appliedsystems.com/DOC_CENTRAL/TR-TRAINING/RECONCILINGOFAGENCYORDIRECTBILLITEMS.HTM
- https://support.microsoft.com/en-us/office/collab-files/view-previous-versions-of-office-files
- https://refer.sourcex.si/terms
