Touchless AP in organized hospitality: automating 500+ invoices/month with perishable produce

"Organized hospitality" is an elegant euphemism for "restaurant chain that no longer fits in a spreadsheet". We're talking about groups of 8 to 50 locations with a shared brand, central admin and partially centralized purchasing. Volume arrives in bursts: each location orders from its usual supplier, receives daily, and at month-end central has to reconcile it all.

It is one of the sectors most hit by manual AP and, paradoxically, one of the least served by generic AP automation software. The reason is simple: tools designed for industrial distribution or B2B services don't account for variable weights, multi-VAT, driver substitutions or crumpled paper delivery notes.

This article is for whoever runs admin in a hospitality chain and is tired of AP eating into food cost. The thesis: touchless AP does work in hospitality, but only if the system understands perishables, multi-location and per-product-family tolerances.

Why organized hospitality is different

The composition of cost is what matters for AP: a very large portion is perishable produce bought from multiple suppliers with daily frequency.

The five characteristics that make this case different:

• High and dispersed volume. 500-1,000 invoices/month in a chain of 10 locations is not unusual. Each location receives 3 to 8 weekly deliveries from different suppliers.
• Perishable product with variable weight. One box of hake doesn't weigh the same as the next. The delivery note sometimes says 14.5 kg, the invoice bills 14.8 kg, and nobody weighed anything at the location.
• Prices that change weekly. Fish market, central market, occasional shortage. The agreed price on Monday doesn't apply on Friday. The supplier reflects it; you find out when reviewing the invoice.
• Substitutions without notice. No zucchini, eggplant arrives. No premium hake, regular hake arrives. The POS doesn't know, the recipe doesn't know, the invoice does.
• Multi-location with duplicates. The same supplier delivers to three locations the same day and issues one invoice per each. Or worse: a single grouped invoice central receives without a specific PO from one location.

Result: an admin team with two people spends 60-80 hours a month just entering invoices and chasing differences. And a percentage of discrepancies still slips through because "it doesn't pay off the time".

Classic AP problems in hospitality

Problem	Typical frequency	Impact
Delivery-note kilos don't match invoice	15-25% of fresh invoices	Direct food cost variance
Substitution prices without adjustment	5-10% of lines	Overpay without traceability
Inter-location duplicates	2-4% of invoices	Double payment if not detected on time
Paper delivery notes from the driver	30-50% of deliveries	Impossible to three-way match
Grouped invoice covering several deliveries	10-20% in big suppliers	Lose the per-location PO match

Food cost impact

Food cost in organized hospitality usually moves between 28% and 35% of sales. A 0.5-1.5 point deviation from undetected AP errors is common when PO and delivery-note matching does not exist.

In a 10-location chain with aggregated EUR 6M sales per year, one food-cost point equals EUR 60,000. That's why the quick math any Finance Director does when we start a conversation is simple: if touchless AP captures half a point, the tool pays itself twenty times over.

The silent bias always favors the supplier. When nobody weighs the box, the supplier bills the weight on their scale. When the price changes, you find out weeks later. When there's a substitution, you get billed for the more expensive product. This isn't bad faith; it's information asymmetry. Touchless AP closes it on the recipient side.

The touchless flow adapted to hospitality

A generic touchless flow doesn't work here. Six phases need adaptation:

1. Multi-location intake. Each location has its mailbox or sub-address. The invoice arrives tagged with the destination location without anyone forwarding. If the supplier sends a grouped invoice to central, the system splits per delivery location.
2. OCR/IDP with multi-VAT. A typical invoice mixes products at 10% (general food), 21% (alcoholic beverages, soft drinks) and 4% (bread, milk, fruit). The extractor must type per line, not apply a header VAT.
3. Three-way matching against contract and delivery. Formal POs don't always exist; what exists is a framework agreement with quarterly negotiated prices. The match is contract vs delivery note vs invoice. When the digital delivery note exists, match line by line. When it's paper, digitize on receipt.
4. Per-supplier risk scoring. The fish supplier has more variability than the oil one. The system learns which supplier generates more discrepancies and applies stricter controls where needed.
5. Smart routing. A quantity variance on fresh produce goes to the location's head chef. A price variance goes to central. A duplicate goes straight to the admin team. Not all humans resolve all exceptions.
6. Export to accounting and dashboard. Clean data enters the ERP and feeds the food cost dashboard by location, family and supplier. Admin stops generating reports by hand.

This flow leaves humans where they add value: kitchen deciding whether to accept the real weight, central renegotiating prices, admin reviewing only the exceptions the system couldn't close.

Per-product-family tolerances

One of the most misunderstood decisions is to apply the same tolerance to everything. In hospitality it doesn't work. A kilo of oil doesn't vary; a kilo of clams does.

A reasonable tolerance framework as a starting point (always line by line, never header):

• Fresh perishables (fish, shellfish, fruit, vegetables). Quantity tolerance 5-8% to absorb shrinkage and weight variability. Price is controlled separately with tight tolerance.
• Dry products (legumes, flour, canned). Quantity tolerance max 1%. No handling shrinkage and exact weight.
• Beverages with 21% VAT. Zero tolerance. They are closed units and the price is in contract. Any variance is an error to review.
• Meat and poultry. Quantity tolerance 2-4% for cutting and deboning shrinkage. Tighter price tolerance.

These numbers are illustrative and tuned in the first weeks with real business data. Universal rule: never use the same tolerance for a box of clams and a box of soft drinks.

