Running Third-Party Payroll Imports in QuickBooks Desktop After Subscription Cutoff
After Intuit ends Desktop payroll service, wage, tax, and job costing entries can still land in the right accounts; our engineers show how.
When Intuit ends payroll service for a Desktop installation, the company file keeps working but the payroll engine inside it goes quiet: no tax tables, no direct deposit, no forms. Moving the processing to a third-party payroll service and importing the results back into QuickBooks Desktop keeps every wage, tax, and job cost entry in the same file it has always lived in.
What stops and what survives
The subscription covers the calculation and filing machinery, not your data. Paychecks already recorded stay in the file, and the general ledger keeps functioning. What you lose is the ability to create new paychecks with computed withholding, updated tax tables, and the liability and forms workflow tied to them. Desktop also retains a manual payroll preference, useful for the occasional off-cycle correction with hand-computed figures. The replacement routine has one goal: get the numbers the payroll service computes into the same accounts, with the same job and class detail, using tools Desktop never takes away, namely journal entries and IIF imports.
Build the account structure first
Before the first import, mirror the payroll service's ledger in your chart of accounts: an expense account per wage type (salary, hourly, overtime, bonus, commission), expense accounts for employer taxes (the employer share of social insurance taxes, federal and state unemployment), and liability accounts for everything withheld or accrued but not yet paid, such as employee tax withholding, garnishments, and retirement plan deductions. If the service debits net pay from the bank on check day, no clearing account is needed; if timing differs, add a payroll clearing account to absorb the gap.
The journal entry routine
Most payroll services publish a journal report or GL export each pay cycle. Record it in Desktop under Company, Make Journal Entry, dated the check date. Debit each wage expense account for gross pay, debit the employer tax expense accounts, credit the liability accounts for withheld and accrued taxes, and credit the bank account (or clearing account) for net pay. Memorize the entry with Ctrl+M so the recurring structure returns each cycle; only the amounts change. When the service debits the bank for a tax remittance, record that payment against the matching liability account so balances clear to zero, and book the service's own fee invoice to a payroll bank charges expense account.
Job costing and class tracking
Journal entry lines accept a Customer:Job assignment and a Class, so wage lines can still carry job costing. Put each job's wages on its own line, assign the job, and use classes for departments or divisions. Two limits matter: reports that filter specifically to payroll transaction types will not see journal entries, and anything driven by payroll items, such as workers compensation tracking by item, stops at the cutover. Job cost reports set to include all transaction types will pick the entries up. If item-level costing is essential, the IIF route can import transactions that carry items.
Importing IIF files safely
Many services export an IIF file directly; if yours exports only CSV, the columns can be mapped into an IIF, and where that mapping is more maintenance than you want, custom QuickBooks programming can build the bridge. Before any import, back up the company file and test on the backup copy. IIF import (File, Utilities, Import, IIF Files) bypasses several of Desktop's validation rules, and the failures our engineers see most often trace to a single cause: an account name that does not match exactly, which silently creates a new account and splits payroll across two ledgers. After importing, run a custom transaction detail report for the pay date and tie the totals to the service's payroll register before trusting them.
Before the cutover
Export the payroll summary, wage, and tax reports for every period the subscription covered while you still can, and store them with the file's backups. Historical paychecks remain in the file, but once new payroll arrives as journal entries, full-year reporting comes from combining the service's reports with Desktop's. Run one parallel cycle if possible: have the service process a pay period while the old subscription still functions, compare every account total line by line, then rely on the import alone.