QuickBooks Payroll CSV Import: What Works by Product and How to Fix

Fast Fix (2 Minutes)

If your QuickBooks payroll import just failed:

1. Confirm your product first — The CSV/XLSX template import in this guide is for QBO Advanced Payroll in the AU and UK markets only. If you are on QBO Standard Payroll in the US, there is no native generic CSV employee import — see the product matrix below.
2. Required field errors — A field the template requires is blank or contains a value that does not exactly match a configured record in your payroll settings. The most common gaps: Pay Schedule, Primary Pay Category, Primary Location. These must match the exact names configured in Payroll Settings.
3. Location not found — Enable "automatically create missing locations" during the upload confirmation step, or correct location values in your file to match the configured location path exactly.
4. Encoding rejected at upload — Re-save the file as UTF-8 from Excel (Save As → CSV UTF-8) before re-uploading.

---

Quick Answer

QuickBooks payroll CSV import capability depends on which QuickBooks product and region you are using. QBO Advanced Payroll — available in AU and UK, powered by Employment Hero (formerly KeyPay) — has a genuine CSV and XLSX employee import via a downloadable template. QBO Standard payroll in the US has no native generic CSV import for employee data; Intuit's stated position is that employees must be added manually, with structured migration available only from ADP, Gusto, or Paychex. QuickBooks Desktop supports employee list import but not payroll transactions, and the IIF format historically used for payroll journal entries is deprecated for QBDT 2021 and later.

---

Note on error strings: QuickBooks import error messages vary by product version and tenant configuration. Error text in this guide is representative of community-reported patterns (May 2026) — exact wording you see may differ. Verify against Intuit Community documentation or your QuickBooks administrator.

---

Not legal or compliance advice. QuickBooks payroll configuration and import capabilities vary by region, product tier, and tenant version. Confirm import requirements with Intuit documentation or your QuickBooks administrator.

---

TL;DR: Running a CSV through "QuickBooks payroll import" produces three different outcomes depending on product and region. QBO Advanced Payroll in AU or UK accepts a template-formatted CSV and validates it row by row before creating records — this is the genuine CSV import surface and the anchor for the error-fix content below. QBO Standard US payroll does not accept CSV employee imports from arbitrary sources; structured migration exists only from ADP, Gusto, or Paychex. QB Desktop accepts employee list records but not payroll transactions. If you are looking for QuickBooks accounting or transaction CSV imports rather than employee data, see the disambiguation section below.

---

QuickBooks Payroll CSV Import: Product Support Matrix

Regional note: The template import described in detail below is for QBO Advanced Payroll in the AU and UK markets. The AU product is explicitly branded "QuickBooks' payroll powered by Employment Hero" (Intuit AU app store). The UK Advanced Payroll product uses the same template import architecture; current UK Intuit marketing pages do not carry the same explicit "powered by Employment Hero" branding, though the import flow and field structure are architecturally identical. This feature does not exist in US QBO Standard payroll products (Core, Premium, Elite).

---

QBO Advanced Payroll (AU/UK): Template Import

QBO Advanced Payroll provides bulk employee import via a downloadable CSV or XLSX template. The import validates every row against your payroll configuration — missing required fields, unrecognized location names, and format mismatches all produce per-row errors in the upload confirmation screen before any records are created.

Reality layer — what a failed template submission looks like:

A payroll coordinator prepares a 47-row employee file for QBO Advanced Payroll (UK) and submits it. The upload confirmation screen shows 39 successes and 8 failures. Six of the eight failures show the representative error 'Default Location Id' should not be empty — not because the Primary Location column is blank, but because the file contains "London" while the configured location name in Payroll Settings is "London Office." The remaining two failures show 'Default Pay Cycle Id' should not be empty because the Pay Schedule value "Weekly" in the file does not match the configured name "Weekly Payroll." All 8 failures are fixable by correcting the exact string values; the 39 successful rows were already committed and are unaffected.

Getting the template:

Navigate to Payroll Settings → Data Extracts (under Business Management) → Employee Data. From the Data Type dropdown, select "Empty Template," then choose CSV or XLSX format and download. Use this file as the source of truth for column names, required fields, and expected value formats — the template reflects your current payroll configuration.

Running the import:

1. From the Payroll homepage, click the dropdown arrow next to "Add Employee"
2. Select Import Employees
3. Select your completed template file
4. On the upload confirmation screen: if location values in your file do not yet exist in your payroll configuration, enable "automatically create missing locations" — this creates the location records during import rather than rejecting affected rows
5. Review the per-row success/error status and resolve all reported errors before confirming

Required fields (representative — field set varies by region and tenant version):

