What Good Xero Reporting Actually Looks Like for F&B Operators

Most F&B operators running on Xero hit the same wall eventually. The books are clean, the bank feed is reconciled, and then someone asks a perfectly reasonable question — "What's our food cost percentage across all three outlets?" or "How much are we actually netting after GrabFood takes its cut?" — and the answer involves a spreadsheet, a lot of manual work, and a dash of quiet suffering.

And getting that answer quickly matters most when margins are thin. In F&B they usually are: costs keep climbing, and there's little room for a bad month to go unnoticed. Finding out about a problem three weeks late can be the difference between a course correction and a closing notice. Staying vigilant on the numbers isn't a nice-to-have — it's how you survive the cycle.

The problem isn't Xero. It's that Xero's default reports weren't designed for the operational complexity of a hospitality business. A single-entity P&L is a starting point. It's not a management tool.

Here's what reporting actually needs to do when you're running one or more F&B venues — and what custom-built logic can unlock.

---

Multi-Entity Consolidation With Your Own Logic

If you run more than one Xero entity — separate companies, a holding structure, or a franchise arrangement — you've probably noticed that Xero's own reports, including Xero Analytics, don't combine organisations. The exception is Xero Ultra, a plan Xero launched in Australia in July 2026 at A$500 a month, which includes consolidation. A UK beta is expected in autumn 2026, and we haven't seen an announcement for Singapore. So in practice, you export, you paste, you align the chart of accounts, and you hope nothing breaks.

Custom consolidation logic solves this properly. That means pulling from multiple Xero organisations, applying your own mapping rules (so "Food Purchases" in entity A lines up correctly with "Ingredients" in entity B), and producing a single consolidated view. You can segment it however you need: by brand, by region, by ownership group.

The critical part is that the logic lives in the report, not in someone's head. If your group has four venues with slightly different chart of accounts, a custom consolidation handles the translation automatically — so the monthly roll-up takes minutes, not an afternoon. (For the long version, see how to consolidate multiple Xero entities and how to handle intercompany eliminations.)

---

Bottom-Up COGS Analysis

High-level food cost percentages are almost useless for operational decisions. What you actually need is COGS broken down by category — food vs. beverage vs. packaging, or by cuisine line in a multi-concept kitchen — so you can see where the pressure is coming from.

A bottom-up COGS report maps your supplier invoices and purchase categories directly against revenue lines. You can track food cost as a percentage of food revenue, beverage cost against beverage sales, and catch drift before it becomes a margin problem. Done properly, this also gives your kitchen team actual accountability metrics rather than a blended number they can't act on.

One caution: supplier invoices are purchases, not cost of sales. Unless you count stock at month end and journal the difference, food cost swings with delivery timing rather than what you actually used. A good COGS report starts from purchases, adjusts for opening and closing stock, and only then divides by revenue. Xero's inventory has no bill of materials, so it can't cost a recipe for you, and the stock adjustment has to happen somewhere else.

---

Multi-Location Reporting With Sub-Entity Traceability

Consolidation is great for the boardroom. But at the venue level, you need the opposite — complete traceability into each location's performance without losing the group view.

The right setup gives you both in the same report: a consolidated group P&L at the top, with the ability to drill into any individual location's numbers. Every line item is traceable back to its source entity and transaction. If outlet three is dragging down the group gross margin, you can see it immediately and act on it — rather than running separate reports and reconciling them manually.

---

Revenue Stream Segmentation

Dine-in, delivery, takeaway, catering, retail — most F&B operators have multiple revenue channels feeding into Xero from different sources (POS, delivery platforms, manual invoices), and they all land in roughly the same accounts.

Custom reporting can split these cleanly. If your POS pushes tracking categories into Xero, or if you've mapped your delivery platform income separately, those signals can be used to build a proper channel P&L. You see dine-in revenue vs. delivery revenue with their respective costs allocated against them — not a blended view that obscures whether one channel is carrying another.

This also works by product category: food vs. beverage, or by daypart if your bookkeeping supports it. Keep service charge in its own revenue account too, so it doesn't blur food and drink margins.

One catch: Xero allows only two active tracking categories, and outlet and channel between them use both. Anything further, like menu category or daypart, has to come from somewhere else (the two-limit problem).

There's a compliance angle too. Under IRAS's GST InvoiceNow requirement, GST-registered businesses send invoice data to IRAS through the InvoiceNow network. New voluntary registrants already have to, and existing registrants follow in phases: April 2028 for those with up to S$200,000 in annual supplies (and for new compulsory registrants), April 2029 up to S$1 million, April 2030 up to S$4 million, and April 2031 for everyone else. You still give diners a normal till receipt, but the POS sales data behind it reaches IRAS, and so do your supplier invoices. Consistent revenue and GST coding across POS, delivery and manual invoices is now a compliance matter as well as a reporting one. Our InvoiceNow guide has your phase date.

