Hong Kong Restaurant Three-Way Match: PO, Delivery Note, Invoice

A Hong Kong restaurant three-way match compares the purchase order, kitchen-signed delivery note, and supplier invoice before payment, so AP can catch short deliveries, price variances, substitutions, and missing credits while the evidence is still fresh. The stakes are not theoretical: the Census and Statistics Department put restaurant sector purchases at HK$8.8 billion in Q2 2025, up 2.7% on the same quarter the year before.

In HK F&B, the match usually means comparing the purchase order (採購單), delivery note (送貨單) or goods received note signed at the kitchen, and supplier invoice (供應商發票). Any one document is only one side of the story. All three together show what was ordered, what arrived, what the kitchen accepted, and what the supplier wants paid.

The workflow has to fit Hong Kong's mixed document environment: formal PDFs from major foodservice suppliers, WhatsApp orders to produce reps, Chinese-script delivery notes at the kitchen door, bilingual invoices at head office, and handwritten wet-market documents. This English guide is for procurement, AP, and finance staff who own that control at head office; staff who work primarily in Chinese can use the Cantonese-language restaurant procurement reconciliation guide.

The Hong Kong F&B procurement document chain

The chain starts with the purchase order. In HK F&B that runs across a wide spectrum and pretending otherwise leads to a workflow that doesn't survive contact with the kitchen. A formal PDF PO sent by email to the supplier's order desk is typical for international foodservice suppliers — Angliss, DCH, Foodgears, Wismettac, the larger HK-headquartered distributors — where the supplier's order team is set up to acknowledge and process structured POs. A WhatsApp message from the chef or outlet manager to the sales rep ("send me 5 boxes of Australian beef tenderloin Wednesday morning, plus the usual produce") is the daily reality for most produce, dairy, bakery, and fresh-protein orders, especially at single-outlet operations and small chains. A phone call to the sales rep with no written confirmation back still happens at the wet-market end of the supplier base. A clean PO carries the supplier name and account, the requested delivery date and outlet, the item code, the item description, the quantity in the unit of measure (UoM, 計量單位) the supplier prices in, the agreed unit price and line total, and the staff member raising the order. Most HK F&B POs in the wild carry some subset of those fields and skip the rest.

The supplier delivers, and the driver leaves a delivery note (送貨單) at the outlet door. Receiving staff or the kitchen manager checks the boxes against the delivery note, signs the kitchen copy, and the driver takes the head-office copy back. That is the sequence in theory. In service-time practice the kitchen manager is mid-prep, signs without counting the cases properly, and discovers the discrepancy later when the cold room inventory doesn't add up. The delivery note is often Chinese-script-signed at the kitchen door even when the head-office copy is bilingual or English-primary; some wet-market and small-supplier delivery notes are handwritten Chinese-only. The fields a delivery note carries — supplier name, delivery date, item code, item description, quantity actually delivered, UoM, kitchen signature — are the ground truth on what physically arrived, and the kitchen-door annotation when receiving spots a problem (count discrepancy noted in pen, damaged stock refused, substitution flagged) is what gives AP a fighting chance to dispute the invoice later. A delivery note signed cleanly is treated as receipt agreed; a delivery note annotated by the kitchen is the start of a credit conversation.

The supplier invoice (供應商發票) arrives later — usually weekly, sometimes fortnightly, occasionally monthly — and aggregates multiple deliveries across the period into a single document that head-office AP receives. Format depends on the supplier. International foodservice suppliers issue English-primary or bilingual invoices on structured templates with item codes and consistent layouts. HK-headquartered distributors usually issue bilingual. Local fresh-produce suppliers and wet-market vendors often issue Chinese-primary invoices, sometimes handwritten. The supplier invoice carries the supplier name and BR Number (BRN, 商業登記號碼), the invoice number, the invoice period or list of delivery dates covered, the line items with item code, item description, quantity invoiced, unit price, line total, and the period total with payment terms. The invoice is the document AP sees first, and without a matching discipline the invoice is also the document AP pays — taking the supplier's word for what was ordered and what was delivered.

