County Revenue Management System (ICRMS)

Strengthen billing, payment reconciliation and revenue oversight

Explore county revenue collection workflows, from billing and payment references to reconciliation and reporting. Request an ICRMS evaluation tailored to your county.

Request a tailored demo

County workspaceSynthetic example

Illustrative workflow

Daily reconciliation review

Batch: DEMO-REC01
Matched receipts: 24
Unmatched payments: 2 to investigate
Close approval: Pending sign-off

Fictional records for illustration. Confirm the workflow in your tailored demonstration.

Start with your operational priorities

County revenue teams need traceable bills, receipts and exceptions across revenue streams. Start with the county’s approved charges, collection procedures and reporting responsibilities.

Disconnected registers make it difficult to reconcile bills and receipts.

Unidentified payments and reversals need controlled resolution.

Revenue targets must be evaluated alongside comparable collection evidence.

Snapshot

A useful evaluation

Scope

Identify the workflows and roles that matter

Demo

Use representative transactions and exceptions

Plan

Agree requirements, dependencies and acceptance

Workflows to explore in your demonstration

We will match the discussion to your organization. Confirm demonstrated capabilities, configuration needs and external dependencies in the proposal.

Revenue billing

Map revenue streams, customer references, approved charges, adjustments and responsible officers.

Payment reconciliation

Review payment allocation, settlement checks, duplicate handling and reversal workflows across agreed channels.

Field collection

Discuss field devices, receipt verification, access permissions and the required connectivity or downtime procedures.

Oversight and reporting

Agree daily reconciliation, exception queues and management reporting with the finance team.

ICRMS standards review

Use the CRA Standards and Guidelines on ICRMS, Gazette Notice 12835 of 9 September 2025, as a source for requirements review. Confirm current applicability and any subsequent instruments.

Implementation planning

Define migration checks, officer training, support arrangements and acceptance evidence for a phased rollout.

Define success before rollout

Clearer responsibilities

Agree who prepares, reviews and approves each operational step.

Traceable exceptions

Include incomplete, disputed and reversed transactions in the evaluation.

Measurable acceptance

Use your baseline and agreed test cases to assess the implementation.

Operational readiness

Confirm officer training, support contacts and fallback procedures before live collections.

Follow the bill, payment and review trail

Start with the register and fee schedule, then follow the bill, receipt and reconciliation decision. A useful evaluation shows who can act on each record and how exceptions reach an accountable reviewer.

Illustration of a bill, receipt and ledger with a separate unresolved receipt — Trace the bill, receipt and ledger entry; keep unresolved payments visible for review.

Illustrative example using synthetic data; not a customer result or a statement of verified product behavior.

Assess the obligation

For fictional bill BILL-1048, record the revenue stream, ward or collection point, fee-schedule version and effective date. Use KES 5,000 as the worked obligation, not an official county tariff.

Allocate the receipt

A KES 3,000 payment leaves KES 2,000 outstanding. Ask to see both records and the allocation linking them; a payment notification alone does not explain the remaining obligation.

Resolve an exception

Keep receipt RCT-2082, KES 700, unallocated while its bill reference is missing. Assign it to a reconciliation officer, record the investigation and follow the configured verification and approval steps. It must not reduce BILL-1048 without an authorized allocation.

Trace the reported total

Filter the report by period, stream, channel and collection location, then trace a total to its source receipts. Keep received, allocated and bank-settled amounts distinct; a repeated payment notification should be tested for a single financial effect.

Questions before you decide

Which 2025 ICRMS instrument should we review?

Distinguish the Treasury’s June 2025 draft-regulation consultation from the CRA Standards and Guidelines published in Gazette Notice 12835 on 9 September 2025. Confirm applicable requirements and later amendments with the responsible county advisers.

Is a revenue increase guaranteed?

No. Results depend on the revenue base, targets, implementation, staffing and operating conditions. Agree a comparable baseline and measure collection, reconciliation and service outcomes.

How should we evaluate the system?

Bring representative transactions, exception cases and reporting requirements to the demo. Ask for evidence against each requirement and agree acceptance criteria before procurement.

How should we prepare existing revenue records for migration?

Identify billing registers, outstanding balances and payment references to bring into the system. Agree data ownership, cleanup and reconciliation checks, then validate a sample import before approving the opening balances.

Connect Water Billing to Revenue Planning

If water-related collections are part of your scope, map the handoff between billing records, payment reconciliation, and service follow-up. Confirm the responsibilities of the county and relevant service provider during discovery.

Explore solutions for water and environment departments

Build an Informed Revenue-System Brief

Understand the county revenue gap

Use the analysis as context for reviewing your own revenue streams, collection performance, and rollout priorities.

Review the ICRMS regulations guide

Use the guide and referenced sources to prepare questions for your revenue-system evaluation.

Evaluating County revenue management system

Evaluate an integrated county revenue management system (ICRMS) against the billing, collection and reconciliation work your county actually performs. Compare a complete transaction trail, not just a payment screen.

What to review in your demonstration

Create a bill using the county's approved revenue schedule and an identifiable payer account.
Match a payment reference to the bill, then review unmatched, reversed and duplicate payments.
Trace receipts, adjustments and approvals through to a revenue report with clear user responsibilities.

What should a county revenue collection system cover?

Scope the revenue streams, billing rules, payment channels, receipting, reconciliation, exception handling and reports together. Confirm demonstrated workflows and implementation dependencies in the proposal.

Does a county revenue system replace IFMIS?

Define the county operational workflows and the required relationship with national financial processes. Agree interfaces, responsibilities and approvals; do not assume that a new revenue system replaces IFMIS.

How is ICRMS pricing scoped?

Share your county, revenue streams, users, collection locations, payment channels and migration requirements. Request a proposal that separates implementation, support and any external integration dependencies.

ROI Calculator

Calculate what this module could mean for your county

Run the full CountyERP Revenue Impact Calculator to estimate annual value across revenue, licensing, health, HR, and procurement.

Run the Full Analysis

Discuss your requirements with CountyERP

Share your organization, product interests and rollout priorities for a tailored walkthrough or proposal.

Request a tailored demo Request pricing