Missing invoices
Statement items with no AP counterpart stay visible on the supplier side.
Vendor reconciliation
AP teams, accountants, bookkeepers, and firms can upload a vendor statement and an internal AP export, then work the exceptions instead of highlighting two printouts.
Try the free vendor statement matcher
Suppliers send statements that do not line up with payables. Missing invoices, unapplied credits, and payment timing differences hide in row-by-row checks. The same comparison repeats across many vendors each period.
Sample preview
Sample vendor result. Fictional counterparties.
| Reference | Counterparty | Amount | Status | Note |
|---|---|---|---|---|
| INV-4412 | Harbor Supplies | $2,180.00 | Missing invoice | On statement, not in AP |
| CR-118 | Harbor Supplies | $240.00 | Missing credit | Credit memo not in ledger |
| INV-4388 | Harbor Supplies | $960.00 | Duplicate | Posted twice in AP |
| INV-4401 | Harbor Supplies | $1,400.00 | Payment difference | Paid $1,360.00 |
How it works
Step 1
Vendor statement plus ledger or AP export.
Step 2
Invoice number, date, amount, credit flag, and vendor identifier.
Step 3
Match invoices and credits, then surface what only one side shows.
Step 4
Missing invoices, missing credits, duplicates, and payment differences.
Step 5
Comment, assign, and export a vendor-ready exception list.
Step 6
Reuse the recipe when the next statement arrives, or run several vendors in bulk.
What this workflow is designed to do with uploaded files.
Statement items with no AP counterpart stay visible on the supplier side.
Credits the supplier issued but the ledger missed are listed separately from invoices.
Repeated invoice numbers or amounts are flagged instead of being counted twice.
Paid amounts that do not equal the open item remain as exceptions.
When statement close and AP close disagree, the difference is part of the result.
Rows that cannot be paired stay in a review queue, not a hidden remainder.
Upload Harbor Supplies' March statement and the AP aging export. The run shows INV-4412 on the statement only, a duplicate INV-4388, and a $40 payment difference on INV-4401. The same recipe can run for the next vendor.
Vendor volume is the constraint. Configuring one statement format and reusing it across vendors is how the work stays repeatable instead of becoming a new spreadsheet for every supplier.
Continue with the workflows that usually sit next to this one.
Exact, tolerance, fuzzy, partial, 1:N, N:1, and N:N matching with visible rules.
Work the rows that did not match — status, comments, assignment, and history.
Save mappings, matching rules, and workflow setup. Configure once. Reuse next month.
Turn run results into Excel, PDF, and management packs a reviewer can open.
Yes. Save the mapping as a recipe and apply it to the next statement, or queue several vendors with bulk processing.
No. It checks the spreadsheet exports you already use. It does not post payables or issue payments.
Map the reference columns and use the matching options available for that run, including fuzzy or multi-column keys when enabled.
Upload a statement and an AP export. Review only the rows that did not match.