Why F&B accounting is different from normal SME accounting

A consulting firm and a café both produce P&Ls every month. Both file Form C-S and pay corporate income tax. Both do bank reconciliations. From the outside, they look like the same accounting problem.

They're not. The accounting setup that works for a desk-based business — a small consultancy, a software firm, a B2B services business — silently fails at F&B. By the time the failure surfaces, the books are months out of date, the operator has stopped trusting the numbers, and decisions are being made on instinct.

This piece walks through what specifically breaks, and what a properly designed F&B accounting stack looks like instead.

Why the standard setup fails F&B

Five structural differences. Each one is manageable on its own. Together they overwhelm a setup that wasn't designed for them.

1. Transaction volume is orders of magnitude higher

A small consultancy might generate 30–80 ledger transactions a month: invoices out, supplier bills in, payroll, a few expense items. A single F&B outlet at modest scale will easily generate 2,000–6,000 transactions a month — every till transaction, every card settlement, every supplier delivery, every petty cash purchase, every delivery platform payout, every staff meal. Manually reconciling that is not a bookkeeping problem; it's a stack-design problem.

2. Multiple payment channels with different timings

The standard SME has one or two payment channels — bank transfer in, bank transfer out. An F&B operator has cash, multiple card terminals, two or three delivery platforms (each with its own commission structure and payout cadence), QR payments via PayNow / SGQR, possibly gift cards, possibly a separate catering / events settlement track.

Each one settles into the bank on a different schedule. Reconciling them together in a single pass — which is what a desk-business setup does — produces noise that can take days to unpick.

3. Cash moves quickly and visibly

For a service business, cash is a slow variable: invoices go out, payments come in 30–60 days later, the bank balance changes weekly. For F&B, cash position can shift materially day-to-day — a slow Tuesday, a big catering payout, a supplier prepayment, payroll going out, a delivery platform settling. An owner who can't see cash live is flying blind.

4. Cost of goods sold actually moves

A consulting firm's “COGS” — direct labour on a project — is mostly stable month to month. An F&B operator's COGS moves daily: food and beverage cost per dish shifts with supplier pricing, portion control, waste, theft, and menu mix. A monthly stock-take is the minimum, but it only catches the damage a month after it happened. The standard accounting setup surfaces COGS once a year at audit. That's 11 months too late.

5. Inventory and labour are the two biggest cost lines

For most service businesses, the two big cost lines are rent and salaries — both relatively stable. For F&B, it's inventory (food and beverage) and labour (kitchen staff, front-of-house, service charge). Both move. Both need visibility at a finer cadence than annual financials give you. Both demand integrations the standard SME setup doesn't come with.

What an F&B-designed stack looks like

The fixes aren't exotic. They are specific.

Chart of accounts cut by outlet and channel

The single most consequential design decision. Your chart of accounts has to let you see revenue and cost by outlet and by channel— not just consolidated. Outlet A's delivery platform revenue is different from Outlet B's; their food costs, labour ratios, and rent structures are all different.

In Xero, this is a combination of tracking categories + a structured chart of accounts. Done at setup, it's free; done retrofitted, it's a multi-week cleanup.

POS data flowing in daily, reconciled by channel

POS exports — sales, voids, refunds, discounts, channel breakdown — should land in your accounting system daily. Not as a single line called “daily sales” but structured so each channel can be reconciled against its own settlement (cash to till, card to bank settlement, delivery platform to platform payout).

A live cash position, not month-end

Bank feeds wired to all operating accounts, refreshed at least daily. An owner dashboard that shows current cash across accounts, expected payouts in the next 7 days, fixed costs due in the next 14 days. The bank balance is not the cash position — receivables in transit and known outgoings have to be in the same view.

COGS visibility monthly, with discipline

Inventory management connected to POS and accounting. End-of-period stock-take inputs that produce a monthly COGS figure by outlet. Variance analysis when COGS drifts. This requires operational discipline from the team — stock-takes have to actually happen — but the software side is straightforward.

Labour visibility at the level it actually breaks

Manpower cost broken down by outlet, role, and shift. Connected payroll feeding into the dashboard. Service charge / tips treated correctly if applicable. Overtime visible before it becomes a quarter-end shock.

Receipts captured at source

The single biggest drag on F&B month-end close: paper receipts living in folders, photos sitting in WhatsApp groups, supplier invoices forwarded to the manager's personal inbox. The fix is capture-at-source — automatically routed from phone, email, or messaging into the ledger, classified, attached. We use a named AI agent (the Receipt Catcher) for this; the discipline is what matters more than the specific tool.

What a clean F&B P&L looks like

When the stack is designed properly, an F&B operator can answer these questions in under a minute on any day of the month:

• What's my current cash position across all outlets and accounts?
• Which outlet is most profitable this month so far?
• What's my food cost as a % of revenue, by outlet?
• What's my labour cost as a % of revenue, by outlet?
• Are any delivery platform payouts running late?
• Are any supplier invoices overdue or approaching due?
• What's my GST exposure for the current quarter?

None of these are exotic questions. They're the basic operating decisions an F&B owner makes constantly. A back office that can't answer them on demand is a back office that's costing the operator decision speed every single week.

If you're running F&B and your accounting setup wasn't designed for the operating reality above, talk to us. Most of the value is on the table the first time it's designed properly.

Common questions about F&B accounting in Singapore

— The Acuitas team