Choosing an ERP for a public agency: IPSAS, controls and procurement

Why public-sector ERP is different

An agency's ERP is a control system before it is a productivity tool. It must enforce appropriations, record commitments before spending occurs, and produce an audit trail that stands up to an auditor-general. Many governments, including Nigeria, have moved to accrual-based IPSAS reporting, which raises the bar for asset registers, accruals and consolidated statements.

Private-sector templates rarely cover these needs out of the box. A credible platform must support budget hierarchies, multi-year appropriations, commitment and obligation tracking, and fund segregation where donor money is involved.

Define the control framework first

Before comparing vendors, document the chart of accounts, budget structure, approval thresholds and segregation-of-duties rules. These decisions drive configuration effort more than any other factor, and they are policy decisions that only the agency can make.

We recommend a fit-gap workshop that walks real processes, such as requisition to payment, payroll and asset disposal, through each shortlisted platform.

Procure for outcomes, not features

Requirements should be written as scenarios with acceptance criteria, for example "produce an IPSAS-compliant statement of financial position for the quarter within five working days of period close". Scenario-based evaluation exposes gaps that feature checklists hide.

Total cost of ownership over five to seven years, including licences, hosting, support and upgrades, matters more than the initial implementation price.

Plan the hard parts

Data migration and adoption cause most ERP delays. Budget for data cleansing, parallel runs and role-based training from the start, and appoint business owners who are accountable for each module after go-live.