Kenya's PBO Act Annual Returns: What Is Now Required, and When

The PBO Regulations 2026 are in force and the transition window closed on 13 May 2026. Annual returns are due six months after financial year end — here is what has to be in the filing.

Author

Sibasi M&E Team

Inside the page

The reporting deadline is derived, not fixed
What goes into the filing
The failure mode is the calendar, not the paperwork
The activity report is where M&E pays for itself
Governance obligations run alongside
What we are deliberately not stating
The short version

Subscribe for newsletter

For most of a decade, Kenyan public benefit organisations planned around a statute that was not in force. That period is over. The Public Benefit Organizations Act, 2013 commenced in May 2024, and the regulations that operationalise it are now live: the Public Benefit Organizations Regulations, 2026, published as Legal Notice 43 and gazetted on 18 March 2026.

The transition window for existing organisations closed on 13 May 2026.

If your organisation has been treating PBO compliance as a forthcoming matter, it is not. This piece covers what the annual return obligation now looks like in practice.

The reporting deadline is derived, not fixed

The single most useful thing to understand about the annual return is that there is no common national filing date. The obligation is expressed relative to your own financial year:

Annual returns are due within six months of the end of the organisation’s financial year.

So the deadline moves with your accounting calendar:

Financial year ends	Annual return due
30 June	31 December
31 December	30 June
31 March	30 September
30 September	31 March

This matters operationally, because it means the return is not a task that arrives with a national reminder. It is a date you have to hold yourself, and it sits six months after a year end that is already busy with audit.

What goes into the filing

The return is not a form on its own. It is a form supported by a set of documents that have to exist, be current, and be consistent with one another:

Audited accounts. Which means an audit has to be commissioned, scheduled and completed inside the six-month window — realistically inside the first three or four months of it.
Financial statements.
An annual activity report — the narrative account of what the organisation did during the year.
An asset register.

The asset register is the item that most often does not exist in the form required. Many organisations track assets across procurement records, a fixed asset note in the accounts, and a partial inventory spreadsheet, none of which is a maintained register. Building one retrospectively, in the same window as the audit, is unpleasant and avoidable.

The failure mode is the calendar, not the paperwork

Six months sounds generous. It is not, once you work backwards from the deadline through what has to happen:

The audit cannot start until the accounts are closed.
The accounts cannot close until year-end reconciliations are complete.
The activity report needs programme data from across the year, from people who have moved on to the next year’s work.
The asset register needs a physical verification if it has not been maintained.

An organisation that starts at month four is filing late or filing thin. An organisation that treats the activity report as a year-round accumulation rather than a year-end write-up files on time without drama.

The practical recommendation is simple and it is the only one in this piece we would insist on: put three dates in the calendar the moment your financial year ends — audit commissioned by month two, draft activity report by month four, filing by month six. The obligation stops being a crisis at that point.

The activity report is where M&E pays for itself

The annual activity report asks what the organisation did and what it achieved during the year. Organisations that run a functioning monitoring system produce it from existing records. Organisations that do not spend three weeks reconstructing the year from emails, event photographs and people’s memories.

If you run a logframe with indicators carrying baselines, targets and period actuals, the activity report is largely an assembly job: this is what we planned, this is what we delivered, this is where we fell short and why. If your indicator values live in a spreadsheet that four people edit, it is a research project — and one conducted in the same weeks as the audit.

There is a second-order benefit worth naming. The same evidence base serves the annual return, the donor reports, and the next funding application. Organisations that maintain it once and use it three times have a real advantage over those that assemble it three times from scratch.

Governance obligations run alongside

The annual return is one obligation among several. The statutory framework also carries expectations around governance and record-keeping — board composition and meetings, member records, conflict of interest, and the ordinary requirement that the organisation’s records reflect what actually happened.

The pattern in the enforcement of comparable regimes elsewhere is that returns are filed and governance records are not maintained, and the gap becomes visible at the worst moment — during a due diligence exercise by a prospective funder, rather than during a regulatory review. Treating minute books, member registers and the asset register as live records rather than year-end artefacts is cheap insurance.

What we are deliberately not stating

Some specifics circulate in secondary commentary that we are not going to repeat, because we have not been able to confirm them to a standard that would justify putting them in a compliance planning document:

Specific form numbers and titles for the annual return filing.
Penalty amounts for late or non-filing.
The precise mechanics of the closed transition window — what an organisation that did not act before 13 May 2026 must now do to regularise its standing.

For all three, the authoritative source is the Public Benefit Organizations Regulatory Authority and the gazetted text of Legal Notice 43 itself. If any of them affects a decision you are making, confirm directly with the Authority rather than relying on a summary — including this one. A regulatory framework in its first year of operation is exactly the period in which secondary sources are least reliable.

The short version

The regulations are in force; the transition window closed on 13 May 2026.
Your annual return is due six months after your financial year end — a date only you are tracking.
The filing needs audited accounts, financial statements, an annual activity report and an asset register.
The audit is the long pole. Commission it early.
The activity report is easy if your M&E system is real and expensive if it is not.
Confirm form numbers, penalties and transition mechanics with the Authority, not with an article.

Monival holds programme results — indicators with baselines, targets and period actuals, against a logframe structure — so that the annual activity report is assembled from records rather than reconstructed. Monival does not generate the statutory return itself, and we would not describe a report builder as a filing tool.

