Xero ships with a default setup that's designed for a generic SME — a small consulting firm, a B2B services business, a low-transaction operation. Drop a restaurant into that default and the books drift inside the first three months: POS sales don't reconcile to bank deposits, delivery platform commissions hide inside a single “Sales” line, food cost gets calculated annually instead of monthly, labour ratio isn't visible at the outlet level.
This piece walks through what a Singapore restaurant Xero should look like — at the chart-of-accounts level, at the integration level, and at the operating-cadence level.
Chart of accounts: outlet × channel × category
The core design decision. For a restaurant operating multiple outlets across multiple channels (dine-in, delivery platforms, catering), three dimensions need to be cut independently:
- The chart of accounts handles what: food revenue, beverage revenue, COGS-food, COGS-beverage, packaging, rent, labour, etc.
- Tracking category 1 handles where: Outlet A, Outlet B, Outlet C, HQ.
- Tracking category 2 handles how: Dine-in, Delivery (GrabFood), Delivery (Foodpanda), Catering, Retail.
With this structure, every report becomes a slice of the same underlying data. We've covered the design principles in detail in our piece on designing a chart of accounts for an F&B business.
POS integration: don't accept the default
The right POS integration imports daily sales into Xero structured by channel and outlet, with tax codes applied correctly. The wrong integration dumps a single line a day called “POS sales”.
Common POS systems in Singapore F&B (StoreHub, Lightspeed, FoodZaps, EasyEat, MegaPOS, Wynn POS) each have their own Xero connectors with different levels of structure. The defaults rarely cut sales by channel out-of-the-box; expect to configure mappings deliberately.
The right test: at end of month, can you pull a Xero report showing “dine-in revenue at Outlet B for the month” without exporting to a spreadsheet and slicing manually? If no, the integration isn't structured properly.
Delivery platform reconciliation
The single most operationally complex part of restaurant Xero setup. Each delivery platform (GrabFood, Foodpanda, Deliveroo, Chope) has:
- A different payout cadence (weekly is typical; some offer faster payouts at a fee)
- A different commission structure (typically in the 20-35% range)
- Promotional rebate flows (operator-absorbed vs platform-absorbed promos need separate handling)
- Refund and adjustment flows that hit the next payout, not the original transaction
The Xero structure needs revenue accounts for gross platform sales, expense accounts for platform commissions, and reconciliation rules that match settlement deposits against platform statements. We walk through the full pattern in our piece on reconciling POS, cash, card, and delivery platform sales.
Bank feeds and reconciliation rules
Restaurant cash flow moves fast and across many channels — card settlements at T+1 or T+2, cash deposits irregularly, platform payouts weekly, supplier autopayments throughout the month. Direct bank feeds (Xero supports DBS, OCBC, UOB, and others) bring all this into Xero automatically.
Reconciliation rules should be coded for:
- Recurring supplier payments (water, electricity, internet, software subscriptions)
- Payroll runs (biweekly or monthly batches)
- Card settlement deposits per terminal / per outlet
- Platform settlement deposits per platform
- CPF payment runs
- GST payment runs (if registered)
With rules in place, the bookkeeper's daily work drops to reviewing the agent's draft and approving — the manual reconciliation is largely eliminated.
Payroll integration
Restaurant labour is variable, multi-role, and often part-time-heavy. Connecting a payroll platform (Talenox, Payboy, HReasily, Justlogin) into Xero brings:
- Payroll run posted to Xero with proper GL coding (by role, by outlet via tracking categories)
- CPF accruals calculated and posted correctly
- Service charge distribution (if applicable) flowing through the right accounts
- IR8A and other year-end reporting prepared
The integration is what makes labour cost visible by outlet weekly, which is the operating metric that drives most restaurant rostering decisions.
Inventory integration
For F&B, the real cost of goods sold moves daily. Monthly stock-takes are the minimum; integrated inventory management (often via a POS-adjacent inventory module or a dedicated tool like MarketMan) is what makes COGS visible continuously.
The pattern: stock movements feed inventory; inventory feeds Xero via a scheduled journal; the bookkeeper reviews the monthly journal at close. The owner sees COGS as a percentage of food revenue refreshed within days of close, not within months.
Restaurants that don't do this run their margin blind for ten months of the year. The inventory integration is the single most under-invested layer in most F&B Xero setups we inherit.
GST configuration
For GST-registered restaurants:
- GST tax codes set up at chart-of-accounts level (revenue accounts default to standard-rated; COGS-food / COGS-beverage default to standard-rated input where supplier is GST-registered)
- Per-supplier GST defaults so coding is automatic
- GST F5 reconciliation each quarter against POS daily totals to catch coding drift early
- InvoiceNow setup ahead of 1 April 2026 if voluntarily GST-registered (mandatory from that date for voluntary registrants)
Restaurant GST is one of the more error-prone areas in SG SME accounting — the volume of transactions and the mix of GST-registered and non-registered suppliers creates opportunities for misclassification. Per-supplier defaults at setup eliminate most of the drift.
Owner reporting cadence
What a properly-set-up restaurant Xero produces:
- Daily: cash position, daily revenue by outlet
- Weekly: labour cost ratio per outlet, delivery platform reconciliation, exception feed
- Monthly: P&L by outlet, prime cost, gross margin, full management report
- Quarterly: trend analysis, GST F5, quarterly review
The dashboard on top of Xero is what surfaces this for the owner. See our F&B owner dashboard demo for what it can look like.
Common questions about Xero for restaurants
Which Xero tier do I need for a restaurant?
Standard is the minimum for any operating restaurant — the Starter tier's monthly transaction allowance runs out fast. Premium becomes worth it when you start transacting in multiple currencies (international suppliers, etc.) or need advanced features.
How long does a Xero setup for a restaurant take?
For a single-outlet restaurant with no existing accounting system: about a week of configuration plus a month of running-in. For a multi-outlet group with existing data to migrate: two to four weeks of configuration plus a parallel-run period.
Can I run a restaurant on Xero without a bookkeeper?
Technically yes; practically no. With proper integrations, the manual work is small — but somebody still needs to handle exceptions, review agent drafts, run month-end, file GST. An owner-operator with finance background can do this for a small single outlet; multi-outlet operators benefit from a dedicated bookkeeper or external service.
What if my POS doesn't integrate cleanly with Xero?
Three options: switch POS (rarely worth it just for accounting), use a middleware connector that bridges the gap (extra cost, extra complexity), or accept a daily manual export with proper structure. For single-outlet operators, the manual export is often workable. For multi-outlet, switching POS to one with cleaner Xero integration is usually the right call during the next refresh cycle.
Xero done right disappears into the restaurant's operating rhythm. The owner sees the numbers when they need to; the bookkeeper closes the month on time; the tax filings happen on calendar. Done badly, Xero is the friction. The design decisions above are what flip which side of that you sit on.
— The Acuitas team