.svg)
Management reporting for restaurants: food cost, prime cost and revenue per seat (2026)
A restaurant earns thin margins on daily revenue — which calls for a report that steers weekly on food cost, labor cost and the use of every seat.
.png)
Management reporting for restaurants: food cost, labor cost and prime cost per week, revenue per seat and per location. Finstack automates the figures from EUR 39/month.
Management reporting for restaurants: food cost, prime cost and revenue per seat
Hospitality earns per cover and loses per percentage point. The reporting that fits — from weekly figures to location comparison and automation.
TL;DR
The management report of a restaurant steers on two cost blocks that together form the prime cost: purchasing (food cost and beverage cost, reported separately) and labor costs including the flexible pool. On top of that: revenue per seat, average spend per guest and — with multiple locations — the P&L per location. The steering rhythm is weekly; the full report follows the seven sections of a good management report monthly. Finstack automates the data flow from EUR 39/month.
What makes management reporting for a restaurant different?
Management reporting for a restaurant differs fundamentally from other business models on three points: the margins are thin and the costs concentrated in two blocks, the steering rhythm is weekly rather than monthly, and the figures come from two systems — the till and the accounting.
The first point determines what the report must be about. In a restaurant, virtually all controllable costs sit in purchasing (food and beverage) and labor; together they form the prime cost. A few percentage points of deviation on either makes the difference between a healthy month and a loss-making one — and both can be influenced daily, through purchasing, portioning and rosters. The report should therefore show those two blocks not as totals but as percentages of revenue, per week, with a norm next to them.
The second point is the rhythm. A management report appearing on day ten covers rosters and purchases from six weeks ago — in hospitality that is history. The steering rhythm is therefore weekly: revenue per daypart, purchasing and staffing against the week’s revenue. The monthly management report remains the decision document for management and investors, but it floats on weekly figures that were already there.
The third point is where the data comes from. Revenue originates in the POS system — per receipt, per revenue group, per daypart — while costs, inventory and the balance sheet live in the accounting. A good report brings the two together: POS revenue reconciled with booked revenue (including the Dutch VAT split between kitchen and alcohol), and purchase invoices set against the revenue of the same period.
The foundation remains the standard structure of a good management report: summary, P&L, balance sheet, cash flow, variance analysis, KPIs and commentary. The rest of this article fills in that structure for restaurants: the KPI set, food cost and prime cost, the weekly rhythm, the location comparison and automation.
Which KPIs belong in the management report of a restaurant?
The management report of a restaurant runs on five to eight KPIs, with food cost and prime cost at the core. This is the set that makes the difference in practice:
- Food cost (% of kitchen revenue). The purchase cost of dishes against the revenue they generate. The kitchen’s daily lever: recipes, portioning, purchasing and waste all come together in it.
- Beverage cost (% of beverage revenue). Separate from food, because the margins differ strongly — and a shift in the mix between kitchen and bar often explains a margin move that otherwise looks inexplicable.
- Labor cost (% of revenue). Including the flexible pool of on-call and agency staff. The KPI follows roster discipline: is staffing planned to the expected revenue per daypart?
- Prime cost (% of revenue). Purchasing plus labor combined. As a rule of thumb, many restaurants aim for a prime cost well below two thirds of revenue — above that, too little remains for rent, overhead and profit.
- Revenue per seat. The use of capacity: revenue divided by the number of seats, per week or per service. Together with the number of covers it shows whether growth comes from occupancy or from spend.
- Average spend per guest. The pricing and selling side: menu prices, upselling and the mix between kitchen and bar.
- Occupancy costs (% of revenue). Rent and fixed charges cannot be influenced weekly, but they do set the revenue a location minimally has to make.
- Revenue and result per location. With multiple sites: every location as its own P&L, built identically — the basis for every portfolio conversation.
Present every KPI as the main article prescribes: level, a trend of at least twelve months and the comparison against budget — and in hospitality also against the same week last year, because season and weather weigh heavily. Keep the first page under eight steering metrics.
How do you monitor food cost and beverage cost?
You monitor food cost by putting two figures side by side: the theoretical food cost (what the dishes sold should have cost in purchasing according to the recipes) and the actual food cost (actual purchasing plus the inventory movement of the period). The difference between the two is the most interesting line of the entire report.
The actual food cost comes from the accounting: purchase invoices for the period, corrected for opening and closing inventory. The theoretical food cost comes from the POS system: quantities sold per dish times the recipe cost. If the actual food cost sits structurally above the theoretical one, margin is leaking away — through waste, generous portioning, breakage, own use or worse. Exactly that difference makes the conversation with the kitchen concrete: not “the margin has to improve”, but “we are losing three points between recipe and reality”.
Three setup rules keep this monitoring reliable. First: split food and beverage consistently, in the POS (revenue groups) and in the accounting (separate purchase accounts) — otherwise neither percentage can be calculated. Second: count inventory at a fixed moment, at least monthly; without the inventory movement, the actual food cost of a short period cannot be determined. Third: register waste separately where possible — what gets thrown away is its own story next to what is portioned too generously.
Supplier price increases deserve their own look: with rising purchase prices, the food cost can climb while the kitchen does nothing wrong. Therefore split the movement into a price effect (more expensive purchasing) and an efficiency effect (more usage per dish) — the first calls for menu-pricing or purchasing action, the second for a kitchen conversation.
How do you keep labor costs and prime cost under control?
In hospitality you steer labor costs in advance, through the roster — not afterwards, through the monthly figures. The report supports that with one core comparison: planned and worked hours times labor cost, set against the revenue of the same daypart or week. A busy weekend with generous staffing can be fine; a quiet Tuesday with the same staffing never is. Also include revenue per hour worked as a simple productivity measure across the weeks.
Include everything in labor costs: fixed contracts, on-call staff, agency staff and holiday-pay and pension surcharges. The flexible pool in particular — the part that should move with revenue — deserves its own line: does it actually move along, or does it sit at the same level every week? A flexible pool that turns out not to be flexible is one of the quietest margin leaks in hospitality.
The prime cost brings purchasing and labor together in one percentage of revenue — the most important line of the restaurant P&L. As a rule of thumb, many restaurants aim to keep the prime cost well below two thirds of revenue; whatever sits above it has to come out of rent, overhead and profit, and at hospitality margins there is hardly any slack there. Report the prime cost weekly as a trend, next to budget and the same week last year: that makes visible whether a deterioration comes from the kitchen, the bar or the roster.
The commentary completes it: which weeks deviated, what was the cause (a public holiday, a price increase, a wave of illness in the team) and what was done about it. Short and concrete — the figures are already there, the story gives them direction.
How do you structure the management report for a restaurant?
The management report for a restaurant follows the seven fixed sections from the main article on the good management report — each filled in for restaurants:
- Summary. One page with the revenue and prime-cost trend as a chart, the location comparison and the three messages of the month.
- Profit and loss statement. Revenue split into kitchen, bar and other; then purchasing (food and beverage separately), labor costs including the flexible pool, occupancy and overhead. Show month and year-to-date next to budget and last year; one-offs separately.
- Balance sheet. Compact: small, perishable inventory, supplier payables, the cash position per location and the investments in fittings and refurbishment against depreciation.
- Cash flow. Hospitality collects immediately and pays on terms — working capital works with you. Watch the fixed obligations above all: rent, repayments and the VAT and payroll-tax remittances.
- Variance analysis. Split the revenue deviation into covers (occupancy) and spend per guest (price and mix), and the cost deviation into price and efficiency effects. Compare with the same period last year because of seasonality.
- KPIs. The set from this article as trends: food cost, beverage cost, labor cost, prime cost, revenue per seat, spend per guest, occupancy costs, result per location.
- Commentary. The story: why the prime cost moved, which location deviates and what happens about it, what the coming period brings (reservations, season, events).
Alongside runs the weekly rhythm: a short weekly overview with revenue per daypart, food and beverage purchasing against the week’s revenue and hours worked against the roster. That is the hospitality equivalent of the weekly cash flash from the main article — steer weekly, account and decide monthly.
For delivery, the norm from the main article applies: within 5-10 working days after month-end, with a month-end close so figures stop shifting — with the POS reconciliation and the inventory count as fixed parts of that close.
Multiple locations: how do you report per location and as a group?
Restaurant groups almost always grow in structure too: an entity per location, a holding on top, and often a separate entity for central purchasing, a central kitchen or the staff. For reporting, that means two levels at once: the P&L per location for steering, and the consolidated group picture for management and investors.
The location comparison is the most powerful instrument here: every location in the same layout — revenue groups, food cost, labor cost, prime cost, occupancy — side by side. Differences in prime cost between comparable sites are almost always the group’s fastest improvement point. Also include revenue per seat and spend per guest in the comparison, so that next to the cost side the revenue side per location becomes comparable too. Do not smooth head-office and central costs away into the location figures, but show them as a separate layer: a location must remain comparable with itself and with the other sites.
The group structure brings intercompany flows: the central purchasing entity supplying the locations, the staffing entity recharging hours, the holding with management fees and rent recharges. At group level those must cancel out, otherwise group revenue double-counts. How elimination and consolidation work structurally is covered in consolidation for SME CFOs and the deep-dive on multi-entity consolidation.
Finstack automates this for groups of 1 to 50 entities: every location entity connects through its own accounting package, charts of accounts are mapped to one group chart, and the engine recognizes the intercompany flows automatically — without setting up separate IC accounts. The result: the location comparison and the group picture from the same source, with every line clickable through to the booking.
How do you automate reporting from your accounting system?
The figures for the restaurant report come from two layers: the POS system (revenue per receipt, revenue group and daypart) and the accounting (costs, inventory, balance sheet, cash). The automation gain sits mainly on the financial side, and it can be made directly.
Dutch hospitality businesses typically run on Exact Online or — often via the accountant — Twinfield, with a daily revenue feed from the POS. Finstack connects these packages directly via API, read-only and at transaction level: the actuals refresh automatically every day, with a manual refresh at any moment. With multiple location entities, the consolidation from the previous section runs along automatically.
Reporting then happens wherever the team wants to work. The Finstack dashboards show revenue, costs and the result per location and consolidated in real time, clickable through to the source transaction. Whoever builds the management report in their own Excel or Google Sheets model — for example to place POS data per daypart next to the financial figures — uses the 2-way integration: the financial actuals refresh in the existing model in one click. You can also share dashboards and reports with stakeholders such as management, investors and the accountant, by giving them access to Finstack, with access rights set per user.
The effect on the rhythm: the financial side of the management report is ready on day one instead of after days of collecting, and the time shifts to where hospitality makes the difference — food cost, rosters and the location comparison. Finstack starts from EUR 39 per month for the first entity: live in 5 minutes, set up within a day.
Do you have an entity per location, with a central purchasing or staffing entity? You do not need separate intercompany accounts for that — Finstack recognizes the internal recharges automatically, on your existing ledger setup, and eliminates them in the group picture.
Explore Finstack.
Free trial for 14 days.
Access to all features. No credit card required.
.png)
The 3 most common mistakes in restaurant reports
Three patterns we see again and again at restaurants. Each costs margin or cash; each is preventable with the right setup.
Calculating food cost without inventory and recipes
Whoever reads food cost as “purchase invoices divided by revenue” without the inventory movement and without the theoretical recipe cost next to it, sees only noise: one large purchase order distorts the week, and margin leaks through waste or portioning stay invisible. Calculate actual and theoretical, and discuss the difference — that is where the money sits.
Only seeing labor costs in the monthly figures
In hospitality, labor costs can only be steered in advance, through the roster. Whoever only sees them in that month’s management report cannot undo four weeks of rosters. Set the hours worked against revenue per daypart weekly, and watch separately whether the flexible pool actually moves with how busy it is.
Reporting locations as one pile
One added-up P&L across multiple sites lets profitable locations mask the loss-making ones — sometimes for years. Report every location as its own P&L in the same layout, with its own rent included and the central costs as a separate layer. The comparison between sites points out by itself where the conversation needs to happen.
Frequently asked questions
Can't find your question? Let us know
Which KPIs matter for a restaurant?
The core: food cost and beverage cost as a percentage of their revenue, labor costs including the flexible pool, prime cost (purchasing plus labor combined), revenue per seat, average spend per guest, occupancy costs and — with multiple sites — the result per location. Weekly as trends, next to budget and the same week last year.
What is prime cost and why does it matter so much?
Prime cost is the sum of purchase costs (food and beverage) and labor costs, as a percentage of revenue — the two cost blocks you can influence daily. As a rule of thumb, many restaurants aim well below two thirds of revenue: whatever sits above that must come out of rent, overhead and profit, with hardly any slack.
How do you calculate a restaurant's food cost?
Actual food cost: purchases for the period plus opening inventory minus closing inventory, divided by kitchen revenue. Put the theoretical food cost from the POS system next to it: dishes sold times recipe cost. The difference between the two shows where margin leaks — waste, portioning or own use — and makes the kitchen conversation concrete.
Why does a restaurant steer on weekly figures?
Because the two largest cost blocks — purchasing and rosters — can be influenced per week and cannot be undone per month. A short weekly overview with revenue per daypart, purchasing against the week’s revenue and hours worked against the roster adjusts course; the monthly management report remains the decision document for management and investors.
How do you report with multiple locations or location entities?
Every location as its own P&L in the same layout, with the central costs as a separate layer — and next to that the consolidated group picture. Recharges from central purchasing, staffing or holding entities must be eliminated at group level, otherwise revenue double-counts. Finstack detects and eliminates those intercompany flows automatically.
What does revenue per seat tell you?
Revenue per seat measures how well capacity is used: revenue divided by the number of available seats, per week or per service. Together with the number of covers and the spend per guest it splits growth into three levers: more guests, higher spend or better use of the existing space.
Which accounting packages does Finstack connect for restaurants?
Finstack connects the packages common in hospitality — Exact Online and Twinfield — plus, among others, AFAS, Odoo, Xero, QuickBooks and MS Dynamics 365 BC. Direct API connection, read-only, at transaction level, with daily sync and manual refresh. From EUR 39 per month, live in 5 minutes, set up within a day.
CFO turned Founder - Finstack
Sources and provenance
- Finstack — Reporting & insights (dashboards, Excel/Sheets sync): finstack.io/solutions/reporting-insights
- Finstack — Integrations with Exact, Twinfield and other packages: finstack.io/solutions/integrations
- Finstack Help Center — Sources & connections (sync frequency, security): help.finstack.io
- Finstack — Pricing (from EUR 39/month): finstack.io/pricing
Last reviewed: 25 July 2026 · Next review: October 2026
Consolidated reporting and forecasting.
