ERP

Common Tyler Munis Implementation Mistakes to Avoid in 2026

Tyler Munis implementation mistakes that cost governments time and money, from rushed timelines to skipped parallel payroll, plus a pre-flight checklist.

Chris Rodney 20 min read
On this page
  1. At a glance
  2. Why Tyler Munis implementation mistakes happen
  3. Mistake 1: Accepting a timeline set by the fiscal year, not by readiness
  4. Mistake 2: Rushing chart of accounts and segment design
  5. Mistake 3: Carrying old processes into new software
  6. Mistake 4: Under-scoping data conversion
  7. Mistake 5: Configuring payroll without every bargaining-unit and timekeeping rule
  8. Mistake 6: Skipping or shortening parallel payroll
  9. Mistake 7: Leaving security roles and workflow approvals to the end
  10. Mistake 8: Mis-scoping utility billing and asset management
  11. Mistake 9: Misreading the split between Tyler’s work and yours
  12. Mistake 10: Assuming reports will “come with the system”
  13. Mistake 11: Not backfilling staff or building internal trainers
  14. Mistake 12: Not managing Tyler project manager and consultant changes
  15. Mistake 13: Treating the cloud vs on-premises decision as an IT detail
  16. Tyler Munis implementation pre-flight checklist
  17. What to do if you are already partway through
  18. Frequently asked questions
  19. Getting your Munis project right from the start

The most common Tyler Munis implementation mistakes are compressing the timeline, rushing the chart of accounts, copying old processes into new software, under-scoping data conversion, configuring payroll and timekeeping without every bargaining-unit rule, and going live without parallel payroll. Most of them are set in motion during planning, long before anyone sees a wrong paycheck or utility bill.

Below are the Munis implementation mistakes we see most often, what each one costs and how to avoid it, followed by a pre-flight checklist your project team can copy into its own plan.

A quick note on names: Tyler now markets Munis as Enterprise ERP. Tyler’s product name update FAQ says the renaming began in February 2022 and gives “Munis will now be Enterprise ERP” as its example. Most finance teams, council packets and job postings still say Munis, so this article uses both.

At a glance

Timeline
A compressed schedule is the root of most other mistakes. Government ERP implementations typically run 12 to 24 months.
Design
The chart of accounts, security roles and approval workflows are hard to change after go-live. Give them real design time.
Data
Conversion needs its own owner, repeated mock loads and a finance reconciliation after each one.
Payroll
Every bargaining-unit rule, overtime rule and step increase must be built, tested and proven in parallel payroll before the first live check.
Scope
Utility billing and asset management are part of the Munis suite. Scope them deliberately, or plan their phase on purpose.
People
Backfill your subject matter experts, build internal trainers, and manage Tyler staffing changes through governance.
Go-live
Decide it on written readiness criteria. The calendar should be an input, nothing more.

Why Tyler Munis implementation mistakes happen

Munis projects usually go wrong because of decisions the government makes about time, staff and scope. Tyler’s Enterprise ERP is a mature, widely used public-sector suite. The trouble that reaches council meetings tends to trace back to how a project was planned and staffed.

The public record bears this out. When the Commonwealth of the Northern Mariana Islands (CNMI) Department of Finance struggled after moving to Munis, the acting Finance Secretary told a Senate confirmation hearing that the original plan allowed at least four to five years for full implementation, and that prior leadership shortened it to 13 months. She said the department could now see “the implications of a rushed implementation.”

Mistake 1: Accepting a timeline set by the fiscal year, not by readiness

In our experience, a go-live date picked because “July 1 is the start of the fiscal year” is one of the most expensive Munis implementation mistakes. The date becomes fixed, and testing, conversion and training get squeezed to fit it.

Fiscal-year starts, calendar-year W-2s and expiring legacy support contracts all create real pressure. Councils want a date, and the vendor schedule gets built backward from it.

In CNMI’s case, the acting Finance Secretary linked employee and vendor complaints to the shortened 13-month plan and said Tyler would need to come back and “conduct a reset.” A reset is a second implementation effort paid for in staff time, vendor hours and lost trust.

Three habits keep the date honest:

Set the target date from the work plan, then add contingency. Our ERP implementation timeline guide walks through the phases of a typical 12 to 24 month project.

Agree with council up front that go-live is a readiness decision with written criteria, and that slipping a date is cheaper than a failed cutover.

