Digital solutions
Revenue collection systems
Digital revenue that can be traced from source to receipt — and reported on without rebuilding the spreadsheet every month.
From scattered registers to a traceable revenue record
Revenue is easiest to lose at the edges: a register that lives in one office, a receipt book that lives in another, a payment confirmed by phone message, and a monthly return assembled by hand. Digital collection does not fix that on its own. It fixes it when the revenue base is mapped, the assessment is recorded against a known payer and service point, the payment is captured where it happens, and the reconciliation can be run by someone who was not involved in collecting it.
Logitech Consultants develops revenue collection systems for county governments and other organisations that bill for services across many locations. Our platform combines GIS and database technology with revenue mapping, process automation and integrations with mobile payment platforms and government financial systems, so that collection, reconciliation and reporting sit on one record rather than several.
What the system covers
-
01
Property and revenue mapping
GIS and database tools used to register properties, business premises, service points and revenue sources, so that what should be billed is visible on a map rather than inferred from an old register.
-
02
Revenue estimation and assessment
Assessments calculated against agreed rates and categories, with the basis of each charge recorded so that a bill can be explained to the payer and defended on review.
-
03
Taxpayer and service-point records
One record per payer, business or property, linking assessments, payments and balances across every revenue stream they are liable for.
-
04
Permits and licences
Application, approval, issue, renewal and expiry tracking, with the permit history available to enforcement officers in the field.
-
05
Multiple revenue streams
Market fees, land rates, parking, house rent, cess and other service charges configured as separate streams that still report into a single position.
-
06
Mobile payment integration
Integration with mobile money and banking channels, with payment confirmation matched back to the assessment and a receipt issued from the system rather than by hand.
-
07
Monitoring, reporting and audit
Collection dashboards by stream, station and officer, exception reports on unpaid or part-paid accounts, and an audit trail of who assessed, waived, collected or amended a record.
-
08
Service-delivery tracking
Where the deployed configuration includes it, service requests and delivery points are recorded alongside the revenue record, so a payment and the service behind it can be seen together.
How a rollout is shaped
Map the revenue base before digitising it
Converting an existing register into a database only digitises its gaps. We start with the revenue sources themselves: which properties, businesses, stalls, parking areas and service points should be paying, where they are, and which stream applies. The mapping exercise is what makes the later reports meaningful. The workflow that follows is deliberately linear — map and register, assess, collect, reconcile, then monitor and report — so each stage leaves a record the next one can rely on.
- Revenue sources and streams agreed with the responsible departments
- Properties, premises and service points captured with location data
- Rates, categories and exemptions confirmed in writing before configuration
- Existing registers reconciled against the field survey, with variances explained
Collection that works at the counter and in the field
A revenue system is used by people standing in a market, a parking bay or a sub-county office, often with intermittent connectivity. The workflow is designed for that reality: a payment can be captured and receipted locally, then reconciled when the connection returns, and a payer can be given proof of payment that the system recognises later.
Reconciliation and oversight
Payments arrive from mobile money, bank deposits and cash counters, and each has to land against the right assessment. We configure the matching rules, the exception queue and the escalation route, then agree who is allowed to waive, reverse or amend a transaction and what evidence that decision requires.
Implementation and support
Revenue systems are judged on the month-end position, so delivery includes the people and the controls around the software.
- Field survey and data capture support during the initial mapping exercise.
- Configuration of streams, rates, stations and user permissions against the agreed schedule.
- Integration with mobile money, banking and government financial systems where the interfaces are available.
- Training for revenue officers, supervisors and finance staff, including reconciliation and exception handling.
- Post-go-live support covering data corrections, reporting changes and periodic review of controls.
Questions we are asked
Can the system collect more than one type of revenue?
Yes. Streams such as land rates, market fees, parking, house rent, cess, permits and licences are configured separately, each with its own rates and rules, but they report into a consolidated position for the department and the finance team.
Does it integrate with mobile money and government systems?
The system is built to integrate with supported mobile-money and banking channels and with government financial systems where those interfaces are available. The exact integrations are confirmed during assessment, because availability depends on the accounts, approvals and specifications in place at the time.
What happens when there is no network connection?
Field collection is designed to keep working through intermittent connectivity: transactions are captured locally, receipted, and synchronised when the link returns. The reconciliation report identifies anything that did not sync, so an interrupted day does not become a missing month.
How do you handle waivers and adjustments?
Waivers, reversals and amendments are permissioned actions that record who made the change, when, on what authority and against which assessment. That trail is usually the part that finance and audit care about most.
Can it work with data we already hold?
Existing registers and spreadsheets are assessed during the mapping phase and migrated where the data is complete enough. Where it is not, the field survey fills the gap and the variance is documented rather than silently imported.
Related capabilities
Let’s build the right solution
Tell us what you are trying to achieve. We will help you assess the requirement, shape the architecture and identify the technology needed to deliver it.