Public bodies are measured differently from companies. The question is not whether a profit was made but whether public money was spent within budget, through a defensible process, with a record that survives scrutiny. That changes which parts of an ERP matter and which are close to irrelevant.
Commitment accounting is the core requirement
In a commercial company, budget overruns are a management problem. In a public body they are a compliance failure. Commitments must be recorded when a requisition is approved, not when an invoice arrives, so that the available balance on a budget line always reflects what remains genuinely uncommitted. An ERP that cannot enforce this is the wrong tool regardless of its other strengths.
Procurement that can be defended afterwards
Tender thresholds, mandatory numbers of quotations, evaluation criteria recorded before bids are opened, committee approvals and a complete document trail. The point is not bureaucracy for its own sake; it is that every one of those steps will be examined at some later date by someone who was not present, and the system is what makes the answer available.
Multi-year budgets and carry-forward
Capital projects do not respect fiscal years. Budgets that span several years, with carry-forward rules, revisions and transfers between lines each requiring their own approval, are standard in the public sector and poorly handled by systems designed for commercial annual budgeting. This is worth testing explicitly before selection, with your own rules.
Assets that exist in the register and on the ground
Public bodies typically hold large, dispersed asset portfolios: vehicles, equipment, buildings, IT. A register that is reconciled to a physical verification, with depreciation, custodianship and disposal recorded, is a recurring audit theme and one of the most common findings when it is absent.
Service delivery to citizens is a separate system
Citizen-facing portals, permits and case management are their own domain. An ERP supports them with the financial and procurement backbone and should exchange defined data with them, but proposals that fold service delivery and back-office finance into a single programme tend to produce long timelines and a system that serves neither purpose well.
Phasing that survives a change of leadership
Public sector programmes outlast the people who commission them. Short phases that each deliver something usable, documented well enough that a new director can understand what was built and why, are worth more than an elegant three-year plan that depends on continuity nobody can guarantee.