Browser-local matcher
Match POs, invoices, and receipts without an AP platform
A useful matcher should explain every exception, retain source-row evidence, and refuse weak automatic matches.
Is your export ready?
| Question | Ready when… | If not |
|---|---|---|
| Can lines join exactly? | PO number and PO-line ID appear in all three files, or PO plus item/SKU resolves to one unique PO line. | Keep the line unresolved. Review a candidate manually. |
| Can vendor consistency be checked? | PO and invoice exports both include vendor. | Do not infer vendor identity from a similar name. |
| Are partials visible? | Every receipt and invoice line is present for the analysis period. | Expand the export range or document the cutoff assumption. |
| Can duplicate lines be traced? | Invoice number and original source row are retained. | Return to the source export before deleting anything. |
| Are line and header totals distinct? | Line total, subtotal, tax/charges/discounts, and whole-invoice total have separate columns. | Map only fields whose meaning is known; repeated header totals are consumed once per invoice. |
What MatchThree classifies
- Exact clean matches, including multiple receipts and multiple invoices.
- Invoice unit prices outside explicit absolute or percentage tolerances.
- Invoice quantities above ordered or recorded received quantities.
- Missing POs/receipts, vendor, currency, UOM, PO-line, and inactive-PO conflicts.
- Invoice line-extension, subtotal, and header-total inconsistencies.
- Exact repeated invoice lines and invoice documents—flagged, never removed.
The free result shows whole-invoice value ready to pay and whole-invoice value held or unresolved, separated by currency. The one-time AP Exception Pack adds the full decision register, arithmetic, evidence, coverage, and reviewer fields.
Use safe sample data first
See the full exception case
The instant demo uses the same synthetic records as the automated integration fixture.