A POS exports a pile of transactions. The accounting system wants a daily sales journal. The gap between those two is where most hospitality bookkeeping goes wrong. Structure the journal right once, and the rest of the rhythm falls into place.

Why POS exports aren’t what the books need

Every hospitality operator who has ever tried to set up their own books has run into this moment: the POS can export transactions, but dumping those rows into Xero or QuickBooks does not produce a clean P&L. Individual transactions bloat the ledger, bank feeds stop matching, and reporting gets slower instead of faster.

The gap is a mismatch of shape. The POS knows every order, every modifier, every payment method. The accounting system wants one daily total per revenue channel, with tax and tips broken out, and a bank-reconcilable deposit total that matches what actually hit the account. Those are different views of the same data, and the translation between them is what pos to accounting restaurant setups live or die on.

In our experience, roughly half the operators we meet are entering POS data one of two wrong ways. Either they’re importing transaction-by-transaction (slow, noisy, bank-feed-breaking) or they’re booking only the deposit total (which loses VAT, tips, and channel margin). This guide covers the middle path, a daily sales journal that works.

What a daily sales journal should look like

One journal per day, per outlet, with the following components:

Daily Sales Journal, 2026-04-18

Revenue (gross, by channel)
  Food revenue: Dine-in            1,240.00
  Food revenue: Takeaway             180.00
  Food revenue: Delivery (Talabat)   420.00
  Beverage revenue: Dine-in          360.00
  Service charge                      58.00
  Total revenue (incl. tax)        2,258.00

Tax (collected)
  VAT / GST output                   107.52

Tips collected (pass-through)
  Tips payable                        78.00

Channel settlements
  Cash received                      410.00
  Card merchant (gross)            1,340.00
  Talabat receivable                 420.00
  Delivery tips payable to staff      78.00

Adjustments
  Discounts                          -45.00
  Comps (cost of food comped)        -18.00

Each line is a dollar-level total, not a transaction stream. Tax is broken out separately. Tips are in their own pass-through account. Payment channels land in their own accounts (cash, card clearing, platform receivable) so the bank reconciliation on each channel is mechanical.

This is the shape that makes a restaurant books setup actually work. The POS provides the numbers; the accounting system only needs the totals in this structure.

What a raw POS export looks like (and why it’s the wrong input)

Most POS systems will happily export a CSV of every transaction with columns like order_id, datetime, item, qty, price, tax, tip, payment_method. That is the wrong shape to push into accounting.

Reasons not to use the raw export directly:

  • Volume. A 100-cover cafe logs 300-500 transactions a day. That’s 100,000 to 150,000 lines per outlet per year. The accounting ledger does not need that detail; it needs the daily summaries. Reports slow down, reconciliations take longer, and journal navigation becomes impossible.
  • Double-counting. Each order has food, tax, tip, and payment components. Naively booking all of them creates tax and tips entries on both the sales side and the payment side.
  • Bank-feed break. The accounting system expects bank deposits to match a cash receipts entry or a card-payout entry. If every transaction is its own deposit, the bank feed cannot match, and every reconciliation becomes manual.

The POS export is the source of truth for operational analysis (item mix, hourly patterns, shift performance). The daily summary is what the books need. Most POS systems provide both. Use the right one for each job.

How each channel lands in the books

A hospitality business typically has four or five payment channels. Each has its own path from the daily sales journal to the bank:

  • Cash. Daily cash takings go to a cash-on-hand account. Deposits to the bank clear the cash account. The reconciliation is daily cash count vs the books.
  • Card. Card transactions go to a card-clearing account (or card-receivable). The card merchant payout (typically T+1 or T+2) clears the clearing account against the bank deposit. Fees are a separate expense line.
  • Delivery platforms. Gross revenue to sales, commission to expense, VAT flows to the right tax accounts, net payout to the platform receivable. When the platform deposit arrives, it clears the receivable. See how to reconcile Talabat revenue and how to reconcile Deliveroo and Uber Eats for the per-platform mechanics.
  • Catering / events (pre-paid). Deposits from customers go to an unearned revenue liability until the event happens, then release to revenue when it does.
  • Account sales (corporate clients). Invoice goes to accounts receivable; payment clears it.

