Build1 publisher3 min readPublished
Public Law 119-21 turns a 10 percent SNAP error rate into a 15 percent state cost share
The penalty starts in fiscal 2028, but FY2025 and FY2026 performance sets each state's tier, and Elastic is selling ingest-time flagging into that window. The national error rate was 10.93 percent in FY2024.
The Engineer · Build desk

What happened
- Public Law 119-21 makes states at or above a 6 percent SNAP payment error rate fund a share of benefit costs from federal fiscal 2028, with the share reaching 15 percent at error rates of 10 percent or more.
- Elastic's post says FY2025 and FY2026 performance sets each state's starting tier, leaving about a year and a half of measured performance to work with.
- The national payment error rate hit 10.93 percent in FY2024, and 44 states filed corrective action plans.
- SNAP served 41.7 million people across 22.2 million households and moved $100.3 billion in federal spending in FY2024.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- cost A state issuing $400 million of benefits a year picks up a $60 million annual bill at the top tier, out of state funds, for performance measured two years earlier.
- constraint Detection stood up in FY2027 cannot change a starting tier fixed by FY2025 and FY2026 numbers; it can only help a state climb out of the tier it is already in.
- decision Agencies have to decide whether they are buying error-rate reduction or fraud recovery, because the statute prices the first while two of Elastic's three layers are built for the second.
The only layer in Elastic's post with implementation detail in it is the first. An ingest pipeline checks each case's income against the state's published limit table as the case is indexed. It tags the case before a caseworker sees it, and attaches a reason tied to policy instead of a hardcoded value [7]. An ingest pipeline is the right place for a threshold check, and it fixes the flag at index time. If the limit table is a lookup the pipeline reads on the way in, every case indexed before the table changes keeps its old tag until someone reindexes it. When the limits move, you have two vintages of flags in one index and a reindex job that has to be scheduled by somebody.
Layers two and three are aimed at something else. Elastic's machine learning, supervised and unsupervised, runs continuously to find drift with no fixed threshold. It looks for income growing past eligibility, an address cycling across counties, claim activity that is statistically anomalous against an entity's own history [9]. Agent Builder puts a conversational interface over the case data. An investigator can ask why a case was flagged and get a recommended next step, and matching runs on a validated compound key instead of a single field [10]. Both are fraud tools. The post draws the line itself: a missed income exclusion, it says, "looks identical to fraud on an audit report, but it's a search problem, not an integrity problem" [8].
The statute prices the payment error rate [2]. Whether continuous drift detection moves that number depends on how the rate is sampled and what counts as an error. Elastic's post skips the measurement [17]. The path from a flagged case to a lower measured rate is what a procurement has to establish before the FY2026 books close.
The exposure is easy to size. At an error rate of 10 percent or higher, the state funds 15 percent of benefit costs [2]. A state issuing $400 million of benefits a year owes $60 million under that tier [14]. The FY2024 national rate was 10.93 percent [4], above the 10 percent line [15], so a state performing at the national average starts in the top tier.
Underneath all three layers is a premise: most systems check eligibility at determination and not continuously, so nobody is watching drift at scale [12]. The support offered for it is the Government Accountability Office's 2025 finding that USDA's Food and Nutrition Service has not comprehensively assessed which theft-prevention measures states use [11]. So there is no verified baseline for who is watching. GAO's finding is about what the federal agency knows. Nobody can rank the states today. That is not evidence that they have stopped monitoring.
What to watch
- FNS publication of FY2025 state-level payment error rates, and which states land above 6 and above 10 percent.
- Whether FNS builds the state-by-state theft-prevention baseline GAO found missing in 2025.
- Whether Elastic documents how the published limit table is loaded and how already-indexed cases get re-tagged.