RICE is a project-planning framework used in ERP migration to identify Reports, Interfaces, Conversions, and Extensions or Enhancements. For Canadian municipalities, a RICE inventory helps make hidden migration work visible before implementation begins, especially when legacy systems, spreadsheets, municipal add-ons, tax workflows, utility billing, payroll handoffs, and PSAB reporting dependencies are involved.
A strong RICE inventory helps municipalities understand what must be rebuilt, redesigned, retired, migrated, or replaced before moving to a modern ERP or civic workflow environment. It acts as an extension of the current-state mapping process.
What does RICE stand for?
RICE stands for:
- Reports
- Interfaces
- Conversions
- Extensions or Enhancements
Each category captures a different kind of work that may be required during ERP migration.
Reports are the outputs the municipality relies on for finance, operations, leadership, audit, council, compliance, and management reporting.
Interfaces are the system connections and handoffs that move data between applications.
Conversions are the data migration activities required to move, clean, transform, validate, or retain legacy data.
Extensions or enhancements are system changes, configurations, workflows, or custom functions needed when standard functionality does not fully support municipal requirements.
Why RICE matters in a municipal ERP migration
Municipal ERP migration is rarely a simple system replacement. Many municipalities have years of accumulated reports, spreadsheets, integrations, side systems, and manual processes connected to finance, tax, utilities, payroll, assets, records, and public works.
Without a RICE inventory, critical dependencies may remain invisible until late in the project.
That can create risk around:
- Year-end reporting
- PSAB schedules
- Audit evidence
- Property tax billing
- Utility billing
- Payroll-to-finance handoffs
- Banking files
- Management reports
- Asset records
- Grant reporting
- Council reporting
- Historical data access
- Cutover planning
Reports: what outputs must continue?
Reports are often the most visible part of a migration, but they are also easy to underestimate.
Municipalities should inventory reports used for:
- Financial statements
- Fund accounting
- Budget reporting
- Grant reporting
- Deferred revenue
- Reserves
- Tangible capital assets
- Accounts payable
- Accounts receivable
- Cash and bank reconciliation
- Tax billing
- Utility billing
- Payroll costing
- Council or board packages
- Department-level reporting
- Audit requests
For each report, the municipality should ask: Who uses it? How often is it used? What decision or process does it support? Which data fields does it depend on? Is it still needed? Can it be replaced by standard reporting? Does it require historical data? Does it support audit evidence or compliance?
Not every report should be recreated. Some should be consolidated, redesigned, or retired.
Interfaces: what systems need to talk to each other?
Interfaces are the handoffs between systems. In a municipal environment, these handoffs often connect finance with operational systems.
Common interfaces may include:
- Payroll to finance
- Property tax to finance
- Utility billing to finance
- Banking and payment files
- Procurement systems
- Asset management systems
- Work order systems
- GIS
- Document management
- Citizen portals
- Payment processors
- Reporting tools
- External compliance or filing processes
Each interface should be documented by source system, target system, business owner, technical owner, data fields, frequency, file type, validation, error handling, cutover, and testing requirements. For municipalities, the key question is not only whether an interface exists. It is whether the municipality understands what happens when that interface fails, changes, or moves to a new platform.
Conversions: what data must move?
Conversions cover the migration of data from legacy systems into the future environment.
Municipalities should classify data into practical groups:
- Data that must be migrated in detail
- Data that can be summarized
- Data that should remain read-only
- Data that should be archived
- Data that should be cleaned before migration
- Data that should not be carried forward
Common municipal conversion areas include: Chart of accounts, fund structures, vendors, customers, employees, property tax/utility accounts, assets, projects, grants, reserves, transactions, opening balances, and audit evidence.
For each data set, municipalities should define ownership, field mapping, validation rules, reconciliation expectations, and retention needs. The most important conversion question is not “can the data be loaded?” It is “can the migrated data be trusted, reconciled, and used after go-live?”
Extensions or enhancements: what gaps need to be addressed?
Extensions or enhancements capture functionality that is not handled cleanly by standard system configuration.
In municipal ERP migration, this may include:
- Special approval workflows
- Municipal billing rules
- Public-sector payroll rules
- Union or collective agreement workflows
- Custom forms
- Specialized reports
- Additional fields
- Data validation rules
- Role-based access requirements
- Resident-service workflows
- Grant tracking needs
- Asset or work order processes
- Document evidence workflows
The goal is not to customize everything. The goal is to separate true requirements from old habits. Each extension or enhancement should be reviewed carefully to verify if it is operatively or legally required, and whether standard configuration can support it instead of building custom functionality.
What should be included in a municipal RICE inventory?
A practical RICE inventory should include more than a name and description.
For each item, capture: RICE type, item name, business process, business owner, technical owner, current system, future-state requirement, frequency of use, criticality, data involved, related reports, current pain point, migration decision, testing requirement, cutover dependency, retirement decision, and open questions. This gives the project team a shared view of what needs attention before implementation accelerates.
How RICE supports PSAB and audit readiness
RICE is especially useful for PSAB readiness and year-end readiness because many reporting and evidence dependencies live outside the core ERP. A RICE inventory helps identify these dependencies—like spreadsheet-based reserve trackers or public works asset tables—before they become audit issues.
How RICE supports Dynamics GP migration
For municipalities moving off Dynamics GP migration planning, RICE is one of the most important planning tools. A Dynamics GP environment may include Management Reporter outputs, Excel-based reports, municipal add-ons, payroll costing handoffs, property tax/utility billing integrations, banking files, and custom import tools. RICE helps the municipality decide what needs to be rebuilt, replaced, retired, migrated, or archived before the new environment goes live.
When should municipalities build the RICE inventory?
The RICE inventory should begin before procurement or early in implementation planning. If the municipality waits until configuration or testing, the project may discover too late that a report, interface, data set, or enhancement is critical.
The best timing is:
- During current-state discovery: Identify existing reports, interfaces, data, and workarounds.
- Before procurement or vendor evaluation: Use the inventory to ask better questions and evaluate fit.
- During implementation planning: Confirm what will be built, configured, replaced, or retired.
- Before testing: Convert the inventory into test scenarios.
- Before cutover: Confirm all critical items have an owner and decision.
What this means for your municipality
RICE is not just a technical spreadsheet. It is a municipal risk-management tool.
For Canadian municipalities, a good RICE inventory helps finance, IT, operations, and leadership understand what the current environment really depends on before migration decisions are locked in. It supports better procurement, safer cutover planning, stronger testing, and clearer PSAB and audit-readiness preparation.