That is where the chain hands off. AP at head office matches the supplier invoice against the corresponding POs and signed delivery notes for the period covered, and the work the rest of this article walks through is the work that happens in that match. The same set of supplier documents — the PO that authorised the order, the delivery note that recorded what arrived at the kitchen, and the invoice that asks for payment — is also what HK F&B operations are obliged to keep as part of FEHD food traceability records that ride on the same supplier documents. Running the matching discipline well means the food-safety record-keeping discipline gets done at the same time, on the same files.

Five divergence patterns — short delivery, over-delivery, price variance, substitution, packaging UoM mismatch

The three documents tell the truth together. When they diverge, the mismatch usually falls into one of five action categories:

Short delivery (短送). The PO ordered 5 boxes, the delivery note shows 4, and the invoice charges for 5. The supplier owes a credit, but AP can only prove it if the signed delivery note and invoice line are compared before payment.

Over-delivery. The PO ordered 5 boxes, the delivery note shows 6, and the invoice charges for 6. The outlet now holds stock it did not plan for, with higher waste risk on dairy, fish, and fresh protein. The match tells procurement whether to return, accept, or reallocate the surplus.

Price variance (加價). The PO went out at HK$120/kg and the invoice charges HK$135/kg. That may come from a lapsed price list, wet-market movement, FX, freight, or supplier error. Until someone compares line prices, the higher rate keeps repeating.

Substitution with price impact. The PO requested Angus tenderloin, the delivery note shows Wagyu, and the invoice charges Wagyu price. The kitchen may have accepted the substitution for service reasons, but finance still needs a decision: absorb, return, renegotiate, or claim a credit if the substitute was cheaper than billed.

Packaging UoM mismatch. The PO ordered 50 single-unit cases, the delivery note shows 25 double-unit cases, and the invoice prices by single-unit case. Product quantity may be correct, but the matching layer needs a unit-of-measure (計量單位) lookup so AP does not chase false exceptions or miss real kg-to-case differences.

A weekly supplier invoice often combines several patterns: short delivery on one line, price variance on three, a substitution on another, and clean matches on the rest. Classifying each exception gives AP a precise next action instead of a vague "invoice does not reconcile" note.

Cross-language matching — Cantonese at the dock, English at head office

The PO line that reads "Australian beef tenderloin" at head office is the same kitchen line that reads "澳洲牛柳" on the Chinese-script-signed delivery note and the same invoice line that reads "Australian beef tenderloin / 澳洲牛柳" on the bilingual supplier invoice that comes in a week later. Three documents, one item, three surface forms — and a matching layer that has to recognise them as one logical line before any quantity, UoM, or price comparison can run.

That cross-script alignment is the working environment most HK F&B chains operate in every week, not a translation footnote. International foodservice suppliers (Angliss, DCH, Foodgears, Wismettac) issue English-primary or bilingual invoices on structured templates. HK-headquartered distributors usually issue bilingual. Local fresh-produce suppliers and wet-market vendors often issue Chinese-primary invoices, and a meaningful share of those are handwritten Chinese-only on a carbon-copy book the driver fills in at the back of the truck. The PO is usually English at head office, because head office runs in English and the procurement system is set up that way. The kitchen-signed delivery note is usually Chinese-script at the kitchen door, because kitchen staff read and sign in Chinese — even when the head-office copy of the same delivery note is English-primary or bilingual. None of this is a problem to fix; it is the document environment to design the matching layer around.

What the matching layer has to do operationally is normalise the three item descriptions to a single canonical line, so the quantity, UoM, and price comparisons can run against a stable identity. Two routes do that work. Where supplier item codes (貨號) are reliable across the three documents, item-code matching does the heavy lifting and the description language barely matters — the codes are language-neutral, and the descriptions are decoration. Where the codes are not reliable, or do not exist, description-level fuzzy matching across English and Chinese is the only route that closes the loop. That is the harder route, and it is where AI extraction earns its place over rule-based parsing: AI extraction can read both scripts, recognise that "澳洲牛柳", "Australian beef tenderloin", and "Aust beef tenderloin (澳洲)" are the same kitchen line item, and align them on the same row of a structured dataset without a hand-built translation table.

The operational consequence for a chain is straightforward. Building an item master keyed by supplier item code where available, and by canonical description (with both English and Chinese forms) where not, is what makes the matching workflow runnable weekly rather than only at month-end. It is also the layer that makes onboarding new suppliers manageable — a new wet-market vendor with handwritten Chinese-only delivery notes can be added to the matching workflow as soon as their delivery notes are extracted into the same structured shape as everything else, with their items mapped onto the existing item master. The bilingual document handling is a layer of the same problem as bilingual invoice extraction generally; the toolchain that can extract bilingual Hong Kong invoices into structured Excel rows is the toolchain that can extract the matching delivery notes and POs into the same structured shape.

Three match modes — header-only, line-by-item-code, line-by-description

A chain choosing how to run the match is choosing how strict the matching layer is. The three modes below are the realistic options, and the choice is governed by the supplier mix more than by ambition. Most HK F&B operations end up running a layered combination rather than picking one.

Header-only match. The supplier's invoice total for the period equals the sum of PO totals or signed delivery note totals for the same period. Within a tolerance — usually 1–2% to absorb rounding and FX noise — the invoice passes; outside the tolerance it gets queued for review. The mode is fast and catches loud failures: a missing invoice, a duplicate invoice, or a delivery charged at a plainly wrong rate. Header-only matching is useful as triage, not as control. It catches gross errors but misses the line-level variances that matter most in F&B.

Line-by-item-code match. Supplier item code on the PO equals supplier item code on the delivery note equals supplier item code on the invoice. Tightest match, fastest to run programmatically, and mechanically clean when it works. The catch is supplier discipline. Many HK suppliers use inconsistent item codes between their internal systems and the documents they actually issue to customers — the warehouse system codes the case, the sales system codes the SKU, and the invoice prints whichever the operator's screen showed that morning. Item codes drift when products are reformulated, repackaged, or rebranded, with no notice to the customer. Smaller suppliers may not assign codes at all. The mode works as well as the worst-disciplined supplier in the mix, and a chain whose supplier base mixes one or two well-coded international foodservice suppliers with four or five locally-coded distributors and a handful of code-less wet-market vendors cannot rely on item-code matching alone. Where the codes are good, item-code matching is the right primary mode; where they aren't, it produces noisy false negatives that the AP team learns to ignore — at which point the matching report stops being trusted.

Line-by-description match. Fuzzy match item descriptions across the three documents against a canonical item master that holds both English and Chinese forms of each line. Looser than item-code matching by definition, but immune to supplier code drift, and the only mode that works on Chinese-only handwritten delivery notes paired with English-primary invoices. Description matching is the pragmatic mode for a HK F&B mixed supplier base, and it is the mode AI extraction unlocks at scale because a model that reads both scripts and normalises across surface variation can do in seconds what a hand-built rules engine would take a quarter to maintain. The trade-off is that fuzzy matching produces a confidence score rather than a binary match, and a low-confidence match has to drop into a review queue rather than auto-passing — but a chain that handles the review queue weekly recovers far more than the queue costs to run.

The practical answer for most HK F&B chains is a layered combination. Header-only runs as a fast triage at the gross-total level. Item-code matching runs against the suppliers whose codes are reliable. Description matching runs as the fallback that catches what the other two miss — and in a HK F&B mixed supplier base it ends up catching most of the line-level work, because most of the line-level errors live with the suppliers whose codes aren't tight. The mode mix should follow the supplier mix, and the mix is worth re-examining as the supplier base evolves.