The template requires fields across four categories: employee identity (name, date of birth), address details (residential and postal), employment configuration (start date, employment type, pay schedule, primary pay category, primary location, pay rate, hours per week), and payment details (bank account details — BSB and account number for AU; sort code and account number for UK). AU-specific fields include TaxFileNumber and superannuation fund details. A blank in any required field causes that row to fail validation — the import does not skip or default blank required fields.

---

QBO Advanced Payroll: Error Cause/Fix Table

---

QBO Standard US Payroll: No Native CSV Import

For QBO payroll in the US — Core, Premium, or Elite — Intuit's stated position is that employee information cannot be imported from other applications; employees must be added manually in QBO. This is not a CSV format problem that reformatting will solve. The generic CSV import path for employee data does not exist in the standard US product.

The one structured import exception: If you are migrating from ADP, Gusto, or Paychex, Intuit provides a structured onboarding import for employees and year-to-date pay history. This is accessed at: Payroll Overview → Start Onboarding → "What did you use to run payroll?" → select your prior provider. This is a provider-specific migration tool, not a generic CSV upload mechanism.

Third-party tools: Third-party apps in the Intuit App Marketplace — such as SaaSAnt Transactions — can perform bulk employee imports into QBO from CSV. These are not native Intuit functionality and operate outside the scope of this guide.

---

QuickBooks Desktop: Employee List Import Only

QuickBooks Desktop supports importing the employee list — names, contact information, and basic profile data — from CSV through File > Utilities > Import. This creates employee records in the system but does not create payroll transaction history.

What cannot be imported: Payroll transactions — earnings, deductions, hours worked, and pay history — cannot be imported natively into QBDT. The IIF format historically used to bring payroll journal entries from external payroll systems into QBDT is deprecated for QuickBooks Desktop 2021 and later. For payroll data from an external system, Intuit's recommended workaround is a General Journal entry.

---

Accounting vs. Payroll Data Import

This guide covers employee and payroll data imports. If you are looking for help with QuickBooks bank transaction imports, GL entries, Chart of Accounts, or accounting CSV imports — rather than employee or payroll records — see QuickBooks CSV Import: Continue Button Grayed Out for transaction-level CSV errors, and QuickBooks CSV Import: Zeros Not Allowed Error Fix for data-value rejection errors in accounting imports.

---

Pre-Import Checklist for QBO Advanced Payroll

Run this before every template import submission:

• Template downloaded from Payroll Settings → Data Extracts → Employee Data → Empty Template (not an older cached version)
• All required fields populated in every row — no blanks in identity, employment configuration, or payment details columns
• Pay Schedule, Primary Pay Category, and Primary Location values match exactly the names configured in Payroll Settings (open in plain text editor to verify — not Excel)
• Date values are in the format the template expects — confirmed from the downloaded template documentation
• Bank account details populated and correctly formatted (BSB + account number for AU; sort code + account number for UK)
• File encoding is UTF-8 — re-save from Excel as CSV UTF-8; verify with SplitForge Format Checker before upload
• "Automatically create missing locations" decision made — enable if location records need to be created, or correct all location values to match existing configuration
• Test with a 3-5 row subset before submitting the full employee file

SplitForge Format Checker validates encoding, delimiter, and intra-file column count consistency in your browser — no file data transmitted. SplitForge Data Cleaner trims whitespace from name and bank fields, removes blank required-field rows, and deduplicates by employee ID — also browser-local.

---

Privacy Note: Preparing QBO Advanced Payroll Files Without Upload

QBO Advanced Payroll import files contain employee PII — full legal name, date of birth, residential and postal address, bank account details (BSB or sort code and account number), tax identification numbers, and employment terms including pay rate and pay schedule. Running these files through an online cleaning or format-checking tool transmits employee PII to a third-party server, creating a GDPR Article 28 processor relationship for the preparation step.

Format Checker and Data Cleaner run entirely in your browser — no file data is transmitted at any point during encoding detection, structural validation, or cleaning operations. Verify this with the browser DevTools Network tab: no POST requests appear during file loading or validation. For the full privacy analysis of what online tools do with payroll files, see Never Upload a Payroll CSV to an Online Tool. For the privacy-first processing framework, see Privacy-First Data Processing Guide. For the HR/payroll data handling framework, see HR & Payroll CSV Data Prep Guide.

---

FAQ

Additional Resources

Import behavior verified against Intuit UK/AU/US help documentation, May 2026.

• Import employees via Excel/CSV in QuickBooks Online Advanced Payroll — Intuit UK Help
• Import employee data into QuickBooks Online — Intuit AU Help
• Import and export employee data in QuickBooks Online (US) — Intuit US Help
• Import employees and pay history from ADP, Gusto, or Paychex — Intuit US Help
• RFC 4180: Common Format and MIME Type for CSV Files

---