---

Delivery Platform Fee Economics

This one is genuinely underreported in most F&B businesses. GrabFood, foodpanda and whichever other platforms you sell through all take a commission. That commission is often recorded as a payment processing cost or ignored entirely, rather than being treated as a direct cost of the delivery revenue it relates to.

A net-of-commission delivery margin report shows you what you're actually making on every delivery order after the platform takes its cut. For most operators, this number is materially different from the gross revenue figure — often enough to change decisions about which platforms to prioritise, which menu items to promote through delivery, and whether certain delivery-only dayparts are actually worth running.

Build it from the platform's settlement statement, not the bank deposit. The deposit is net of commission, merchant-funded promotions, refunds and adjustments, so booking it as revenue understates sales and hides what each platform really costs. Record gross order value as delivery revenue, put each deduction on its own line, then report margin after commission per platform.

---

Labour Cost as a Percentage of Sales

Labour is typically one of the two largest costs in F&B, alongside food, and it's rarely set up as a percentage of revenue split by outlet, channel or week. You see the payroll expense. You see the revenue. Connecting them, outlet by outlet, requires manual calculation.

A labour cost report that automatically calculates payroll as a percentage of total sales — and splits it by outlet, by week, or by revenue channel — gives operators a live view of one of their most important efficiency metrics. When labour creep starts, you see it in the report before it shows up in a bad monthly result.

---

Prime Cost: Food and Labour Together

Food cost and labour cost each tell half the story. Added together they make prime cost, the number operators tend to watch closest. A good report shows prime cost as a percentage of net sales, by outlet and by week, next to its two components, so you can tell whether a bad month is a purchasing problem, a rostering problem, or both.

You define once which accounts count as food, beverage, packaging and labour, and the report calculates it the same way for every outlet.

---

Functional Opex Breakdown

Not all operating expenses are equally useful lumped together. The difference between what you're spending on rent, payroll, marketing, and systems matters — both for understanding cost structure and for conversations with investors or partners.

A functional opex breakdown restructures your P&L into meaningful categories, regardless of how accounts are coded in Xero. The mapping logic sits in the report: account 430 might be "Utilities," but in your functional view it rolls up under Occupancy. You define those categories once, and the report applies them automatically every period.

---

Comparative Reporting: MoM, YTD, PY, Actual vs Budget

Xero can do some comparison natively, but the moment you want a proper side-by-side — this month vs. last month vs. same month prior year vs. budget, all in one view — you're outside what the standard reports handle well.

Custom comparative reports can pull all of those dimensions simultaneously. Month-on-month variance, year-to-date tracking, prior year comparison, and budget vs. actuals can all live in the same structured output. For operators reviewing weekly or monthly with their ops team, having that context in a single view changes the quality of the conversation. (Why the native budget vs actual report falls short.)

---

Mixed-Ownership Profit Sharing

Some F&B groups run venues with different ownership structures — a venue that's 50/50 with an operating partner, another that has a minority investor, a third that's wholly owned. Calculating each party's share of the profit at period end is usually a manual exercise done in a spreadsheet.

Custom reporting can encode those ownership splits and apply them automatically to each venue's net profit figure. Each owner sees their share. The underlying data stays in Xero. The calculation is consistent and auditable every time — not something that changes based on who built the spreadsheet that month.

---

Automated Monthly Board and Management Packs

This is where operational reporting and executive reporting meet. A well-structured F&B group should be able to generate a complete management pack — group P&L, location-level breakdowns, KPI dashboard, prior year comparisons, budget variances — with minimal manual effort at month end.

The key word is automated. That means the data flows from Xero into a structured format, the KPIs are calculated from live figures, and the pack is ready to send without anyone needing to rebuild it. It can also run on a schedule: the pack lands in the right inboxes on the 3rd of each month as a Google Sheet, with a one-click Excel download. For operators producing board packs manually, this often means several hours of work each month, per entity. Too often it's done by the most expensive person on the team.

Store-level detail (outlet-by-outlet performance) and group-level summary can coexist in the same document. Investors get what they need. The ops team gets their numbers. Nothing needs to be rebuilt.

---

The Common Thread

All of these use cases share the same underlying issue: Xero holds the data, but the reporting layer that makes it useful for F&B operators doesn't exist out of the box.

The businesses that solve this properly don't do it with more spreadsheets. They encode their business logic once — what a delivery channel looks like, how labour costs map to revenue, how ownership splits are applied — and let that logic run automatically every period.

If you're spending meaningful time at month end rebuilding reports that should already exist, Cheetah is worth a conversation.

---

Updated 20 September 2026: removed Deliveroo, which left Singapore in March 2026, made the intro evergreen, and updated the consolidation section for Xero Ultra. We also added guidance on stock adjustment, delivery settlements and prime cost, a note on GST InvoiceNow, and links to newer guides.