Pos reconciliation is what connects this structure to the actual bank. Done correctly, every daily sales journal ties out to the bank within a day or two. Done incorrectly, the book balance drifts from the bank balance and nobody quite knows why.

Tax handling

Hospitality tax hits every daily journal, and the structure determines whether the tax return is mechanical or reconstructive.

  • VAT / GST collected (output tax) goes to a tax-payable liability on every sale.
  • VAT / GST on discounts reverses proportionally. A 10% discount on a 100 bill reduces VAT / GST by the same 10%.
  • Tips aren’t taxable revenue in most hospitality jurisdictions (UAE, Australia). Keeping them separate from the revenue account avoids inflating the tax base.
  • Service charge is usually taxable when listed separately on the bill (VAT and GST both treat it as part of the service fee for the meal). Book it as its own revenue line with tax applied.

The daily sales journal collects the tax portion into the payable liability automatically. The quarterly VAT return or BAS becomes a sum of those daily postings, not a rebuild from raw POS data.

Tips handling

Tips handling is the detail most operators quietly get wrong. The rule:

  • Tips are not revenue. They’re a pass-through liability from customer to staff.
  • Book tips collected to a tips-payable liability, not to sales.
  • When tips are paid out to staff (via payroll, cash, or whatever mechanism), the liability clears.
  • Tips through delivery platforms flow the same way: into the platform receivable first, then out to the tips-payable account, then to staff.

Tips booked as sales inflate the revenue line by ~5-15% depending on the venue. That flows through to VAT, GST, BAS, and every percentage-based metric in the P&L (food cost %, labour %, etc.). It’s a systemic distortion.

The daily rhythm

A clean pos to accounting restaurant rhythm runs daily, not weekly:

  1. End of day. POS generates the daily sales summary. Someone (owner, manager, or automated integration) captures the daily sales journal into the accounting system.
  2. Next morning. Cash from the prior day is counted against the POS cash total. Any variance is logged and investigated.
  3. Each card-payout day. Card merchant deposit hits the bank, clears the card-clearing account.
  4. Each platform-payout day. Platform deposit hits the bank, clears the platform receivable.
  5. Weekly. Bank reconciliation ties everything together. All four channels should clear against their respective accounts; anything that doesn’t is an investigation item.

When this holds, month-end close is a 30-minute review. When it doesn’t, month-end becomes a multi-day reconstruction because every reconciliation has drifted.

Common mistakes

  • Importing raw POS transactions. Too much detail, breaks bank feeds, slows everything down.
  • Booking only the deposit total. Loses VAT, tips, and channel margin visibility.
  • Skipping the tips-payable account. Inflates sales and distorts tax.
  • Lumping all card transactions into one “Sales” line. Loses the ability to see channel mix.
  • Not reconciling daily cash. Cash variances compound fast; catching them daily is easy, monthly is nearly impossible.
  • Manual re-entry. Most modern POS systems can integrate with Xero or QuickBooks directly. Manual entry is a stopgap, not a steady state.

Daily sales journal checklist

  • One journal per day per outlet, not per transaction
  • Revenue split by channel (dine-in, takeaway, each platform, catering, retail)
  • Tax (VAT / GST) broken out to its own payable account
  • Tips in a pass-through liability, never in sales
  • Payment channels in separate clearing / receivable accounts
  • Discounts, voids, and comps recorded correctly
  • Daily cash count reconciled against POS cash total
  • Card and platform payouts clear their respective accounts when they arrive
  • Weekly bank reconciliation proves everything tied

Next step

If your POS data is landing in the books one transaction at a time, or only as a weekly bank-deposit lump, the free books health check is the practical first step. We look at how sales are actually flowing from the POS to the ledger and what a clean daily journal should look like for your setup.

Last updated: April 2026.