Identify a fallback date (for example, the next quarter or the next calendar year for payroll) before you need it.

Mistake 2: Rushing chart of accounts and segment design

The chart of accounts is the foundation every Munis report, budget and audit schedule sits on, and it is the hardest thing to change after go-live. Teams that “just map the old codes” usually regret it within the first year.

Account design meetings feel abstract compared to payroll or utility billing, so they get compressed. Some teams also avoid the hard conversations about how departments, funds, grants and projects should roll up.

A structure that does not fit fund accounting, grant tracking or the way council reads the budget leads to workarounds: spreadsheets for ACFR schedules, manual allocations, and reports nobody trusts. Restructuring later means re-mapping budgets, history and every interface.

A sounder way to lock the structure:

Design the account structure (in Munis terms, how your org and object codes and any project strings combine) around the reports you must produce: the budget book, the ACFR, grant reimbursements, state reporting and department dashboards.

Check with your state auditor or local government finance office whether a uniform chart of accounts or specific state reporting codes apply to you. Requirements vary by state, and a system change is the easiest moment to adopt them.

Have your external auditor review the proposed structure before it is locked.

Get sign-off from finance, budget and at least two operating departments, in writing.

Mistake 3: Carrying old processes into new software

Recreating your legacy system inside Munis wastes most of the value you paid for. The goal is to adopt the software’s standard processes wherever your policies allow, and to change policies that exist only because the old system forced them.

Staff know the old process, and copying it feels safe. Asking “why do we do it this way?” takes time the schedule may not allow.

Old processes translated directly can produce wrong results. When the City of Hoover, Alabama moved from a payroll system more than 25 years old to Munis in July 2022, the city attorney said the old setup “doesn’t translate very well,” and more than 100 employees, including police officers and firefighters, were overpaid or underpaid, with overpayments exceeding $100,000.

What helps:

Run a short “future state” session for each major process before configuration starts. Document what changes, who approves it, and which policy or ordinance needs updating.

Keep a decision log. Every “we will keep the old way” decision should name the reason and the owner.

Expect resistance and plan for it. Our guide on managing staff resistance to new ERP software covers practical tactics.

Mistake 4: Under-scoping data conversion

Data conversion is usually the largest hidden workload in a Munis project, and most of it falls on the government. Tyler loads the data. Your staff extract it, clean it, check it and sign off on it.

Contracts often list conversions as line items (“vendors,” “open POs,” “budget history”), which makes them look like simple deliverables. The effort to clean and reconcile the source data rarely shows up in anyone’s plan.

The City of Appleton, Wisconsin offers a candid example. At an April 2025 committee meeting, the city’s IT director explained that the utility billing move to Munis, underway since mid-2023, was on its fifth or sixth conversion date, because balances had to line up account by account before cutover. He noted that “you can’t even do a balance forward until all those services are attached to correct accounts” (All Things Appleton, April 2025). To its credit, the city planned parallel billing before cutover rather than going live on unreconciled balances.

Ways to keep conversion under control:

Decide how much history to convert early. Converting everything is expensive. Converting nothing leaves auditors and staff without context. A common middle path is several years of summary budget and actuals plus open transactions.

Plan at least three full mock conversions, each followed by a reconciliation that finance signs off.

Assign a named owner per data object (vendors, employees, utility accounts, assets) who is accountable for cleanup.

Reconcile converted balances in full to the legacy trial balance, payroll registers and utility aging reports. Spot checks miss too much.

Mistake 5: Configuring payroll without every bargaining-unit and timekeeping rule

Munis payroll is only as accurate as the rules you give it. Every union contract, overtime rule, shift differential, step increase, leave accrual and retirement contribution needs to be documented, configured and tested before the first live payroll.

Many rules live in memory, side letters or legacy custom code rather than in a document. Public safety schedules, such as 24-hour fire shifts and FLSA work periods, are especially easy to under-specify. Teams also treat timekeeping (Tyler’s Time & Attendance, which many agencies still know as ExecuTime, or a third-party system such as TimeClock Plus) as a separate project from payroll.

Hoover’s payroll problems centered on overtime: the city’s administrator later said the new system was “over-calculating” overtime, and the fire department saw the largest overpayments (ABC 33/40). In September 2024, DeKalb County School District employees in Georgia reported late or short paychecks, including a missing step increase, and district officials attributed the errors to the new “MUNIS” payroll system (Atlanta News First).

Steps that prevent most payroll surprises:

