Teller Cash Over and Short Tracking Log

Use this template when branch staff need to record daily teller variances and route repeated issues to a supervisor. It is a fit for bank branches, credit unions, and other cash-handling counters that reconcile teller drawers at shift close. The log is usually completed by the teller or branch associate and reviewed by a manager. If your process does not track individual teller variances, this template may be more detailed than you need.

This template is designed for daily use, typically at the end of each shift or business day. That cadence helps capture the variance while the transaction details are still fresh and makes it easier to spot repeat patterns within 30 days. If your branch runs multiple shifts, complete one entry per teller per shift. For occasional cash handling, you can adapt it to each reconciliation event instead of every day.

In addition to the variance amount, the log captures the expected cash, cash counted, variance type, and whether the difference was posted to the Cash Over and Short account. It also includes fields for the cause, corrective action, supporting reference, and repeat outlier review. That structure helps move the record from a simple discrepancy note to a usable audit trail. It also makes supervisor review more consistent.

A repeat outlier is any teller or shift pattern that keeps showing unusual overages or shortages within the review window you set, such as 30 days. The template includes fields for repeat_outlier, outlier_count_30_days, and supervisor_review_needed so you can define your own threshold. Many teams use the same rule for all branches to keep review criteria consistent. If your policy differs by location, customize the threshold field labels and review notes.

The log ties each variance to a date, branch, teller, shift, explanation, and manager sign-off, which creates a clear audit trail. The posted_to_account field shows whether the difference was recorded in the Cash Over and Short account. The supporting_reference field can point to a deposit slip, cash count sheet, or incident note. That makes it easier to trace the entry during internal review.

Common mistakes include leaving the cause vague, skipping the supporting reference, and failing to mark whether the variance was posted to the account. Another frequent issue is using free-text notes instead of a defined variance type, which makes reporting harder. Teams also sometimes forget to flag repeat outliers, so patterns are missed. This template is built to reduce those gaps with structured fields and review prompts.

Yes. You can add fields for drawer number, station, cash recycler ID, or incident ticket if those details matter in your workflow. You can also adjust the variance cause options to match your branch procedures and add conditional logic for extra explanation when 'Other' is selected. If your process uses anonymous escalation for suspected fraud, add a separate route rather than putting sensitive allegations in the main log. Keep the form focused on the minimum necessary data.

Start by standardizing the required fields, variance categories, and review threshold so every branch records the same data. Then assign one owner for daily completion and one manager role for review and sign-off. Train staff on when to use the log, what evidence to attach, and how to handle repeat outliers. A short pilot at one branch often reveals whether the field list is too long or whether the review step needs clearer instructions.