Minnesota · Public-sector ERP

Government ERP consultant in Minnesota.

Senior, vendor-neutral ERP consultants for Minnesota counties, cities, 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 Minnesota landscape

87 counties, one State Auditor.

Minnesota's local governments report to one of the most active State Auditor's offices in the country, under a Truth in Taxation process the state pioneered. That's exactly the environment senior, vendor-neutral ERP leadership is built for.

87
counties reporting to the Office of the State Auditor
850+
cities running their own finance and payroll
330
school districts on their own books
TNT
the Truth in Taxation process Minnesota pioneered
Why Minnesota is different

Minnesota doesn't run ERP like anywhere else.

A platform that works elsewhere still has to satisfy Minnesota's rules — the Office of the State Auditor, the Truth in Taxation process, metro fiscal disparities, and PERA reporting. We build for them from day one because we've closed the books under them.

The State Auditor sets the reporting bar

Minnesota's Office of the State Auditor reviews local government reporting closely, with prescribed reporting forms and chart of accounts. If the fund structure doesn't map, reporting becomes a yearly reconstruction.

Truth in Taxation drives the budget calendar

Minnesota pioneered Truth in Taxation, with proposed levies, notices, and public hearings on a fixed schedule. An ERP that can't support the TNT process turns budget season into a scramble.

Fiscal disparities complicate the metro

In the Twin Cities, the fiscal disparities program shares commercial-industrial tax base across jurisdictions. An ERP that can't handle the contribution and distribution puts levy math on a fragile workbook.

PERA and TRA shape payroll

Minnesota payroll runs on the Public Employees Retirement Association and TRA for teachers, each with its own reporting. Configured wrong, payroll and pension break at the first cycle.

What we do for Minnesota 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 Minnesota's reporting.

01

ERP selection & RFP advisory

Vendor-neutral selection that turns how your Minnesota 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
02

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
03

Recovery & stabilization

The call Minnesota 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
04

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 Minnesota reporting

The compliance details a national vendor misses.

These are the requirements that decide whether your Minnesota 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.

  1. 01

    State Auditor reporting

    Fund and account structure mapped to the Office of the State Auditor's chart of accounts and reporting forms so annual reporting comes out of the system.

  2. 02

    Truth in Taxation

    Proposed levy, notices, and hearing dates supported in the budget module so the TNT process is on schedule and defensible.

  3. 03

    Fiscal disparities & levy

    Metro fiscal-disparities contribution and distribution handled so levy and tax capacity math holds up.

  4. 04

    PERA & TRA reporting

    Contributions and reporting to the Public Employees Retirement Association and TRA configured so payroll and pension reconcile.

  5. 05

    LGA & restricted funds

    Local Government Aid, county program aid, and grants tracked so restricted-use reporting holds up.

  6. 06

    Procurement & competitive bidding

    Uniform Municipal Contracting Law thresholds kept compliant through selection and contract.

Outcomes

From an ERP that fights Minnesota to one built for it.

What senior, vendor-neutral leadership changes for a Minnesota government — how ERP tends to go without it, and what it looks like with us accountable to you.

Before
  • Reporting is rebuilt by hand for the State Auditor
  • Truth in Taxation is a budget-season scramble
  • PERA reporting breaks after go-live
  • The vendor drives the timeline, not you
  • Audit findings surface reporting gaps late
After
  • Reporting satisfies the State Auditor
  • Truth in Taxation stays on schedule
  • PERA and TRA reconcile every cycle
  • Your team owns the platform, not the vendor
  • The books are clean before the audit
Across Minnesota

From the Twin Cities to the Iron Range.

We work with Minnesota jurisdictions statewide — on site when a go-live or a close needs hands in the room, and remotely for the steady work in between.

Twin Cities metro

Hennepin, Ramsey, and the suburban counties under fiscal disparities.

Southern Minnesota

Rochester, Mankato, and the counties along the I-90 corridor.

Central Minnesota

St. Cloud and the fast-growing counties north of the metro.

Northern Minnesota & the Range

Duluth, the Iron Range, and the counties of the north.

Testimonials

In our customer's words.

What public-sector leaders say after working with KCT — the same senior team that would lead your Minnesota 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.
Casey Clay Former HCM Director, Southern California City
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.
Donna Simons Sr. Director, Projects & Development — Leander ISD (Texas)
FAQ

Government ERP in Minnesota, answered.

+Do you work with Minnesota 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 Minnesota is the reporting layer: the State Auditor, Truth in Taxation, and PERA payroll, and that's exactly what we build for.
+Which ERP platforms do you support for Minnesota 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 satisfy the State Auditor and Truth in Taxation?
Yes — it's one of the first things we design for. We map your fund structure to the State Auditor's chart of accounts so reporting comes out of the system, and we support the Truth in Taxation levy, notices, and hearings.
+Does your work stay within Minnesota procurement rules?
Yes. We scope selections and RFPs to hold up under the Uniform Municipal Contracting Law. 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 Minnesota 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.
Minnesota public-sector ERP

Bring senior ERP leadership to your Minnesota 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.