What one agency system cannot explain about a commission clawback: a policy read before and after

Short answer

Each system, read alone, tells a misleading story about the same policy. The agency management system shows the sale, the cancellation and both payment lines, but not how finance treated the clawback or whether the books ever agreed. The matching spreadsheet shows one month cleared and a later month with an orphan line and no reason. The general ledger shows revenue up in one month and down in another, blended with every other account. Only connected do they reveal a sale, a mid-term cancellation and money taken back four months later.

Visual briefFull-size diagram
A $3,825 clawback line sits above three blank fields; context rises into place from Applied Epic, the matching spreadsheet and the ledger, naming the April 30 cancellation, the orphan list and the $5,400 February posting, and the joined result shows $1,575 net kept.
Illustrative policy. The clawback looks like an error until the other systems fill in its history.

This before-and-after reading belongs to the guide on insurance brokerage statement to reconciliation records. The case is Illustrative: a fictional 160-person commercial agency, one direct bill liability policy, a $5,400 commission received in February, a cancellation effective April 30 and a $3,825 clawback four months after the original payment. All figures are invented.

Before: three single-system readings of one policy

Give a reviewer one export at a time and ask what happened.

Applied Epic alone. The policy, its expected commission, the February payment line, the cancellation and the clawback line all appear, each carrying the policy number. Epic tracks a status on each commission statement and can tie a statement to a receipt, disbursement or journal entry. If nobody made that tie, Epic is silent on how finance booked the clawback.

The spreadsheet alone. 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. A later sheet shows the clawback on an orphan list with no note. A reviewer would flag it as an error, or a carrier mistake still to chase.

The ledger alone. Commission revenue for that carrier rises in February and falls months later, each as one lump sum mixed with dozens of other policies. The cancellation is invisible, and so is the policy.

After: the connected reading

Line the three up by policy number and statement reference and one story appears:

  1. January: policy sold, $5,400 commission expected.
  2. February: the carrier pays $5,400; it is cleared, the statement is closed, and finance posts the month.
  3. April: the insured shuts its only site; cover ends April 30.
  4. Four months after payment: the carrier takes back $3,825 of unearned commission on a fresh statement. With the February item closed, the person doing the matching parks the clawback on the orphan list.
  5. Net: the agency kept $1,575 in the end, the figure the books should finally show.

Every step is accurate in its own place, and none explains itself. Connected, the sequence includes an exception and a human workaround, which is exactly what makes accounting history useful for training and evaluating systems that handle reconciliation exception work.

What is lost and where the context lives

Lost when one system is read aloneWhere the context livesWho usually holds it
That the clawback is the tail of FebruaryApplied Epic: both lines under one policy numberAccounting manager
Why cover ended, and whenApplied Epic: cancellation on the policyAccount manager
How the clawback was handledThe spreadsheet's orphan list and any noteWhoever does the matching
Whether the ledger ever agreedLedger journals, plus any tie made in EpicController or fractional CFO
What each month's matching looked like at the timeEarlier saved editions of the spreadsheetAccounting manager
Net commission on the policyOnly the joined historyNobody, until joined

Illustrative. Rows describe the example, not a tested export.

The fifth row is the easiest to lose without anyone noticing. Microsoft documents that version history in Microsoft 365 works only for files stored in OneDrive or SharePoint. A spreadsheet saved over each month on a local drive or plain file server survives only as its last state unless a backup kept older copies, so February's matched decision may no longer exist as it stood in February.

When the joined history is most at risk

The connection between the three systems is rarely stored anywhere; it lives in people's habits and in the spreadsheet. It is most likely to be lost at three moments:

  • A roll-up. When a private-equity platform folds acquired agencies into one ledger, old spreadsheets and journal references are often left behind; see insurance agency roll-ups.
  • An ERP replacement. If history is migrated as opening balances, the journal numbers that once bridged Epic and the ledger disappear; the ERP replacement handoff checklist covers what to keep.
  • The person doing the matching leaving. The orphan list and its unwritten rules go with them.

If the agency mentions any of these, note the year and what was kept. The keys that would join the systems are mapped in the record chain for this workflow.

What a partner asks, and who decides

Three questions to the accounting manager, none needing a record:

  1. When a return commission arrives after the original month is closed, where does it go, and is a note kept?
  2. Where do last year's monthly spreadsheets live, and can you open an earlier saved edition?
  3. Were statements associated with journal entries in Epic, or only matched in Excel?

The CEO can authorize a licensing discussion, and in an owner-run agency that is usually the principal; the CFO, or the platform CFO in a backed group, may sponsor the introduction. The accounting manager can describe the records but cannot authorize licensing them. 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 allow, whether client details can be de-identified to a buyer's standard, which years matter and any offer. Partners never ask for or handle statements, trackers or ledger exports, and this page does not imply a SourceX connector to Applied Epic or any ERP. More: Applied Epic agency histories and the systems hub.

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 trace a late return commission back to its original payment and still holds its earlier spreadsheets, register as a partner, check it against who qualifies, and read the program terms before introducing its principal.

  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

Why does the connected history matter more than any one export?

Because the decision is spread across systems. The cancellation is in Epic, the matching workaround is in the spreadsheet and the money is in the ERP. Only together do they show what happened and why the books are right.

Does the partner need to know the amounts?

No. The figures on this page are fictional. A partner notes whether late return commissions can be traced back to the original payment, not what they were.

Sources

  1. help.appliedsystems.com/Help/Epic/2023.2en-US/General_Ledger/Reconci…
  2. support.microsoft.com/en-us/office/collab-files/view-previous-vers…
  3. 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