Delivery receiving discrepancy log for restaurants: reconcile before approval
A restaurant receiving record for comparing purchase orders with delivered quantity, condition, site-defined checks, photos, rejection decisions, and invoice adjustments.
A receiving discrepancy is a difference between the expected delivery and the physical or documented receipt. The difference may involve quantity, unit, condition, timing, product identity, an unrequested substitute, or evidence that has not yet been reviewed. National Restaurant Association guidance on electronic filing highlights receiving records that verify quantities, condition, time, and photo evidence. Restaurant receiving procedures add the need to compare the order and delivery, make site-defined checks, document rejection, and request an invoice adjustment when the received result differs. The record is most useful when created at the dock or receiving point, before memory and paperwork diverge.
Build the receiving record around the line
Begin with the purchase order and delivery document, then create one receiving line for each expected product. Preserve the ordered quantity and unit, the delivered quantity and unit, and the accepted quantity and unit as separate values. If your site converts cases into eaches, document the conversion rather than replacing the original unit. Add receipt date and time, location, person or role, condition observation, site-defined quality or temperature check, evidence reference, and decision. The purpose is not to create a long form for its own sake. It is to let another operator understand why a line was accepted, rejected, held, or sent for correction.
- Use one stable order and delivery reference across the receiving record, photo folder, invoice, and supplier message.
- Distinguish missing quantity from damaged quantity and wrong item; each can require a different follow-up.
- Record the physical unit first. Put a verified conversion in a separate field when a pack, case, tray, or each relationship matters.
- Describe condition using observable facts such as crushed packaging, leakage, seal issue, or visible damage rather than an unsupported conclusion.
- Give an evidence reference to every photograph or attachment and avoid attaching unrelated images to a discrepancy line.
Connect rejection to invoice and supplier follow-up
The receiving decision is not complete when a box is placed aside. A rejected or short line needs a communication path and a commercial follow-up. Link the discrepancy to the invoice review, credit memo, replacement request, or other action that your operation uses. Keep quantities separate: ordered, delivered, accepted, rejected, and credited are not interchangeable. If a supplier disputes the observation, append the response and preserve the original receiving record. A recurring issue may belong in a supplier scorecard or a sourcing review, but this log should remain the evidence for the specific delivery rather than becoming a general reputation label.
Clearly labeled illustrative example: ordered, received, accepted
A restaurant enters an example to reconcile one delivery line. Every quantity, price, reference, and decision below is illustrative and entered by the operator, not a supplier fact, customer result, demand signal, legal conclusion, or performance guarantee. Replace them with your purchase order, delivery document, site-defined checks, photographs, and current jurisdiction-specific requirements.
| Ordered | 6 cases × 12 units = 72 units expected | Illustrative purchase-order quantity |
|---|---|---|
| Physically received | 5 cases × 12 units = 60 units delivered | Illustrative count recorded at the site |
| Condition decision | 4 damaged units rejected; 56 units accepted | Illustrative observable condition decision; record actual evidence |
| Reconciliation | 56 accepted + 4 rejected + 12 not delivered = 72 ordered units | Illustrative quantity bridge |
| Commercial follow-up | Invoice line for 56 accepted units reviewed; 16 units linked to a site-defined correction request | Illustrative workflow status, not a promise of supplier credit |
The line closes numerically, but the 16-unit correction still needs a real supplier response or internal disposition. Site and operator inputs replace every illustrative figure. Do not mark the exception closed merely because the arithmetic balances.
A repeatable delivery discrepancy process
- 1Prepare the reference. Open the purchase order and delivery document, identify supplier and receiving site, and load the expected product lines with their original units.
- 2Inspect and record. Count the delivery, note receipt time and condition, perform the checks defined by your site, and attach line-specific photographs or other evidence.
- 3Decide each line. Mark quantities as accepted, rejected, held, missing, over, wrong, or pending according to the operation's documented procedure. Record who decided and why.
- 4Reconcile documents. Link the receiving record to the invoice, credit memo, replacement request, or supplier message. Keep ordered, delivered, accepted, rejected, and adjusted values distinct.
- 5Close and learn. Confirm the commercial or operational follow-up, record any supplier response, and route repeated patterns to a scorecard or sourcing review without rewriting the specific delivery evidence.
FAQ
- What should a restaurant record when a delivery is short?
- Record the expected quantity and unit, the quantity actually delivered, the accepted quantity, receipt time and location, the delivery reference, the person receiving, and any site-defined evidence. Link the short line to the invoice adjustment, credit request, replacement, or other follow-up your operation uses.
- Should damaged and missing items use the same discrepancy reason?
- Usually they are worth keeping distinct because the observable facts and follow-up can differ. Use the reason vocabulary defined by your site, describe what was seen, and avoid asserting a cause that the receiving record cannot establish.
- Does receiving guidance prescribe one universal temperature limit?
- No single universal value should be copied into this workflow. Record the checks and acceptance rules defined for your site and product, and verify current, jurisdiction-specific requirements with the relevant authority. This guide intentionally does not provide a universal temperature limit.
- Is a receiving discrepancy log the same as credit-memo tracking?
- No. The receiving log records what arrived and the site's decision. Credit-memo tracking records the financial follow-up. Link them with order, delivery, invoice, or case references, but keep status and ownership clear for both records.
- Does one delivery problem mean we should switch suppliers?
- No automatic sourcing decision follows. Resolve and document the specific exception first, then review the pattern and the supplier relationship. Depending on your evidence, you may keep, consolidate, renegotiate, substitute, or switch deliberately.
Keep reading
- Credit memo tracking: recover the money owed for returns and shortages
Track supplier credits for returns, shortages, substitutions, and pricing errors—and quantify uncredited-return loss.
- A 15-minute invoice review that catches what audits miss
Five checks, in order, that surface pricing errors before they reach your books.
- Score your suppliers on more than price
A simple scorecard for restaurant suppliers: fill rate, substitutions, accuracy and price stability alongside cost.
Browse by category
Want to review your purchasing?
Submit the details and we will confirm which invoices are useful.
Review 3 invoices free