Integration with hospitality POS and ERP

AP doesn't live alone. The invoice enters, gets reconciled, and clean data feeds the food cost dashboard that combines purchases with POS sales. Chains with a mature stack usually combine:

• POS and floor management with products like Wivai (Glop), Lightspeed Restaurant, Revo, GoCash or equivalents. They provide sales by recipe and family.
• ERP and accounting with Holded, Sage 50/200, A3 ASESOR or sector verticals. They receive clean entries from AP.
• AP automation layer between the supplier email and the ERP. This is where ininvoice lives: intake, reading, three-way matching, export.

The idea is not to duplicate masters. Suppliers stay in the ERP; ininvoice reads them. Recipes live in the POS or the ERP, not in AP. The AP layer only cleans and matches.

Verifactu and hospitality

When food and beverage suppliers move gradually to Verifactu and B2B e-invoicing, hospitality chains will receive invoices with signed structured data. This changes AP input quality: less OCR on pixels, more QR and XML reading.

For a chain, the practical effect is twofold: the invoice received is easier to process automatically, and at the same time AEAT receives the same data from the supplier in real time. Any divergence between what your accounting reflects and what the supplier declared becomes detectable. We went deeper on this in the article on Verifactu and accounts payable. [VERIFY WITH TAX ADVISOR] the timeline applicable to your suppliers.

Estimated case: 10-location chain

Illustrative figures for a 10-location chain with 700 invoices/month and two admin staff.

Metric	Manual AP	Touchless with ininvoice
Hours/month on capture and reconciliation	~80 h	~20 h (exceptions only)
Average invoice-to-book time	9-14 days	<48 h
% discrepancies detected	~40%	>95%
Attributable AP personnel cost	~EUR 1,600/month	~EUR 400/month
AP software cost	EUR 0	EUR 49/month
Estimated monthly net savings	—	~EUR 950-1,300

This excludes recovered food cost. If the chain recovers half a point on EUR 6M/year in sales, that's an additional EUR 30,000 that usually dilutes into "we don't know exactly where the margin goes".

Checklist for Operations Director

1. Inventory the real volume: how many invoices/month each location receives and from how many distinct suppliers.
2. Identify the top 10 suppliers by volume and top 10 by amount. They usually don't overlap.
3. Measure how much time admin spends on capture vs discrepancy resolution.
4. Audit a real week of delivery notes per location: how many on paper, how many digital, how many missing.
5. Compute current food cost by location and family. The spread between locations is usually revealing.
6. List variable-weight (fresh) vs fixed-weight (packaged) suppliers. Define per-family tolerances.
7. Confirm with the POS which sales data by recipe and family are available for the food cost dashboard.
8. Confirm with the advisor or accounting team how clean data enters the ERP (Holded, Sage, A3).
9. Define exception routing: what goes to the head chef, what to central, what to admin.
10. Pilot with two locations before extending to the whole chain. Track KPIs for 4-6 weeks.

Frequently asked questions

Does this work if my suppliers still send paper delivery notes?

Yes, but three-way matching loses precision until the delivery note is digitized. Recommended: use the location's mobile app to photograph the delivery note on receipt, or ask the supplier to send it by email. The photo enters as input into the same OCR/IDP flow.

What about grouped invoices mixing several locations?

The system splits per delivery location using the delivery note data (when available) or the invoice line. If the supplier doesn't differentiate, you must request it; it's good accounting practice and not negotiable medium-term.

How are prices that change weekly handled?

The system keeps the agreed price for the active period and compares each invoice against that price. If the supplier raises price without notifying, an exception is raised and sent to central. The only way to avoid overpaying without realizing.

Do I need a formal PO for each order in each location?

Not strictly. What is needed is a framework agreement with prices and authorized suppliers. The match is contract vs delivery note vs invoice. A formal PO per line is only usual in large centralized purchases.

How does the system separate 4%, 10% and 21% VAT?

Line by line, reading the rate applied on the invoice. Each line is posted with its rate. Totals are reconciled at the end. A single VAT is never applied to the header; that causes errors on form 303.

What integrations does it have with hospitality POS?

ininvoice exports clean data via CSV/API to your ERP. POS integration depends on the specific provider and is discussed case by case.

How long does it take to be operational in a chain?

It starts on mailbox connection. Extension to the rest of the locations depends on volume and supplier heterogeneity. Most chains have full coverage within 4-6 weeks.

Does it replace the ERP or accounting?

No. ininvoice is pure AP automation. Not an ERP, not accounting, not POS. It sits between the supplier email and your ERP. Clean entries are exported to Holded, Sage or A3.

Three takeaways

Organized hospitality is not just another AP case. It is one of the hardest there is and, exactly for that reason, where there is most room to automate well.

1. Manual AP in chains of 8-50 locations eats whole food cost points in silence. Half a point recovered pays touchless AP twenty times over.
2. Generic touchless doesn't work. You need to tolerate shrinkage on perishables, tightly control beverages, separate multi-VAT per line and route exceptions to the right decision maker.
3. The working stack is light: supplier email → AP automation layer → ERP. The POS feeds the food cost dashboard in parallel. No mega-projects.

Related content

• Three-way matching: how to cross-check invoice, PO and delivery note line by line
• Touchless accounts payable: what it means and how to measure it
• Hospitality invoices: protecting your food cost
• Verifactu and accounts payable
• Touchless rate: how to measure your automation