Restaurant Cash Variance Report Template: Expected vs Counted Drawer
A shift-level report for calculating expected drawer cash, recording the independent count, explaining differences and closing corrective actions.
Last verified: 2026-08-30
A restaurant cash variance report explains the difference between the cash the POS and authorised records say should be in a drawer and the cash physically counted. It does not start by blaming the cashier. It starts by rebuilding every cash movement: opening float, cash sales, cash refunds, paid-outs, deposits, drawer transfers, tips and closing count.
General internal-control guidance supports physical safeguards, transaction records, separation of custody and review, and periodic reconciliation. In restaurant operations, those controls work best at every custody change and day close. The report below preserves the equation, evidence, investigation and final approval.
Cash variance calculation
| Line | Calculation or source |
|---|---|
| Opening float | Signed opening count |
| Plus cash sales | Closed POS orders paid in cash |
| Plus other authorised cash in | Documented drawer transfer or approved receipt |
| Minus cash refunds | Approved POS refund records |
| Minus paid-outs | Authorised voucher, if the drawer policy allows them |
| Minus cash drops/deposits | Signed safe, bank or handover evidence |
| Equals expected closing cash | System total rebuilt from controlled components |
| Actual closing cash | Independent denomination count |
| Variance | Actual closing cash minus expected closing cash |
Copy-ready variance report header
| Field | Entry |
|---|---|
| Identity | Branch, terminal/drawer, shift, business date and report number |
| Custody | Opening cashier, closing cashier, manager and handover times |
| Systems | POS close/Z-report ID, offline orders, payment-terminal or MFS references |
| Counts | Opening count, expected cash, actual count and signed denomination sheet |
| Difference | Short/over amount, currency and detected time |
| Evidence | Voids, refunds, paid-outs, transfers, deposits, corrections and attachments |
| Cause/status | Confirmed cause, probable cause or unresolved |
| Closure | Accounting entry, corrective action, reviewer and closure date |
Count at every custody change
The person giving up the drawer and the person accepting it should count together where practical and sign the denomination total. If a drawer is shared, the report cannot reliably attribute a difference to one person. Use named logins and clear handover times, and avoid unrecorded access by managers, waiters or delivery staff.
Count away from customers with the drawer closed to new transactions. Record notes, coins and any approved cash equivalents separately. Do not include tips, owner money, petty cash or customer deposits unless the written drawer policy explicitly includes and identifies them.
Freeze the records before investigation
Capture the POS close report, order list, payment breakdown, voids, discounts, refunds, offline-sync status, paid-outs, drawer opens, cash drops and correction log. Preserve original timestamps and user IDs. Do not edit an order or create a voucher only to force the expected amount to match the count.
Where lawful and proportionate, preserve relevant access or camera evidence before it is overwritten. Restrict access to the investigation record and follow the restaurant's privacy and employment process. Evidence should clarify events, not create a public accusation.
Reconcile payment type before cash
Check whether an order paid by bKash, Nagad, card or marketplace was mistakenly closed as cash, or a cash order was recorded as another method. Compare external settlement or terminal references separately; those balances are not physical notes in the drawer. A payment-type error can create an equal cash variance and digital-settlement variance in opposite directions.
Review split or changed payments only if the POS supports and records them. Do not invent a split history from customer memory. Correct the payment classification through an authorised audit trail and preserve both the original and corrected record.
Check refunds, voids and paid-outs
Match every cash refund to the original order, approval, recipient and amount. A void before payment should not remove cash that was never received; a refund after cash receipt should. Confirm timing because a refund entered on the next business date can distort both shifts.
If the restaurant permits paid-outs from the drawer, require a numbered voucher and evidence. Otherwise move small expenses through the separate petty-cash process. Mixing purchases with sales cash makes cashier performance and expense reporting unreliable.
Verify cash drops, deposits and transfers
Each removal from the drawer needs amount, time, source drawer, destination safe or person, and signatures or system confirmation. Count sealed bags under the approved process and preserve bag or deposit IDs. A cash drop reduces the expected drawer but remains restaurant cash until properly handed over or deposited.
General control guidance emphasises safeguarding vulnerable assets and reconciling original logs to later deposits or accounting records. The person who prepared a deposit should not be the only person confirming the source log and final amount when staffing allows.
Sources for this section: GAO internal-control report on cash logs, segregation and reconciliation · GAO Internal Control Management and Evaluation Tool
Classify the variance without guessing
Do not select theft, cashier fault or system error without evidence. Keep probable and confirmed causes separate. A fair report can remain unresolved while additional records are checked. Management should apply employment policy and law consistently, with the employee able to explain relevant facts.
| Status | Use |
|---|---|
| Counting error corrected | Second controlled count found and documented the mistake |
| Timing difference | Transaction belongs to another shift/date and is traced |
| Payment classification error | Cash vs digital method corrected with audit trail |
| Documented process error | Refund, paid-out, drop or change handling failed |
| System/offline issue | Order or sync evidence explains the expected total |
| Confirmed loss/overage | Evidence supports final amount and accounting decision |
| Unresolved | Evidence is incomplete; investigation remains open |
Set corrective actions by cause
A counting mistake may need a clearer denomination sheet; payment misclassification may need POS training or permission changes; repeated no-sale drawer opens may need access restriction; late cash drops may need staffing or safe-location changes. Match the action to the confirmed process gap rather than using generic retraining for every event.
Give each action an owner, due date, test and reviewer. Reconcile the next comparable shifts after the change. If the variance repeats, reopen the root cause. Do not claim success because one shift happened to close at zero.
Post and close with accounting review
The accountant or authorised finance role should decide how the final shortage, overage, timing difference or correction is posted. Link the journal or expense reference to the variance report. IAS 7 is the broader statement-of-cash-flows standard; it does not replace transaction-level drawer controls or the restaurant's accounting policy.
Close only when the expected cash has been rebuilt, actual cash confirmed, difference classified, necessary accounting entry posted and corrective action assigned. Preserve unresolved reports on an ageing list. Reopening a closed report should create a revision history, not overwrite the original conclusion.
Sources for this section: IFRS Foundation: IAS 7 Statement of Cash Flows
Weekly cash-control review
Use trends to improve the process, but do not publish a universal acceptable variance rate. A zero variance can still hide control problems if transactions were edited or differences shifted to another account. Review both the result and how it was produced.
- Variance count and amount by branch, drawer and shift
- Shortages and overages shown separately
- Confirmed, probable and unresolved causes
- Payment-method corrections
- Refund, void and paid-out exceptions
- Late or unmatched cash drops
- Shared-drawer or permission issues
- Open corrective actions and repeat events
- Reports closed without independent review
- Unresolved items by age
How we calculated and verified this
The variance equation is an operating reconciliation template: opening drawer plus documented cash inflows minus documented cash outflows and drops equals expected closing cash; actual counted cash minus expected cash equals the variance. A restaurant must adapt the components to its POS, refund, deposit, tip, petty-cash and branch policies.
GAO sources support general reconciliation, safeguarding and segregation principles but are not Bangladesh restaurant law. No acceptable shortage percentage or automatic disciplinary threshold is supplied. Management must investigate evidence fairly and have its accountant approve posting and financial treatment.
A restaurant cash-variance report is a controlled reconstruction of the drawer, not a quick accusation. It connects the signed float, POS cash sales, authorised movements, actual count and evidence to a fair cause and corrective action.
Use the equation and report fields at every custody change and day close. Keep digital payments, petty cash, tips and customer deposits separate, and never create a backdated transaction merely to make the variance zero.
Related guides
- Restaurant Cashier Closing Checklist
- Restaurant Daily Sales Report Template
- Restaurant Day Close and Z-Report
- Restaurant Petty Cash Voucher Template
See this workflow in Rosuii: Review restaurant sales, payments, expenses and day-close reports in Rosuii
Sources checked
Frequently asked questions
How is restaurant cash variance calculated?
Does a cash shortage prove the cashier stole money?
Should bKash, Nagad or card totals be counted as drawer cash?
When should a restaurant count the drawer?
Can management create an expense voucher to remove a variance?
Run your restaurant on Rosuii
POS, menu, inventory, payroll and more — built for Bangladeshi restaurants.
Start free
