Carrier statements we already know how to read

Every commission platform that publishes a supported-carrier list ends up maintaining a lie. Carriers change formats, acquire each other, add bonus files, and send different layouts to different distribution channels. A list that was accurate in January describes something else by June.

LyncCIS takes the opposite approach. The unit of support is not the carrier's brand, it is the statement layout — and layouts are mapped, saved and reused. If a carrier can export a statement you can open, LyncCIS can be taught to read it.

1. 1

   Upload the file as sent

   CSV or XLSX on any plan, PDF conversion on paid plans. No pre-cleaning, no re-ordering columns, no deleting header rows.

2. 2

   Confirm the key columns

   The mapping wizard shows the file's own headers next to the fields LyncCIS needs: writing number, policy identifier, insured, premium, commission amount, effective date and paid date.

3. 3

   Review the sample rows

   Before anything posts, you see how the first rows will be interpreted — which agent they will match, which policy they will attach to, and what will be classified as new versus renewal.

4. 4

   Save the template to the carrier

   Once confirmed, the mapping belongs to that carrier. Next cycle you upload and it processes without touching the wizard again.

5. 5

   Resolve exceptions once

   Unrecognised writing codes and unmatched policies queue for review. Attach them once and they resolve automatically on future statements.

Carriers rename columns, change casing, and add or remove spacing between cycles — usually without telling anyone. Alias matching recognises common variants automatically, so "Comm Amt", "COMMISSION AMOUNT" and "Commission_Amount" resolve to the same field.

When something genuinely new appears, the import pauses on that field rather than guessing. You confirm the mapping once and the alias is remembered.

For a clean map, a statement needs to identify five things. Most carrier files carry all of them:

• Who wrote it — a writing number or agent code the carrier assigns.
• What it is — a policy number, or enough identifying detail to match one.
• What it paid — the commission amount, and ideally the premium it was calculated from.
• When — effective and paid dates, used for new versus renewal classification.
• Direction — whether the line is a payment or a reversal, so chargebacks track back to the original.

If a statement is missing one of these, the mapping wizard will tell you at import rather than producing a report that quietly under-counts.

Production bonuses, override true-ups and annual reconciliation files usually arrive in a different layout than the monthly statement. Each gets its own saved template under the same carrier, so a quarterly bonus file does not force you to remap the format you use every month.

Ask us. Send a sample statement through the contact page and our team will confirm the mapping with you — usually within one business day. Once mapped, it behaves like every other carrier in your account, feeding straight into reconciliation and hierarchy distribution.