Build a pay rules inventory for every bargaining unit and non-represented group: earnings codes, overtime triggers, differentials, call-back and standby pay, accrual caps, step dates and retirement plans.

Have HR and the labor relations lead sign the inventory along with payroll.

Configure and test timekeeping and payroll together. Tyler describes its Time & Attendance product as handling complex time tracking rules, pay codes and FLSA guidelines, and integrating with Enterprise ERP. Those rules still have to be defined by you.

Test edge cases on purpose: a firefighter working a holiday on an FLSA cycle boundary, a mid-period step increase, a retroactive raise.

Mistake 6: Skipping or shortening parallel payroll

Parallel payroll means running the same pay periods in your legacy system and in Munis, then comparing results employee by employee. Skipping it, or running it on a sample, is how payroll errors reach real paychecks.

Parallel runs are labor-intensive, and they land right before go-live, when the schedule is tightest. Teams sometimes run one parallel, see differences they cannot explain, and go live anyway.

When payroll goes wrong at go-live, the costs show up in overpayment recovery, retroactive payments, penalties, union grievances and lost employee trust. Hoover hired a third-party auditor to double-check payroll records and set up repayment plans for overpaid employees (WBRC).

How to run it properly:

As a rule of thumb, we plan for at least two full parallel payroll cycles covering every employee, and a third if the second still shows unexplained variances.

Pick parallel periods that include overtime-heavy weeks, a holiday and, if possible, a step increase date.

Set a written tolerance: every variance is either explained and accepted, or fixed and re-run.

Compare deductions, employer contributions, retirement reporting and GL postings as well as net pay.

Mistake 7: Leaving security roles and workflow approvals to the end

Security roles and approval workflows decide who can do what in Munis, and they directly affect internal controls and your audit. Designing them in the final weeks leads to either over-broad access or blocked transactions on day one.

Roles depend on finalized processes, so teams wait. Then the last month fills up with testing and training, and roles get copied from a template or from one “power user.”

Weak access design is an audit finding waiting to happen, and confused approvers stall purchasing and payments. In CNMI, a senator told the hearing that a major source of complaints was the lack of training for employees and approving authorities on how to use the new system. In Hoover, the 2024 Kroll review cited staffing gaps and employees who were “not equipped or trained for the responsibilities they were given,” and the city summarized findings that included a lack of written policies and procedures (WBRC, August 2024).

A better sequence:

Design roles from job duties and segregation-of-duties rules, starting during process design.

Map every approval workflow (requisitions, POs, invoices, journal entries, budget transfers, personnel actions) with dollar thresholds that match your purchasing policy and council-approved limits.

Run user acceptance testing with real role assignments. Administrator accounts hide access problems.

Ask your auditor to review the role matrix before go-live.

Mistake 8: Mis-scoping utility billing and asset management

Munis includes both utility billing and asset management, and each deserves its own scope and plan. Tyler’s Enterprise Utilities covers billing and customer information for water, sewer, electric and gas, and its Enterprise Asset Management covers work orders, preventive maintenance and fleet.

Some agencies buy the modules and then defer them indefinitely. Others bundle them into the financials go-live without the staff to handle both. Utility billing in particular touches meter reading, payment channels, rate ordinances and customer service all at once.

Utility billing errors are public. Appleton’s IT director made the point directly at the April 2025 meeting, noting that a billing failure would be highly visible to residents, unlike internal tools.

What to put in the plan:

Treat utility billing as its own phase with its own go-live criteria, including at least one parallel billing cycle.

Inventory every rate, fee and special charge in your ordinances, and test bills for each customer class.

Confirm meter reading, AMI, payment and bank file interfaces early. Our overview of utility billing software for municipalities covers what to evaluate.

For asset management, align the asset register with capital assets in the general ledger before you configure work orders, so GASB 34 reporting and maintenance data agree.

Mistake 9: Misreading the split between Tyler’s work and yours

Tyler’s implementation methodology assumes the government provides decision-makers, subject matter experts, data and testing. Teams that expect Tyler to “implement the system” for them fall behind in the first phase.

Statements of work are long, and responsibilities are spread across sections. Many agencies have not run an ERP project in 15 or 20 years.

When the government misses its tasks (decisions, data extracts, test scripts, sign-offs), the schedule slips and change orders follow. In our experience, a good share of change requests on Munis projects trace back to a government task that was missed or late.

Practical fixes:

