How to find out if your employer has been caught stealing wages in Kansas City

Wage theft is the crime that does not look like one. Nobody breaks a window. The paycheck simply comes up short (the overtime that was not counted, the half hour before the clock started, the tips that went somewhere else), and the person it happened to usually has no way to find out whether it has happened to anyone else at the same place.

There is a way. The federal government keeps the record and publishes it, and it runs a second tool that answers a more urgent question: whether it is already holding money that belongs to you, and how long you have to claim it.

Here is how to use both, what the Kansas City record actually says, and the four places this data will mislead you if you let it.

The thirty-second version

If you want to know whether money is waiting for you, go to webapps.dol.gov/wow, the Workers Owed Wages search. Type an employer’s name or a keyword, optionally filter by state, and look for yourself. It is free, needs no account, and takes about a minute.

If you want to know whether an employer has been caught, the Department of Labor’s Wage and Hour Division publishes every concluded compliance action: employer, address, city, industry, which laws were broken, back wages agreed to, employees affected, and penalties assessed.

Before you trust either, read “Four ways this data will fool you” below. One of them is the difference between “no record” and “clean,” and they are not the same thing.

The money with a deadline

This is the part most people do not know exists, and it is the part with a clock on it.

When the Wage and Hour Division wins back wages for workers, it does not always manage to hand the money over. People move. Businesses close. In the tool’s own words:

“When the Wage and Hour Division finds labor law violations, we often get unpaid wages on behalf of workers. If we cannot locate these employees, we hold their back wages while we continue to look for them. After three years, if we remain unable to find the person owed back wages, we are required to send the money to the U.S. Treasury.”

So the money is real, it is sitting there with a worker’s name attached, and if that worker never turns up it stops being theirs. Three years.

The search takes a company name or a keyword (the tool suggests an industry or a product, like drywall) and an optional state filter. If your former employer is in there, you then check for your own name and, if it appears, request a claim form. The Stare confirmed on September 10, 2026 that the tool answers ordinary requests and returns Kansas City-area employers on a plain keyword search with the state set to Missouri.

If you have worked a job in this metro where the math on a paycheck never quite added up, this is the ninety seconds most worth spending.

What the federal record says about Kansas City

The Stare pulled the complete Missouri and Kansas enforcement file on September 10, 2026 — every concluded federal wage-and-hour compliance action in both states, 12,725 of them. Filtered to 24 metro municipalities on both sides of the state line, here is the record:

That is roughly $761 per worker, across a file that runs from 1999 to April 2026.

Sorted by which law was broken, the Fair Labor Standards Act (minimum wage and overtime, the ordinary machinery of a paycheck) accounts for 1,833 metro cases and $23.2 million of the total. The Service Contract Act and Davis-Bacon, which govern work done under federal contracts, account for another $4.9 million between them. Two hundred and eight cases involved the Family and Medical Leave Act.

Another 170 metro cases involved child labor: 748 minors employed in violation of federal law, with $1,887,703 in civil money penalties assessed. Child labor violations carry penalties rather than back wages, which is why that figure appears in the penalty column and not the wage one.

By industry, full-service restaurants lead the metro on both counts (344 cases and $4.34 million in back wages), with limited-service restaurants adding 183 cases and home health care 43. Restaurants are among the most heavily investigated industries the division works, so a ranking like this reflects where inspectors look as much as where the conduct is; it is not a league table of the worst employers in town.

No employer is named in this article. They are named in the data, in public, and any reader can run the search below and read the names for themselves. That is a decision this paper has made about its own pages, not a limit on what you can find out.

Four ways this data will fool you

1. “No record” does not mean “clean”

This is the most important thing on the page, and the Department of Labor says it first. From the dataset’s own published description, captured September 10, 2026:

“NOTE: Findings Start Date and Findings End Date are not equal to Case Open Date and Case Close Date, which are not included in the dataset.”

The file records when an investigation’s findings period began and ended. It does not record when the case opened, when it closed, or when it was published. Which matters, because the recent years look like this:

Read carelessly, that is a collapse in federal wage enforcement. It cannot be read that way, and The Stare is not reading it that way. A file of concluded actions is a rear-view mirror: an investigation opened last year has not concluded, and a case that concluded last quarter may not be published yet. The dataset updates quarterly, its catalog record was last updated June 4, 2026, and the newest findings end date in Missouri or Kansas is April 17, 2026. The data cannot separate lag from decline, so this paper reports the shape and does not assign it a cause.

