QuickBooks Online invoice CSV import: required columns, line items, and common gotchas

What QuickBooks Online expects when importing invoices

QuickBooks Online (QBO) supports importing multiple invoices from a CSV file, but it is strict about how rows are structured.

At a minimum, QBO’s invoice import documentation commonly references fields like:

• invoice number
• customer
• invoice date
• due date
• item amount

(Exact column names can vary depending on the import flow and region, so always confirm by downloading QBO’s sample file for your account.)

If your goal is to go from scanned invoices → QuickBooks-ready CSV, start here: QuickBooks integration.

How to represent multiple line items in a CSV

A common gotcha: an invoice with multiple line items is usually represented as multiple rows, repeating invoice-level fields.

Example approach:

• Row 1: invoice header fields + line item #1 fields
• Row 2: same invoice number/customer/dates + line item #2 fields
• Row N: …

This also helps if you have long item descriptions: instead of embedding multi-line text inside a CSV cell (often flattened to spaces), keep each line item on its own row.

Practical export strategy for invoice OCR tools

If you’re exporting from OCR, treat invoice data as two layers:

1) Header fields (repeat per row)

• invoice number
• vendor/customer mapping
• invoice date
• due date
• currency (if supported)

2) Line item fields (unique per row)

• item/service name (or a placeholder)
• description
• quantity
• unit price
• line total

Not every QBO import flow accepts every field. When in doubt, export a “minimal” CSV that QBO imports reliably, then enrich inside QuickBooks.

Common QuickBooks CSV import issues (and how to avoid them)

1) Items must match Products/Services

Many QBO imports require the item/product/service to match an existing entry in your QuickBooks Products & Services list.

If you don’t have a mapping yet:

• start with a default “Invoice item”
• later map vendors to standard items

2) Dates must be in a supported format

Stick to ISO-like formats where possible (YYYY-MM-DD) or exactly match the sample CSV QBO provides.

3) Decimal separators and currency

If your locale uses commas for decimals, make sure the import flow expects that. Otherwise, normalize to ..

4) Negative lines (discounts/credits)

Some invoice import flows reject negative amounts. If your invoices include discounts, consider:

• moving discounts into a summary field
• or representing them in a way QBO accepts

5) Duplicate invoice numbers

If you import an invoice number that already exists for the same customer, QBO may reject it or create conflicts.

This is also a valuable validation check upstream in OCR export.

Recommended workflow: OCR → review → QuickBooks CSV

1. Extract invoice header + line items
2. Run validation (totals reconciliation, required fields)
3. Review exceptions
4. Export QuickBooks-ready CSV

For a practical view of line item quality, read: Invoice OCR line item extraction: what to look for.

If you want to try the workflow, start here: Sign in.

FAQ

Can I import a multi-line description inside one CSV cell?

Often it gets flattened during import. It’s usually more reliable to keep one line item per row.

What’s the minimum viable QuickBooks CSV?

One that imports consistently: invoice number + customer + invoice date + due date + amount. Add more columns only after the basic import is stable.