ICRMS Regulations 2025: What Every Kenyan County Must Know

Published: March 2026  |  Audience: CEC Members for Finance, Chief Officers Finance, County Revenue Directors

Background: Why the ICRMS Mandate Exists

Kenya's counties collectively targeted KES 57.37 billion in own-source revenue (OSR) in FY 2022/23. They collected only KES 37.81 billion — a 34.1% national shortfall of KES 19.56 billion, as documented in the Controller of Budget's Budget Implementation Review Report.

The Office of the Controller of Budget, the Commission on Revenue Allocation, and the National Treasury have consistently identified the same root causes: fragmented revenue collection, manual reconciliation, weak audit trails, and county dependence on fintech intermediaries charging 4–15% commission per transaction. In response, the National Treasury introduced the Integrated County Revenue Management System (ICRMS) Regulations in 2025, establishing a legal requirement for every county to operate an ICRMS-compliant revenue platform.

What the Regulations Require

The ICRMS Regulations establish a framework for how county governments must collect, reconcile, and report own-source revenue. Core requirements include:

• Integration across all revenue streams — land rates, single business permits, market fees, parking charges, hospital/health facility fees, and other OSR categories must be managed in a single system
• Real-time collection tracking — revenue receipted must be trackable in real time against approved targets, eliminating the end-of-month reconciliation gap
• Digital payment channels — M-Pesa (Daraja API/STK push), bank integration, and eCitizen gateway connectivity are required payment channels
• Audit trail integrity — every transaction must carry a receipt number, agent identity, payment channel, and timestamp that can be retrieved for COB audit purposes
• IFMIS interoperability — revenue data must be exportable in formats compatible with the Integrated Financial Management Information System used by the National Treasury
• Reporting outputs aligned with CFSP/CBROP — the system must support the OSR performance data required for the County Fiscal Strategy Paper (due 28 February) and County Budget Review and Outlook Paper (due 30 September)

Who Is Responsible for Compliance

Accountability for ICRMS compliance sits with the County Department of Finance, ICT, and Economic Planning. In practice, the decision chain looks like this:

• CEC Member for Finance — politically accountable for OSR performance, CFSP targets, and audit findings; must champion the ERP procurement case to the county executive committee
• Chief Officer, Finance — responsible for systems implementation, IFMIS submissions, and ensuring financial management aligns with PFM Act requirements
• County Revenue Director / Director of Revenue — operationally responsible for daily collections, reconciliation, and agent oversight
• County ICT Director — accountable for system integration, uptime, cybersecurity compliance, and technical vendor management

The Fintech Commission Problem the Regulations Address

A 2024 Commission on Revenue Allocation analysis found that more than 33 counties had contracted fintech intermediaries who charged 4–15% commission per revenue transaction. In some cases, counties were spending more on vendor commissions than they were netting from the collection arrangement — a structural revenue leak that ICRMS compliance is designed to eliminate.

Under the ICRMS framework, county revenue should flow through an integrated platform the county owns and controls, rather than through intermediary systems that extract commission at the point of collection. Compliance means moving from a "collect via vendor" model to a "collect via integrated system" model where the county retains the full revenue value.

What ICRMS Compliance Looks Like in Practice

An ICRMS-compliant county will be able to demonstrate:

• A single integrated revenue system covering all 10 major OSR categories (land rates, SBPs, parking, market fees, hospital charges, and others that collectively account for ~71% of national OSR)
• A real-time dashboard showing collection against target — by stream, by subcounty, by collection agent
• Monthly reconciliation reports with zero manual adjustment entries (or a formal audit trail for each adjustment)
• IFMIS-compatible revenue export files submitted on schedule to the National Treasury
• OSR performance data that feeds directly into CFSP and CBROP preparation, reducing the time the finance team spends compiling statutory reports from weeks to hours
• COB audit support — the ability to retrieve any transaction record, receipt number, or reconciliation report for any period within minutes, not days

Key Deadlines Counties Must Plan Around

• 28 February — County Fiscal Strategy Paper (CFSP) due; OSR performance data must be current and audit-ready
• 30 September — County Budget Review and Outlook Paper (CBROP) due; full FY revenue outturn required
• 1 July — New financial year begins; revenue targets set; ICRMS-aligned collection must be operational from day one
• Throughout the year — COB interim and annual audit queries require rapid access to transaction records

Counties that complete ICRMS procurement and implementation during the November–April budget planning window are positioned to enter the new financial year (July) fully compliant.

Evaluating ICRMS-Ready Vendors: What to Ask

Not all revenue collection software meets the ICRMS standard. When evaluating vendors, county finance and procurement teams should ask:

• Does the system integrate all 10 major OSR streams in a single database, or does it aggregate from separate standalone modules?
• Is the M-Pesa Daraja API integration directly licensed, or does it pass through a fintech intermediary that charges per transaction?
• What IFMIS export format does the system produce, and has it been validated against National Treasury requirements?
• Can the system generate CFSP and CBROP OSR data automatically, or does it require manual export and reformatting?
• What is the vendor's COB audit support record — have other counties used their data exports in successful audit responses?
• Is the system offered as a county-owned platform (licence or SaaS) or as a revenue-share/commission arrangement?

How CountyERP's Revenue Collection System Addresses the ICRMS Standard

CountyERP's Revenue Collection System was designed to meet the ICRMS Regulations framework. Key features include:

• All 10 major OSR streams managed in one integrated platform — not siloed modules
• Direct M-Pesa Daraja API integration, eCitizen gateway, and bank payment channels — no fintech intermediary commission
• Real-time collection dashboards by stream, subcounty, and agent
• Automated IFMIS-compatible reporting outputs
• CFSP and CBROP data preparation built into the reporting layer
• Full transaction audit trails with receipt retrieval for COB audit support

CountyERP is deployed across 5+ county governments and supports over KES 4.5 billion in annual revenue management.

If your county is evaluating ICRMS compliance options, the most useful first step is a revenue gap assessment — mapping your current collection achievement against CFSP targets, identifying which streams are underperforming, and quantifying the commission cost of existing fintech arrangements. CountyERP offers a County Revenue & ROI Calculator that lets your finance team model the impact of tighter collection controls across each revenue stream.