PFM SolutionsPFM Solutions

PFM reform commentary

What makes public financial management reform work?

An implementation perspective on connecting reform objectives with everyday decisions, institutional responsibilities and reliable information.

PFM Solutions — AI-assisted editorial content
· 4 min read

Define the improvement before the solution

The World Bank describes financial management information systems as supporting the automation and integration of public financial-management processes, including budget formulation, execution, accounting and reporting. This breadth is a reminder that a system has to serve an institutional purpose. Choosing technology is one part of a reform discussion; defining the financial-management problem should come first.

We propose expressing the objective in terms that a manager or user can test. It might concern the reliability of a financial report, the visibility of an outstanding obligation or the time needed to complete a controlled process. These are illustrative objectives, not claims about an existing project. A clear objective helps the team decide which changes belong in the reform and which can wait.

Source: World Bank — Financial Management Information Systems: scope and implementation resources ↗

Map the process and its owners

Before redesigning a process, the reform team should describe how it currently works. Who initiates a transaction, who checks it, who authorises it and who uses the resulting information? Where does a record pass between offices? We would validate this map with the people doing the work and retain a record of exceptions, rather than rely only on a formal procedure manual.

The proposed process should then identify responsibility at each stage. If a task moves to a different office, the design should explain what authority and support move with it. Where responsibilities overlap, the team should resolve who makes the final decision. These are practical design questions that need an institutional answer before they become requirements in a software specification.

Make information requirements explicit

A reporting requirement should state what the report is intended to support, who will use it and which underlying records it depends on. We recommend reviewing classifications, definitions and reconciliation arrangements early. A useful acceptance exercise would ask users to follow a reported amount back to the relevant transactions and explain any adjustment. This makes the quality of information something that can be demonstrated.

Where historical records must be transferred, the team should agree how completeness and accuracy will be checked and how unresolved differences will be treated. The migration plan should name the officials responsible for accepting the records. A timetable should allow those officials to review the evidence, rather than treat the transfer itself as the end of the task.

Prepare people for routine use

Staff preparation should be organised around the tasks people will perform. We would ask users to practise ordinary transactions, correct errors and handle authorised exceptions. Supervisors should know how to identify problems and where to obtain support. Training attendance can be recorded, but the proposed test of readiness should be whether staff can carry out the relevant process under realistic conditions.

The implementation plan should also specify support after launch. Who receives an issue, who decides its priority and who confirms that it has been resolved? Institutions should agree how changes to procedures and access rights will be approved. These arrangements give the reform an operating structure beyond the project’s initial delivery timetable and make continuing responsibilities visible.

Judge progress through evidence of use

We recommend distinguishing delivery milestones from evidence that the reform is functioning. A completed configuration, an issued manual or a training event can be important milestones. Acceptance should also examine routine use: whether the agreed process is followed, whether information reconciles and whether responsible managers can use it for the intended decisions. The criteria should be agreed before the implementation team reports success.

A short, regularly reviewed issue register can keep attention on what still prevents that use. Each entry should identify an owner, a next action and the evidence required for closure. Reform then becomes a sequence of accountable improvements that can be checked and adjusted. Its value should be assessed through the public-finance function it improves, with any wider service-delivery claims supported separately.

Sources & further reading

Sources checked 2 October 2026. Practical recommendations are editorial proposals; they are not claims of project outcomes.