How to Record a POS Void or Cancelled Order Before Payment Is Collected
Reversing a sale that was incorrectly entered in the POS before any payment was received.
| Account Name | Type | Debit ($) | Credit ($) |
|---|---|---|---|
| Food Sales Revenue | Revenue (-) | 50.00 | - |
| Sales Tax Payable (VAT Output) | Liability (-) | 8.00 | - |
| Cash in Hand | Asset (-) | - | 58.00 |
💡 Accountant's Note
A void cancels a transaction as if it never happened. It is a direct reversal of the original entry. This is different from a refund, which happens after payment has been collected.
Practitioner & Systems Framework
💻 ERP Architecture
POS voids should require manager PIN authorization and be logged with a reason code (wrong item, customer cancelled before cooking, entry error). The void reversal entry is automatically generated by the POS and should sync to the GL via the daily sales import. Review the void log daily — excessive voids without clear reasons may indicate internal fraud.
⚠️ Audit Flags
High void rates on the POS are a major red flag for auditors and forensic accountants — voiding a sale after collecting cash and pocketing the cash is a classic restaurant fraud. Auditors will request the complete void log and verify that no cash was received for voided transactions by cross-referencing the kitchen order receipts (KOTs) to the void records.
📄 Required Documentation
POS void log with manager authorization, reason code analysis, kitchen order ticket (KOT) confirming food was or was not prepared, and daily cash count confirming no cash was collected on voided items.
Automate this entry with the JEH Accounting Suite
Stop doing manual entry. Our VBA-powered ERP automatically generates your ledgers, Trial Balance, and Financial Statements.
No Subscriptions. Own your data.
Expert Analysis by Qusai Ahmad
General Accountant Supervisor & IFRS Specialist
Specialized in SAP GUI automation and Middle Eastern tax compliance. Building digital tools for the next generation of finance leaders.