ATM Surprise Balance Audit

It covers the full unannounced balance check for an ATM, from confirming the machine ID and audit start time to counting cash by denomination and reconciling the physical total to the system balance. The template also documents dual custody, access control, variance explanations, and corrective actions. It is designed to produce a clear audit trail when cash on hand does not match the recorded total.

Use it when you need an independent, surprise verification of ATM cash integrity, such as during routine controls, after a variance trend, or as part of a fraud-prevention program. It is also useful after replenishment activity when you want to confirm that cash handling and system postings align. It is not a substitute for scheduled maintenance or a full security review of the ATM environment.

A two-person team should run it, with one person acting as the balancer and a different person acting as the replenisher or access holder. That separation supports segregation of duties and reduces the risk of self-checking. If your organization uses internal audit, cash operations, or field service teams, assign the roles so the people handling the count are not the same people responsible for replenishment.

The cadence depends on your risk level, transaction volume, and prior variance history. Many teams use it on a surprise basis within a recurring control program rather than on a fixed public schedule. If you are seeing repeated unexplained variances, increase the frequency until the root cause is identified and corrected.

This template supports internal control and audit practices rather than a single industry law. It aligns well with segregation-of-duties expectations, documented reconciliation controls, and evidence-based corrective action used in compliance programs and financial operations. If your organization also has physical security or workplace safety requirements, you can extend the template to reflect those policies.

Common mistakes include announcing the audit in advance, letting the same person replenish and balance the ATM, and recording only a yes/no result instead of the actual cash total and variance. Another frequent issue is failing to count reject or exception bins separately, which can make the reconciliation inaccurate. Teams also sometimes skip documenting the explanation and escalation path when a variance remains unresolved.

Yes. You can add fields for cassette count, denomination mix, reject bin handling, access method, and model-specific notes so the audit matches your equipment. If your fleet includes different ATM configurations, create a version that lists the expected cassette layout and any model-specific exceptions. That makes the count faster and reduces ambiguity during the walk-through.

This audit works best when linked to replenishment logs, cash settlement records, and incident or exception reports. The audit captures the independent verification, while the other records explain who loaded the cash, when it was loaded, and whether any access issues occurred. Connecting those records helps you trace a variance from discovery to resolution without relying on memory.

Record the variance amount immediately, document any plausible explanation, and escalate unresolved differences according to your cash-control procedure. Do not adjust the result without a review trail that explains the discrepancy and who approved the next step. If the variance suggests a process failure or access issue, preserve the evidence and open a corrective action item.