End-of-day cash reconciliation at a retail branch is not a financial exercise. It's a verification exercise. The goal is not to add up money — you can do that in your head — the goal is to prove that what the register says happened and what the cash drawer actually contains are the same number, or to document precisely how they aren't.
The Denomination Layer Nobody Wants to Log
The laborious part of any cash audit is the count-by-denomination step. Most staff want to skip straight to a total. This template doesn't permit that.
Eight denomination fields — $50 notes, $10 notes, $5 notes, $2 notes, $1 coins, $0.50, $0.20, $0.10 — create a granular physical count that cannot be faked by rounding. When a branch total comes out $2.20 short, knowing whether that variance is explained by one misread note or a pile of small coins tells the difference between a counting error and a process problem. A single $2 note misattributed as a $5 note produces a $3 discrepancy that looks exactly like three missing dollar coins in a summary total but has a completely different cause and a completely different remediation.
The Total cash collected $ field is a calculated field. It multiplies each denomination count by its value and sums them. This means the total is derived, not entered — a staff member cannot type in a total that disagrees with the individual counts. The arithmetic is enforced at the point of capture.
ST, CR, RA, PO — The Four Numbers That Determine Everything
The reconciliation logic lives in three calculated fields:
Expected Amt $ = ST (Sales Total) + RA (Receivable Accountable) − PO amt (Purchase Order amount). This is the theoretical cash that should be in the drawer based on the register's record of what happened during the day.
Printout vs Collection = Total cash collected − Expected Amt. This is the variance. Zero means clean. Non-zero means you have a conversation to have.
Cash less RA = Total cash collected − RA. This strips out receivables to show net collected cash, useful for branches where credit or account transactions partially offset the drawer balance.
The four source fields (ST, CR, RA, PO) are the only inputs that require judgment. Everything else is arithmetic. The template's value is that it makes the arithmetic transparent — every number that feeds into the variance calculation is individually visible and individually auditable.
The Branch Field Is Not Decoration
Two locations: Holland Dr 46 and Bedok North St 1, 217. The branch field is a choice field, which means it can be filtered. A manager reviewing a month of records doesn't read sixty entries — they filter by branch, sort by date, and look at the Status column (close vs. discrepancy) as a triage view before drilling into any specific entry's full denomination breakdown.
The Discrepancy status does not calculate automatically — it requires a human judgment call about whether a Printout vs Collection variance is explainable or flags a genuine problem. That distinction is not a bug. Not every non-zero variance is a discrepancy, and not every zero variance means the reconciliation was done correctly.
The image fields at the end exist for branches that photograph the physical count or print a register tape. The photograph and the denomination breakdown entered in the record exist independently — if someone photographs a different count than they logged, the inconsistency becomes discoverable.