Restaurant three-way invoice matching: prove the line before payment

The three records answer different questions. The purchase order records what the restaurant authorized before receipt. The goods received note or equivalent records what the site says arrived and what it accepted. The invoice requests payment and may contain its own quantities, prices, tax details, references, and corrections. A total can agree while one line is wrong, so the comparison must preserve the line identity and unit basis. The GOV.UK Procure to pay part 4 guidance presents the PO-to-invoice comparison and the PO, GRN, invoice comparison as control options within a broader process. It also emphasizes accurate transaction recording, one recording of an invoice, and approval controls around overrides. Use those principles to design your own process rather than treating UK guidance as a rule for every jurisdiction.

Build a stable line-level comparison

Before opening an invoice, capture the original PO number and revision, supplier identity, receiving location, and the source references for the receipt. For each line, retain the product identifier or description, ordered quantity, ordered unit, accepted quantity, accepted unit, invoiced quantity, invoiced unit, agreed price basis, invoiced price basis, tax code or rate as entered, and extension. If a pack conversion is necessary, show the source unit and the operator-entered conversion separately. Do not silently turn a case into an each or a weight into a portion. A later reviewer needs to understand whether a difference is a real commercial variance, a receiving decision, or merely a unit mapping issue.

• Use a stable line reference so the PO, receiving record, invoice image, correspondence, and correction cannot be confused with a neighbouring line.
• Compare accepted quantity, not merely shipped or invoiced quantity. A rejected or held quantity needs its own status and evidence.
• Keep the supplier description and your internal product identity visible together when names, pack wording, or abbreviations differ.
• Separate unit price, quantity extension, tax amount, and total so a rounding or tax question does not conceal a product mismatch.
• If the receipt is missing, stop the three-way decision and route a receipt request; do not infer acceptance from an invoice alone.

Tolerances need a local owner and a reason

A tolerance is an instruction for handling a defined difference; it is not permission to ignore evidence. Your finance lead, accountant, or control owner should define which differences can be accepted, by product class or transaction type if appropriate, and which require escalation. Record the version of the tolerance, the operator applying it, the reason, and the approval when an override occurs. A small price variance may need a different path from an unreceived quantity, a wrong product, or a tax-code question. UK guidance discusses tolerance limits and approval controls for manual overrides, while the European Commission validator offers a technical context for checking invoice data. Neither source determines your restaurant’s permissions, tax period, or commercial agreement.

Clearly labeled illustrative example: one line, one decision

A repeatable three-way matching process

1. 1Lock the source records. Retrieve the approved PO revision, receiving or GRN record, invoice image or structured data, supplier identity, and receiving site before making a decision.
2. 2Align the line identity. Map each PO, receipt, and invoice line using product identity, description, pack, and unit. Show any verified conversion rather than replacing the source values.
3. 3Compare commercial fields. Review ordered, accepted, and invoiced quantity; unit; price basis; extension; discounts or adjustments; tax fields; and invoice references at line level.
4. 4Apply the local rule. Use the tolerance and approval matrix defined by your operation. Record the version, operator, reason, and approver for every accepted variance or override.
5. 5Assign and evidence exceptions. Route quantity, price, identity, tax, missing-receipt, duplicate, or document issues to a named owner with due date, supplier communication, and supporting evidence.
6. 6Close or hold deliberately. Approve only supported lines, hold unresolved amounts, link correction or credit records, preserve the audit trail, and close when the financial and operational follow-up is documented.