Identify the instrument precisely
The National Treasury’s June 2025 notice concerns consultation on draft ICRMS regulations. Separately, Gazette Notice 12835 of 9 September 2025 publishes the Commission on Revenue Allocation’s Standards and Guidelines on Integrated County Revenue Management System. These should not be described as one instrument.
Record the title, issuer, notice number, date and relevant provision for each requirement. Confirm current applicability and any subsequent instruments with the responsible county advisers before procurement or a compliance declaration.
Build a requirements matrix
Translate the applicable provisions into reviewable requirements with a responsible county owner. Separate billing, collection, reconciliation, reporting, access and operational continuity requirements. Keep the source reference alongside each requirement.
For each proposed solution, record the relevant product release, demonstration, configuration dependency, integration approval and acceptance evidence. A generic compliance badge does not replace this matrix.
Check external connections
Payment channels and national reporting processes may require third-party access and approval. Ask which interfaces are available for the actual deployment and who owns onboarding, test data and production acceptance.
Demonstrate error handling and reconciliation at the system boundary. An export or a sandbox test should be identified as such and should not be described as production approval.
Align the project with the budget process
The PFM Act sets several county planning milestones: the budget circular by 30 August, the Annual Development Plan submission by 1 September, and CBROP submission to the County Executive Committee by 30 September. Verify current provisions and the county’s published timetable.
Later milestones include the County Fiscal Strategy Paper by the end of February, budget estimates by 30 April and assembly approval by 30 June. Sector-hearing dates vary; do not present 15 December as the national section 128 deadline.
Ask for evidence before accepting a claim
Request a demonstration covering normal transactions and exceptions, with sample reports and permissions. Agree which requirements are met by the demonstrated release and which depend on configuration, further delivery or another organization.
Use procurement, legal, finance and ICT review to establish the required scope. This guide supports a structured evaluation; it does not certify a product or a county’s compliance.
Sources and further reading
Reviewed 10 October 2026. Confirm current instruments and deployment requirements with the responsible specialists.