Know what you were paid — and what you weren't

A growing agency does not have one commission problem, it has four at once. Statements arrive in different formats from every carrier. The data has to be matched to policies you already know about. Overrides have to be distributed down a hierarchy that changes month to month. And someone has to notice when a policy that should have paid simply did not.

Spreadsheets can hold two of those four. They cannot hold all four at once, and they cannot tell you what is missing, because a spreadsheet only knows about the rows someone typed into it.

1. 1

   Upload the statement

   Drop the carrier's CSV or XLSX file — or a PDF on paid plans — into the import screen. Nothing has to be reformatted first.

2. 2

   Saved mapping is applied

   LyncCIS reads the file using the column template saved for that carrier: writing number, policy identifier, premium, commission amount, effective and paid dates.

3. 3

   Lines are matched

   Each line is matched to a policy in your registry and to the writing agent behind it, using the carrier's own writing code rather than a manual name lookup.

4. 4

   Commission posts and distributes

   The payment is classified as new business or renewal, splits are applied, and hierarchy overrides are calculated at each upline level using that carrier's rates.

5. 5

   Exceptions are queued, not hidden

   Anything that cannot be matched with confidence lands in a review queue with the original line intact so you can resolve it and re-run.

Classification is not cosmetic — it determines what an agent is owed and what an upline earns. LyncCIS separates new business from renewal at the line level so your production reporting reflects what actually happened, and so renewal-only override arrangements pay correctly.

Chargebacks are tracked against the original payment they reverse rather than posted as an unrelated negative, which means an agent's net position, the downline overrides paid on that business, and your own exposure all move together. Split business is handled with explicit percentages against the correct producers, so a shared case does not need a side spreadsheet.

The reconciliation dashboard is built around the three patterns that hide most missing money:

• Active policies with no commissions. The policy is in force in your registry, but no carrier statement line has ever paid against it.
• Orphaned commissions. A carrier paid you for something your registry does not know about — often business written under a writing code you have not mapped yet.
• $0 payouts. The line exists, the policy exists, and the amount is zero. Sometimes correct, frequently not.

Each of these is actionable the day the statement lands, which is the difference between a phone call to the carrier and a write-off.

Five branded report templates — Classic, Modern, Detailed, Summary and Corporate — export to PDF and CSV. Reporting is role aware, so column privacy is enforced by the report engine itself: a producer's export cannot contain compensation data outside their permitted scope, even if they build the report themselves.

That matters more than it sounds. Agencies that hand agents a spreadsheet either over-share or spend hours redacting. Neither builds confidence. A statement an agent can pull themselves, that always shows the same numbers as yours, ends the argument before it starts.

Agencies and FMOs that receive statements from more than one carrier and pay more than one producer. If you write everything yourself under a single carrier code, a spreadsheet is genuinely fine. The moment you have downline agents, per-carrier override rates, or more than a handful of statements a month, manual reconciliation stops scaling and starts costing money you never see.

Override structures are covered under agent & upline management. For how LyncCIS reads a specific carrier's format, see carrier support, and the full capability list is on the features page.