What a CEC Member for Finance Asks Before Approving a County ERP

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

Why This Guide Exists

County ERP procurement decisions involve significant public expenditure — Kakamega County's integrated ERP was tendered at KES 509 million; Kericho County's ICRMS tender required a KES 400,000 tender security. These are not decisions that proceed on vendor enthusiasm alone. A CEC Member for Finance presenting to the County Executive Committee and ultimately to the county assembly needs answers to specific, substantive questions.

This guide organises those questions into five categories, explains the evidence that supports each, and describes what good answers look like. It is intended to help county finance teams run a rigorous evaluation — and to help vendors understand what the standard of proof is.

Question 1: How Much Can This Improve Our OSR — and What Evidence Supports That?

The CEC Member for Finance is accountable to the county assembly for own-source revenue performance against CFSP targets. An ERP vendor that cannot quantify OSR improvement has not made the case for procurement.

What good evidence looks like

• Named county references with verifiable before/after OSR data — not anonymised case studies
• Revenue improvement attributed to specific system capabilities (e.g., direct M-Pesa integration replacing agent cash collection; automated arrears follow-up; permit renewal digitisation)
• Methodology that distinguishes system-driven improvement from broader economic growth or target-setting changes
• COB Budget Implementation Review data that corroborates the vendor's claims

Red flags

• Percentage improvement claims without named counties or verifiable data
• Revenue sharing or commission arrangements that give the vendor a financial stake in collection figures
• Systems that count total collections processed rather than net improvement versus prior period or target

Kenya's counties collectively missed KES 19.56 billion in OSR in FY 2022/23 (COB, Budget Implementation Review). A credible ERP vendor should be able to explain how their system addresses the specific causes of that gap — inaccurate billing data, weak collection infrastructure, fintech commission drag, and disconnected revenue and finance systems.

Question 2: Will It Integrate with IFMIS, ICRMS, IPPD, and iHRIS?

County systems do not operate in isolation. National interoperability requirements define the technical baseline. A county ERP that cannot demonstrate integration with national systems creates compliance risk and additional manual work for the finance team.

Required integrations to verify

• IFMIS — the Integrated Financial Management Information System operated by the National Treasury; counties must submit financial data in IFMIS-compatible formats for national reporting and conditional grant administration
• ICRMS — the Integrated County Revenue Management System framework mandated by National Treasury Regulations 2025; the county ERP revenue module must meet ICRMS compliance requirements
• IPPD — the Integrated Payroll and Personnel Database operated by the national government; counties with staff on secondment or national payroll require IPPD data exchange
• iHRIS — the Integrated Human Resource Information System used in the health sector; county health departments require iHRIS alignment for HMIS reporting and health workforce management
• eCitizen — the national citizen services portal; revenue collected via eCitizen must reconcile with county revenue accounts
• KRA / iTax — for PAYE remittance, NHIF, NSSF, and Housing Levy compliance reporting

What to ask vendors

• Which integrations are live and tested versus planned or "on the roadmap"?
• Which counties use these integrations in production today?
• Who bears the cost of integration maintenance when national systems are updated?

Question 3: What Is the Total Cost of Ownership Versus Our Current Arrangements?

Many counties underestimate the true cost of their current arrangements. A rigorous TCO comparison should include:

Current cost baseline (what you are paying now)

• Fintech commission charges — if your county pays 4–15% per transaction, calculate the annual total against your collected OSR figure. A county collecting KES 500 million with a 10% commission arrangement is paying KES 50 million annually to a vendor
• Manual reconciliation labour — hours spent by finance staff on spreadsheet reconciliation, end-of-month closure, and audit response preparation
• Audit finding remediation costs — time and resources spent responding to COB qualification findings, correcting manual payroll errors, and addressing CFSP data inconsistencies
• Fragmented system licensing — many counties pay separately for HR software, a revenue collection platform, a document management tool, and finance reporting tools that do not share data

Vendor cost structure to clarify

• Is this a per-transaction fee, a revenue-share arrangement, or a fixed annual licence/SaaS fee?
• What are the implementation costs (professional services, data migration, training)?
• What does the annual support and maintenance fee cover?
• Who pays for upgrades when regulatory requirements change (e.g., new ICRMS requirements, KRA iTax updates)?
• What are the exit costs if the county decides to change systems after year three?

A fixed annual licence with no per-transaction commission is almost always lower TCO than a commission-based arrangement for a county with significant collection volume. The procurement case should model this explicitly over a three-to-five-year horizon.

Question 4: How Will It Reduce Our Audit Risk?

County assembly scrutiny and COB qualification findings represent the most visible governance risk for a CEC Member for Finance. Four audit exposure areas should be specifically addressed:

Manual payroll and ghost-worker risk

The Office of the Controller of Budget flagged over KES 3 billion paid through manual payrolls in a single quarter across Kenya's county governments. Ghost workers — employees on the payroll who have left, retired, or never existed — remain a persistent audit finding when HR and payroll systems operate in silos without automated reconciliation. An integrated HR and payroll system should maintain a single employee register that drives payroll calculations, preventing the manual override paths that create ghost-worker exposure.

Pending bills and commitment control

Pending bills — obligations incurred but not yet paid — have grown significantly across many counties and represent a major COB audit focus. An integrated financial management system should provide commitment control at the point of purchase order creation, ensuring that expenditure cannot be committed beyond available budget without authorisation.

Development budget absorption

Unabsorbed development budgets — capital allocations that are not spent by financial year-end — represent a COB finding in almost every annual review. Real-time project tracking linked to CIDP allocations and procurement workflows is the mechanism that addresses this.

CFSP and CBROP data integrity

Statutory planning documents that contain inconsistent or manually assembled data create audit exposure. A system that generates CFSP and CBROP outputs directly from the same database that drives revenue collection and financial management eliminates the reconciliation risk between operational data and statutory reports.

Question 5: What Change Management and Capacity Building Does the Vendor Provide?

Technology implementation failures in county government are rarely caused by the software. They are caused by insufficient change management, inadequate training, and vendor disengagement after go-live. A CEC Member approving a significant ERP investment should require specific commitments on:

• Staff training programme — not a one-day handover, but a structured programme for finance officers, revenue agents, HR officers, and system administrators, with documented competency outcomes
• Data migration responsibility — who is accountable for migrating existing property records, employee data, and financial history into the new system, and what validation process confirms accuracy
• Parallel running period — for critical systems (payroll, revenue collection), a period of running the old and new systems simultaneously before full cutover, with defined criteria for cutover approval
• Post-go-live support — guaranteed response times for critical issues, defined escalation paths, and local support capacity (not just remote helpdesk)
• Ongoing system updates — a committed roadmap for regulatory updates (ICRMS, KRA iTax, National Treasury reporting requirements) without additional project fees

Structuring the Procurement Case

A county ERP procurement case presented to the County Executive Committee should include:

• OSR performance baseline — current collection vs. target, by stream
• Quantified cost of current arrangements — fintech commissions, manual labour, audit remediation
• System-specific improvement case — based on comparable county data, not generic estimates
• TCO comparison over 3–5 years — new system cost vs. current arrangement cost
• Compliance requirement — ICRMS Regulations 2025 mandate and timeline
• Risk mitigation — audit exposure addressed by the proposed system
• Implementation plan — milestones, resource requirements, go-live date

CountyERP's County Revenue & ROI Calculator generates the core financial model for this procurement case. It allows your team to enter your county's actual OSR figures, payroll size, and current system costs to produce a five-year ROI analysis. For a structured walk-through of how CountyERP addresses each of these five questions for your county's specific context, book a finance department demonstration.