State and local governments have different needs than private companies when implementing enterprise resource planning (ERP) systems. They work with tighter budgets, face more regulatory oversight, deal with aging workforces and operate under constant public scrutiny. ERP implementation success needs a real understanding of government accounting, treasury management and how public finance departments actually work. At Baker Tilly, we bring this unique combination: depth of expertise in government accounting, coupled with deep Oracle Cloud know-how. From our experiences with state and local clients, we have consolidated the following insights to inform prospective organizations as they embark on their Oracle Cloud ERP journey.
How local government organizations are different
Government does not pursue profit. They manage risk, meet compliance and respond to constant pressures from nature to politics. Technology decisions in this sector are often reactive rather than strategic. A failed audit, key staff departures, an inability to close the books – any of these factors can trigger urgent modernization efforts with compressed timelines and inadequate planning.
Government technology projects also involve competing stakeholder interests. Elected officials focus on public perception. Finance directors prioritize audit compliance. Information technology (IT) departments care about stability and security. On top of that, the public visibility of major technology investments slows down decisions.
Achieving buy-in: Three critical stakeholder to address
- Treasury management: Treasury management is where government ERP implementations most often fail. The complexity of fund accounting, cash pooling, investment tracking and bank reconciliations creates significant configuration challenges. Common failures include late or failed bank reconciliations, fund balance calculation errors, investment tracking deficiencies and intergovernmental transactions that process incorrectly. Therefore, treasury management requires dedicated focus during requirements gathering, configuration and testing, with subject matter experts actively involved throughout.
- Controller’s office and front-line users: When IT departments drive implementations without meaningful finance department input, systems get configured in ways that do not reflect how work actually gets done. The consequences of these decisions surface after go-live, when they are far more expensive to fix. Finance staff face pressures that make engagement difficult:
