How to Automate PO Invoice Matching for Restaurants

Written by: JJ Tan, Founder, Jelly | Last updated: 14 August 2026

Why automated PO–invoice matching matters for your restaurant

• Three-way matching reconciles purchase orders, goods-received notes and supplier invoices to prevent overpayments and protect gross profit.
• Manual reconciliation consumes 10–20 hours per week and quietly erodes margin through missed price hikes and quantity errors.
• Jelly automates the workflow, from digital PO creation and delivery logging to OCR invoice capture and tolerance-based matching.
• Configurable tolerances, exception handling and HMRC-compliant VAT retention deliver measurable results within 90 days, including a 2-percentage-point GP improvement.
• See how automated matching works for your operation and learn how Jelly can recover hours and margin for your restaurant.

The hidden cost of manual PO–invoice matching

Manual PO–invoice matching drains time and margin from multi-site restaurant operations. Every delivery generates three documents that someone must reconcile by hand. Across a busy kitchen, that process consumes 10–20 hours per week, pulling finance managers, head chefs and owners into spreadsheets instead of service and strategy.

The financial impact grows quietly in the background. Invoice discrepancies covering items billed but not received, unflagged price changes and quantity errors chip away at gross profit. For a site turning over £500,000 in food purchases annually, these issues can create significant uncaptured losses each year. Automation recovers many of those discrepancies and protects margin.

The timing of detection compounds these losses. Delayed reconciliation means price hikes go unnoticed for weeks. By the time a monthly accountant’s report surfaces the problem, the damage is done and supplier credit windows have usually closed.

What you need in place before switching on Jelly

Successful 3-way matching in Jelly starts with a few core building blocks. You establish the data foundations that make accurate matching possible, then connect them into a single workflow.

• An existing purchase order process, even a basic one, so PO numbers can be matched against delivery notes and invoices
• Admin access to your POS system (Square, EPOS Now, Lightspeed and Toast all integrate natively with Jelly)
• A Xero account for accounting integration and MTD-compliant VAT filing
• A Jelly subscription at £129 flat per site per month, with no per-user fees
• Roughly one week to go live and start seeing real-time margin data

Ready to see how this setup works in practice? Walk through the setup for your operation with a Jelly specialist.

Step 1 – Create a digital purchase order in Jelly

Every matched transaction starts with a digital PO. In Jelly, you build purchase orders by selecting ingredients already populated from previously scanned invoices. Descriptions, units of measure and SKUs stay consistent from day one.

For operators importing POs from an existing system, Jelly maps supplier product descriptions to your internal ingredient master during onboarding. This step keeps recipe costing, GP reporting and stock counts accurate by maintaining one record per real ingredient with a consistent name, correct unit of measure and every supplier linked to that single record, as outlined in this guide to item master data hygiene. A simple naming convention of product, descriptor and pack size, applied consistently, prevents the same ingredient appearing as multiple line items across supplier catalogues.

Troubleshooting: If a supplier description does not map automatically, Jelly flags the unmatched line for a one-time manual link. After you link it, all future invoices from that supplier resolve automatically.

Step 2 – Log goods-received quantities at delivery

Accurate goods-received notes keep matching reliable. When a delivery arrives, the receiving team logs actual quantities against the open PO inside Jelly, either on a tablet at the back door or via the mobile app. For ambient and packaged goods, this is a straightforward case count. For fresh produce and catch-weight items such as whole fish or butchered meat, Jelly records the actual weight delivered instead of the estimated order quantity.

This distinction feeds directly into the tolerance rules applied in Step 4. Quantity tolerances are configured differently for categories such as fresh seafood and ambient dry goods to reflect natural variation and avoid unnecessary exceptions.

Troubleshooting partial deliveries: Modern invoice matching best practice supports partial matching for split deliveries, so each delivery can match the same PO without confusion. In Jelly, a partial GRN is saved against the original PO and the outstanding quantity remains open until the remainder arrives or is cancelled.

Step 3 – Capture supplier invoices

Fast, accurate invoice capture keeps the workflow moving. Jelly captures supplier invoices through two routes:

• Dedicated email inbox: Suppliers send invoices directly to a unique Jelly address. OCR extraction pulls every line item, including quantity, SKU, unit price and tax code, within minutes of receipt.
• Smartphone photo: Kitchen staff photograph a paper invoice. Jelly processes the image and extracts line-item data, typically within 24 hours of upload.

Both routes remove manual data entry. The extracted data feeds straight into the matching engine described in Step 4 and, once approved, pushes to Xero via a one-click integration. This setup satisfies HMRC’s Making Tax Digital requirement for digital links between systems, which has applied to VAT-registered businesses above the threshold since 1 April 2021 and to all VAT-registered businesses since April 2022.

Step 4 – Run automated 3-way matching

With the PO, GRN and invoice in Jelly, the matching engine compares them line by line against configurable tolerance rules. The table below shows recommended starting thresholds for common restaurant spend categories, based on standard AP practice that combines percentage and absolute caps to stop small percentages hiding large overpayments.