Build a responsibility matrix from the signed SOW before kickoff. List every task assigned to the client, with an internal owner and due date.

Appoint a government project manager with authority to make decisions, and protect at least half of that person’s time for the project.

Hold Tyler and your team to the same weekly status: tasks due, tasks late, decisions pending.

If your team does not have the bandwidth to run that side of the project, that is the gap KCT’s ERP implementation service is built for: we lead the government’s side, manage the integrator against the contract and control change orders. KCT has hands-on Tyler experience across Munis financials, HCM, payroll, timekeeping, utility billing, EAM and permitting. We are not a Tyler partner or reseller and take no referral fees from Tyler.

Mistake 10: Assuming reports will “come with the system”

Munis ships with standard reports, but the reports your council, auditors and departments rely on usually need to be defined, built and tested during the project. Leaving them until after go-live means the first month-end close happens without the reports finance needs.

Reporting feels like a post-go-live activity, and nobody owns the inventory of current reports.

Teams fall back to exporting data into spreadsheets, which undermines trust in the new system and slows the first close and the ACFR.

Before go-live, do the following:

Inventory every report you produce today, who uses it and how often. Retire the ones nobody reads.

Map each remaining report to a standard Munis report, a report your team will build, or a dashboard. Confirm with Tyler which reporting and analytics tools are included in your contract and under what names, since product names and licensing change.

Test month-end, year-end and ACFR reports during user acceptance testing with converted data.

Mistake 11: Not backfilling staff or building internal trainers

Your best finance, payroll and utility billing staff will spend a large share of their week on the project. Without backfill, either the project or daily operations suffers, and often both do.

Backfill costs money up front, and agencies assume staff can absorb the extra work.

Plumas County, California chose Munis in 2017. In November 2023, the county administrative officer said the county had spent more than $1 million over five-plus years and the system was still not fully operational, citing high turnover among department heads and staff along with pandemic disruption (Plumas Sun). Supervisors approved another $50,000 for outside help. In Appleton, two of the three IT staff who knew the legacy system had retired by the time utility billing was ready to move (All Things Appleton).

Ways to protect the project and daily operations:

Budget for backfill (temporary staff, overtime or contracted accounting help) in the project budget that goes to council.

Name an internal trainer in each department and train them early. In our experience, vendor training centers on how the software works, so your own trainers need to cover how your agency uses it.

Document configuration decisions and procedures as you go, so knowledge survives turnover.

Mistake 12: Not managing Tyler project manager and consultant changes

Vendor staffing changes are normal on a 12 to 24 month project, but an unmanaged handoff can cost weeks of momentum. Your contract and governance should treat a new Tyler project manager as an event that needs a plan.

Agencies assume continuity and do not ask for transition plans. Knowledge sits in the departing person’s head or inbox.

Lost decisions get revisited, and open issues get re-triaged from scratch. In CNMI, the acting Finance Secretary described the reset phase as starting with “a change over of project manager from Tyler,” with new people on the ground back in an assessment phase.

What to put in place:

Keep your own decision log, issue log and configuration register alongside the vendor’s copies.

Ask for written notice and an overlap period for any change to key vendor staff.

Run a formal handoff meeting covering open issues, pending decisions and upcoming milestones.

Mistake 13: Treating the cloud vs on-premises decision as an IT detail

Whether you run Munis as Tyler-hosted SaaS or on your own servers changes your upgrade cadence, your IT staffing, your security model and your long-term costs. Make it a deliberate decision with finance, IT and leadership at the table.

The decision is sometimes made during contracting by default, without modeling the operating impact.

Tyler is clearly moving its client base toward the cloud. In its fourth-quarter 2025 earnings release, Tyler reported SaaS revenue up 20.6% for the year and said both the number and value of on-premises-to-cloud “flips” signed in the quarter were new quarterly highs. An agency that installs on-premises today should expect that conversation to come back.

Questions to settle before you sign:

Compare SaaS and on-premises over a seven to ten year horizon, including hardware, database licensing, IT staff time, disaster recovery and upgrade effort.

In SaaS, plan for regular vendor-driven updates and assign someone to review release notes and regression-test key processes.

Confirm data ownership, export rights and service levels in the contract.

Tyler Munis implementation pre-flight checklist

Use this checklist before kickoff and again before go-live. Copy it into your project plan, assign an owner to each line, and review it at every steering committee meeting.

Swipe to see all columns →

