Back to solution library
B10

Receipts, Reconciliation, and Cash Controls

Cash Controls

Overview

What This Option Does

Protect the money already being paid by making sure every payment gets an official receipt and every collection point reconciles back to the ledger and bank deposit. In many user-fee streams, leakage happens after the user has already paid. Strong cash and reconciliation controls therefore deserve to be treated as a revenue reform, not only as finance-office housekeeping.

Most Useful When
  • Many payments are still made in cash.

  • Users report that they paid but the system does not show it.

  • There are unexplained gaps between collections, deposits, and reported receipts.

Legal requirements

Finance rules should require official receipts, reconciliation, and deposit procedures. If these are weak, a standing internal order can usually tighten practice quickly.

Administrative requirements

Use numbered or digital receipts, separate collection from reconciliation, carry out daily or same-week balancing, and review exceptions while evidence is still fresh.

Usually Not Best First Move
  • The stream is already fully cashless and well reconciled, though even then digital reconciliation still needs close review.

Full details

Overview

Protect the money already being paid by making sure every payment gets an official receipt and every collection point reconciles back to the ledger and bank deposit. In many user-fee streams, leakage happens after the user has already paid. Strong cash and reconciliation controls therefore deserve to be treated as a revenue reform, not only as finance-office housekeeping.

Practical implementation path
  • Standardise official receipts across all payment channels and make sure customers and staff can easily tell what a valid receipt looks like.

  • Reconcile cash, digital payments, and bank statements every day or every shift, depending on the volume and risk of the stream.

  • Separate collection, reconciliation, and supervisory approval roles as much as staffing allows, and use spot checks where staffing is thin.

  • Review discrepancies quickly and document how they were resolved so small control failures do not turn into routine leakage.

Legal and institutional requirements

Finance rules should require official receipts, reconciliation, and deposit procedures. If these are weak, a standing internal order can usually tighten practice quickly.

Administrative Setup

Use numbered or digital receipts, separate collection from reconciliation, carry out daily or same-week balancing, and review exceptions while evidence is still fresh.

When this is a strong fit
  • Many payments are still made in cash.

  • Users report that they paid but the system does not show it.

  • There are unexplained gaps between collections, deposits, and reported receipts.

When this is less suitable
  • The stream is already fully cashless and well reconciled, though even then digital reconciliation still needs close review.

  • The administration cannot yet issue reliable notices, post payments accurately, or distinguish inability to pay from deliberate non-compliance.

Risks And Design Notes
  • Essential-service enforcement needs hardship screening and clear political backing; otherwise the city can damage trust faster than it improves payment.

  • Receipts and reconciliation matter as much as reminders. People stop paying when posted balances and their own records do not match.