Guides

How to import a PDF bank statement into QuickBooks Online

QuickBooks Online can't read a PDF bank statement. It imports transactions from files: a CSV in a specific layout, or a Web Connect file (.qbo, and in many cases OFX/QFX). If all you have is a PDF, you need to convert it first.

This guide covers both file routes, the formatting QuickBooks expects, and the checks worth doing before you import.

Before anything else: bank feeds and bank downloads

If the account can connect to QuickBooks through a bank feed, that's usually the best ongoing option. If your online banking offers a QuickBooks (.qbo) or CSV download for the dates you need, use that next. Both come from the bank's own data.

PDF conversion is for the gaps: periods before a feed was connected, closed accounts, client statements that only exist as PDFs, or banks that don't offer downloads.

Option A: import a CSV

QuickBooks Online accepts CSV files in one of two layouts.

3-column layout (single signed amount):

4-column layout (separate money in and out):

During import, QuickBooks asks you to map your columns and confirm the date format, so the exact header names matter less than the structure.

Formatting rules that prevent failed imports:

• One header row, then transactions only. Remove opening balance lines, subtotals and repeated page headers.
• One date format throughout. Choose it explicitly during import. A DD/MM statement mapped as MM/DD will either fail or silently swap day and month.
• No currency symbols or thousands separators in amount cells.
• Negatives as -86.40, not (86.40) or 86.40 DR.
• Descriptions on a single line. Multi-line descriptions from the PDF must be merged.

If you're building the CSV by hand from a PDF, the bank statement to CSV guide covers the cleanup steps.

Option B: import a QBO (Web Connect) file

A .qbo file is an OFX-based format that QuickBooks reads natively. It carries dates, amounts, payee text and a unique transaction ID for each entry, which helps QuickBooks avoid importing duplicates. There's no column mapping step.

You can't easily make a QBO file by hand; it needs a converter. If your bank offers one as a download, that's ideal. Otherwise a converter can produce one from a PDF.

Upload steps in QuickBooks Online

Intuit changes menu labels from time to time, so treat this as the general path and check Intuit's current help article if something doesn't match.

1. Go to Banking (or Transactions → Bank transactions, depending on your navigation).
2. Choose Upload transactions (sometimes shown as "Upload from file", often under a dropdown beside Link account).
3. Select your CSV or QBO file.
4. Choose which QuickBooks account the transactions belong to.
5. For a CSV, map the columns and confirm the date format.
6. Select the transactions to import and confirm.

The imported transactions appear in the For review list. Nothing is posted to your books until you categorise and accept each one, or set up rules to do it.

Limits to check: QuickBooks has restrictions on how far back and how many transactions you can import in a single file. They have changed over time, so check Intuit's current documentation before preparing a large historical import. Splitting by month is a safe default.

Check before you import

Undoing a bad import means excluding or deleting transactions one by one. A few minutes of checking first is cheaper.

1. Count the rows. Does the number of transactions match the statement?
2. Check the totals. Opening balance + money in − money out = closing balance on the statement.
3. Check signs. Payments out should be negative (3-column) or in the Debit column (4-column).
4. Check the date range. First and last dates should match the statement period.
5. Check for overlap. If a bank feed is already connected for part of that period, importing the same dates again will create duplicates for you to clear.

If the statement prints a running balance, recomputing it row by row will pinpoint any missing or wrong transaction. The reconciliation guide shows the formulas.

Where Rowsafe helps

Rowsafe converts text-based PDF statements into QuickBooks-ready files without uploading them anywhere.

• Local processing. The PDF is read in your browser. There's no server-side copy, and you can confirm in developer tools that the file isn't sent.
• Balance-checked output. Rowsafe recomputes the running balance for every row and flags any row that doesn't reconcile, before you export.
• QBO and CSV. Export a .qbo Web Connect file or a CSV, plus OFX for other accounting apps.
• Column fixes in the preview if a statement layout comes out wrong.

QBO, OFX and Excel exports are part of Pro ($12/month or $96/year), which also includes unlimited statements and batch conversion. The free plan gives you 3 statements a day with CSV export, which you can map into QuickBooks using the CSV route above. See pricing.

Limitations: text-based PDFs only; scanned statements aren't supported yet. Rowsafe doesn't connect to QuickBooks directly. You download the file and upload it yourself, which keeps your data on your device.

FAQ

Why does QuickBooks say my file can't be read? Usually a formatting issue: extra header rows, mixed date formats, currency symbols or text in amount cells. Open the CSV in a text editor to see what QuickBooks sees.

Will importing the same file twice create duplicates? QBO files carry transaction IDs that help QuickBooks detect repeats. CSVs don't, so be careful with overlapping dates.

Does this work for QuickBooks Desktop? QuickBooks Desktop also imports Web Connect (.qbo) files, through its own menus. The steps above are for QuickBooks Online; check Intuit's Desktop documentation for the current path.

Can I import a credit card statement the same way? Yes, into a credit card account rather than a bank account. Sign conventions differ for cards; see the credit card statement guide.