#CheckpointOwnerWhenDone when
1Go-live criteria approved by steering committee and briefed to councilExecutive sponsorBefore kickoffWritten criteria signed
2Client responsibility matrix built from the SOWGovernment PMBefore kickoffEvery client task has an owner and date
3Backfill funded for key SMEsFinance director, HRBefore kickoffBackfill staff in place
4Chart of accounts design signed off, auditor consultedFinance directorDesign phaseSigned structure and crosswalk
5Future-state process decisions loggedProcess ownersDesign phaseDecision log complete
6Pay rules inventory signed for every bargaining unitHR, payroll, labor relationsDesign phaseSigned inventory
7Timekeeping rules configured and tested with payrollPayroll, department timekeepersBuild phaseEdge-case tests passed
8Security role matrix and approval workflows reviewedFinance, IT, auditorBuild phaseRole matrix approved
9Report inventory mapped to Munis reportsFinance, budgetBuild phaseEach report has a source
10Three mock conversions reconciled to legacy balancesData ownersBuild and testFinance sign-off on each
11Utility billing test bills for every customer classUtility billing managerTest phaseBills match legacy
12Parallel payroll, all employees, two or more cyclesPayroll managerPre-go-liveVariances explained or fixed
13Internal trainers trained, end users trained by roleDepartment trainersPre-go-liveAttendance and sign-off recorded
14Cutover rehearsal completed with timed runbookGovernment PM, Tyler PMPre-go-liveRehearsal within planned window
15Post go-live support plan through first close and first quarter of payrollsGovernment PMPre-go-liveNamed support roster

As a rule of thumb, if more than two of these are open at your go/no-go meeting, move the date.

What to do if you are already partway through

If your Munis project is already underway, the most useful step is an honest status check against the checklist above. Score each line as done, in progress or not started, and share the result with your steering committee.

Projects that are slipping can usually be recovered with re-baselined scope, clearer government ownership and stronger vendor governance. One example from our own work: the City of Oxnard, California brought KCT in after a prior consulting firm had not gotten its multi-module ERP project started, and moved to split go-lives, one module at a time, with each cutover rehearsed (Oxnard case study).

Frequently asked questions

How long does a Tyler Munis implementation take?

A Tyler Munis implementation for a city, county or school district typically takes 12 to 24 months, depending on modules, size and data quality. Financials often go live first, followed by HR and payroll, then utility billing or permitting. Agencies that compress the schedule to hit a fiscal-year date usually pay for it later.

Is Tyler Munis the same as Tyler Enterprise ERP?

Tyler Munis and Tyler Enterprise ERP are the same product. Tyler began renaming its products in February 2022, and its product name FAQ uses Munis becoming Enterprise ERP as the example. Many agencies, council documents and job postings still use the Munis name.

Does Tyler Munis include utility billing and asset management?

Tyler Munis includes utility billing and asset management. Tyler’s Enterprise Utilities handles billing and customer information for water, sewer, electric and gas, and Enterprise Asset Management covers work orders, preventive maintenance and fleet. Each needs its own scope, data conversion and testing plan.

What is ExecuTime in Munis?

ExecuTime is the time and attendance product many Munis agencies use alongside payroll, now marketed by Tyler as Time & Attendance. Tyler describes it as handling complex time rules, pay codes, FLSA guidelines and public safety scheduling, with integration into Enterprise ERP. Its rules must be configured and tested together with payroll.

Should we run parallel payroll before a Munis go-live?

Parallel payroll should be part of every Munis payroll go-live. Running the same pay periods in both systems and comparing every employee’s results catches overtime, deduction and step-increase errors before real paychecks go out. As a rule of thumb, we plan for at least two full cycles.

Do we need an outside consultant for a Munis implementation?

An outside consultant is not required, but many agencies use one when they lack staff to run the government’s side of the project. Fees depend on modules, departments, stakeholders and procurement support. An assessment should come first, and firms differ: some focus on selection, some on implementation, and some can support you at any point.

Getting your Munis project right from the start

Most of the mistakes above are decided before configuration starts: the date, the staffing, the account structure and who owns each government task. Those decisions are cheap to get right early and expensive to fix after go-live.

If you are planning a Munis project or are in the first months of one, run the pre-flight checklist with your team this month. If you want a second set of hands on the government’s side, learn how KCT’s ERP implementation services work or book a conversation with our team.

Ready when you are

Let's talk before it slips.