Written by: JJ Tan, Founder, Jelly | Last updated: 22 June 2026
Key Takeaways
- Three-way matching reconciles purchase orders, goods received notes and supplier invoices before payment to protect margins in UK hospitality venues.
- Manual reconciliation consumes 10–20 hours monthly and risks significant overbilling that erodes gross profit targets.
- Jelly automates invoice capture, line-item digitisation, PO and GRN matching and exception routing within configured tolerance thresholds.
- Automated workflows push clean data to Xero and update live recipe costing, giving chefs real-time visibility of dish margins.
- Book a demo with Jelly to implement automated three-way matching in under a week and recover valuable admin time.
Why three-way matching protects gross profit in busy kitchens
UK restaurants, pubs and hotels turning over £500k or more handle a constant stream of supplier invoices. Each invoice carries line items for ingredients priced in different units, affected by seasonal changes and occasional supplier error. Checking every line manually against a delivery note and a purchase order consumes between 10 and 20 hours of admin time every month, time that owners, finance managers and executive chefs cannot afford to lose.
The financial exposure is significant. Automating three-way matching in hospitality AP processes catches billing errors before payment, preventing tens of thousands of pounds in annual overbilling for a typical venue. For a kitchen running on 65–70% gross profit targets, even a 1–2% food-cost overrun caused by unchecked price creep or duplicate invoices can wipe out a month of net profit.
Manual processes also create a lag. By the time a finance manager reconciles last week's deliveries, the kitchen has already used the ingredients, priced the dishes and served the covers. The margin damage is done before anyone notices. Automated three-way matching removes this lag by processing invoices in real time through a structured workflow.
The 4-step automated three-way matching workflow
- Invoice capture. Every supplier invoice arrives by email to a dedicated Jelly inbox or is photographed on delivery. No manual data entry is required at this stage.
- Line-item digitisation. Jelly scans every line, including quantity, SKU, unit price and tax, and converts it into structured data within 24 hours of receipt.
- Automatic PO and GRN match. Jelly compares the digitised invoice against the corresponding purchase order and goods received note. Lines that match within the configured tolerance are approved automatically. Lines that fall outside tolerance are flagged as exceptions and routed for review.
- Clean data push to Xero and live recipe costing. Matched invoices are pushed to Xero in one click, which removes manual bookkeeping. At the same time, updated ingredient prices feed directly into Jelly's live dish-costing engine, so every recipe reflects current costs the moment a new invoice is processed.
Setting tolerance thresholds for ingredient price variance
Three-way matching needs realistic tolerance thresholds to separate normal movement from genuine errors. Fresh produce prices fluctuate with seasonality, and partial deliveries are routine in commercial kitchens. A rigid zero-tolerance policy would generate exception queues that undermine the value of automation.
A practical starting point for UK venues is a ±2% tolerance on dry goods and ambient products, where prices are relatively stable. A ±5% tolerance suits fresh produce categories such as meat, fish and vegetables, where market pricing shifts weekly. Partial deliveries, where a supplier delivers eight cases against a ten-case PO, should trigger a quantity exception rather than a price exception, prompting the kitchen to confirm the shortfall on the GRN before the invoice is approved.
These tolerance bands should be reviewed quarterly to ensure they still fit your supplier relationships. If a supplier consistently invoices at the top of the tolerance band, that pattern reveals pricing pressure that gives you leverage during the next contract negotiation.
Handling discrepancies and routing exceptions
Automated three-way matching routes out-of-tolerance lines to the right person instead of blocking the entire invoice. The workflow keeps most invoices moving while focusing human attention on the few that need a decision.
Partial produce delivery. A fishmonger delivers four portions of sea bass against a six-portion PO. The GRN records four portions received. Jelly flags a quantity mismatch, holds payment on the two undelivered portions and notifies the head chef to confirm the shortfall. Once confirmed, a credit note request is generated automatically and the invoice is approved for the four delivered portions only.
Service invoice without a GRN. A maintenance contractor submits an invoice for a call-out with no corresponding goods received note because no physical goods changed hands. Jelly routes this to the owner or finance manager for manual approval, keeping it out of the kitchen workflow entirely.
Exception routing keeps the majority of invoices that match cleanly on a straight-through processing path. It concentrates human effort on the minority that genuinely require review.
GRN example for a fresh produce delivery
A restaurant raises a PO for 10 kg of heritage tomatoes at £4.20/kg, totalling £42.00. The delivery arrives and the kitchen records 9.5 kg on the GRN. The supplier invoices for 10 kg at £4.35/kg, totalling £43.50. Jelly identifies two discrepancies, a 0.5 kg quantity shortfall and a £0.15/kg price increase that was not agreed in the PO.
Both lines are flagged. The chef confirms the 9.5 kg receipt, and the finance manager queries the price increase with the supplier. The approved invoice is adjusted to 9.5 kg at £4.20/kg, £39.90, and pushed to Xero. The dish cost for any recipe containing heritage tomatoes updates automatically. With the workflow mechanics clear, the next step is setting up automated three-way matching in your own venue.
Implementation checklist for UK venues
- Set up a dedicated supplier email address through Jelly so invoices arrive directly into the platform. Use this address with UK-based and regional suppliers from day one.
- Brief kitchen staff on photographing paper invoices on delivery using the Jelly mobile interface. Reinforce this during busy UK service periods such as weekend evenings.
- Connect Xero via the one-click accounting integration. Confirm VAT codes and UK tax settings match your existing chart of accounts.
- Connect your POS system via the Jelly integrations tab, which typically takes around five minutes per system. Complete this before building recipes so sales and cost data align.
- Build or import your supplier list and configure per-category tolerance thresholds. Apply the ±2% and ±5% guidance, then refine based on your UK supplier contracts.
- Build dish recipes in the Jelly Cookbook using ingredients already populated from scanned invoices. Link these recipes to your POS buttons so sales and cost data stay in sync.
- Run a parallel check for the first two weeks, comparing Jelly-matched invoices against your existing process to validate accuracy before switching fully. Use this period to fine-tune tolerances and exception routing.
Generic AP tools compared with hospitality-specific automation
General-purpose accounts payable software handles invoice approval workflows competently, but it has no concept of a recipe, a dish margin or a GRN for a partial produce delivery. When an ingredient price changes in a generic AP tool, that information stays inside the finance module. It never reaches the kitchen, never updates a dish cost and never triggers a menu pricing review.
Hospitality-specific automation closes that loop. Because Jelly connects invoice data directly to live recipe costing and POS sales data, a price change on chicken thighs surfaces immediately as a margin movement on every dish that contains them. The executive chef sees a red margin indicator on the dish before the next service, not in a monthly management report. That real-time connection between procurement costs and menu profitability is structurally absent from generic finance tools.
How to measure success with automated matching
Four directional KPIs show whether automated three-way matching is delivering value as a complete system. Start with monthly admin hours, where operators typically recover the 10–20 hours per month previously spent on manual invoice reconciliation. That time saving depends on a low unmatched invoice rate, and the proportion of invoices requiring manual exception handling should fall below 10% within the first month as tolerance thresholds are calibrated.
When exceptions do occur, credit note turnaround measures how quickly they are resolved. The time between identifying a discrepancy and receiving a supplier credit note should shorten from days to hours once exception routing is automated. These operational improvements enable the most important metric, daily dish margin visibility. Every dish in the Cookbook should display a live GP percentage updated with each new invoice, giving chefs and owners a real-time view of profitability rather than a retrospective one.
Jelly customers reduce food costs by an average of 3% and add approximately 2 percentage points to gross profit within the first three months.
Advanced tips for multi-site and menu performance
Once three-way matching runs cleanly, the matched invoice data becomes the foundation for more sophisticated analysis. Linking matched ingredient costs to Jelly's Sales Mix report, populated via POS integration, supports menu engineering decisions grounded in actual cost data rather than estimates. Dishes with high popularity but declining margins can be repriced or reformulated before they become a structural problem.
For operators expanding to multiple sites, Jelly's flat-rate per-location pricing means the same automated workflow scales without additional configuration overhead. Each site maintains its own supplier relationships and tolerance settings, while owners and finance managers retain a consolidated view of spending, margins and exceptions across the entire estate. Populu, for example, lifted gross profit from 68% to 72% across 16 locations after implementing Jelly's automated invoice and costing workflow.
Frequently Asked Questions
What happens when a supplier changes a price mid-week without notice?
When a new invoice arrives with a price that differs from the most recent agreed rate, Jelly's Price Alert feature flags the change immediately, showing the exact ingredient, the old price, the new price and the supplier name. The kitchen team does not need to spot it manually. The flagged invoice is held from automatic approval until the price change is either accepted, which updates the recipe cost in real time, or disputed with the supplier. This means mid-week price changes are caught at the point of invoice receipt rather than discovered in a month-end reconciliation.
How does three-way matching work across multiple sites with different suppliers?
Each Jelly location operates its own supplier list, purchase orders and GRNs, so a site in Manchester and a site in London can use entirely different suppliers without any cross-contamination of data. Exceptions are routed to the relevant site manager or chef. Owners and finance managers with access to the central dashboard can view matched and unmatched invoices across all sites simultaneously, which makes it straightforward to identify whether a discrepancy is site-specific or a supplier-wide pricing issue affecting the whole estate.
When does matched invoice data appear in Xero, and does it affect reconciliation timing?
Matched invoices are pushed to Xero via a one-click export as soon as the three-way match is approved, either automatically for clean matches or manually for reviewed exceptions. The data arrives in Xero as a coded, line-item invoice ready for bank reconciliation, with supplier, amounts and tax already populated. There is no batch delay or end-of-day sync. This means your Xero ledger reflects approved purchase costs in near real time, and your accountant or bookkeeper works from data that is already reconciled against deliveries rather than raw, unchecked invoices.
Conclusion: turning invoice admin into margin control
Manual three-way matching is a margin leak disguised as a routine admin task. For UK restaurants, pubs and boutique hotels turning over £500k or more, the cumulative cost of unchecked price creep, unresolved quantity discrepancies and delayed financial visibility is measured in percentage points of gross profit every month.
Automating the process, capturing invoices by email or photo, digitising every line item, matching against POs and GRNs within configured tolerances, routing exceptions and pushing clean data to Xero and live recipe costs, converts that monthly admin burden into a workflow that runs largely without human intervention. The result is measurable margin improvement within three months and a kitchen team that spends its time on food and service rather than paperwork.
Book a demo and see how Jelly's automated three-way matching works for your venue.
