For EZLynx users
Commission reconciliation for agencies on EZLynx
The CSV statements you already import into EZLynx are the easy part. This page covers what else to bring, and where an independent check differs from an import.
Lapidar is not affiliated with, endorsed by or sponsored by EZLynx. EZLynx is a trademark of its owner, used here only to describe compatibility with exported files.
In short
- Lapidar has no EZLynx integration. It works from files: a book export, your commission schedule, and the statements your carriers sent.
- Statements: CSV, XLSX or PDF with selectable text. Book and schedule: CSV or XLSX.
- Statements about EZLynx below come from EZLynx’s own public pages, cited on our EZLynx comparison (checked 12 Oct 2026).
What EZLynx documents for statements
An EZLynx blog post, dated January 2016, describes importing whole commission statements as CSV, using EZLynx’s template or a custom field mapping per carrier that is reused each month, and matching imported line items to policies. It is the most specific EZLynx page on statement import we found, so current behavior may differ; ask EZLynx.
Which statements to bring
The CSV files you import into EZLynx can go to Lapidar unchanged. Lapidar works the same way on layout: you match a carrier’s columns once and it remembers them for that carrier. Statements that arrive only as PDFs, which the EZLynx post does not mention, can be uploaded directly if the PDF has selectable text; scanned PDFs can’t be read. XLSX works too, without converting to CSV.
Import vs check
An import matches the lines that are on the statement to policies. A check also starts from the other side: Lapidar takes every policy in your book that should have paid commission in the period and flags the ones with no statement line at all, and compares each paid amount with your schedule rate.
The book export from EZLynx
We did not find a public EZLynx page describing a policy list export, so we don’t name one. Use a listing with one row per policy saved as CSV or .xlsx.
Whatever report you use, Lapidar needs one row per policy, with columns for carrier (named the way you name it in your schedule), policy number, line of business, new or renewal and written premium; insured name, effective date and number of installments help if you have them. The first time, you tell Lapidar which column is which. Policy numbers that differ from the carrier’s only by dashes, spaces, a renewal suffix or leading zeros (after any prefix you list) are matched automatically. Files can be up to 20 MB.
Every supported format and limit is on the product page; the output is on the sample report (invented data). Weighing reconciliation options for EZLynx rather than files? See EZLynx: your options.
Frequently asked questions
Can I use the CSV I already import into EZLynx?
Yes. Lapidar reads statements as CSV, XLSX or a PDF with selectable text, in the carrier’s own layout, and remembers the column match per carrier.
Does Lapidar write findings back to EZLynx?
No. There is no EZLynx integration in either direction. You get a findings list and a printable report per carrier; corrections go into EZLynx by hand.
Is Lapidar affiliated with EZLynx?
No. Lapidar is independent and not affiliated with, endorsed by or sponsored by EZLynx. EZLynx is a trademark of its owner.