---

The credit-note tracker — recovering credits and reconciling supplier statements

When the kitchen catches a short delivery, the driver often promises a credit on the next invoice. Sometimes the kitchen manager writes "short 1 case, driver to credit" on the delivery note. More often the promise is verbal — "我哋下次落single到" — and disappears once service starts. Without a tracker, the credit either never arrives or arrives as an undetailed adjustment that nobody ties back to the short delivery.

The matched-variance dataset is the natural input to that tracker. Each exception becomes a row: supplier, delivery date, invoice number, item, quantity or HKD value owed, evidence from the signed delivery note, driver or sales rep where known, and a status such as "open", "credit promised", "credit received", "written off", or "disputed". AP can run the open list weekly: chase at 14 days, escalate to procurement at 30, and write off at 60 with the reason recorded.

When the credit note (貸項通知單) arrives, AP should match it back to the originating delivery before applying it. That prevents the same credit being claimed twice and gives procurement a supplier-by-supplier record of who honours verbal promises, how long credits take, and how much leakage is being written off. The record lets procurement compare suppliers on actual credit behaviour instead of relying on memory.

Supplier-statement reconciliation is the month-end safety net on top of the per-delivery match. The supplier's monthly statement (月結單) may reveal invoices the chain never received, credit notes never recorded, paid invoices still showing open, or payment-application errors between the chain and supplier. A chain that already has a matched invoice and credit register can reconcile the statement as a structured cross-check instead of re-keying the month from PDFs. Teams that run the statement workflow primarily in Cantonese can use the Cantonese-language supplier statement reconciliation guide alongside this English control.

---

Tooling routes — Excel, restaurant procurement software, AI extraction of all three documents

A HK F&B operation has three realistic routes. The right choice depends on document volume, supplier discipline, and how quickly exceptions need to be disputed.

Manual reconciliation in Excel. An AP clerk keeps three tabs — POs, signed delivery notes, and supplier invoices — then sorts and matches by supplier, delivery date, item, quantity, and price. This is practical for an independent restaurant or a small chain with a short supplier list. For a Hong Kong cafe receiving one delivery a day from three or four suppliers, a weekly Excel match is often enough for the owner-operator to catch short deliveries and price changes. The ceiling appears when a five-outlet chain has hundreds of weekly line items and the work collapses back to header-only checks.

Restaurant-procurement software with built-in matching. Procurement platforms work best when suppliers sit inside the platform catalogue and orders, receiving, and invoices stay in that system. HK F&B chains rarely have that clean supplier base. Local distributors, wet-market vendors, and irregular suppliers still send PDFs, scans, printed invoices, or handwritten delivery notes, so the matching workflow often stalls at the document boundary.

AI extraction of all three documents into structured form. AI extraction is the document-handling route: convert POs, delivery notes, and supplier invoices into the same structured row format, then run the match in Excel, the accounting system, or a BI layer. The practical workflow every section above assumes is the ability to extract POs, delivery notes, and supplier invoices into structured spreadsheets across English, Chinese, and bilingual supplier documents, leaving the variance register and supplier-statement reconciliation to run against clean data rather than PDFs.

AI extraction does not fix supplier-side discipline. If a supplier issues handwritten Chinese delivery notes with no item codes, the extraction layer can read and structure them, but it cannot invent codes the supplier never used or force an order desk to acknowledge WhatsApp orders. Its value is making the chain's side rigorous: every document is structured, every variance is surfaced, and every dispute has the underlying records attached.

Once the invoice is validated, downstream handling depends on the operating model. Multi-outlet chains can code each validated invoice to the outlet that consumed it, hotel F&B teams can apply USALI department coding for supplier invoices, and every operator should retain the matched PO, delivery note, invoice, credit note, and variance trail for the IRD Section 51C seven-year record-keeping requirement.