In this article
AI and Payroll: What Payroll Failures Cost, and What Is Known About AI Doing It
Sources checked: November 9, 2026. AI-assisted draft, pending editor review.

Payroll is where "usually right" is not good enough. The same inputs must give the same pay every time, and a mistake lands in someone's paycheck. Generative AI writes fluent answers, but it can also write a confident wrong one. That makes it a poor calculator and a useful assistant around the calculation. The record shows why.

What payroll errors cost, in numbers
| Evidence | Figure | What it tells you |
|---|---|---|
| U.S. Wage and Hour Division, fiscal year 2025 | More than $259 million in back wages for 176,957 employees, about $1,465 per worker. Fiscal year 2024 was about $203 million | Wage-and-hour enforcement recovers hundreds of millions of dollars a year. These are violations of all kinds, not only payroll-system errors |
| Canada's Phoenix pay system | By July 2018, pay problems for close to 80% of 290,000 public servants. Cost over C$5.1 billion (Canadian dollars) by June 2025 against a budget of about C$310 million. A backlog of 216,000 pay transactions remained in February 2026 | A payroll failure can last for years and cost many times the budget |
| Kronos Private Cloud outage, December 2021 | A ransomware attack kept a hosted payroll product down for several weeks. Employers used manual time sheets or repeated earlier payrolls. Settlements include about $13 million (PepsiCo), $2.4 million (Cargill), $1.2 million (UMass Memorial) and a $5.5 million UKG fund | Even correct software fails when it is unavailable, and wage claims follow late or short pay |
| NYC MyCity chatbot, 2024 | Said an employer could take a cut of workers' tips, which is wrong | A fluent answer about pay can be illegal |
| Air Canada chatbot, 2024 | A tribunal held the airline responsible for a wrong policy answer from its chatbot and awarded the customer about 812 Canadian dollars in total, including interest and fees | In this dispute the airline answered for its chatbot, which is a reason to test any bot you deploy, not a general legal rule |
View the numbers as a table
| PepsiCo | $13M |
|---|---|
| UKG settlement fund | $5.5M |
| Cargill | $2.4M |
| UMass Memorial | $1.2M |
From the table above. PepsiCo's is 'nearly $13 million' per Bloomberg Law via Legal Dive.
The Wage and Hour Division's own data show how recoveries have moved. Fiscal year 2025 was the highest since 2019, although fewer employees were paid back than in 2019 to 2021.
| Fiscal year | Back wages recovered | Employees receiving back wages |
|---|---|---|
| 2025 | $259.3 million | 176,957 |
| 2024 | $202.7 million | 151,989 |
| 2023 | $212.3 million | 163,768 |
| 2022 | $213.2 million | 152,970 |
| 2021 | $234.4 million | 193,796 |
| 2020 | $257.8 million | 229,934 |
| 2019 | $322.5 million | 313,941 |
View the numbers as a table
| FY 2025 | $259.3M |
|---|---|
| FY 2024 | $202.7M |
| FY 2023 | $212.3M |
| FY 2022 | $213.2M |
| FY 2021 | $234.4M |
| FY 2020 | $257.8M |
| FY 2019 | $322.5M |
From the table above. These cover violations of all kinds, not only payroll-system errors.
What we found, and did not find, about AI doing payroll
The first three rows of the first table above are not AI failures. They show what payroll errors cost. We searched for a verified case of a generative AI tool causing a payroll error at scale and did not find one. The closest item is a November 2025 blog post relaying an anonymous account of an AI payroll tool halting a paycheck over an "irregular" timecard, which we could not verify. On the vendor side, UC Today reported on May 13, 2026 that UKG launched an AI payroll product that flags errors while payroll professionals keep approval control. A 2019 Censuswide survey commissioned by payroll software vendor MHR, of 251 HR and payroll managers at UK private employers with 1,000 or more staff, found 76% admitted paying employees incorrectly or late at least once in the past year, and 52% still used spreadsheets in payroll. It is a vendor-commissioned survey, but it shows the baseline is not perfect even without AI. So the advice below rests on how payroll works and on the AI cases that exist (MyCity, Air Canada), not on a documented AI payroll failure.
Keep two jobs separate
- Calculating pay needs fixed rules, the same result for the same inputs, and a record of how the number was reached. Use payroll software or a payroll provider.
- Explaining, checking and communicating can use AI, as long as a person reviews the output.
Where AI can help
| Use | How to keep it safe |
|---|---|
| Explain a pay stub line in plain language | Use a made-up or redacted example, then check the explanation against your payroll system's documentation |
| Draft the message about a payday change | Read it, fix the facts, then send it yourself |
| Spot odd entries in an export (a rate that jumped, hours that look doubled) | Treat each flag as a question to check, not a verdict |
| Turn the payroll calendar into a checklist | Compare against the calendar your provider gives you |
| Summarize a policy change for managers | Confirm against the policy text |
Where it cannot be trusted by itself
- Calculating wages or taxes. The federal overtime rule alone has details: for covered employees, hours over 40 in a workweek are paid at not less than one and one-half times the regular rate, and what counts in the regular rate is its own question. See the DOL overtime fact sheet. State rules add more.
- Deciding whether someone is exempt or an employee. That is a legal classification. See W-2 vs 1099.
- Filing or paying anything without a person approving it.
- Keeping the required records. The Department of Labor lists the information employers must keep: hours worked each day and week, regular hourly rate, straight-time and overtime earnings, deductions, total wages per pay period and the date of payment. Payroll records must be kept at least three years, and time cards and wage computation records two years.
A test you can run this week
- Take one past pay period where you know the right answers.
- Give the tool the same inputs you would use in real life, with names removed.
- Compare every number with your payroll system. Write down each miss.
- Decide the allowed use. If it misses anything in a calculation task, keep it out of calculations. If it explains well, keep it for explaining.
- Repeat after any tool update, and sample outputs regularly.
Plan for the day payroll breaks
The Kronos and Phoenix cases both ended in employers improvising. Write a one-page plan now: who can approve an off-cycle payment, how you would pay from the last good payroll, how you would tell employees, and where the last export is stored. Test it once a year.
Keep the data safe
Payroll data is among the most sensitive a company holds: names, Social Security numbers and bank details. IBM's 2025 report put the average breach cost at $4.44 million globally and $10.22 million in the U.S. The FTC's business guide advises knowing what personal information you keep, keeping only what you need, protecting it, disposing of what you no longer need and planning for incidents. Read AI Tools and Employee Data before any pay data goes into an AI tool.
General information, not legal or tax advice. Confirm current requirements with the official sources below and your payroll provider.
Sources
- U.S. Department of Labor: fiscal year 2025 back wages
- U.S. Department of Labor: Wage and Hour Division data
- U.S. Department of Labor: Fact Sheet #21, FLSA recordkeeping
- U.S. Department of Labor: Fact Sheet #23, overtime pay
- Wikipedia: Phoenix pay system
- Baker Botts: Kronos agrees to a $6 million settlement
- Legal Dive: UKG to settle class action over the Kronos outage
- Cybersecurity Dive: Cargill's $2.4M Kronos settlement
- HR Dive: UMass Memorial's $1.2M Kronos settlement
- The Markup: NYC's AI chatbot tells businesses to break the law
- Civil Resolution Tribunal of British Columbia: Moffatt v. Air Canada, 2024 BCCRT 149
- UC Today: UKG launches Pro Pay with Workforce AI
- MHR: UK's largest employers frequently pay their workforces incorrectly, 2019
- IBM: 2025 Cost of a Data Breach Report
- FTC: Protecting Personal Information, A Guide for Business