Robin Digital / County revenue
CRMS.
County Revenue Management System
From the first charge to the final county report, one connected record follows every collection.
A transaction, end to end
Illustrative market-fee example · not live county data
- 01
Charge
A market stall fee is recorded against a registered stall.
- 02
Payment
The collection is linked to its payer and collection point.
- 03
Receipt
A traceable receipt carries the transaction reference.
- 04
Reconcile
Finance matches the receipt with the settlement.
- 05
County view
The collection appears in market and county reporting.
Revenue in motion
One record, from source to settlement.
A collection is more than a payment. CRMS keeps the payer, service, receipt, officer and settlement connected so a county can follow the full story.
At the market
Market collection
Collector · trader · market master · finance
Record
A collector selects the stall and fee on their phone. If the network drops, the collection stays in the sync queue.
Pay & receipt
The trader pays; the collector issues a traceable receipt tied to the stall, officer and time.
Reconcile
Synced collections appear by market and collector. Finance matches receipts against the payment settlement.
Resolve
An unmatched settlement stays visible as an exception for review rather than disappearing into a daily total.
Modules in this journey
Inside the workflow
The same transaction. Different perspectives.
The field, the resident and the finance office each see the part of the record they need.
A fee can be recorded in a low-connectivity area and synchronised when the device reconnects.
Market collection
Stall fee
Illustrative interface and example records · not live county data
Control by design
Accountability runs through the transaction.
A county sets its own tariffs, collection zones, roles and approval rules. External connections are configured to its payment and reporting arrangements.
People & approvals
Access follows county, department and role. Sensitive changes, waivers and reversals move through approval steps, with the actor recorded.
Receipt to settlement
Each charge and receipt stays linked to its stream. Bank and mobile-money settlements are matched against transactions; differences enter an exception queue.
Offline, then accounted for
Field records captured without a connection sync back into the shared ledger. Officer, location and time travel with the collection record.
A record of decisions
Changes, approvals and reconciliations remain traceable for audit. Reports can drill from a county total down to the underlying transaction.
Explore the system
23 modules. One connected record.
Start with the services your county collects from. Follow each one through payments, enforcement and reporting.
Revenue collection
Every major county revenue stream, mapped and managed.
AI-powered module advisor
Tell us your challenge. See where CRMS fits.
Describe your county's revenue-management needs in your own words. The advisor recommends relevant CRMS modules and explains how each addresses your needs. Suggestions are a starting point for conversation, not a formal proposal.
One ledger
More ways to pay. One place to account.
CRMS brings 10 payment channels into a single ledger, with reconciliation workflows that keep every collection traceable.
County-configured connections
Systems CRMS works with.
Payment services, government records, health systems, communications and monitoring are connected according to each county’s setup. Availability depends on the county and the external service.
Your county, your priorities
Let’s map your revenue journey.
Tell us which streams you collect from, where the gaps are and what your teams need to see.