Touchless AP in organized hospitality

ininvoice: A chain of 8 to 50 locations receives between 500 and 1,000 invoices a month from food and beverage suppliers with prices changing weekly, kilos that don't match the delivery note and daily deliveries without reliable weight control. Manual AP doesn't scale: every food-cost point that slips through is between EUR 30,000 and 90,000 per year in a mid-size chain. Touchless AP specific to hospitality cross-checks invoice, PO and delivery note line by line and shows whether each exception is a price or a quantity issue, so the team knows whether it is a question for the head chef or for central. A person approves every invoice.

"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, multiple locations and line-by-line 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. Recovering even half a point is EUR 30,000 a year.

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. Five phases need adaptation:

Multi-location intake. Each location has its mailbox or sub-address, and invoices from every mailbox land in the same queue without anyone forwarding. ininvoice does not assign a location or cost centre; that allocation is done in the ERP.
OCR/IDP with multi-VAT. A typical invoice mixes products at 10% (general food), 21% (alcoholic beverages, sugared soft drinks) and 4% (bread, milk, fruit), as set by VAT Law 37/1992, arts. 90 and 91. The extractor must read the rate per line, not apply a header VAT.
Three-way matching against the PO and delivery note. The match is purchase order (with the agreed price) vs delivery note vs invoice, line by line. Purchase orders and delivery notes come in like invoices, by e-mail or upload; a paper delivery note is photographed on receipt.
Who answers each exception. A quantity variance on fresh produce is a question for the location's head chef. A price variance is one for central. A possible duplicate is one for the admin team. ininvoice shows the type and the reason of each exception; your team decides who follows it up, and a person approves the invoice.
Export to accounting and dashboard. Once a person has approved them, invoices are exported as a CSV or Excel file that the ERP imports, and from there they feed the food cost dashboard by location, family and supplier.

This flow leaves humans where they add value: kitchen deciding whether to accept the real weight, central renegotiating prices, admin reviewing exceptions and approving invoices.

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, a starting point for your own policy to be reviewed with real business data. In ininvoice the tolerance is set by the organisation; the default is 2% or EUR 1.50 per line in OR mode. Universal rule: never use the same tolerance for a box of clams and a box of soft drinks.

What does this look like on your real invoices?

ininvoice ingests location invoices by email, cross-checks them line by line with your delivery notes and leaves them ready for a person to approve; approved invoices are exported as CSV or Excel. See it with your locations’ invoices.

Is your group in hospitality? The hospitality accounts payable page gathers what changes with many suppliers and venues. See accounts payable for hospitality

Integration with hospitality POS and ERP

AP doesn't live alone. The invoice enters, gets reconciled and approved, and the approved 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 import the approved invoices from AP as a CSV or Excel file.
AP automation layer between the supplier email and the ERP. This is where ininvoice lives: intake, reading, three-way matching, approval by a person and export of approved invoices.

The idea is not to duplicate masters. Suppliers stay in the ERP; ininvoice does not read them. Recipes live in the POS or the ERP, not in AP. The AP layer reads, matches and, once a person has approved, exports.

Verifactu and hospitality

When food and beverage suppliers start issuing with Verifactu and B2B e-invoicing, hospitality chains will receive more invoices with structured data. They are two rules with different calendars. B2B e-invoicing (Law 18/2022, developed by Royal Decree 238/2026) applies from 6 October 2027 to companies with turnover above EUR 8 million and from 6 October 2028 to everyone else, according to the AEAT implementation calendar. Verifactu (Royal Decree 1007/2023) requires the issuer to have its billing system adapted before 1 January 2027 if it pays corporate income tax and before 1 July 2027 in all other cases, after Royal Decree-law 15/2025; businesses keeping their VAT books through the SII are outside it. On 5 October 2026 the Ministry of Finance announced a delay of Verifactu to October 2028, which for now is only an announcement. The recipient of the invoice has no Verifactu obligation.

For a chain, the practical job does not change: every invoice received, whether it arrives as a PDF, an image or a scan, has to match its purchase order and delivery note line by line before it is paid. If the supplier uses the VERI*FACTU mode, its billing records also reach the AEAT when issued, so a divergence between your books and what the supplier invoiced is easier to spot. We went deeper on this in the article on Verifactu and accounts payable.

Estimated case: 10-location chain

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

Metric	Manual AP	With ininvoice (estimate)
Hours/month on capture and reconciliation	~80 h	~20 h (exceptions only)
Average invoice-to-book time	9-14 days	<48 h
Discrepancies detected	Only what someone reviews by hand	Every matched line is checked
Attributable AP personnel cost	~EUR 1,600/month	~EUR 400/month
AP software cost	EUR 0	Tailored pricing
Estimated AP staff saving (before software)	—	~EUR 1,200

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

Inventory the real volume: how many invoices/month each location receives and from how many distinct suppliers.
Identify the top 10 suppliers by volume and top 10 by amount. They usually don't overlap.
Measure how much time admin spends on capture vs discrepancy resolution.
Audit a real week of delivery notes per location: how many on paper, how many digital, how many missing.
Compute current food cost by location and family. The spread between locations is usually revealing.
List variable-weight (fresh) vs fixed-weight (packaged) suppliers. Decide whether one tolerance policy fits every family.
Confirm with the POS which sales data by recipe and family are available for the food cost dashboard.
Confirm with the advisor or accounting team how approved invoices are imported into the ERP (Holded, Sage, A3).
Agree who answers each exception: the head chef, central or admin.
Pilot with two locations before extending to the whole chain. Track KPIs for 4-6 weeks.

How would your invoices match today?

Send invoices from two locations, with their purchase orders and delivery notes, and see line by line which ones match. Try it on your own invoices.

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: photograph the delivery note with a phone on receipt and send it to the mailbox, or ask the supplier to send it by email. The photo enters the same reading flow as any other document.
What about grouped invoices mixing several locations?: ininvoice does not split invoices by location or assign them to one; that allocation is done in the ERP. If the supplier doesn't differentiate locations on the invoice, you must request it; it's good accounting practice and not negotiable medium-term.
How are prices that change weekly handled?: Each invoice line is compared against the price on its purchase order. If the supplier raises the price without notice and the line exceeds the tolerance, it is flagged as an exception for a person to review. Keeping the agreed price on the PO is the only way to avoid overpaying without realising.
Do I need a formal PO for each order in each location?: For line-by-line matching, yes: ininvoice compares the invoice against the purchase order (with the agreed price) and the delivery note. Purchase orders and delivery notes come in like invoices, by e-mail or upload. Without a PO there is no agreed price to compare each line against.
How does the system separate 4%, 10% and 21% VAT?: Line by line, reading the rate applied on the invoice. Each line keeps its own 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 approved invoices as a CSV or Excel file importable into your ERP. There is no native POS or ERP connector.
How long does it take to be operational in a chain?: It starts on mailbox connection: without implementation or a consultant, it is up and running in 24–48 hours. Extension to the rest of the locations depends on volume and supplier heterogeneity.
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. Approved invoices are exported as a CSV or Excel file that Holded, Sage or A3 can import.

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.

Manual AP in chains of 8-50 locations eats whole food cost points in silence.
Generic touchless doesn't work. You need to tolerate shrinkage on perishables, tightly control beverages, separate multi-VAT per line and make sure each exception reaches the right decision maker.
The working stack is light: supplier email → AP automation layer → ERP. The POS feeds the food cost dashboard in parallel. No mega-projects.

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