Related Blogs

County M&E Under CIMES: The Structure, the Reports and the Calendar

Kenya's County Integrated Monitoring and Evaluation System (CIMES) is the county-level component of the national M&E architecture — the structure through which a county is meant to track implementation of its County Integrated Development Plan and report upward to the national Monitoring and Evaluation Directorate (MED). It is well specified on paper and unevenly implemented in practice. KIPPRA found in January 2024 that only 17% of counties were fully compliant with CIMES requirements. That figure is worth sitting with, because it means the majority of counties are producing something other than what the system asks for — and organisations working with county government are frequently expected to plug into a system their counterpart is not fully running. This piece sets out what CIMES actually requires, so that NGOs, implementing partners and county M&E officers are working from the same picture. The committee structure CIMES is built on committees, not on a database. The anchor at county level is the County Monitoring and Evaluation Committee (CoMEC), which is the body responsible for coordinating M&E across county departments, reviewing performance data, and signing off the county's reports before they go anywhere. Below CoMEC the system extends downward through the county's administrative tiers, with M&E structures at sub-county and ward level, and data originating at village level. The design intent is a chain of custody for performance data: information is generated where implementation happens and is consolidated as it moves up. The practical implication for anyone supporting a county: the CoMEC is the entry point. Data that has not gone through it does not become county performance data, however good it is. Programmes that build a parallel reporting line to a single department and never engage the CoMEC produce information the county cannot use in its own reporting. The aggregation chain The reporting flow runs upward through four tiers: Village → Ward → Sub-county → County Each tier consolidates what it receives from the tier below and passes it up. This is the part of CIMES that most often breaks in practice, for an unglamorous reason: the lower tiers frequently have no systematic way to capture and transmit data, so consolidation happens by whatever means are available — paper, phone, a WhatsApp group, a spreadsheet emailed to a sub-county officer. Where a partner programme can add genuine value, it is usually here, at the ward and sub-county consolidation step, rather than at the county dashboard everyone wants to build. The report family CIMES defines a family of reports, and the acronyms are a common source of confusion — the naming varies somewhat between guideline editions and between counties, so confirm the current usage with your county before assuming. The reports you will encounter:CAMER / C-APR — the county annual monitoring and evaluation report, also referred to as the County Annual Progress Report. This is the principal annual product: the county's account of implementation progress against its plan. CoMER — the county monitoring and evaluation report produced through the CoMEC structure. CAPER — the county annual performance evaluation report.The distinction that matters in practice is between monitoring reports, which track implementation progress against planned targets, and evaluation reports, which assess performance and results. Counties commonly produce the monitoring product and thin out the evaluation one, which is one of the compliance gaps KIPPRA's assessment picks up. The calendar Two dates govern the annual cycle, and both are frequently missed:County annual progress report finalised by 31 July. Submitted to the national Monitoring and Evaluation Directorate by 30 August.Working backwards from 31 July is the whole game. Ward and sub-county consolidation has to be complete well before it — a county that begins collecting in July is producing a report from whatever happens to be available rather than from a year of monitoring. If you are a partner whose programme data feeds a county report, your own reporting cycle needs to land data with the county in time to be consolidated, not in time to meet your own deadline. That is usually a quarter earlier than partners assume. The planning artefact CIMES guidance ships a logical framework template as Annex A10. This matters more than it sounds. It means that in Kenya the logframe is not only a donor artefact. It is the expected planning and monitoring instrument for county programmes, including domestically funded ones. An NGO working with a county that presents its programme in logframe terms — result levels, indicators, means of verification, assumptions — is presenting it in the county's own format. It also means the indicator discipline applies. A county indicator without a fixed definition, a baseline and a stated means of verification has the same problems as a donor one, and the aggregation chain makes it worse: an indicator defined loosely at county level will be operationalised four different ways by four sub-counties, and the consolidated figure will be uninterpretable. What partners get wrong Building a county dashboard first. Dashboards are the visible end of the system and the least useful part to fix. If ward-level data is arriving by phone call, a dashboard displays a well-formatted version of an unreliable number. Ignoring the CoMEC. Covered above, and the most common structural mistake. Reporting on a partner calendar. If your data lands in August it cannot be in the 31 July report, regardless of quality. Assuming full compliance. With roughly one in six counties fully compliant as at KIPPRA's January 2024 assessment, the responsible starting assumption is that the structures exist on paper and are partially operational — and that finding out which parts work in your county is the first piece of work, not something to skip. Introducing indicators the county cannot sustain. An indicator that requires a data source only your programme funds will stop being reported the month your programme closes. If the aim is to strengthen the county system, indicators have to be collectible by the county. A note on what we are not asserting We have deliberately not cited a specific edition year for the CIMES guidelines, or the weightings applied to M&E within county performance contracting. Both circulate in secondary sources in versions that do not agree, and getting them wrong in a planning document is worse than omitting them. Confirm both with your county planning department or with MED directly before building either into a workplan.Monival's results module holds result nodes at impact, outcome, output and activity level with their indicators, means of verification and assumptions, displayed as a grouped logframe matrix — the same structure as the CIMES Annex A10 template. Data can be collected offline at ward level and consolidated centrally, which is the tier where county aggregation most often breaks.