Taxpayers Subsidize Low-Wage Employers (The Math)

Few phrases start an argument faster than corporate welfare low wages. Critics on the left use it to describe employers who pay too little. Critics on the right use "corporate welfare" for tax breaks and bailouts. The two meet in the middle on one point: public money should not quietly cover a private payroll. The evidence for how often it does is stronger than most people expect, and the limits of the claim matter too.

What does corporate welfare for low wages actually mean?

It means a shortfall with a payer. An employer sets pay at a level a worker cannot live on. The worker enrolls in SNAP, Medicaid, or housing aid, or claims the Earned Income Tax Credit. The household survives, shows up to work, and the employer keeps filling the job at that wage. The public absorbs the cost that the wage did not.

No law calls this a subsidy, and no employer receives a check. The economic effect is what critics point to: labor costs stay lower than they would if wages had to cover basic needs. The UC Berkeley Labor Center has estimated annual public spending on working families through Medicaid, CHIP, SNAP, the EITC, and TANF at well above $100 billion.

Which employers show up in benefit data?

Researchers and state agencies have repeatedly found that large low-wage industries, especially retail, fast food, and home care, account for many workers in benefit enrollment. Several state Medicaid and SNAP agencies have released employer-level counts over the years, and advocacy groups have compiled them.

Treat any single named-company figure with care. Counts vary by state, year, and method, and a large employer with hundreds of thousands of workers will show large raw numbers even when most of its staff is not enrolled. The sturdier finding is structural: industries that pay near the minimum send more of their workers to public programs, because their wages sit nearest the eligibility lines.

How does this compare to real corporate welfare?

It sits beside it. Federal, state, and local governments also hand out tax abatements, grants, and incentive packages to attract or keep employers, often with weak job-quality conditions. Groups such as Good Jobs First have documented the scale of local subsidy deals, and the pattern is bipartisan: governors of both parties compete on incentives.

The two issues overlap when a company receives an incentive package to open a site and then pays wages that leave its staff eligible for benefits. The public pays at the front door and again at the benefits office. Whether that happens in a given case depends on the deal's terms and the wage floor, which is why wage standards attached to subsidies draw support across the spectrum.

Is the argument airtight?

No, and it helps to say where it bends. Economists disagree about who captures the benefit of a wage subsidy such as the EITC. Some research finds that employers may offer slightly lower pay when workers receive a credit, while other work finds most of the gain stays with workers. Safety-net programs also serve people who do not work: children, seniors, and people with disabilities. The claim is not that every benefit dollar subsidizes an employer. The claim is that a meaningful share of spending exists because wages sit below living costs.

That distinction keeps the debate honest. It also keeps it tied to a testable question: what happens to benefit spending when wages rise? The numbers behind that question appear in how low wages cost taxpayers, and the objection that higher pay triggers machines instead is covered in the automation argument. For employers who see it differently, see business owners who support a living wage. The wider cost picture lives on our stats page.

What should a fair standard look like?

Start with the principle that a business should cover the cost of the labor it uses. Wage standards tied to the cost of living, such as those in the MIT Living Wage Calculator, give a measurable target. The bigger case is laid out in why we should raise the minimum wage.

What would employers pay if there were no safety net?

This is the thought experiment that makes the critique sharp. Suppose SNAP, Medicaid, and the EITC vanished tomorrow. Workers at $7.25 could not survive on that pay. Employers would face two options: raise wages to attract staff, or lose them. The safety net removes that pressure. It keeps the labor supply stable at a wage that otherwise would not hold it.

Defenders of the current system respond that the safety net exists for good reasons and that dismantling it would harm children and families. That is correct, and it is not the argument being made. The claim is narrower: when public programs make a low wage survivable, they reduce the cost to employers of paying it. Keeping the programs and raising the floor are compatible goals.

Some employers have drawn the same conclusion on their own. Companies that raised starting pay report easier hiring and less turnover, a tradeoff taken up in business owners who support a living wage. The ones that did not are, in effect, relying on the public to cover the rest.

The policy options are familiar. States and cities can attach wage standards to subsidies and contracts. Congress can raise the federal floor. Employers can raise pay voluntarily. Each moves cost from the benefit line to the payroll line, and each draws opposition from the firms that benefit most from the status quo.

Low pay does not disappear when public programs absorb it. It changes address. A country that wants smaller safety-net bills and fewer working families in line for aid has one lever that works on both: set a wage floor that a person can live on.