Cash Handling Fundamentals: Investigating Discrepancies and Documenting Variances

1) Variance thresholds and escalation paths

A cash variance is the difference between the cash you should have (per system totals and required cash on hand) and the cash you actually have after balancing. Variances happen as shortages (less cash than expected) or overages (more cash than expected). Your goal is to respond consistently: confirm the variance, document it objectively, and escalate based on predefined thresholds.

Define thresholds (example policy)

Use clear, numeric thresholds so every cashier and supervisor responds the same way. Adjust the numbers to match your operation, but keep the structure.

Escalation paths (who to tell, when)

• Cashier → Shift lead: first notification once a variance exceeds the “minor” threshold or if you cannot resolve it after the first recount.
• Shift lead → Supervisor/manager: when variance exceeds the “moderate” threshold, when refunds/voids look unusual, or when policy requires a second person to verify.
• Manager → Finance/Loss prevention: for large variances, patterns across shifts, suspected fraud, or policy triggers (e.g., repeated shortages by the same drawer).

Professional standard: escalate based on the amount and the evidence, not based on assumptions about a person.

2) Step-by-step discrepancy troubleshooting

Troubleshooting should be repeatable. Use the same checklist every time so you don’t miss common causes. Work from the simplest checks to the most detailed reviews.

Discrepancy troubleshooting checklist (in order)

1. Pause and secure the work area
   • Stop nonessential activity at the drawer.
   • Keep cash in view; minimize handling by multiple people until you decide a second count is needed.
2. Recount the cash (same method you used initially)
   • Recount bills and coins carefully.
   • Confirm you included all compartments (including under the till insert if your setup allows items to slip beneath).
   • Confirm you didn’t double-count a bundle or skip a stack.
3. Recount using a different method
   • If you counted by denomination stacks, recount by making a running total on paper.
   • If you used a running total, recount by grouping into standard bundles (e.g., $25 or $100 bundles) and verifying each bundle.
   • Goal: catch “method bias” (the same mistake repeated the same way).
4. Review large bills and high-impact denominations
   • Confirm the count of $50s/$100s (or your highest denomination).
   • Check for stuck bills (two bills that feel like one).
   • Verify any “straps” or banded bundles match their label (do not assume).
5. Check drops and drop logs
   • Compare the physical drop receipts (if used) to the drop log entries and the system record.
   • Look for: missing drop entry, duplicate entry, wrong amount, wrong time, wrong drawer ID.
   • Confirm whether a drop was recorded but cash was not actually removed (or removed but not recorded).
6. Review refunds, voids, and corrections
   • Pull the transaction list for the shift (or the relevant window).
   • Focus on: high-dollar refunds, multiple voids, repeated corrections, and any manual price overrides (if applicable).
   • Verify each item has required approval/signature per policy and matches the receipt/customer documentation.
7. Verify starting float / beginning cash
   • Confirm the starting amount issued to the drawer matches the recorded amount.
   • Check whether the drawer was swapped, re-floated, or topped up mid-shift and whether that was documented.
   • Look for a common error: starting float recorded for Drawer A but issued to Drawer B.
8. Check for “timing mismatches”
   • Confirm the shift cut-off time used for reports matches the time you’re balancing.
   • Identify any late-posted transactions (e.g., a refund processed after the report window).
9. Second-person verification (when required)
   • Have a supervisor or designated verifier recount independently.
   • Both parties should sign the variance documentation if policy requires.

Quick diagnostic cues (what the pattern suggests)

3) Writing objective variance notes

Variance notes are not a story; they are a factual record that allows a supervisor, auditor, or future shift to understand what happened and what was checked. Write as if someone who was not present must reconstruct your steps.

Continue in our app.

You can listen to the audiobook with the screen off, receive a free certificate for this course, and also have access to 5,000 other free online courses.

Or continue reading below...

Download the app

What to include (minimum fields)

• What: shortage/overage amount and currency (e.g., “Short $12.00”).
• When: date, time, shift window, and when the variance was discovered.
• Where: store/location, register/drawer ID, terminal ID (if applicable).
• System expected vs. actual: expected cash amount, actual cash amount, and resulting variance.
• Actions taken: recounts performed, methods used, logs reviewed, transactions reviewed.
• People involved: who counted, who verified, who approved (names/IDs per policy).
• Outcome: resolved/unresolved; if unresolved, escalation and next steps.

Objective language: do and don’t

Variance note template (copy/paste)

Date/Time discovered: ____________   Shift: ____________   Location: ____________   Drawer/Register ID: ____________
Expected cash (per report): $__________   Actual cash (counted): $__________   Variance: Short/Over $__________

Counts performed:
1) Method: ____________  Result: $__________  Counter: ____________  Time: ____________
2) Method: ____________  Result: $__________  Counter: ____________  Time: ____________

Checks completed (mark and note findings):
[ ] Large bills verified (notes): ____________________________________________
[ ] Drops reviewed (log/receipts) (notes): ___________________________________
[ ] Refunds/voids reviewed (notes): _________________________________________
[ ] Starting float verified (notes): ________________________________________
[ ] Other (notes): _________________________________________________________

