Reconcile vendor statements against your AP records
In US accounts payable workflows, “vendor statement” usually means the same supplier-issued account summary called a “supplier statement” elsewhere. SupplierRecon compares that statement with an AP ledger export and keeps uncertain results for human review.
Vendor and supplier are workflow terms, not different features
The product name uses supplier terminology, while this page uses vendor terminology for US search and AP teams. Both routes describe the same controlled task: compare one vendor's statement with authorized AP data for a confirmed supplier and accounting period.
Inputs and workflow boundary
- Input one vendor statement and one AP ledger or open-item export in CSV or XLSX.
- Select the worksheet and header row, then map reference, amount or debit/credit, date, currency, vendor, type and description fields.
- Confirm whether the AP export contains one vendor or multiple vendors. Multi-vendor runs require an AP vendor mapping and a confirmed filter value.
- SupplierRecon does not connect to an ERP, retrieve invoices, read PDF statements or apply OCR.
Deterministic results and review boundaries
| Result | Product treatment | Finance responsibility |
|---|---|---|
| Exact match | A unique one-to-one reference, amount and currency key passes the supplier and date safeguards. | Continue normal validity, approval, cut-off and payment controls. |
| Needs review | Amount tolerance, grouped sums, similar references or competing candidates remain suggestions. | Inspect source rows and choose a supported treatment or leave unmatched. |
| Unmatched | No eligible candidate exists under the confirmed rules. | Investigate missing invoices, credits, timing, duplicates, scope and postings. |
Reviewable output for the AP file
The downloaded Excel workpaper separates exact and reviewed matches, unmatched statement and AP rows, data warnings and ten deterministic exception categories. It also retains reconciled source sheets, control totals by source and currency, rule parameters and a run manifest with source hashes. These records support review; they are not an approval record, audit opinion or tamper-proof attestation.