Standalone Payroll Exports Blocked When QuickBooks Online Already Runs Payroll

Standalone Workforce Payroll customers are hitting a hard wall at export time. QuickBooks will not move pay data from a standalone subscription into a QuickBooks Online company that already runs payroll. Two restrictions sit behind the trouble, and the accepted fix addresses both.

Who runs into this

The affected setup is specific. A business pays its people through QuickBooks Workforce Payroll, at the Core, Premium, or Elite level, with no accounting attached. The books live in a separate QuickBooks company file, with payroll switched off there. Paychecks cross the gap through an export: a direct sync into QuickBooks Online, or an IIF file imported into QuickBooks Desktop. Quicken users can ride the same export, since the setup lists Quicken for Windows and Mac as a destination.

Why does the export fail?

Two rules do the damage. First, standalone payroll cannot export transactions into a QuickBooks Online account that has payroll attached. Second, attaching payroll to that account ends the export connection on the standalone side, and the link expires rather than failing loudly. Users who add payroll to their books subscription often discover the break only when paychecks stop arriving in the company file.

Once payroll is attached in QuickBooks Online, the standalone export cannot be revived; the two cannot both feed the same company.

A second blocker involves permissions. Export setup must be completed by the Primary Admin of the payroll account. If that admin also holds a Firm user role, the setup will not go through. The accepted guidance is blunt: transfer the Primary Admin role to a non-Firm user before configuring the export. Accounting firms run into this rule, because the person holding admin rights is often part of the firm.

The accepted fix, step by step

We traced the working sequence through the accepted answer; it runs in two parts. Configure the export once, then push the paychecks across. Configuration happens inside the Core, Premium, or Elite payroll account.

1. Open Settings, then Payroll settings, in the payroll account.
2. In the Export section, select Edit and choose a destination: QuickBooks Desktop for Windows, QuickBooks Desktop for Mac, QuickBooks Online, or Quicken.
3. For QuickBooks Online, sign in and select the company that should receive the transactions, so the two accounts sync.
4. Select Continue. QuickBooks then creates default accounts for wages, expenses, and liabilities. Edit any of them so they match the chart of accounts in the receiving company.
5. Select Done twice to finish.

With the connection configured, the export itself is quick.

1. Go to Payroll, then Employees, and open the paycheck list. The View paychecks option and the Paycheck list under All apps both work.
2. Select the paychecks to export, using the filters to narrow the range.
3. Choose the option to export the selected paychecks.

The accountant route and the batch limit

Accountants working inside a client’s payroll follow a parallel path. From the client account’s Settings and Payroll settings, the Export area offers an option to export transactions. Filters narrow the list, and selections are capped at 20 transactions at a time per category. Twenty is the ceiling, applied per category rather than per batch. Larger runs take several passes, which surprises users expecting one bulk push.

The IIF import on the desktop side

Exports aimed at QuickBooks Desktop arrive as an .IIF file. The initials stand for Intuit Interchange Format. The file lands in the computer’s downloads folder. Inside QuickBooks Desktop, open File, then Utilities, then Import, and choose Import IIF. Select the downloaded file, confirm, and the payroll data posts into the company file.

What should you check before assuming a bug?

Most failed exports trace back to the same three checks. The destination QuickBooks Online account must not have payroll attached, and turning payroll on there later kills the existing connection. The person configuring the export must be the Primary Admin, without a Firm user role attached. On the desktop side, the import file is the .IIF download from the payroll account.

The payroll side keeps running while the bridge is down. What breaks is the movement of data between payroll and the books. The bridge has rules about who may build it and where it may land. Clear those two rules first, then rerun the export.