Escalation/approvals:
Notified: ____________ at ____________   Supervisor verification: Yes/No

Status:
Resolved: Yes/No   If unresolved, next step: ________________________________

4) Maintaining integrity and avoiding blame

How you respond to a variance affects trust, morale, and the quality of the investigation. Professional handling means protecting the facts and protecting people from assumptions.

Integrity standards during an investigation

• Do not “force” the drawer to balance by adding/removing cash to make numbers match.
• Do not delay reporting to “see if it fixes itself.” Report per threshold rules.
• Limit handling of the cash during troubleshooting; document who touched the drawer.
• Keep documentation complete: attach relevant receipts, approval slips, and system printouts per policy.
• Separate facts from hypotheses: record what you observed; if you suspect a cause, label it as “possible” and support it with evidence.

Blame-free communication scripts

Use neutral phrasing that focuses on process and verification.

• To a supervisor: “I’m showing a $12 shortage after two counts. I’ve verified large bills and checked the drop log; next I’m reviewing refunds/voids. Can you perform an independent recount per policy?”
• To a coworker who used the drawer earlier: “We’re reconciling a variance and need to confirm the timeline. Do you recall any drops, refunds, or unusual transactions during your window?”
• If a customer dispute is involved: “Let’s review the receipt and the tender recorded so we can confirm the amount processed.”

5) Corrective actions to prevent repeat issues

Once the variance is documented (resolved or not), the next step is preventing recurrence. Corrective actions should match the likely cause and be measurable.

Process adjustments (examples)

• Standardize recount triggers: require a second-method recount for any variance above a set amount.
• High-denomination handling rule: separate and face large bills immediately; verify count before placing in drawer.
• Drop discipline: require drop receipt attachment to the log entry; verify drawer ID and amount before finalizing the entry.
• Refund/void checklist: ensure approvals and supporting documentation are consistently captured and filed.
• Shift handoff clarity: document exact time of drawer handoff and any mid-shift adjustments.

Refresher drills (skill reinforcement)

• 10-minute recount drill: practice two different counting methods on the same cash set and compare results.
• Variance simulation: intentionally introduce a known $5 or $20 discrepancy in a training drawer and have learners follow the troubleshooting checklist.
• Documentation practice: write variance notes from a sample scenario; supervisor scores for objectivity and completeness.

Supervisor review and pattern tracking

• Trend review: track variances by drawer ID, shift, daypart, and transaction type (refunds/voids/drops).
• Coaching plan: if a pattern appears, schedule targeted observation (e.g., change-making under rush conditions) and retraining.
• Control check: verify whether procedures are realistic during peak times; adjust staffing or workflow if the process is routinely bypassed.

6) Case studies: complete a discrepancy report from evidence

Read each case, then complete the discrepancy report fields. Focus on: (1) expected vs. actual, (2) steps taken, (3) evidence reviewed, (4) escalation and status.

Case Study A: Small shortage with clean logs

Evidence:

• Drawer/Register ID: R2
• Shift: 14:00–22:00
• Expected cash (report): $1,248.50
• Actual cash (count 1): $1,246.50
• Actual cash (count 2, different method): $1,246.50
• Large bills verified: counts match report denominations
• Drops: none
• Refunds/voids: 0 refunds; 1 void for $3.99 with approval recorded
• Starting float verified: matches issuance record

Task: Write objective notes and decide escalation based on an example threshold table.

Case Study B: Overage that matches a refund amount

Evidence:

• Drawer/Register ID: R5
• Shift: 09:00–17:00
• Expected cash (report): $980.00
• Actual cash (count 1): $1,005.00
• Actual cash (count 2): $1,005.00
• Variance: +$25.00
• Refunds: one refund for $25.00 shows tender type = cash in system; customer copy indicates refund should have been to card; manager approval present
• Drops: one $300 drop logged and receipt attached; amounts match
• Starting float verified: matches issuance record

Task: Document the facts and list the specific record(s) you would attach or reference.

Case Study C: Shortage with a drop log mismatch

Evidence:

• Drawer/Register ID: R1
• Shift: 16:00–00:00
• Expected cash (report): $1,420.00
• Actual cash (count 1): $1,320.00
• Actual cash (count 2 by supervisor): $1,320.00
• Variance: -$100.00
• Drop log: entry shows $500 drop at 20:15
• Physical drop receipt found: $400 at 20:15 (same drawer ID)
• Safe count (if available): includes a $400 bundle labeled R1 20:15
• Refunds/voids: normal volume; approvals present
• Starting float verified: matches issuance record

Task: Write variance notes that clearly explain the mismatch without blaming. Identify the likely correction needed (recording error vs. cash missing) based on evidence.

Case Study D: Repeated small shortages (pattern problem)

Evidence:

• Drawer/Register ID: R3
• Last 10 shifts: 7 shortages between $1.00 and $4.00; 3 balanced
• Shortages occur mostly during peak hour (12:00–13:00)
• No unusual refunds/voids; drops consistent
• Second-person recount confirms shortages (not a counting-only issue)

Task: Propose corrective actions that focus on process and training, and document them as next steps (not as accusations).