Kenya's Integrated County Revenue Management System (ICRMS) framework, gazetted in 2025, converts what used to be a modernisation ambition into a compliance requirement: every one of the 47 county governments must operate a single, integrated system covering the full revenue cycle — billing, collection, reconciliation, enforcement, and reporting. For county revenue directors and CECMs for Finance, the question has shifted from whether to automate to whether the county's current arrangement will pass scrutiny.
The stakes are not abstract. Counties collect roughly 65% of their own-source revenue (OSR) targets on average, and the gap concentrates in exactly the places manual and fragmented systems cannot see: cash-handled streams like parking, markets, and cess, and unreconciled collections that never reach the county revenue fund. Counties that moved early to integrated platforms have demonstrated what closing that gap is worth — Kiambu County collected KES 5.45 billion after moving to an ERP-driven revenue system.
What the ICRMS framework actually requires
The compliance checklist
Before drafting a tender, score your current arrangement honestly against these ten questions. Any "no" is both a compliance gap and, in our experience, a revenue leak in the same location.
- Can you produce a single report showing all revenue streams, all channels, for yesterday — without manual compilation?
- Is every M-Pesa, bank, and agency collection automatically matched to an invoice or bill?
- Can you trace any receipt from the payer to the county revenue fund with a complete audit trail?
- Are waivers and adjustments subject to maker-checker approval, with named officers logged?
- Do field collectors (markets, parking) use devices that work offline and reconcile daily?
- Is enforcement (defaulter lists, demand notices) generated from the system rather than by hand?
- Can the Controller of Budget and Auditor-General be given read access rather than compiled returns?
- Does the county own the source code, or at minimum have escrow and full data-export rights?
- Is the system interfaced — or interface-ready — with national treasury systems?
- Is personal data handled in line with the Data Protection Act, 2019, with an identified data controller?
What the Auditor-General will look for
Audit queries on county revenue follow a predictable pattern: unreconciled collections, revenue collected but not banked, waivers without authority, and variances between receipting records and bank statements. An ICRMS-compliant system answers these structurally — the audit trail exists because the system will not process a transaction without creating one. If your revenue officers spend the audit season reconstructing paper trails, the system is the finding.
Planning the procurement
Since 1 July 2025, county procurements run through the national e-Government Procurement portal, which means your tender documentation and the bidder compliance requirements are more visible — and more scrutinised — than before. Three practical recommendations: first, specify outcomes (reconciliation coverage, reporting latency, audit-trail completeness) rather than brand features. Second, require ICT Authority accreditation in Systems & Applications and Information Security as mandatory criteria — it is the most legible capability filter available to an evaluation committee. Third, put sustainability in the contract: source-code handover, administrator training, and a named support SLA. Systems fail at handover far more often than they fail at go-live.
""The counties that close their revenue gap are not the ones with the most enforcement officers — they are the ones where the system sees every shilling from bill to bank.""
Rosewill Bome Technologies builds ICRMS-aligned county revenue systems with county-owned code and data, M-Pesa and bank reconciliation, and Auditor-General-ready audit trails. Request a technical presentation or an ICRMS readiness review through our county revenue management page.