Which files can I upload?

PDF, Excel, and CSV carrier statements, including scanned PDFs read by OCR.

How does matching handle inconsistent bond numbers?

The matching process allows for prefix, suffix, and spelling differences in bond numbers and customer names, then places exceptions beside the AMS360 entry.

What happens to an item paid before the statement arrived?

EvenPenny separates already-paid items from the ready-to-remit list so the review can follow the prior payment.

BUILT AROUND AGENCY-BILL WORK

Carrier statement reconciliation for insurance agencies

Turn an agency-bill carrier statement into a verified remittance list. EvenPenny reads the statement, matches it to AMS360 transactions, and puts each exception beside the record that explains it.

How it works

EvenPenny reads the uploaded PDF, Excel, or CSV statement; scanned PDFs are read with OCR. The statement detail is ready for matching.
EvenPenny reads the uploaded PDF, Excel, or CSV statement; scanned PDFs are read with OCR. The statement detail is ready for matching.
EvenPenny parses and matches each line to AMS360 transactions on the same bond, allowing for prefix, suffix, and spelling differences in bond numbers and customer names. You see the paired records.
EvenPenny parses and matches each line to AMS360 transactions on the same bond, allowing for prefix, suffix, and spelling differences in bond numbers and customer names. You see the paired records.
EvenPenny sorts the results into ready to remit, needs review, and already paid. You see three lists whose totals foot to the carrier’s statement total.
EvenPenny sorts the results into ready to remit, needs review, and already paid. You see three lists whose totals foot to the carrier’s statement total.
EvenPenny shows the statement line and AMS360 entry side by side with a suggested reason: rate difference, prior payment, missing in AMS, or carrier error. You see the evidence behind each exception.
EvenPenny shows the statement line and AMS360 entry side by side with a suggested reason: rate difference, prior payment, missing in AMS, or carrier error. You see the evidence behind each exception.
EvenPenny generates the remittance from the verified list only, in the carrier’s format. You get a remittance you can copy into an email.
EvenPenny generates the remittance from the verified list only, in the carrier’s format. You get a remittance you can copy into an email.

Your agency decides the exceptions, approves the remittance, and sends the payment.

Follow the amounts

Sample data.
Bond	Statement net	AMS360 net	Result
A	$2,160	$2,160	Ready to remit
B	$1,080	$990	Needs review: rate difference
C	$720	—	Needs review: missing in AMS
D	$1,350	$1,350	Already paid

What your team gets

Statement totals tied to the three review lists.
A side-by-side record for each exception.
A remittance built from the verified list.

The statements you already receive

12 carrier statement formats. PDF, Excel, and CSV, including scanned PDFs read by OCR. New carrier formats are added during onboarding.

Start with the reports you already use

Runs on exports from Vertafore AMS360.

Running Applied Epic, HawkSoft, or EZLynx? Send us a sample export and we'll tell you what it takes.

Common questions

Which files can I upload?: PDF, Excel, and CSV carrier statements, including scanned PDFs read by OCR.
How does matching handle inconsistent bond numbers?: The matching process allows for prefix, suffix, and spelling differences in bond numbers and customer names, then places exceptions beside the AMS360 entry.
What happens to an item paid before the statement arrived?: EvenPenny separates already-paid items from the ready-to-remit list so the review can follow the prior payment.