Category	Price tolerance	Quantity tolerance	Restaurant example
Fresh fish / seafood (catch-weight)	±15–25%	allows for natural weight variation	Whole sea bass ordered at £8.50/kg, invoiced at £9.00/kg, within band and auto-posted
Fresh meat (catch-weight-aware)	±5–10%	allows for natural weight variation	Beef fillet PO at £28/kg, GRN weight 4.8 kg vs 5 kg ordered, within quantity band
Ambient / dry goods	±3–5% or ±£0.05/case	tight tolerance	Tinned tomatoes PO at £18.40/case, invoiced at £18.43, within absolute cap and auto-posted
Alcoholic beverages	±2–3%	0%	12-bottle case of house red, exact quantity match required before auto-posting

Invoices that fall within tolerance are auto-posted. Those that exceed the configured band move into an exception queue. If exception rates rise above 20–25%, tolerances are probably too tight and generating false positives. If exceptions are rare but payment errors still occur, tolerances may be too loose. Jelly’s settings can be adjusted per category at any time.

Step 5 – Handle exceptions

Clear exception categories keep decisions quick and consistent. Exceptions fall into four main types, each with a defined resolution path:

• Price variance: The invoice unit price exceeds the PO rate beyond the configured tolerance. Jelly’s Price Alert flags the specific line, supplier and percentage increase so the finance manager can approve the variance, request a credit note or update the PO rate for future orders.
• Quantity shortfall: GRN quantity is lower than the invoiced quantity. Jelly holds payment on the short-shipped lines and generates a credit-note request to the supplier.
• Duplicate invoice: Jelly’s duplicate detection checks invoice number and supplier against the full invoice history and flags any repeat before it reaches the payment queue.
• Missing GRN: An invoice arrives with no corresponding goods receipt. Jelly routes it to the head chef or receiving manager for confirmation before anyone can approve it.

Resolved exceptions push clean, approved data to Xero in a single click. Modern AP systems use configurable approval matrices to route unusual cases to the right decision-makers, with override capabilities for authorised users. Jelly follows the same principle and keeps chefs out of the finance workflow.

Step 6 – Maintain HMRC VAT compliance

Jelly keeps VAT records complete and accessible. Every invoice processed through Jelly is stored digitally with its full line-item breakdown, satisfying two core HMRC obligations:

• Six-year retention: VAT purchase invoices must be kept for at least six years. Jelly’s cloud storage retains every scanned invoice and its extracted data for the full statutory period.
• MTD digital links: HMRC accepts electronic VAT invoices when they contain the same mandatory information as paper invoices and demonstrate authenticity and integrity. Jelly’s Xero integration maintains a digital link between the captured invoice and the posted VAT transaction, with no manual re-keying.

Mixed-rate supplier invoices need extra care. For example, a delivery containing both zero-rated cold food and standard-rated hot-food products must apply the correct VAT rate at line level to avoid errors in VAT reclaim, as explained in this UK VAT and MTD guide. Jelly’s OCR extraction captures the VAT rate per line item and flags any invoice where the rate looks inconsistent with the product category.

Audit-ready export reports are available at any time, covering the full invoice register, VAT breakdown by period and exception log.

How Jelly turns matching data into real-time margin visibility

Automated 3-way matching creates clean data that Jelly turns into live margin insight. Once invoices are matched and posted, Jelly’s Price Alert feature surfaces every ingredient price movement, up or down, on the same day it appears on a supplier invoice. Stuart Noble, Head Chef at Cairn Lodge Hotel, cut food costs by 5% within a month using Jelly’s price visibility tools.

Jelly’s Flash Report combines live cost data from matched invoices with real-time sales data from your POS. Your POS connects via native API in under five minutes and feeds gross profit margin by day, week or period without manual calculation. Sushi Revolution used Jelly to set separate target gross profits on dine-in and delivery menus, accounting for 30% delivery commissions, and achieved actual gross profits 2–3% higher on average.

The Xero integration then pushes every approved, matched invoice with correct VAT coding in a single click. Bookkeeping time drops by around 90%, and the month-end data-entry backlog that delays financial reporting disappears.

Want to see live margin data within a week? See what your operation looks like inside Jelly and review the exact margin view you would get.

Success criteria and 90-day results

A well-configured 3-way matching workflow in Jelly delivers clear benchmarks within 90 days. These targets help you track whether the process is working as intended.

• Exception rate below 5% of total invoice lines processed
• The weekly admin time described earlier fully recovered across the finance and kitchen team
• A 2 percentage-point improvement in gross profit margin, consistent with results reported by Jelly customers including Amber restaurant in East London, which saves £3,000–£4,000 per month and has achieved a 68× return on investment
• Zero duplicate invoice payments and a documented credit-note recovery process for quantity shortfalls

Payback on purchase order automation software typically arrives within 6–12 months for UK SMEs, and at Jelly’s flat-rate pricing the ROI calculation stays straightforward.

Next steps – credit-note chasing, delivery menus and multi-site rollout

Once 3-way matching runs cleanly at a single site, three natural extensions increase the return further. Each one builds on the same accurate data and workflows.

