A receipt confirms what the customer ordered and paid. Reconciliation confirms that the restaurant’s orders, refunds, provider statements and bank deposits agree. They are connected, but they solve different problems.
This guide is the starting point for an independent UK takeaway that wants a reliable record from checkout to bookkeeping. It does not assume that every customer receipt is a VAT invoice, that every bank deposit equals sales, or that one dashboard contains the whole truth.
Build one traceable record for every order
Every completed order should be traceable through a stable reference shared across the systems that handle it. The record should connect:
- the customer order and channel;
- delivery or collection details;
- the amount presented at checkout;
- payment status and transaction reference;
- the kitchen ticket or KDS record;
- refunds, redeliveries or adjustments;
- the provider or marketplace statement;
- the settlement reaching the bank;
- the bookkeeping entry.
Where systems use different identifiers, maintain a mapping. Staff should not have to search by customer name, card amount and approximate time whenever a discrepancy occurs.
Customer receipt, payment receipt and VAT invoice are not identical
| Document | Main purpose | What to verify |
|---|---|---|
| Order confirmation | Shows that the ordering system received or accepted an order | Order status, items, fulfilment method, promised time and total |
| Payment confirmation | Shows the result of a payment attempt | Authorised, failed, pending or refunded; provider reference |
| Customer receipt | Gives the customer a readable record of the transaction | Business identity, order details, total, payment method and contact route |
| VAT invoice | Supports VAT accounting where the VAT invoicing rules apply | Required HMRC information and the correct invoice format |
| Marketplace statement | Explains gross orders, deductions and payout | Commission, promotions, refunds, adjustments, tax documents and settlement |
A well-designed digital receipt can also meet the requirements of a VAT invoice where appropriate, but it does not become one merely because it was emailed or contains a VAT number. A retail takeaway should confirm its VAT invoicing process with its accountant and current HMRC guidance.
Design receipts around the customer’s real questions
A useful receipt should make it easy to answer:
- What did I order?
- Was it delivery or collection?
- What time was promised?
- What was the full price?
- Which payment method was used?
- Was a discount, tip or service charge applied?
- How do I report a problem?
Do not put unnecessary card data on the receipt. A masked reference may help identify the payment, but full card details, security codes and authentication data should never appear.
Choose a receipt-delivery model
| Method | Useful when | Main control |
|---|---|---|
| Checkout page and account history | The customer can retrieve the order without giving another contact detail | Make the record available after payment and after any refund |
| A durable copy is useful for direct orders | Use the address for the service message only unless marketing rules are separately met | |
| SMS link | The operation already uses mobile updates | Keep the message clear, secure and distinguishable from marketing |
| Printed receipt | Collection, cash or kitchen handover needs a physical record | Avoid relying on paper as the only accounting record |
| Marketplace record | The platform controls the customer-facing transaction history | Retain the restaurant-side order and payout evidence as well |
Reconcile in three layers
1. Order-level reconciliation
Match each completed order to a valid payment outcome. Review duplicates, payments without orders, orders without payments, partial refunds and manual amendments.
2. Settlement reconciliation
Match provider or marketplace statements to bank deposits. A net payout may contain many orders and several deductions, so preserve the underlying statement rather than recording only the bank amount.
3. Accounting reconciliation
Confirm that gross sales, VAT treatment, discounts, tips, service charges, refunds, commissions and other fees are recorded in the correct categories. Escalate tax treatment to the accountant rather than inferring it from a provider label.
Daily control
- Count completed orders by channel.
- Compare order totals with payment totals.
- Review failed and unknown-status transactions.
- Confirm refunds and voids raised during the shift.
- Match card-terminal batches and cash to the till.
- Record unexplained differences with an owner and target date.
Settlement-period control
- Download the provider or marketplace statement before access expires.
- Match the expected payout to the bank.
- Separate commission, delivery charges, promotions, refunds and adjustments.
- Check whether a previous-period correction has been included.
- Confirm that disputes and chargebacks are reflected once, not twice.
- Post the correct gross and net figures to bookkeeping.
Discrepancies that deserve immediate investigation
| Symptom | Likely areas to check | First action |
|---|---|---|
| Customer charged, no kitchen order | Gateway callback, ordering platform, duplicate protection | Search by transaction and order reference before recreating the order |
| Completed order, no payment | Cash status, terminal payment, manual override, integration error | Confirm the actual payment route and staff action |
| Bank payout lower than expected | Fees, refunds, reserve, correction, failed settlement | Rebuild the payout from the statement line by line |
| Refund shown twice | POS adjustment plus gateway refund, marketplace correction | Confirm which system moved the money and reverse only the duplicate record |
| VAT report differs from sales report | Tax mapping, discounts, delivery charges, zero-rated items, reporting period | Stop manual balancing and inspect the underlying tax configuration |
Retention and access
Keep records in a format that can be retrieved, read and exported after a supplier change. Restrict financial exports to staff who need them, use individual accounts, and preserve an audit trail for refunds and corrections.
HMRC generally requires VAT records to be kept for at least six years, subject to the detailed rules and any applicable exceptions. VAT-registered businesses are also within Making Tax Digital for VAT unless exempt. Confirm the retention period for other taxes and employment records with the appropriate adviser.
Implementation checklist
- One stable order reference across ordering, payment and POS records.
- Receipt content tested for delivery, collection, discounts, tips and refunds.
- Service receipts kept separate from marketing consent.
- Daily order-to-payment check assigned to a named role.
- Provider statements retained and matched to bank deposits.
- VAT and accounting mappings reviewed professionally.
- Export and retention tested before signing a long-term supplier contract.
- Documented recovery route for payments without orders and orders without payments.
Related guides
- Payments — the main guide for the wider topic.
- How to Reconcile Online Orders, Payments and Refunds — a detailed next step for putting this guidance into practice.
- How to Set Up Digital Receipts — a detailed next step for putting this guidance into practice.
- Payment Security and Compliance — a closely related operational control to review alongside this page.
- Refunds and Chargebacks — a closely related operational control to review alongside this page.
- Record Keeping for Tax and Compliance — a connected decision that can change the recommended approach.
Official guidance checked
- HMRC: VAT guide, including VAT invoice requirements
- HMRC: record keeping for VAT
- GOV.UK: keeping VAT records
- ICO: planning direct marketing, including e-receipt data
Guidance checked: 24 July 2026. VAT status, retail-scheme treatment, retention requirements and supplier statement formats must be checked for the individual business.
