Common QuickBooks import errors — and how to fix each one

A rejected QuickBooks import is frustrating, but the messages are predictable. Almost every failure comes down to a handful of causes, and each has a clear fix. Here are the ones you’ll meet most often and how to clear them.

Required field is missing

QuickBooks requires certain fields for each record type — a customer needs a name, a transaction needs a date and an account, and so on. If a required field is blank, that row is rejected. Fix: identify the required fields for the record type and fill every one before importing.

Account (or name) not found

A transaction points at an account, customer or item that doesn’t exist yet in QuickBooks. Fix: import lists in the right order — chart of accounts, then names and items, then transactions — so every reference already exists when the transaction lands.

Name too long or contains invalid characters

QuickBooks limits field lengths and disallows certain characters in names. Fix: trim over-long names and strip invalid characters before import; standardising names also prevents duplicates.

Duplicate document or transaction number

Two transactions share the same reference number, or a row is duplicated in the source. Fix: de-duplicate the source and make sure document numbers are unique.

Date out of range or wrong format

Dates outside an open period, or in a format QuickBooks doesn’t expect, get rejected. Fix: normalise every date to a single valid format and keep them within the period you’re importing into.

Item type or account type mismatch

An item or account mapped to the wrong type causes either a rejection or a silently wrong result. Fix: confirm every account and item type maps correctly before import — this one often passes the import but breaks your reports.