Headlee and Proposal A constrain the levy
Michigan caps taxable-value growth under Proposal A and rolls back millage under Headlee. An ERP that can't model the rollback and taxable value puts the levy on a fragile workbook.
Michigan · Public-sector ERP
Government ERP consultant in Michigan.
Senior, vendor-neutral ERP consultants for Michigan counties, cities, villages, townships, and school districts — from a stalled go-live to a clean month-end close, a defensible platform selection, or steady managed support.
Senior public-sector ERP operators — trusted by cities, counties, school districts, and special districts across the country.
The Michigan landscape
1,240 townships and one Uniform Act.
Michigan's local governments all budget and report under the Uniform Budgeting and Accounting Act, watched by the Department of Treasury. That's exactly the environment senior, vendor-neutral ERP leadership is built for.
83
counties reporting to the Department of Treasury
280+
cities and 250+ villages statewide
1,240
townships running their own books
800+
school districts on their own finance and payroll
Why Michigan is different
Michigan doesn't run ERP like anywhere else.
A platform that works elsewhere still has to satisfy Michigan's rules — the Uniform Budgeting and Accounting Act and the F-65, the Headlee millage rollback and Proposal A, and MERS reporting. We build for them from day one because we've closed the books under them.
Treasury reporting has its own format
Michigan local units file the F-65 Annual Local Unit Fiscal Report and audit with the Department of Treasury. If the fund structure doesn't map, filing becomes a yearly reconstruction.
MERS and MPSERS shape payroll
Michigan payroll runs on the Municipal Employees Retirement System and, for schools, MPSERS, each with its own reporting. Configured wrong, payroll and pension break at the first cycle.
The Uniform Act sets the guardrails
Michigan's Uniform Budgeting and Accounting Act and Treasury Numbered Letters govern how you budget and account. We keep the selection and configuration inside those rules.
What we do for Michigan governments
The full ERP journey, led by people who've done the work.
Whether you're choosing a platform, leading a full ERP implementation, rescuing one that's slipping, or keeping a live system healthy with managed services and support, the same senior operators lead the engagement end to end — vendor-neutral, embedded with your team, and accountable to Michigan's reporting.
ERP selection & RFP advisory
Vendor-neutral selection that turns how your Michigan jurisdiction actually runs into a defensible platform choice — with an RFP that survives procurement review and a TCO your board can stand behind.
- Requirements built around state reporting
- RFPs aligned to state procurement law
- 7–10 year total cost of ownership modeling
Implementation leadership
Senior program leadership for new finance, HCM, utility billing, and EAM deployments — on-time go-lives with the state's reporting configured from the start, not retrofitted after audit findings.
- Chart of accounts mapped to state filings
- Payroll built for the state retirement system
- Engineered go-lives, scope held
Recovery & stabilization
The call Michigan finance directors make when an implementation is slipping, close won't reconcile, or a new firm just left the project half-built. We stabilize the system and finish the work.
- Stalled go-lives put back on a timeline
- Reconciliation and close-cycle repair
- Reporting back in compliance
Managed services & support
Ongoing, senior-led support that keeps a live ERP healthy through fiscal year-end and staff turnover — without the dependency model that keeps you paying for problems you didn't create.
- Month-end and year-end close support
- Enhancement, patching, and upgrade paths
- Knowledge transfer, so you're never trapped
Built for Michigan reporting
The compliance details a national vendor misses.
These are the requirements that decide whether your Michigan ERP is a clean system of record or a source of annual pain. We design for each one before go-live — not in a corrective action plan afterward.
-
01
Treasury F-65 & audit reporting
Fund and account structure mapped so the F-65 and audited statements satisfy the Department of Treasury.
-
02
Headlee rollback & Proposal A
Millage rollback and taxable-value calculations supported in the budget module so the levy is defensible.
-
03
MERS & MPSERS reporting
Contributions and reporting to the Municipal Employees Retirement System and MPSERS configured so payroll and pension reconcile.
-
04
Act 51 & restricted funds
Act 51 road funds, revenue sharing, and grants tracked so restricted-use reporting holds up.
-
05
Procurement & competitive bidding
Local charter and statute bidding thresholds kept compliant through selection and contract.
-
06
Utility billing & DDAs
Water, sewer, and downtown development authority accounting configured so exceptions and rebills stay the exception.
Outcomes
From an ERP that fights Michigan to one built for it.
What senior, vendor-neutral leadership changes for a Michigan government — how ERP tends to go without it, and what it looks like with us accountable to you.
- The F-65 is rebuilt by hand every year
- Headlee and Proposal A math is a fragile workbook
- MERS reporting breaks after go-live
- The vendor drives the timeline, not you
- Audit findings surface reporting gaps late
- The F-65 comes out of the system
- Headlee rollback and taxable value are modeled
- MERS and MPSERS reconcile every cycle
- Your team owns the platform, not the vendor
- Reporting is clean before Treasury and the auditor
Across Michigan
From Metro Detroit to the U.P.
We work with Michigan jurisdictions statewide — on site when a go-live or a close needs hands in the room, and remotely for the steady work in between.
Metro Detroit
Wayne, Oakland, and Macomb — the state's largest, most complex jurisdictions.
West Michigan
Grand Rapids, Kent, and the lakeshore communities.
Mid-Michigan & the Capital
Lansing, Ann Arbor, Flint, and Saginaw.
Northern Michigan & the U.P.
From the resort communities up north to the Upper Peninsula.
Testimonials
In our customer's words.
What public-sector leaders say after working with KCT — the same senior team that would lead your Michigan engagement.
★★★★★
KCT transformed our implementation from start to finish. Their expert team provided seamless, tailored support, ensuring every step of the process was efficient and effective. With a proactive approach and deep industry expertise, KCT quickly resolved challenges, paving the way for long-term success. Their commitment to excellence and true partnership has had a lasting impact on our operations. I highly recommend KCT to any organization seeking exceptional support during both implementation and ongoing operations.
★★★★★
The KCT Team takes the time to understand our processes and invests in our team's success, which has fostered a strong sense of trust in their ability to lead us to effective solutions. Their communication has always been timely, and their project management skills are exceptional. KCT brings a wealth of tools, expertise, and experience to the table, consistently delivering positive results for our district. I highly recommend them for any organization seeking a reliable partner in technical solutions.
FAQ
Government ERP in Michigan, answered.
+Do you work with Michigan governments even though your case studies are in other states?
Yes. Our published case studies are in California and Texas, but public-sector ERP is a national discipline and the operating model is identical — senior operators, vendor-neutral, embedded with your team. What changes in Michigan is the reporting layer: the F-65 and the Uniform Act, Headlee and Proposal A, and MERS payroll, and that's exactly what we build for.
+Which ERP platforms do you support for Michigan agencies?
We're hands-on with every major public-sector ERP platform and strictly vendor-neutral — no reseller, referral, or partnership with any vendor. We tell you which platform genuinely fits your jurisdiction's size, reporting, and procurement path.
+Can you make our ERP produce the F-65 and handle Headlee?
Yes — it's one of the first things we design for. We map your fund structure so the F-65 and audited statements satisfy Treasury, and we model the Headlee rollback and Proposal A taxable value.
+Does your work stay within Michigan procurement rules?
Yes. We scope selections and RFPs to hold up under your charter and statute bidding requirements. We're not the vendor, so our advice on the buy is genuinely independent.
+We're mid-implementation and it's slipping. Can you step in?
That's one of the most common ways Michigan finance directors first call us. We join a live project, stabilize the go-live, repair close and reconciliation, and get reporting back in compliance — whether the original firm is still on the project or already gone.
Michigan public-sector ERP
Bring senior ERP leadership to your Michigan government.
A 30-minute discovery call. Tell us your jurisdiction, your platform, and where things stand — a selection ahead, an implementation slipping, or a close that won't reconcile. You'll reach Chris Rodney, our Client Relationships Director, and the senior operators who would lead the work.