Fare Box Reconciliation Audit
Use this Fare Box Reconciliation Audit template to compare farebox revenue, probe data, vault counts, and bank deposits for a fixed-route transit period. It helps you document variances, explain timing differences, and close the audit with clear sign-off.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Public Transit · Municipal Transportation · Transit Finance And Accounting
Overview
The Fare Box Reconciliation Audit template is used to verify that fixed-route transit revenue recorded at the farebox matches the probe, vault, and bank deposit records for a defined audit period. It gives you a structured way to document what was collected, what was counted, what was deposited, and where any difference occurred.
Use this template when you need a controlled reconciliation for cash-based transit revenue, especially when multiple collection units, vault counts, or deposit timing differences can create confusion. It is a good fit for daily, weekly, monthly, or exception-driven audits where the goal is to prove revenue accountability and preserve a clear chain of custody. The template also helps when you need to show that source documents were available and complete before the audit was closed.
Do not use it as a substitute for a broader financial statement audit or for non-fare revenue streams that follow different controls. It is also not the right tool when the underlying source records are missing, because the template depends on farebox, probe, vault, and deposit evidence to reconcile properly. If your process includes mixed revenue types, separate them before using this audit so the variance analysis stays clean and defensible.
Standards & compliance context
- This template supports internal control documentation practices commonly used in public-sector transit finance and revenue assurance programs.
- The chain-of-custody section helps evidence handling controls that are often expected under audit standards and organizational cash management policies.
- Exception logging and corrective action tracking align with ISO 9001-style non-conformance management and follow-up discipline.
- If your agency is subject to grant oversight or municipal audit requirements, use this record to show traceability from collection to deposit.
- Customize tolerance thresholds and approval steps to match your local finance policy, transit authority procedures, and any applicable oversight rules.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Audit Scope and Revenue Period
This section defines exactly which dates, routes, and revenue sources are included so the reconciliation has a clear boundary.
-
Audit period matches the selected deposit and collection dates
Verify the start and end dates/times align to the revenue period under review.
-
Fixed-route service included in scope is identified
Document the routes, garages, or service groups included in the audit.
-
Revenue sources included in the audit are documented
Select all revenue sources reviewed in the reconciliation.
-
Supporting source documents are available and complete
Confirm the audit packet includes the required reports, deposit slips, and reconciliation worksheets.
Farebox, Probe, and Vault Data Review
This section compares the core revenue sources and shows whether the recorded totals reconcile within the allowed tolerance.
-
Farebox recorded revenue is captured for each collection unit
Enter the total farebox-recorded revenue reviewed in the audit.
-
Probe data is available for the audited revenue period
Confirm probe data exists for the same period and collection units under review.
-
Vault count data is available for the audited revenue period
Confirm vault data exists for the same period and collection units under review.
-
Farebox, probe, and vault totals reconcile within tolerance
Verify the recorded amounts agree or that differences are explained by approved adjustments.
-
Variance amount documented when totals do not reconcile
Enter the unexplained variance amount if any discrepancy remains after review.
Bank Deposit and Chain of Custody
This section proves where the reconciled revenue went and documents the transfer path from collection to deposit.
-
Bank deposit amount matches reconciled revenue
Confirm the deposit amount equals the reconciled farebox revenue or approved adjusted amount.
-
Deposit date and reference number are documented
Record the deposit date, bank reference, or deposit slip number.
-
Chain of custody from collection to deposit is documented
Verify transfer records identify who handled the revenue and when custody changed.
-
Unresolved deposit timing differences are explained
Confirm any timing differences between collection and deposit are supported by documentation.
-
Deposit support documents are attached
Attach deposit slips, bank confirmations, or scanned reconciliation support as evidence.
Exceptions, Controls, and Follow-Up
This section captures every variance, explains the root cause, and assigns corrective action so issues do not disappear after the audit.
-
All exceptions are logged and categorized
Confirm discrepancies are recorded with a reason code or exception category.
-
Exception categories selected
Select all categories that apply to the audit exceptions.
-
Root cause analysis completed for material variances
Document whether a root cause was identified for significant discrepancies.
-
Corrective action owner and due date assigned
Identify the responsible person or department and the target completion date.
-
Repeat variance pattern reviewed for trend
Rate whether the same discrepancy pattern appears across multiple periods.
Closeout and Sign-Off
This section records the final result and formal approval so the audit can be retained as a complete control record.
-
Overall reconciliation result
Select the final audit outcome.
-
Final audit summary
Summarize key findings, variances, and follow-up actions.
-
Inspector signature
Inspector signs to confirm the audit findings and supporting evidence are complete.
-
Audit completion date
Record the date and time the audit was completed.
How to use this template
- 1. Enter the audit period, identify the fixed-route service in scope, and attach the source documents that support the selected collection and deposit dates.
- 2. Record farebox revenue for each collection unit and add the probe and vault totals for the same revenue period.
- 3. Compare the farebox, probe, and vault figures, then document any variance amount and note whether it falls within your tolerance.
- 4. Match the reconciled revenue to the bank deposit, capture the deposit date and reference number, and explain any timing difference that remains unresolved.
- 5. Log each exception, assign a category and root cause where needed, and name the corrective action owner with a due date.
- 6. Complete the closeout summary, confirm the overall reconciliation result, and sign and date the audit record.
Best practices
- Tie every total to a named source document so the reviewer can trace the number without leaving the audit record.
- Separate timing differences from true variances, because a late deposit is a control issue but not always a revenue loss.
- Flag material variances for root cause analysis instead of closing them with a generic comment.
- Use consistent exception categories across audits so repeat patterns can be compared over time.
- Document chain of custody from collection to vault to deposit, including who handled the revenue at each step.
- Review probe and vault records for the same period before comparing them to the bank deposit, not after the variance is already noted.
- Attach deposit support and count records at the time of audit completion so the file is self-contained.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this Fare Box Reconciliation Audit template cover?
This template covers a single audit period for fixed-route transit revenue and walks through the full reconciliation path: farebox-recorded revenue, probe data, vault count data, and the related bank deposit. It also captures chain of custody, unresolved timing differences, exception handling, and final sign-off. Use it when you need a documented revenue accountability check rather than a simple cash count. It is designed to show where the numbers came from and why they do or do not match.
When should this audit be performed?
Use it on the deposit and collection dates selected for the audit period, or on a recurring schedule set by your transit finance or compliance team. It is especially useful after collection runs, at month-end close, or when a variance needs investigation. If your operation has high cash volume or multiple collection units, a regular cadence helps identify repeat issues early. The template works best when the audit period is clearly bounded and source records are complete.
Who should complete the reconciliation?
A finance auditor, revenue analyst, transit accounting lead, or other authorized reviewer should complete it, ideally someone independent from the collection process. The person running the audit should be able to review source documents, compare totals, and document exceptions without having to guess at missing data. If your organization uses segregation of duties, the collector, vault counter, and depositor should not be the same person. The sign-off section is meant to capture accountability, not just completion.
Does this template support compliance requirements?
Yes, it supports internal control and audit documentation practices commonly used in public transit revenue operations. It aligns with the kind of evidence trail expected under general financial controls, chain-of-custody procedures, and documented exception management. If your agency is subject to public-sector audit rules, grant conditions, or internal control policies, this template helps standardize the record. It is not a legal opinion, so you should map it to your own finance and transit governance requirements.
What are the most common mistakes when using this audit?
The most common issues are missing source documents, unclear deposit timing, and unexplained differences between farebox, probe, vault, and bank totals. Another frequent problem is documenting a variance without identifying whether it came from collection, counting, posting, or deposit timing. Teams also sometimes skip chain-of-custody details, which makes later review difficult. This template is built to force those details into the record before the audit is closed.
Can I customize the exception categories and tolerance rules?
Yes, and you should. Different transit systems may use different tolerance thresholds, route groupings, deposit timing rules, or exception categories such as equipment error, counting error, posting delay, or missing support. The template is meant to be adapted to your local controls and revenue process. Keep the structure intact so you still capture the same core evidence, even if the labels change.
How does this compare with a manual spreadsheet reconciliation?
A spreadsheet can calculate totals, but it often does not force the reviewer to document source completeness, chain of custody, exception ownership, and follow-up. This template turns the reconciliation into a repeatable audit record instead of a one-off calculation. That makes it easier to review trends, assign corrective actions, and support later questions from finance or oversight teams. It is better suited for controlled review than an ad-hoc worksheet.
What should I attach to the audit record?
Attach the deposit support documents, probe reports, vault count records, and any source documents needed to explain the audit period. If there is a variance, include the evidence that supports the root cause and any follow-up notes. The goal is to make the audit self-contained so a reviewer can trace the numbers without searching elsewhere. If your organization uses scanned receipts or system exports, include those as supporting files.
Related templates
Go deeper on the topic
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
-
See how MangoApps Forms helps teams collect, track, and analyze employee data in real time — with mobile access, file uploads, and enterprise-grade security.
-
Software bloat warning signs explained—spot bloated software early and choose leaner tools that boost performance, adoption, and ROI.
-
Gallup 2026 workplace report reveals falling engagement, manager burnout, and $10T losses—actionable HR insights for leaders.
Ready to use this template?
Get started with MangoApps and use Fare Box Reconciliation Audit with your team — pricing built for small business.