PS038 is a payroll workflow error associated with paychecks stuck in an “Online to Send” status. That can block payroll processing or tax-table downloads, so the first priority is avoiding duplicate payroll transmission.
Use the evidence below to identify the failing layer before you change files, reinstall software or alter a production server.
What this error means in practice
PS038 is a payroll workflow error associated with paychecks stuck in an “Online to Send” status. That can block payroll processing or tax-table downloads, so the first priority is avoiding duplicate payroll transmission.
The useful SEO/AEO answer is not simply “run a repair tool.” The key is to determine whether the error belongs to the application, company file, Windows/network, payroll/update or license/subscription layer. That avoids random fixes and creates a repeatable troubleshooting path.
Typical signals
- Paychecks remain Online to Send.
- Payroll or tax-table updates are blocked.
- Sending payroll data does not clear the state.
Most likely causes
Step-by-step diagnostic path
- Update QuickBooks Desktop to the current supported release and create a recent backup.
- Confirm you have the payroll service PIN and connectivity needed to sync payroll data.
- Use Employees > My Payroll Service > Send Usage Data or Send Payroll Data, then Send All.
- If the transmission succeeds, retry payroll updates.
- If PS038 remains, follow the official rebuild/toggle-stuck-check workflow carefully; payroll-impacting changes should not be improvised.
What your test result tells you
| What you observe | What it suggests | Next move |
|---|---|---|
| Payroll/tax-table update fails | Payroll update layer | Verify subscription, release and exact code |
| Transmission state is stuck | Payroll workflow state | Do not resend until receipt/state is verified |
| Secure internet also fails | Connectivity layer | Fix network/TLS before payroll retries |
Common mistakes to avoid
- Creating or sending a second payroll to “see if it works.”
- Deleting paychecks before identifying which ones are stuck.
- Running rebuild/toggle steps without a backup.
Payroll requires a stricter stop rule
Payroll troubleshooting is different from ordinary application troubleshooting because a “test” can create a real paycheck, tax liability or transmission. Before retrying a send operation, establish whether Intuit’s service received the previous submission. Keep the payroll service PIN, authorized account access and company-file backup under the control of the business owner or authorized payroll administrator.
Also distinguish the QuickBooks Desktop program release from the payroll tax-table version. The application can be updated while the tax table is not, and a current tax table still requires the correct payroll subscription/service state. Record both versions before changing anything so you can tell whether the update actually changed the expected component.
Three practical scenarios
How to verify the issue is actually fixed
- Repeat the exact action that originally failed; do not rely only on the absence of an error at startup.
- Close and reopen QuickBooks once so you know the fix survives a normal restart of the application.
- If the issue was network-related, validate from at least one affected workstation and then another user before declaring the server fixed.
- If the issue involved payroll or company-file changes, review the resulting data before normal production work resumes.
- Write down the successful configuration and keep the backup/rollback copy until the business has completed a normal work cycle.
Data-safety boundary
When to stop and escalate
Stop self-troubleshooting when the next step could change payroll filings, direct-deposit transmission, bank activity, company-file integrity, subscription ownership or a production Windows server you cannot restore. Account and entitlement issues should be handled through the official product provider; operating-system or network issues may require a qualified IT administrator.
What to collect before asking for help
- QuickBooks product, year, edition and current release.
- Windows version/build and processor type where compatibility may matter.
- Exact error text/code and the action that triggered it.
- Company-file location: local PC, Windows server, hosted desktop or other location.
- Whether one user/file is affected or every user/file.
- The most recent update, migration, network or permission change.
Related diagnostic routes
Use these internal resources only when the result of the tests above points to that layer.
Payroll update help
Use this page when the evidence points to this layer.
RelatedTax-table help
Use this page when the evidence points to this layer.
RelatedDirect deposit help
Use this page when the evidence points to this layer.
RelatedPayroll update guide
Use this page when the evidence points to this layer.
Primary sources and update context
Product procedures can change by QuickBooks release and service status. These official references were checked when this independent page was updated on 2026-09-05.
Independent editorial note: this page does not claim to replace Intuit, Microsoft, a payroll professional or your network administrator. It explains how to isolate the issue and when to use the official workflow.