The practical consequence for a worker or a job applicant: an employer with nothing recent in this file has not been cleared of anything. It has no concluded federal case in a file that is structurally behind. Most employers are never investigated at all.

2. The repeat-offender field is blank 94 percent of the time

There is a column called flsa_repeat_violator, and it is the one you would most want. Across all 12,725 Missouri and Kansas records it reads:

• N/A: 11,948 records (93.9%)
• R (repeat): 689
• RW: 65
• W: 23

So the field that would answer “has this employer been caught before” declines to answer on nineteen records out of twenty. If you want to know whether there is a pattern, do not trust the flag. Search the employer’s name, get every case, and read the list yourself.

3. A violation is not money

Of the 2,266 metro cases where violations were found, 583, or 25.7 percent, carry zero dollars in back wages.

A violation can be technical. It can be corrected without a monetary finding. Penalties are assessed on a separate track from back pay, which is why child labor shows 170 cases and $0 in back wages alongside $1.89 million in penalties. Count cases and you overstate what workers recovered; count dollars and you understate how often employers were found in violation. Quote both.

4. The city name is free text, and it will betray a search

The cty_nm field is typed, not chosen from a list. In Missouri and Kansas:

• Kansas City: 1,309 records
• KANSAS CITY: 49 records

They are different strings. An exact-match search for the ordinary spelling silently drops 49 cases.

Go the other way and search for the substring “kansas city” and you pick up 13 records from Arkansas City, a town in Cowley County roughly 200 miles from here, because its name contains the letters. You also collect North Kansas City, which is a different municipality with its own government.

The fix is the boring one: match case-insensitively on the whole field, not on a fragment of it.

One more thing the description gets wrong

The dataset’s published description opens: “The dataset contains all concluded WHD compliance actions since FY 2005.”

It contains more than that. 251 Missouri and Kansas records carry findings periods that ended before FY2005, the earliest on January 15, 1999, more than five years before the stated start. This is a case of a file being more complete than its own label, which is the harmless direction for a discrepancy to run, but it is worth knowing before you tell someone the record only goes back to 2005.

Check us

The Workers Owed Wages tool needs nothing but a browser: webapps.dol.gov/wow.

The enforcement dataset sits behind a free API key from dataportal.dol.gov, which requires a Login.gov account and two-factor enrollment. A human has to register it, and no script can do it for you. With a key, the pull that produced every figure above is two requests. The filter syntax is worth writing down, because the obvious form fails:

# WORKS — an object with an "and" array
filter_object={"and":[{"field":"st_cd","operator":"eq","value":"MO"}]}

# FAILS with HTTP 500 — the bare array
filter_object=[{"field":"st_cd","operator":"eq","value":"MO"}]

The 500 it returns complains that keywords must be lowercase, which is not the problem and will send you looking in the wrong place. Pages cap at 6 MB, so request 1,000 rows at a time, and pace them: a fast burst earns an HTTP 429 that persists for a good while.

The Stare keeps a script that re-derives every number in this story from the archived pull, and it ran clean on September 10, 2026.

Where this record does not reach

State claims. This is federal wage-and-hour law only. A claim under Missouri or Kansas state law — including state minimum wage law — does not appear here at all. For those, start with the Missouri Department of Labor and Industrial Relations or the Kansas Department of Labor.

Anything that was never investigated. The file is a record of federal compliance actions, not of conduct. It contains the employers the division looked at.

Your own case, if it is open. Concluded actions only. If you have a live complaint, it is not in here, and its absence means nothing.

If you think wages were taken from you, the division takes complaints directly, and filing one does not require a lawyer or a fee. The record above is the part that is already public. The part that is not is the one somebody has to report.

---

Sourcing: all enforcement figures are The Kansas City Stare's own counts from the U.S. Department of Labor's Wage and Hour Division enforcement dataset, the complete Missouri and Kansas slice pulled from the department's v4 open-data API on September 10, 2026 and archived at editorial/_sources/wage-theft-lookup-2026-09/ with a script that re-derives every figure. Quotations of the dataset's scope and of its note on case dates are from the department's own catalog record, captured the same day. The description of the Workers Owed Wages tool and the three-year Treasury rule are quoted from that tool's own page, also captured the same day. No employer and no individual is named in this piece; the underlying records are public and name both.