What to look for in a revenue collection system

Digitising revenue collection is often described as a payments problem. In practice, payments are the easiest part. The difficult part is knowing what should have been collected, from whom, and being able to prove that what was collected matches it.

A revenue collection system has to cover the full chain: revenue source, assessment, collection, reconciliation and reporting. Weakness anywhere in that chain shows up as leakage, disputes or reports that nobody trusts.

Start with the revenue map, not the app

Before a single screen is designed, the revenue base has to be mapped. For county and municipal revenue this means identifying properties, businesses, service points and markets, and linking each to the revenue streams that apply to them. GIS and database technology makes this practical: a mapped property can carry its assessment history, its permits and its payment record.

Without that foundation, a system can only record what someone chooses to declare. With it, the system can show what was expected and highlight what was not collected.

The revenue streams to cover

• Land rates and property charges, linked to the mapped property register.

• Permits and licences, with validity periods and renewal reminders.

• Market fees, cess and other point-of-collection charges.

• Parking, house rent and facility charges.

• Other county or institutional services that currently rely on manual receipts.

Integrations decide whether it works

Most revenue now arrives through mobile money. Integration with payment platforms such as M-Pesa is not optional, and neither is integration with government financial systems such as IFMIS where reporting and accounting have to align. The integration should settle in near real time, carry a reference back to the assessment, and handle failures cleanly — a payment that succeeds at the telco but does not reach the revenue system is a dispute waiting to happen.

Reconciliation and audit trails

Reconciliation is where collection systems earn their keep. Ask how the platform will:

• Match each payment to a specific assessment or invoice.

• Handle partial payments, overpayments and reversals.

• Show a daily position per collection point, per stream and per officer.

• Record who changed an assessment, waived a charge or reversed a receipt, and when.

• Produce audit trails that survive scrutiny from internal audit and external reviewers.

Digital revenue is not about removing cash. It is about making every shilling traceable from assessment to bank reconciliation.

Reporting that management will actually use

Revenue reporting should answer operational questions, not only produce a monthly total. Which streams are behind target, which collection points are underperforming, which assessments are unpaid and how old are the arrears, and how much of the expected revenue is actually reaching the account. Dashboards are useful only when the underlying data is complete and consistent.

Implementation realities

A revenue platform touches many people who are not IT staff: revenue officers, clerks at service points, supervisors and finance teams. Implementation therefore has to include device and connectivity planning for collection points, training for each role, a fallback procedure for when connectivity fails, and a support arrangement that continues after go-live.

Phase the rollout. Starting with the highest-value streams and a limited set of service points gives the team room to fix process issues before the system is extended across the whole institution.

A short specification checklist

• Revenue mapping and estimation against a maintained register.

• Taxpayer and service-point management with a single identifier per payer.

• Permit, licence and fee management with automated renewals.

• Mobile payment and bank integration, with reconciliation reports.

• Role-based access, approval workflows and immutable audit trails.

• Reporting and analytics for management, audit and finance.

• A training and support plan with clear ownership after go-live.

Logitech Consultants develops and integrates revenue collection systems with GIS-based revenue mapping, payment integrations and reporting, alongside the ICT and security infrastructure they depend on.