If you have ever tried to drag a PDF statement straight into QuickBooks, you already know how this ends: it does not work. QuickBooks cannot read a PDF. The data has to be in a format it understands first. This guide covers the two formats that work, and the exact import steps for QuickBooks Online and QuickBooks Desktop.
I work on statement conversion every day, so the order here is the one that causes the fewest surprises at import time.
Why QuickBooks will not read your PDF#
QuickBooks imports structured data: rows and columns with a clear date, description, and amount. A PDF has none of that structure saved inside it, it just looks like a table on screen. So the first job is always to turn the statement into something with real columns.
You have two good options:
- CSV, a plain spreadsheet of transactions. Works in QuickBooks Online and Desktop.
- QBO, QuickBooks' own bank-feed format. Works in QuickBooks Online, where it imports as a feed and offers to match transactions for you.
If you are not sure, use CSV. It is the most forgiving and it works everywhere.
Step one: convert the statement to CSV#
Before you touch QuickBooks, get a clean CSV out of the PDF.
- Upload your PDF statement to the converter.
- Check the parsed rows, paying attention to the dates and the amount column.
- Download the CSV.
If you want the full detail on this step, including scanned and password-protected statements, see the pillar guide on converting a PDF bank statement to Excel or CSV.
Convert your statement to CSV first
Turn the PDF into a clean CSV with a date, description, and amount column, ready for the QuickBooks import.
Import into QuickBooks Online#
- Sign in and go to Transactions, then Bank transactions.
- Choose the account, then select Upload from file (under the dropdown next to "Link account").
- Upload your CSV and click through to the mapping screen.
- Map the columns: tell QuickBooks which column is the date, which is the description, and which is the amount. If your file has separate money-in and money-out columns, choose the two-column option.
- Set the date format to match your file, for example dd/mm/yyyy, so the days and months do not get swapped.
- Review the preview, then import.
QuickBooks drops the rows into the For review tab. Nothing posts to your books until you accept each transaction, so you get a second chance to catch anything odd.
Using QBO instead of CSV
A QBO file imports as a bank feed, which is smoother if you reconcile through the feed every month. Convert to QBO when QuickBooks Online is your main workflow and you want it to suggest matches. The trade-off is that QBO is pickier, so if an import is rejected, fall back to CSV.
Import into QuickBooks Desktop#
QuickBooks Desktop does not take a plain CSV without help, so you import through the built-in tool.
- Go to File, then Utilities, then Import, then Web Connect Files for a QBO file. For CSV, use the Import Data option or a CSV import tool, depending on your edition.
- Select your converted file.
- Choose the bank account the transactions belong to.
- Review the list and confirm the import.
If your edition only accepts Web Connect files, convert the statement to QBO rather than CSV. The transactions then arrive the same way an online bank download would.
The two mistakes that cause most import problems#
After converting, two issues account for nearly every failed QuickBooks import.
Dates in the wrong order. A date like 03/04 is the 3rd of April in some countries and the 4th of March in others. QuickBooks reads it however its setting says, so a statement from the UK or India can land a month off. Always set the date format in the import dialog to match the file, and eyeball the first few rows.
Amount signs. Money out should be negative and money in positive, or split into two columns. If everything imports as a credit, your single amount column probably lost its minus signs, or the money-out column was mapped as money in. Fix the mapping and re-import.
Check before you accept
QuickBooks does not post imported rows until you approve them in the review tab. Use that step. It is far easier to fix a mapping and re-import than to unpick wrongly posted transactions later.
Where to go next#
That is the whole flow: convert the PDF to CSV or QBO, then import. The conversion is the part that goes wrong most often, so it is worth getting a clean file before you start. Begin with the PDF to CSV converter, and if you already have an OFX file from your bank, the OFX to QBO converter gets you a QuickBooks-ready file in one step.
If you also work in other tools, the same converted data drops into Tally or a Google Sheet just as easily.