ListenIf you’ve worked with us for a while, you’ve noticed: we ask a lot of questions about how transactions get coded. Sometimes we circle back weeks later to recategorize something that already looked fine on the books. We know it can feel like overkill on a $400 invoice. It isn’t. Here’s why.
The Minneapolis Story Every Charter Leader Should Read
In April 2026, Minneapolis Public Schools announced the results of an outside review of how the district had coded special education expenses over multiple years. What they found was not fraud, not mismanagement, and not a budget mistake in the traditional sense. It was a coding problem.
By reclassifying miscategorized expenses and correcting underutilized reimbursement mechanisms, MPS expects to recover:
- +$10.7 million in state special education revenue this year
- +$10.8 million next year
- A projected budget gap that drops from $50.5 million to $39.7 million
The spending didn’t change. The students didn’t change. The staff didn’t change. The codes on the transactions changed.
For Minnesota charter schools operating on margins measured in tens of thousands rather than tens of millions, the same dynamic (even at 1 to 2% of total revenue) can mean a teaching position, a paraprofessional, or a curriculum adoption lost every year, compounding quietly in the background.
What UFARS Is, and Why It Controls More Than You Think
UFARS stands for Uniform Financial Accounting and Reporting Standards. It’s the account coding system Minnesota requires all public schools (including charters) to use when recording financial transactions. Every expense, payroll entry, and revenue line gets tagged with a structured string of codes that tell the state what the money was for, who it served, and under what program.
That might sound like a bookkeeping requirement. It’s actually a funding formula.
The Finance codes, Source codes, and Program codes you record this year feed directly into the calculations the Minnesota Department of Education uses to determine next year’s aid. Special education aid. Compensatory revenue. English Learner funding. Lease aid. Each of these revenue streams is driven, at least in part, by what shows up in your UFARS data.
That’s the part that catches school boards off guard: Coding discipline is a revenue issue, not just an expense one. A miscoded salary or service contract doesn’t only land in the wrong category on your financial statements. It can quietly suppress what your school is actually owed from MDE.
Common UFARS Coding Mistakes That Cost Schools Money
Most coding errors are not dramatic. They’re the kind of thing that looks fine on a quick review and gets flagged (if it gets flagged at all) months later at audit. Some of the most common patterns:
Special Education Payroll Miscoding
Salaries for staff who spend meaningful time on special education services are sometimes coded entirely to general education programs. This underreports the district’s special education expenditures, which directly reduces the special ed aid MDE calculates for the following year.
Special Education Org-Site Miscoding
All special education expenses should be coded to the Org-Site where the expenditure occurs. The MDE will compare the Org-Site cost per service hours. When the cost per service hours is out of bounds, the lowest amount of reimbursement is applied for those hours.
Compensatory Revenue Underreporting
Compensatory revenue is tied to services delivered to students who qualify based on low income, homelessness, or other factors. When service costs aren’t mapped to the correct Finance and Program codes, schools miss reimbursement they’ve earned.
Grant-Funded Expenses Coded to General Funds
When restricted grant dollars are coded to the wrong Source, schools can inadvertently blend restricted and unrestricted funds, creating compliance exposure and distorting the revenue picture.
Default Coding Instead of Intentional Coding
This is the most common issue. Accounting systems often have default account strings that populate automatically. When staff don’t override defaults thoughtfully, transactions accumulate in whatever bucket the system chose, not necessarily the right one.
Finance Code Mismatches on Contracts
Service contracts that span program areas (a therapist who serves both special ed and general ed students, for example) require intentional allocation. A single Finance code applied to the full invoice often leaves revenue on the table.
What Rigorous UFARS Coding Actually Looks Like
Catching these issues requires more than a year-end review. By the time an auditor sees a miscoded transaction, it has usually already affected at least one funding cycle. The work that prevents the Minneapolis scenario looks like this:
- Building the full 17-digit UFARS string intentionally, not by default. Every transaction should have a coded string that reflects a real decision, not an auto-populated placeholder.
- Mapping payroll cleanly to Program and Finance codes. Payroll is usually the largest line item on any school’s budget. For staff who serve multiple programs, that means maintaining current allocation records and updating them when roles change.
- Catching issues at the transaction, not at the year-end audit. Monthly reconciliation between the general ledger, SMART Finance, payroll, and invoices is what creates the opportunity to correct errors while they’re still correctable in the current year.
- Staying current with MDE’s annual UFARS updates. MDE revises the UFARS chart of accounts each year. Codes that were correct last year may be retired or reclassified. Schools that don’t track those updates can find themselves coding to obsolete strings without realizing it.
When we ask “should this really be Program 401?” or “is this Finance code right for that grant?” That’s the system working as intended. The detail is the point. Our goal is always to catch these things together, early, before they affect your funding.
Is Your School Leaving Revenue on the Table?
We work with Minnesota charter schools specifically because this detail work matters and most schools don’t have someone doing it consistently in-house. If you’re unsure whether your current coding practices are capturing everything your school is owed, that’s worth a conversation.
Sources
Minneapolis Public Schools, Budget Update: Special Education Revenue (April 2026); Bring Me The News (May 6, 2026); Minnesota Department of Education, UFARS Manual.
