Retail three-way matching compares what a retailer agreed to buy, what a store or warehouse actually received, and what the supplier is billing. The three core records are the purchase order, the goods-receipt or receiving record, and the supplier invoice. A delivery note can support the receiving step, but it should not replace the retailer's own confirmation of what arrived.
Matching only the invoice total is not enough. A supplier may bill the correct total while using the wrong SKU, quantity, unit price, discount, freight charge, or store allocation. Line-level matching helps the retailer separate clean invoices from exceptions before money leaves the business.
The evidence behind a retail three-way match
| Record | What it establishes | Key fields |
|---|---|---|
| Purchase order or accepted order confirmation | What the retailer authorized | Vendor, SKU, description, quantity, price, discount, delivery location, terms |
| Delivery note | What the supplier says it dispatched | Delivery reference, item, quantity, date, destination |
| Goods-receipt or store receiving record | What the retailer actually accepted | Actual item and quantity, condition, receiver, location, exceptions |
| Supplier invoice | What the supplier is requesting in payment | Invoice number, item, quantity, unit price, charges, currency, amount, due date |
The retailer's receiving record is the operational truth about quantity and condition. If the delivery note and invoice both show ten units but the store counted nine, the two supplier documents may agree with each other while the payable is still wrong.
What to compare at line level
Supplier and reference numbers
Confirm the vendor identity, purchase-order number, delivery reference, invoice number, and receiving location. Similar supplier names or repeated invoice numbers can create duplicate records or attach an invoice to the wrong order.
SKU, model, size, and unit of measure
Retail products may differ by color, size, volume, pack, season, or barcode. Match the internal SKU, supplier item code, or complete product specification. A similar description is not enough when the item has a different cost or resale value.
Ordered, delivered, and accepted quantity
Show the three quantities separately. A split delivery should reduce the open quantity on the purchase order without marking the full order received. Damaged, rejected, or substituted items should remain visible as exceptions.
Unit price, discounts, freight, and other charges
Compare the invoice price with the authorized price and effective date. Check volume discounts, promotional allowances, freight, packaging, and other charges. A new supplier price should require the appropriate commercial approval rather than being accepted by the receiving store.
Store or cost-centre allocation
A centralized order may be delivered to several stores. Each goods receipt and invoice line needs the correct location or allocation rule so one store does not absorb another location's inventory cost.
Returns, credits, and corrections
Link every return, credit note, replacement, refund, or corrected invoice to the original order, receipt, and invoice. Do not overwrite the original record merely to make the numbers agree.
A practical retail invoice-matching workflow
1. Create a purchase reference before delivery
Use a unique order reference even when the purchase was placed by email or messaging. Record the authorized items, quantities, prices, destination, and terms. Ask the supplier to repeat the reference on delivery notes and invoices.
2. Record the store's actual receipt
The receiving employee should count the items and record the date, location, and condition. Short shipments, over-deliveries, wrong SKUs, substitutions, and damage should be documented immediately, with photos or comments where useful.
Signing a supplier delivery note without recording exceptions can make later investigation difficult. The store's own receiving record should show what was accepted, rejected, or still expected.
3. Keep split deliveries open
One purchase order may be fulfilled through several deliveries. Record each receipt separately and maintain the remaining quantity. If the supplier invoices the full order before all items arrive, the unmatched quantity should remain blocked or disputed according to the retailer's policy.
4. Compare the invoice by line
Match each invoice line to the authorized order and confirmed receipt. Clean lines can proceed to approval. Differences should enter an exception queue with a reason, owner, and next action rather than being hidden inside a manually adjusted total.
5. Resolve exceptions before payment release
Useful statuses include:
- waiting for store confirmation;
- waiting for the remaining delivery;
- waiting for a corrected invoice;
- waiting for a credit note;
- substitution accepted;
- price variance approved;
- ready for payment.
Every exception needs a responsible person and target date. Otherwise, invoices either remain blocked indefinitely or are paid simply to clear the backlog.
6. Retain the final decision trail
Keep the original order, receipt, invoice, exception, supplier response, adjustment, approval, and payment reference connected. The history should explain not only the final amount but why it differs from the original invoice.
Set tolerances without hiding meaningful differences
Retailers may allow small differences to pass automatically or through simplified review, but the tolerance should be approved and documented. It can be defined by amount, percentage, item category, vendor, or transaction type.
For example, a small rounding difference may be low risk, while a one-unit difference in a high-value product is material. New SKUs, changed bank details, unapproved freight, duplicate invoices, and unusual discounts should not pass merely because the total variance is below a general threshold.
A tolerance policy should state:
- which fields can vary;
- the amount or percentage allowed;
- who owns and reviews the rule;
- which vendors or product categories it covers;
- which exceptions always require manual approval;
- how often the rule is tested against actual errors.
Common retail discrepancies and next actions
| Discrepancy | Recommended action |
|---|---|
| Short or missing delivery | Record the accepted quantity; request fulfilment, correction, or credit |
| Over-delivery | Do not assume acceptance; return it or obtain purchase approval |
| Wrong SKU or specification | Isolate the item and confirm replacement, return, or approved substitution |
| Damaged goods | Record quantity and condition; track replacement, refund, or credit note |
| Higher invoice price | Check the approved price and effective date; route the variance for approval |
| Missing discount or unexpected freight | Compare the commercial terms and request an explanation or correction |
| Duplicate invoice | Compare vendor, number, amount, date, and purchase reference; block payment |
| Return awaiting credit | Keep the amount in an exception status until the formal adjustment arrives |
The objective is not to force every document to display the same number. It is to preserve the source values and document how the difference was resolved.
Divide responsibility across stores, purchasing, and finance
Store or warehouse teams confirm what arrived. Purchasing owns the authorized item, price, and supplier terms. Finance captures the invoice and controls payment release. A multi-store retailer should use the same vendor IDs, purchase references, SKU data, location names, and exception statuses across all three groups.
A daily or weekly exception review can focus on:
- deliveries with no receiving record;
- invoices with no purchase reference;
- open quantities on split deliveries;
- price or quantity variances waiting for a decision;
- returns waiting for a credit note or refund;
- matched invoices approaching their due date.
This exception-led approach is faster than rechecking every document at month-end.
Use InstantFlow to prepare supplier invoice data for focused review
InstantFlow can extract recognizable fields from uploaded supplier invoices and receipts, including supplier, date, amount, currency, and line details. It can suggest expense categories while keeping the source document available for review. This reduces the time finance spends retyping wholesale invoices before reconciliation can begin.
Teams can retain the payment method on confirmed expense records and ask Genie, InstantFlow's AI business agent, questions such as, “Which costs were recorded for this supplier?”, “Which store recorded the most purchases in this category?”, “Which supplier documents still need categorization?”, or “Which expenses have no payment method?” Genie surfaces the relevant expense data so staff can concentrate on comparing it with the receiving evidence and resolving exceptions.
InstantFlow accelerates invoice capture, categorization, search, and investigation; the retailer's authorized staff still confirm the goods received, commercial terms, credits, and payment decision. Start with one high-volume supplier and one receiving location, review the invoice lines and exception pattern, then expand the workflow after the references and responsibilities are consistent.
Frequently asked questions
Can a retailer perform three-way matching without a formal purchase order?
Yes, but the business still needs evidence of the authorized order, such as an accepted supplier quote, email, message, or replenishment record showing the item, quantity, price, and location. As volume grows, a consistent purchase reference makes matching and exception tracking more reliable.
How should a retailer match one purchase order delivered in several shipments?
Record each goods receipt separately and reduce the open quantity after every delivery. Link each invoice to the delivery or deliveries it covers. If the supplier invoices the full order early, keep the undelivered quantity unmatched until it arrives or is formally adjusted.
What tolerance should be used for retail invoice matching?
There is no universal tolerance. Define it by risk, product value, vendor, and discrepancy type. Small rounding differences may be acceptable, while an extra unit of a high-value SKU, an unapproved price change, or a duplicate invoice should require review regardless of percentage.
Can an invoice be paid while a return is waiting for a credit note?
Follow the retailer's approved policy, but the disputed amount should remain visible and controlled. Keep the return evidence and supplier confirmation connected, pay only the verified amount where appropriate, and close the exception when the credit note, correction, replacement, or refund arrives.
How can InstantFlow support retail three-way matching?
InstantFlow can extract supplier invoice fields and line details, suggest expense categories, retain payment methods, and let teams use Genie to find supplier, store, category, or incomplete expense records. Staff can reach the relevant invoice data faster, then compare it with the authorized order and actual receipt before approval.
Conclusion
Retail three-way matching should prove that the retailer authorized the purchase, received the goods, and was billed correctly. SKU, quantity, price, location, returns, credits, and exceptions must remain traceable at line level rather than disappearing inside an adjusted total.
Begin with one supplier and one store. Standardize the purchase reference, record receipt exceptions on the day of delivery, and use InstantFlow to capture and search the supplier invoice data. Related reading: retail accounts payable, restaurant invoice reconciliation, and InstantFlow’s retail industry page. Once clean lines move quickly and exceptions have clear owners, the retailer can expand the same control across more locations and vendors.
Michael Tang · Digital Content Manager
Focused on digital content, AI tools and enterprise technology trends, researching and distilling practical information that turns complex technology and AI applications into clear, accessible content for business owners and professionals.
