QuickBooks Online Imports: Order, Formats, and the Missing First Row

QuickBooks Online users who move books in from spreadsheets keep hitting the same walls. Imports fail on file type, lists land in the wrong order, and one row of data always seems to vanish. The accepted answer on this topic, recently updated by Intuit, works through the questions that recur most. Here is the substance, with the regional caveats spelled out.

The data types QuickBooks Online accepts

Ten kinds of records can come in through the import tools. Bank and credit card data heads the list, alongside customers, vendors, and the chart of accounts. Products and services, invoices, credit memos, and sales receipts follow. Journal entries and bills round out the set. Each type runs through its own import screen, so a full migration means several passes rather than one.

Does import order really matter?

Yes, and the answer is explicit about it. Lists go first, in a fixed sequence: chart of accounts, then customers, then vendors, then products and services. Transactions come after the lists, with invoices ahead of bills and journal entries last. The reasoning is mechanical. An invoice import needs its customer to exist; a bill needs its vendor; a journal entry needs every account on its lines. Import transactions before the lists they reference and the file either fails or lands unlinked.

Accepted file formats and split sources

Three formats clear the gate: CSV, Google Sheets, and XLS or XLSX. CSV files hold table data as plain text, with fields split by a comma, a semicolon, or another delimiter. Google Sheets are online spreadsheets that live in Google Drive. XLS is the Excel format from 1997 through 2003; XLSX has been the Excel standard since 2007.

Split data gets no shortcut. If your contacts sit partly in Excel, partly in Google Sheets, and partly in a CSV export from another program, you run the import once per source. The tools do not merge files for you.

Journal entry imports and the regional journal code

Journal entries can now be imported from an Excel or CSV file. The route starts at the plus button, labeled New on some plans and Create on others, then runs through Journal Entry to an import option. The file needs particular columns: a journal number, a journal date, an account name, the memo line, debit amounts, credit amounts, and a date format selection.

The journal code column carries one caveat. Intuit’s list includes it, but the column is tied to regional editions; QuickBooks France is the edition that actually requires it. Users on other regional versions generally do not need it. One further rule prevents a failed run: if the entries reference accounts that do not exist yet, add them to the chart of accounts before importing the journal file.

Why does the first row of your spreadsheet disappear?

Because QuickBooks Online spends it on mapping. The tool reads row one as column headers, matches each header to a field in its records, and imports only what sits below. Content placed in the first row never arrives as data. Users who start their entries on row one lose exactly one line, and it reads like a bug the first time. It is simply how the mapping step works. Put headers in row one, start the data in row two, and nothing goes missing.

Before you start the import

• Import lists in sequence: chart of accounts, customers, vendors, products and services, then transactions.
• Save the file as CSV, Google Sheets, XLS, or XLSX.
• Import each source file separately rather than merging them first.
• Add any new accounts to the chart of accounts before importing journal entries.
• Keep the journal code column only if your regional edition requires it.
• Reserve the first row for headers and start your data on row two.

The recurring import complaints trace back to a handful of causes, and the accepted answer names most of them. Order, format, and the mapping row account for the bulk of what breaks. Get those three right and a migration usually runs quietly.