Back to solution library
B7

Regular, Understandable Billing

Clear Billing

Overview

What This Option Does

Issue bills on a regular cycle and make them easy to read. Each bill should show the service, billing period, basis of charge, arrears carried forward, and what the user should do if something looks wrong. Irregular or confusing billing is one of the fastest ways to create arrears even when users are otherwise willing to pay.

Most Useful When
  • Users complain that they do not understand the charge.

  • Billing intervals are inconsistent or long gaps occur between cycles.

  • Arrears grow after missed or delayed billing runs.

Legal requirements

The city needs authority to issue standard bills and, where relevant, recognise digital notices.

Administrative requirements

Maintain a stable billing calendar, use clear templates, and make sure every bill carries a usable account reference and contact point for questions or corrections.

Usually Not Best First Move
  • The register is too incomplete to support regular billing.

  • The underlying service-basis data are still too unreliable to produce credible bills.

Full details

Overview

Issue bills on a regular cycle and make them easy to read. Each bill should show the service, billing period, basis of charge, arrears carried forward, and what the user should do if something looks wrong. Irregular or confusing billing is one of the fastest ways to create arrears even when users are otherwise willing to pay.

Practical implementation path
  • Set a regular billing calendar and keep it predictable enough that customers know when to expect a bill and when payment is due.

  • Redesign the bill so it states clearly what service is being charged, the basis of the charge, the due date, arrears if any, and how to pay or dispute it.

  • Check that bills can be matched reliably to the right customer or service point before the cycle is released.

  • Monitor returned bills, complaint patterns, and late-payment spikes to improve the bill layout and delivery process over time.

Legal and institutional requirements

The city needs authority to issue standard bills and, where relevant, recognise digital notices.

Administrative Setup

Maintain a stable billing calendar, use clear templates, and make sure every bill carries a usable account reference and contact point for questions or corrections.

When this is a strong fit
  • Users complain that they do not understand the charge.

  • Billing intervals are inconsistent or long gaps occur between cycles.

  • Arrears grow after missed or delayed billing runs.

When this is less suitable
  • The register is too incomplete to support regular billing.

  • The underlying service-basis data are still too unreliable to produce credible bills.

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.