For AP controllers reviewing invoices before payment
Know which invoices match and which ones stay on hold.
Supply the invoice, purchase order, receipt, and the tolerances your team uses. MatchHold links the documents, compares the line facts, and returns a reviewable result without approving a payment.
Sign in and you go straight back to the MatchHold conversation. Work happens in chat. This page never asks for your card details or email address.
CLOSED VOCABULARY
- matched
- hold
- duplicate
10 DEMO-CHAIR · USD 12.00
10 units invoiced · USD 12.00
HOLD8 units received · short by 2
Prices matched. Quantity did not. No payment was approved.
FIRST REAL RESULT
An exceptions-only three-way match report that holds every invoice it cannot prove clean
matched · hold · duplicate — never a paymentCONTROLLED HOLD / PO-001
INV-001 held because GR-001 was two units short
Project MH-EVIDENCE-SMALL-2026-08-30: PO PO-001 for 10 DEMO-CHAIR units at USD 12.00, receipt GR-001 for 8 units, invoice INV-001 for 10 units at USD 12.00, quantity and price tolerances 0, with an explicit instruction not to approve or schedule payment.
- Invoice
- INV-001 · qty 10
- Purchase order
- PO-001 · qty 10 · USD 12.00
- Receipt
- GR-001 · qty 8
- Returned status
- hold · quantity_mismatch · shortfall 2
One status=hold JSON record with exception kind=quantity_mismatch: invoice quantity 10 exceeded received quantity 8 by 2 units. Prices matched. No payment was approved or scheduled. Public proof: matchhold-three-way-hold.png, 201533 bytes.
HOW THE THREE DOCUMENTS ARE HELD TOGETHER
Link by the identifiers you supplied. Stop when a required document is missing.
- 01
You provide the invoice batch, its purchase orders and receipts, and the tolerances that define an acceptable match.
- 02
MatchHold links records by the supplied purchase-order and line identifiers instead of guessing missing relationships.
- 03
It compares quantities, prices, currencies, receipt status, and duplicate keys in document order.
- 04
You receive the match record and an exceptions-only review queue; payment remains outside the workflow.
A result for every invoice marked as matched, held, or duplicate
An exceptions list that names each mismatched field and the documents compared
Hold reasons for missing receipts, unresolved links, and facts outside tolerance
A duplicate record that keeps the original and repeated invoice visible
WHAT YOU PUT UNDER THE CLAMP
The three documents stay named. Tolerances stay yours.
Accounts-payable controllers and finance teams that already receive invoices, purchase orders, and goods receipts but spend hours reconnecting them before a payment review.
An invoice can look correct while its quantity, unit price, currency, receipt, or purchase-order reference disagrees with the supporting records. Manual comparison makes those exceptions easy to miss and hard to explain later.
- 01
Invoice files with invoice numbers, purchase-order references, currencies, and line items
- 02
Purchase orders with supplier, SKU, quantity, and price details
- 03
Goods receipts or service acceptance records for the same purchases
- 04
The quantity, price, and currency tolerances your team wants applied
THE PAYMENT LINE
A clean match is still not a payment approval.
- Approving, scheduling, or recording supplier payments
- Filling in a missing receipt or purchase order from an assumption
- Batches without stable document or line identifiers that can support a defensible comparison
- Replacing the controller who decides whether a held invoice can proceed
STARTER
Open a matching workspace.
$19.00 is stated here before you register; card payment runs through Stripe Checkout inside the signed-in workspace.
$19.00 per month
Continue to workspace billingBEFORE YOU MATCH
Questions
What documents does MatchHold need?
Provide the invoice, its purchase order, and the related goods receipt or service acceptance record. Include the tolerance and currency rules your team uses for review.
What happens when a receipt is missing?
The invoice stays on hold with a missing-receipt reason. MatchHold does not infer that goods or services were received.
Does a matched result approve payment?
No. A matched result records that the supplied documents agree within the supplied tolerances. Payment approval and execution stay with your finance process.
How are duplicate invoices handled?
Repeated invoice keys are reported as duplicates and do not create a second clean match. The result keeps the duplicate reason visible for review.
What will the reviewer receive?
The reviewer receives a per-invoice status, a field-level exceptions list, named hold reasons, and the source document links used for each comparison.