"Payroll not working" isn't one problem — it's a category of several distinct ones that happen to feel the same when you're staring at a blocked pay run. The paychecks might calculate wrong. Run Payroll might not open at all. QuickBooks might refuse to send data to Intuit's servers. Or the payroll subscription, tax table, direct deposit, bank connection, or employee records behind the scenes might be the actual point of failure, even though the symptom shows up as "payroll is broken."
That distinction matters because the fix is different for each cause. Run the connection-error sequence on what's actually a data-corruption problem, or wait on a subscription reactivation when your real issue is a stuck tax table, and you can lose an hour or more before a pay date without moving any closer to a working payroll. This page starts by helping you identify which specific failure you're looking at — including pointing you to a different, more detailed page when your issue turns out to be narrower than a general payroll fault — then walks through the official fix for the general causes that belong here: outdated software, paycheck calculation errors, payroll connection and server errors, data damage, and the distinct Payroll Setup error 00000-XXXXX.
Most payroll failures trace to one of four places: your subscription or account standing with Intuit, the data inside your company file, your connection to Intuit's payroll servers, or your payroll setup and calculation configuration. Once you know which of those four a symptom belongs to, even one this page doesn't list by name, you know roughly where to look.
Before troubleshooting anything, match your symptom to the right page. This site covers several payroll failure modes separately, in more depth than a single general page could manage — sending you to the wrong one wastes time you don't have.
Your symptomWhere to goPayroll subscription shows inactive, expired, or won't verifyOur Payroll Subscription Issues pageTax table won't download or updateOur Payroll Tax Table Update Problems pagePayroll updates in general won't installOur Payroll Update Not Working pageDirect deposit didn't go through, or shows the wrong statusOur Payroll Direct Deposit Not Working pageBank account won't connect for payroll fundingOur Payroll Bank Account Connection Problems pageAn employee is missing, or their info isn't showing correctlyOur Payroll Not Showing Employee Information pagePaychecks calculate the wrong amountsStay here — covered belowRun Payroll won't open, freezes, or won't respondStay here — covered below"Payroll Service Server Error" or "Payroll Connection Error" appearsStay here — covered belowPayroll Setup Wizard throws error 00000-XXXXXStay here — covered below
If your symptom isn't on that list, or you're not sure which bucket it falls into, keep reading — the general causes below account for most of what's left.
Two checks resolve a meaningful share of "payroll isn't working" cases before any deeper diagnosis is needed, and both take a few minutes.
1. Update QuickBooks Desktop to the latest release. Go to Help > Update QuickBooks Desktop, open the Options tab, and either turn on automatic updates or select Update Now, then Get Updates. When it finishes, restart QuickBooks and select Install Now if prompted. An outdated release is a documented contributing factor behind several payroll symptoms, including calculation and connection errors, which is why it's the first thing worth ruling out rather than the last.
2. Confirm your payroll subscription is actually active. Go to Employees > My Payroll Service > Account/Billing Info and check the status. If it shows anything other than active, that's your real problem, and it isn't a general payroll fault — it needs its own fix path. Reactivating a lapsed payroll subscription is a different task than repairing a calculation or connection error, and Intuit's own documentation notes it can take up to 24 hours to fully process, so it's worth ruling out before troubleshooting anything else on this page.
If both check out, move on to whichever section below matches your actual symptom.
Here, the pay run completes — it's the numbers on it that are wrong, which puts this failure in a different bucket than payroll refusing to run at all. Intuit's own documentation names four contributing causes:
Which fix applies depends on scope — whether it's hitting every employee or just one — and which tax is involved.
Federal or income tax wrong for every employee. Install the latest QuickBooks and payroll updates first, since a stale payroll tax table is a common trigger. Then revert the affected paychecks and recreate them so they recalculate against the current tables.
Federal or income tax wrong for one employee. Go to Employees > Employee Center, select the employee, then Payroll Info > Taxes. On the Federal tab, confirm the correct W-4 form is selected and that the employee's W-4 information is entered accurately. If the employee genuinely claims exempt status, that has to be set explicitly in the Filing Status dropdown — a paycheck calculates federal withholding as if it isn't exempt until that field is set correctly.
SUI wrong for every employee. Verify the SUI rate on file is correct — states update these periodically, and QuickBooks doesn't know a rate changed until you update it — then recreate the affected paychecks once it's fixed.
SUI wrong for one employee. Check the year-to-date SUI amount on that employee's paycheck detail against the state's wage base limit. Once an employee's YTD wages cross that limit, SUI correctly stops calculating for the rest of the year — what looks like a bug is often the wage base doing exactly what it's supposed to.
Deductions or contributions look wrong. Run a payroll tax and wage summary report and check whether the deduction or contribution has hit a limit set on the payroll item itself. If the amount is off in a way a limit doesn't explain, confirm the payroll item's tax tracking type is configured correctly — an incorrectly set tax tracking type changes how an amount calculates and whether it's taxed, independent of any limit.
Unlike a calculation error, this symptom usually isn't tied to one confirmed root cause — so instead of a single fix, work through these in order and let each step rule something out.
1. Confirm payroll is actually enabled and set up. It sounds basic, but a payroll feature that was disabled in preferences, or a setup that didn't fully complete, produces exactly this symptom — Run Payroll appears to not open because the feature underneath it isn't fully switched on. This takes under a minute to check and costs nothing to rule out first.
2. Run Verify Data, then Rebuild Data if it finds a problem. Close all windows, go to File > Utilities > Verify Data. If it comes back clean, data damage isn't the cause. If it flags an integrity problem, go to File > Utilities > Rebuild Data — QuickBooks will prompt you to save a backup first; accept that prompt, choose a save location, and let the rebuild finish. Verify typically finishes in a couple of minutes; Rebuild can take longer on a large company file, so budget more time for it than for the connection-error steps below. If you're on Assisted Payroll, Intuit's own guidance is to contact them before rebuilding rather than doing it unassisted, since Assisted Payroll data ties directly into Intuit's processing on their end. After a rebuild, run Verify Data again to confirm the repair actually held.
3. Restart and retry. After an update, a rebuild, or a preferences change, fully close QuickBooks, restart the computer, and try Run Payroll again — a surprising number of "won't open" cases clear simply because a locked process or a partially applied update needed a clean restart to take effect.
Where this article has to be honest with you: Intuit's own support documentation and staff responses on this exact symptom don't point to one single, confirmed root cause the way they do for the calculation and connection errors above. If steps 1 through 3 don't resolve it, that's not a sign you missed a step — it's a sign this particular failure needs account-level troubleshooting from Intuit support, which can see diagnostic detail a standard user can't. If the freeze happens across QuickBooks generally, not just inside payroll, you may be looking at a broader QuickBooks Desktop crash pattern rather than a payroll-specific fault.
Unlike the errors above, this one is specific to QuickBooks Desktop Payroll's connection to Intuit's servers — Assisted, Basic, and Enhanced versions alike — and it's well documented. You'll typically see wording like "Payroll Service Server Error. Please try again later" or "Payroll Connection Error" when trying to send payroll or download an update.
Six causes are documented for this one:
The fix, in order:
Each of these four steps normally takes only a few minutes on its own. Test after each one rather than running all four blind — it tells you which one actually mattered, in case the same error shows up again later. If firewall or security software interference is the suspected cause and the steps above don't clear it, the exact firewall ports QuickBooks requires are covered in more depth on that dedicated topic, since it's a deeper subject than this page can address without duplicating that page's job.
One related error worth knowing by name: PS038, which appears when paychecks get stuck in "Online to Send" status and blocks payroll from running or tax tables from downloading. If that's your exact situation, the fix involves finding and clearing the stuck paycheck specifically — a distinct process covered on that dedicated page, since it shares more with that topic's stuck-update scenarios than with the general connection errors here.
Everything above assumes payroll was already running at some point. This error family blocks the Payroll Setup Wizard itself, before payroll ever runs — if you're mid-setup and hit a code formatted like 00000-99867, this is what's happening.
Find the specific cause first. Open the error message and select View Report, then double-click ReportHeader.xml. Press Ctrl+F and search for "Exception String 0" — the text that follows tells you which of the causes below actually applies, instead of guessing.
Once you know which cause you're dealing with, here's the fix for each:
Most general payroll faults clear with the steps above: an update, a subscription check, a targeted calculation fix, Verify/Rebuild Data, or the connection-error sequence. If you've worked through the section that matches your symptom and the same problem returns immediately, that's a sign to escalate rather than repeat the same fix.
It's also worth calling for help sooner, rather than continuing to troubleshoot alone, if your next pay date is inside 24 to 48 hours and payroll still isn't running — the cost of guessing wrong at that point is higher than the cost of a support call. Intuit's payroll support team can see account- and server-side diagnostic detail a standard user can't, and a QuickBooks ProAdvisor can help if the underlying issue turns out to be a setup or data problem specific to your company file.
Once payroll is working again, two quick habits reduce the odds of landing back on this page before your next pay run: confirm the subscription status and tax table are current a day or two before you process payroll, not the same day, and keep QuickBooks Desktop's automatic updates turned on so you're not troubleshooting an outdated release in addition to whatever triggered the original error.
Will fixing a payroll error affect paychecks I've already sent or printed? No. The fixes on this page — updating QuickBooks, correcting a calculation, resolving a connection error, or running Verify/Rebuild Data — address paychecks currently blocked or miscalculating. They don't retroactively change paychecks that already processed and sent successfully.
Do I need to redo my whole payroll setup if I hit error 00000-XXXXX? No. This error blocks the Setup Wizard until the specific triggering issue — a duplicate name, a blank field, missing state information — is corrected. Once that's fixed, the wizard proceeds from where it stopped rather than restarting from scratch.
Why does Payroll Service Server Error only happen sometimes, not every time I send payroll? Because several of its documented causes are intermittent by nature — a network timeout, a brief connectivity drop, or multi-user mode only being active on some send attempts. That inconsistency is itself a useful clue: an error that happens every single time points more toward a fixed cause like an incorrect system date, while one that comes and goes points more toward network conditions or user-mode timing.
Can I keep processing payroll manually while a connection error is unresolved? That depends on your payroll service level and what "manually" means for your situation. If the real complication is a stalled direct deposit transmission rather than the connection error itself, that's worth confirming and addressing separately — getting the timing wrong risks a payroll tax filing or payment issue that's harder to unwind than the original error.
Is Rebuild Data safe to run, or could it lose payroll data? Rebuild Data is Intuit's own official repair tool for this exact situation, and it requires you to save a backup before it proceeds — which is the safeguard against data loss, not a formality to skip past. If you're on Assisted Payroll, contact Intuit before rebuilding rather than running it unassisted, since that service ties your file to processing on Intuit's end in a way self-service rebuilding doesn't account for.
"Payroll not working" almost always turns out to be one of a handful of specific things: a lapsed subscription, a stuck tax table or update, a direct deposit or bank connection failure, employee records that aren't displaying correctly, a paycheck calculation issue, a connection error reaching Intuit's servers, data damage, or the distinct Setup Wizard error 00000-XXXXX. Start by matching your actual symptom to the right page using the triage table above, then update QuickBooks and confirm your subscription is active — those two steps alone clear a meaningful share of cases. For what's left, work through the section that matches your symptom in order, and if the same problem keeps returning with a pay date close, that's the moment to bring in Intuit support or a ProAdvisor rather than keep retrying alone.
