ATM cash reconciliation for gas stations and c-stores.

What is an ATM at a gas station?

Most independent gas stations and c-stores host an ATM as a customer-convenience and revenue-generating appliance. The operator typically owns the machine (or leases it from an ATM service provider), loads it with cash, and earns a surcharge revenue per transaction ($2.50–$3.50 is the standard range, with some high-traffic locations charging more).

The three financial flows per ATM:

• Cash loaded, physical cash placed into the ATM's dispensing cassette. Comes from the store safe or an armored carrier.
• Cash dispensed, physical cash given to customers per transaction. The ATM's terminal log records this.
• Surcharge revenue, the per-transaction fee the customer pays. Settled to the operator's bank account on the ATM network's schedule (typically 1–3 business days).

The five-step ATM reconciliation workflow

1. Record cash loaded

Every load event: amount, time, who loaded (owner, manager, armored carrier). Recorded before the ATM is closed and sealed. The cash comes from the store safe, so the load amount also writes to a corresponding safe debit, every dollar leaving the safe for the ATM has a paired audit row.

2. Record cash dispensed

ATM transaction log (from the terminal's journal print or network report). Per-transaction amount and timestamp. Most ATMs print a journal automatically on a thermal slip; modern ATMs make this available via the network's reporting portal.

3. Compute remaining cash

Cash loaded minus cash dispensed = expected remaining when the next load cycle begins. The next load opens with a physical count of remaining cash, which should equal that expected number (within rounding).

4. Track surcharge revenue separately

Surcharge fee × transaction count = surcharge revenue earned. This flows into the operator's bank account from the ATM network, separately from the cash dispensed. Reconcile against the network settlement report.

5. Flag variance above threshold

Variance over the configurable threshold (typically $20) triggers investigation. Common causes: data-entry error on load amount, missed transaction on the journal, customer dispute (rare), mechanical cash-handling error (rare). Theft is possible but typically the rarest cause.

Worked example: a clean ATM cycle

ATM cycle: 7 days (Monday 6 AM load → Sunday 6 PM next load)

Load event (Monday 6 AM):
  Cash loaded: $8,000 (16 straps of $500 in $20s)
  Loaded by: owner
  Source: store safe
  Audit row: cash_to_atm = $8,000, safe debit logged

Daily dispensed (per terminal journal):
  Mon: $812 (4 transactions)
  Tue: $1,140 (6 transactions)
  Wed: $980 (5 transactions)
  Thu: $1,260 (7 transactions)
  Fri: $1,800 (9 transactions)
  Sat: $1,420 (8 transactions)
  Sun: $620 (3 transactions)
  Total: $8,032 (42 transactions)

Surcharge configuration: $3.00 per transaction
Surcharge revenue earned: 42 × $3.00 = $126

Next load (Sunday 6 PM):
  Pre-load count: -$32 (overdispensed)

Wait, that's a problem. Let me re-check the math.

  Cash loaded:    $8,000
  Cash dispensed: $8,032
  Expected remaining: -$32

Reality check, that can't actually go negative. The ATM has
$2,000 cash reserve below the loaded amount that I forgot to
count. Re-running:

Cash loaded:           $8,000
Pre-load reserve:      $2,000
Total available:      $10,000
Cash dispensed:        $8,032
Expected remaining:    $1,968

Pre-next-load count:   $1,940
Variance:              $-28 (under threshold of $20? Above by $8)

Under $50 reasonable for a 7-day cycle. Flag for review at
next-load attribution; most likely missed-transaction (one
$20 transaction not in the journal) or a journal-print
truncation.

Bank deposit from ATM network (settlement 2 days post-cycle):
  Surcharge revenue: $126.00 ✓
  Reconciled against transaction count and per-transaction fee.

Common ATM reconciliation mistakes

• Treating ATM cash as separate from the store cash flow. The ATM is loaded from the safe. Every load is a safe debit. Bypassing the safe-debit audit row produces phantom cash variance at EOD.
• Skipping the pre-load count.The remaining cash at next load is the only physical evidence the prior cycle's reconciliation is correct. Skip it and you're reconciling against nothing.
• Confusing cash dispensed with cash debited from the customer.The customer's bank debits their account; the ATM dispenses cash to them. The operator's reconciliation is about the cash dispensed, the customer-debit side is the network's job.
• Not tracking surcharge revenue separately.Surcharge revenue settles via the ATM network 1–3 business days post-transaction. It's a separate bank-feed line item from cash deposits and needs to reconcile against the transaction count, not the dispensed cash.
• Reconciling at month-end instead of per cycle. Variance attribution dies fast, by end-of-month, who loaded which cycle and what the per-transaction history looked like is gone.
• Aggregating armored-carrier and owner loads.Different documentation, different responsibility, different escalation paths. Reconcile per load type.

Owner-loaded vs. armored-carrier-loaded ATMs

Surcharge revenue: the overlooked income line

At $3.00 per transaction and 30 transactions per day, an ATM generates $32,850/year of surcharge revenue. At 50 transactions/day, $54,750. This is a meaningful income line that often gets buried in "other income" without per-transaction tracking.

Per-transaction reconciliation matters for three reasons:

• Verify the network settlement matches the terminal log. Settlement should equal transaction count × surcharge fee. Mismatch means either a misconfigured terminal or a settlement error.
• Catch transaction-count drift. A machine with declining transaction count signals declining utility (broken ATM, competing machine opened nearby, customer behavior shift).
• Optimize surcharge configuration.Periodic review against market rates and competing ATMs nearby. Higher surcharge increases revenue per transaction but may decrease transaction count.