Half of Utah city spending has no named vendor. Here's why, and how to fix it
When you pull a Utah city's spending from the Utah Public Finance Website and break it out by vendor, a striking share of the money has no vendor attached to it. It's filed under "Not Applicable." Across the nine cities this project indexes, that bucket holds $5.0 billion of $9.8 billion in spending, about 51%. Half of every dollar these cities report can't be traced to a named payee.
| City | Reported spending | "Not Applicable" | Share |
|---|---|---|---|
| Provo | $3.6B | $2.3B | 64% |
| Santaquin | $322M | $168M | 52% |
| Spanish Fork | $1.95B | $965M | 50% |
| Payson | $672M | $285M | 42% |
| Salem | $365M | $154M | 42% |
| Vineyard | $381M | $152M | 40% |
| Lehi | $2.1B | $823M | 39% |
| Mona | $23M | $9M | 38% |
| Nephi | $331M | $104M | 31% |
What "Not Applicable" actually means
Not all of that is hidden in a sinister sense. The bucket lumps together a few different things, and some of them are reasonable.
The biggest piece is usually payroll. Employee wages and benefits aren't reported as payments to a "vendor," because they're people, and the state publishes compensation in a separate dataset. So a chunk of "Not Applicable" is just salaries showing up in the wrong column for a vendor search, not money that's actually concealed.
The second piece is genuine legal protection. Some payments go to individuals the law shields: recipients of assistance, refunds to residents, settlements involving private parties, or records protected under Utah's records statute. Publishing a named individual there can be inappropriate or illegal, and redacting the name is the right call.
The third piece is the threshold problem. Many entities only itemize transactions above a dollar cutoff and roll everything smaller into an aggregate. A thousand small purchases, none individually named, add up to real money that no one can see.
Where it goes wrong
The trouble is that these three reasons get blended into one opaque label, and the label gets overused. A few patterns turn a reasonable practice into a transparency gap.
Whole-transaction suppression is the worst of them. When a payment needs one field protected, say a private recipient's name, some entities drop the entire record instead of masking just that field. The amount, the date, the fund, and the purpose all vanish along with the name, even though none of those are protected.
Low or unexplained thresholds make it worse. If a city only names payments above a high cutoff, a large volume of legitimate spending stays invisible for no reason other than convenience.
And almost no one publishes a reason. "Not Applicable" never says whether a given dollar is payroll, a protected individual, or an under-threshold aggregate. Without that, the public can't tell ordinary bookkeeping apart from something worth questioning.
What governments should do
Cutting the redaction rate doesn't require exposing anyone the law protects. It requires reporting more carefully.
Report at the transaction level, with a named payee wherever no statute requires protection. The default should be a name, with redaction as the documented exception.
Redact the field, not the record. If a recipient's name is protected, mask the name and keep the amount, date, fund, and purpose. A protected name shouldn't erase a public dollar.
Lower the itemization threshold, or drop it. Modern accounting systems can export every transaction. Aggregating small purchases is a choice, not a technical limit.
Publish reason codes. Tag each protected entry with why it's withheld, citing the specific statute. A resident should be able to see that a redaction is payroll versus a protected individual versus an under-threshold rollup.
Reconcile the vendor feed against the check register. The payments a council approves in public should all be traceable in the published data. Where they aren't, the gap is a reporting choice the city can fix.
What residents can do now
Until the reporting improves, the records still exist inside the city. Utah's Government Records Access and Management Act lets you request the detail behind an aggregate: the invoices, the vendor, the purpose. If a city's published spending is half "Not Applicable," a GRAMA request for the underlying transactions in a specific fund is the fastest way to see what the label is hiding. Each city portal includes a GRAMA library with pre-drafted requests for exactly that.
A redaction rate isn't a scandal on its own. But 51% is high enough to be worth asking about, city by city, line by line.
*Source: Utah Public Finance Website (transparent.utah.gov), vendor-level feed for nine cities, FY2014 to 2026; Utah GRAMA, Utah Code 63G-2.*