Small cash, same controls
It’s tempting to treat petty cash informally precisely because the amounts are small - a $10 disbursement doesn’t feel like it needs the rigor of a large payment. But the same three controls that protect any cash apply here too, just at a smaller scale: someone accountable for custody, a real-time log of every movement, and a periodic audit that actually happens.
The fixed-fund method
Establish a set amount for the fund - enough to cover a normal period of small purchases without running dry, not so much that a loss would be significant. When it’s replenished, it’s always topped back up to that same fixed amount, which makes tracking simple: the fund total plus receipts on hand should always equal the original fixed amount.
| Component | What it should equal |
|---|---|
| Cash remaining in the box | Fixed fund amount minus total of receipts not yet replenished |
| Cash + receipts on hand | The original fixed fund amount, always |
Reconciling the fund at any moment
Custody: one person, one key
Who holds it, and how
- Cash is kept in a locked drawer or box, not an open drawer
- Access is restricted to one named, trustworthy person - not shared broadly
- That person is also who signs off on each disbursement, creating clear accountability
- A backup custodian is named for when the primary is out - handoffs should be logged, not silent
Logging: at the moment, not from memory
Every disbursement gets logged immediately - date, amount, purpose, and who approved it - with the receipt attached to the entry, not filed separately "for later." A log reconstructed at week’s end from memory is where errors and gaps quietly creep in; a log built in real time at the moment of each disbursement doesn’t have that problem.
Replenishment is a built-in checkpoint
Because the fund only gets refilled when it runs low, replenishment naturally forces a review moment - every receipt since the last top-up gets checked against the log before new cash goes in. Use that moment deliberately; don’t just refill on request.
Audits: unannounced beats scheduled
A scheduled monthly count catches genuine carelessness - a missing receipt, a math error. An unannounced spot-check is what actually deters deliberate misuse, because nobody can prepare for it in advance. A healthy petty cash system uses both: routine review at replenishment, and the occasional surprise count.
Setting up petty cash controls from scratch
- 1
Set the fixed fund amount
Based on a normal period’s worth of small purchases - not arbitrarily large.
- 2
Name the custodian and backup
One accountable person, one clearly designated backup.
- 3
Build the log template
Date, amount, purpose, approver, receipt attached - every field, every time.
- 4
Set the replenishment threshold
A clear low-balance point that triggers a top-up and a review.
- 5
Schedule the audit rhythm
Routine review at every replenishment, plus occasional unannounced spot-checks.
How much should a petty cash fund actually hold?
Enough to cover a normal period of small purchases without frequently running dry - large enough to be useful, small enough that a loss wouldn’t be significant. There’s no universal figure; size it to your actual pattern of small-cash spending.
Who should have access to petty cash?
One named, trustworthy custodian, with a clearly designated backup for when they’re out. Broad access defeats the purpose of accountability - if several people can take cash without a clear owner, nobody is actually responsible when the count is off.
What’s the most important habit for keeping petty cash accurate?
Logging every disbursement at the moment it happens, with a receipt attached immediately - not reconstructing the log from memory later. Real-time logging is what actually prevents the small errors and gaps that compound into real shrinkage over time.
Petty cash isn’t petty when nobody can say where it went.
Resources
Was this guide helpful?