• Credit-note chasing: Jelly’s exception log provides a ready-made record of every quantity shortfall and price variance. Finance managers use it as the basis for structured supplier conversations, with the data to support every claim.
• Delivery menu costings: Jelly’s Cookbook section allows operators to duplicate existing dishes and layer in delivery commission overheads, typically 25–30% for major platforms, to build a separate, profitable delivery menu with live GP tracking.
• Multi-site rollout: Each additional site connects at the same rate. The ingredient master, supplier mappings and tolerance rules configured at site one are replicated, so subsequent sites go live faster. Group-level spending reports aggregate across all locations, giving operations directors a consolidated view of supplier pricing and margin performance.

Frequently Asked Questions

How does Jelly handle a rate mismatch between a PO and an invoice?

When the unit price on a supplier invoice exceeds the rate on the original purchase order by more than the configured tolerance for that ingredient category, Jelly routes the invoice line to an exception queue instead of auto-posting it. The finance manager or owner receives an alert showing the PO rate, the invoiced rate and the percentage variance. From there, they can approve the variance and update the PO rate for future orders, reject the line and request a credit note from the supplier, or place the invoice on hold pending a supplier callback. The full audit trail of the decision stays attached to the invoice record for HMRC purposes. Jelly’s Price Alert feature also logs the price movement against the ingredient’s history so patterns of incremental supplier price creep become visible over time.

What invoice tolerance rules work best for UK restaurants?

Effective tolerance rules reflect the natural variability of each spend category rather than a single blanket percentage. For catch-weight fresh produce and seafood, a price tolerance of up to 15–25% is practical given market volatility, while quantity tolerance should allow for natural weight variation at delivery. Fresh meat usually operates on a tighter price band of ±5–10% with a similar quantity allowance. Ambient and dry goods warrant the tightest controls, typically ±3–5% on price or a fixed absolute cap such as ±£0.05 per case, whichever is lower, with a tight tolerance on quantity. Alcoholic beverages are often held to zero quantity tolerance, meaning the exact case count must match before the invoice auto-posts. Jelly allows these thresholds to be configured per ingredient category, per supplier or per individual SKU so operators can tighten controls on high-value lines without creating false positives across the full invoice register.

Does Jelly’s automated matching satisfy HMRC VAT record-keeping requirements?

Yes. Jelly stores every captured invoice digitally with its full line-item breakdown, including supplier VAT registration number, VAT rate per line, net amount, VAT amount and gross total, which covers all fields required for a valid full VAT invoice under HMRC rules. Records are retained in cloud storage for the full six-year statutory period. The Xero integration maintains a digital link between the captured invoice and the posted VAT transaction with no manual re-keying, satisfying the MTD digital-link requirement described earlier in Step 6. For mixed-rate deliveries, such as an invoice covering both zero-rated cold food and standard-rated items, Jelly’s OCR extraction captures the VAT rate at line level and flags any inconsistency for review before the invoice is approved and posted.

How long does it take to go live with Jelly’s 3-way matching workflow?

Most operators start generating value within the first week. The fastest route to live is directing suppliers to send invoices to the dedicated Jelly email address so price alerts and spending insights appear within 24 hours of the first invoice arriving. POS integration takes approximately five minutes and requires only admin access to the POS account. The ingredient master is populated automatically from scanned invoices, so there is no manual data-entry phase. Supplier description mapping, which links a supplier’s product name to your internal ingredient record, is completed during onboarding and needs a one-time review for any lines that do not resolve automatically. For multi-site operators, each additional site replicates the configuration of the first, which shortens subsequent go-live time.

Can Jelly handle partial deliveries in the 3-way matching process?

Yes. When a delivery is short-shipped, the receiving team logs the actual quantity received against the open PO in Jelly. The system creates a partial GRN and holds the outstanding quantity as open on the original PO. When the supplier invoices for the full ordered quantity, Jelly flags the discrepancy between the invoiced amount and the GRN quantity and routes it to the exception queue. The finance manager can then approve payment for the delivered portion only and generate a credit-note request for the shortfall. If the remainder arrives in a later delivery, it is logged against the same PO and matched against the outstanding balance. The full delivery and payment history stays attached to the original PO record, giving a clear audit trail for internal review and supplier disputes.

Conclusion

Manual reconciliation of purchase orders, goods-received notes and supplier invoices no longer needs to drain time and margin. The six-step playbook above, covering digital PO creation, GRN logging at delivery, invoice capture via email or photo, automated tolerance-aware matching, structured exception handling and HMRC-compliant VAT retention, removes the 10–20 hours of weekly admin and closes the 2–3% gross profit gap created by undetected price hikes and overpayments.

Jelly is built for UK restaurants, pubs and boutique hotels at the £500k+ revenue stage. At the flat monthly rate with a one-week go-live, the payback window stays short and the margin impact becomes visible within 90 days. Every invoice is matched, every price movement is flagged the same day and every approved transaction pushes clean data to Xero, with a full audit trail ready for HMRC at any point.

See how 3-way matching works for your operation this week and review the exact workflow with the Jelly team.