F&B purchasing financial control · Hotels
Regain financial control of your F&B purchasing
From order to payment: clean closes, reliable accruals and per-hotel data, without forcing your ERP.
The problem isn't negotiating better: it's that operations reach the close too late
The gap isn't in negotiating better —your central purchasing office already solves that—. It's that the negotiated policy is executed unevenly at each hotel, and Finance inherits too late whatever broke in operations: unreconciled delivery notes, manual accruals, invoices that don't match what was received and analytical data that has to be rebuilt entity by entity. This page treats order-to-payment traceability as financial control, not operational efficiency.
Why your ERP doesn't close this gap (and shouldn't try)
Your ERP is the financial core: accounting, legal entities, consolidation. It isn't designed for a consumption point to order, receive and validate delivery notes every day. Forcing it into that operation means expensive custom development, an unmanageable product master —the same item multiplied by supplier, format and legal entity— and recipe costings that break with every supplier change. The gap isn't closed by pushing it into the ERP: it's closed with a specialized operational layer that executes purchasing at each hotel and hands Finance clean, bookable data. Your ERP consolidates and books, your central purchasing office negotiates, Controliza executes. Negotiating better doesn't guarantee saving more: the saving is captured in execution. Why the ERP isn't the tool to manage HORECA purchasing →
The order → receipt → delivery note → invoice → payment chain, and where the margin leaks
Between order and payment there are five links, and the margin leaks through the small deviations that repeat thousands of times: a price off-tariff, a quantity that never arrives, a substituted brand, a product no one ordered. Individually no one notices them; added up, they accumulate into what the sector estimates at a 1–3% delivery-note deviation on purchased volume (an industry reference range, not a figure attributed to any client). They aren't controlled at the close, once they're already paid: they're controlled at the moment of receipt.
- What to control between order and payment — that the price matches the contract, that the quantity tallies and that the product is the approved one
- Only validated goods move forward — whatever doesn't tally is flagged at goods receipt and doesn't contaminate the next link
- The hidden cost becomes visible — the deviation is no longer discovered in the month's P&L and is seen while you can still dispute it
The delivery note is the first billing point (the blind spot)
The delivery note is the most critical document and the least controlled. It's the first billing point: if it enters wrong, the error travels all the way to the invoice and Finance can only correct it late, when no decision is possible anymore. Validation has to happen at goods receipt, not when the invoice arrives. There, price, quantity and product are checked against the order and the contract; whatever doesn't tally is flagged and doesn't contaminate the chain. That way the delivery note stops being a slip someone keys in and becomes the financial source of truth on which accruals, matching and expense are built. The delivery note as the financial source of truth →
Monthly close and goods received pending invoicing
At the close, part of what was received still has no invoice. Today that accrual is estimated by hand, arrives late and no one can defend it line by line. Controliza calculates it on its own from the delivery notes already validated but not yet invoiced: a clean accrual, aggregated by account, family, hotel and dimension, posted on the last day of the month and reversed on the 1st of the next. Finance closes with a figure traceable back to the delivery note that originates it, not with an estimate. Inventory versus expense, received versus invoiced: everything tallies without rebuilding the month after the fact. Finance defines the criterion; the system executes it.
Invoice-to-delivery-note matching and payment risk
Only validated goods move to payment. When the invoice arrives, it's matched against the already-approved delivery notes: if everything tallies, it moves forward; if not, it stops. Whatever was read at goods receipt but not accepted was left with zero received and doesn't enter the invoice, so you don't pay for a product not received or an off-tariff difference no one validated. Payment risk no longer depends on someone reviewing invoice by invoice at month-end. Intelligent delivery note reconciliation →
Inventory vs expense: when to recognize the cost
Not everything received is an expense the day it arrives. Finance defines the criterion and the system executes it: what's received into the central warehouse is inventory, and it becomes an expense when it moves to the consumption point or when it's sold via recipe costing. That distinction —inventory versus consumption— is what makes the change in inventory tally without heroic counts at the close. Stock, traceability and counts →
Analytical data per hotel and cost center, not per legal entity
Finance needs legal entity, account and dimension; Operations needs hotel, consumption point and product family. They're two axes of the same data and normally each lives in a different place. The operational layer keeps both at once and exports aggregated and clean: you see the spend on a product across all hotels without going entity by entity, and the journal entry reaches the ERP with the dimension Finance needs. One dataset, two readings, without rebuilding anything.
The architecture: operational layer + financial ERP
Three layers, each doing its own job. Your central purchasing office negotiates supplier, tariff and catalog. The operational layer —Controliza— executes and controls: order, goods receipt, delivery note, validation, stock and analytical data. The ERP books and consolidates: validated invoice, journal entry, legal entity, dimension. Controliza doesn't replace either of the other two; it's the missing bridge between the negotiated policy and the accounting, where purchasing actually happens.
Strategy · Central purchasing office
Negotiates supplier, tariff and catalog. Defines the group's centralized purchasing policy. It doesn't run each hotel's daily operation.
Operational layer · Controliza
Executes and controls: order, goods receipt, delivery note validation, stock and the analytical data per hotel and center.
Accounting · ERP
Books and consolidates: validated invoice, journal entry, legal entity and dimension. Receives the data already clean.
How to validate it without a big bang
There's no need to migrate everything at once. It's validated with a bounded, measurable pilot by clusters: you start with a group of hotels and a concrete scope —goods receipt and matching, for example— and you measure before scaling. These are the metrics a CFO uses to judge the pilot:
% of orders inside the system
How much of actual purchasing goes through the controlled circuit versus what slips out by phone, WhatsApp or emergencies.
€ of deviations detected
Price, quantity and product differences caught at goods receipt that used to be paid without validation.
Goods received not invoiced identified
Amount of the accrual calculated automatically at the close, traceable back to the delivery note.
Admin hours avoided
Time Finance and the hotels stop spending on manual matching and accruals.
Invoices with a complete document trail
What percentage of invoices arrive with order, validated delivery note and matching all linked.
Bring your F&B purchasing under financial control, from order to payment
Request a Free DemoFrequently asked questions about purchasing financial control
Why not manage F&B purchasing directly in the hotel's ERP?
Because the ERP is the financial core —accounting, legal entities, consolidation— and it isn't designed for a consumption point to order, receive and validate delivery notes daily. Forcing it means expensive development, an unmanageable master and recipe costings that break with every supplier. Purchasing is executed in an operational layer that hands Finance clean, bookable data.
What is goods received pending invoicing and how is it accrued?
It's what the hotel has received at the close and doesn't yet have an invoice for. Controliza calculates the accrual from the delivery notes already validated but not invoiced: a figure aggregated by account, family, hotel and dimension, posted on the last day of the month and reversed on the 1st of the next, traceable back to the delivery note that originates it.
How do you avoid paying for products not received or off-tariff?
Only validated goods move to payment. The invoice is matched against the delivery notes approved at goods receipt; whatever was read but not accepted was left with zero received and doesn't enter the invoice. That way you don't pay for a product not received or a price difference no one validated.
Does Controliza replace my ERP or my central purchasing office?
No: it complements them. Your purchasing office negotiates supplier, tariff and catalog; your ERP books and consolidates; Controliza executes and controls purchasing at each hotel and returns the data with the dimension Finance needs.
Can it be rolled out without a large migration project?
Yes. It's validated with a bounded pilot by clusters: a group of hotels and a concrete scope —goods receipt and matching, for example— with close metrics before scaling to the rest of the group. No big bang.
