QuickBooks Online is at its best when transactions arrive through a bank feed. But plenty of bookkeeping work happens without one: a catch-up client who is a year behind, a closed account, a feed that was connected late, or a credit card the bank won't connect. In those cases all you have is the PDF statement, and QuickBooks needs the transactions in a file it can upload.
This guide shows the cleanest way to do it: convert the PDF into a .QBO file and upload that. It also covers the CSV route, and how to avoid the commonest problem, duplicate transactions.
The short version
- Convert the PDF statement into a .QBO (QuickBooks Web Connect) file.
- In QuickBooks Online, upload it to the right bank or credit card account.
- Review the transactions in the For review list, then add or match them.
Why .QBO instead of CSV?
QuickBooks Online accepts transaction uploads as CSV, QBO or QFX files (Intuit: manually upload transactions). CSV works, but it puts the work on you:
| CSV | .QBO | |
|---|---|---|
| Column mapping on upload | Yes. You match Date, Description and Amount, or Credit and Debit, by hand | No. The file says what each field is |
| Money in vs money out | Depends on your columns and the choices on the mapping screen. Easy to get backwards | Every transaction is explicitly marked |
| Date format | Has to match what you pick on the import screen | Fixed format, no ambiguity |
| Re-uploading the same unchanged file | Can create duplicates | Each transaction carries a unique ID; re-uploading the same file doesn't create duplicates |
For bookkeepers doing catch-up work across many statements, the last two rows are what matter. They're where reversed signs and doubled transactions come from.
Step 1: Convert the PDF statement to .QBO
There's no way to save a PDF as .QBO directly. The transactions have to be read out of the PDF first.
With PDFDrill:
- Upload the statements. A whole batch for one client is fine, digital or scanned. Bank and credit card statements can go in the same batch.
- PDFDrill extracts every transaction and checks each statement balances: opening balance plus transactions must equal the closing balance, to the cent. Credit card statements use the card's own rule, where purchases increase the amount owed and payments reduce it. It also checks that each month's closing balance matches the next month's opening balance.
- Review anything flagged. Overlapping transactions from statements that share a few days are marked as duplicates and left out of the export.
- Export "QuickBooks Web Connect (.QBO)". Choose one account for each export. Very large accounts are split into files of up to 1,000 transactions each, downloaded together in a ZIP. It's included on the Pro plan and above.
Scanned statements? See how to convert a scanned bank statement for getting a clean scan. The balance check is what catches misread digits.
Step 2: Upload the .QBO file to QuickBooks Online
- In QuickBooks Online, go to Transactions → Bank transactions. In some versions this is under Banking.
- Click the arrow next to Link account and choose Upload from file.
- Choose your .QBO file.
- Pick the QuickBooks account these transactions belong to: the right checking account, savings account or credit card. If it doesn't exist yet, add it here.
- Finish the upload.
Menu names change between QuickBooks versions. Intuit's own guide has the current steps: Manually upload transactions.
Credit cards: upload the card's file to the credit card account in QuickBooks, not to a bank account. That way purchases add to what's owed and payments reduce it.
Step 3: Review before anything reaches the books
Uploaded transactions go to the For review list. They don't go straight into the books. From there you can:
- Match a transaction to one that already exists (for example, an invoice payment you already recorded);
- Categorise it and add it;
- Exclude anything that shouldn't be in the books.
Bank rules you've already set up in QuickBooks apply here too, which speeds up categorising.
How to avoid duplicates
Duplicates are the commonest import problem. They happen when:
- the upload overlaps a period the bank feed already covers;
- two statements share a few days at the join, and both get uploaded;
- the same file is uploaded twice.
What helps:
- Check the account's date range first. Note the last transaction date already in QuickBooks and only import after it.
- Remove overlaps before exporting. PDFDrill marks transactions repeated across overlapping statements and leaves them out of the .QBO file.
- Use .QBO rather than CSV. PDFDrill keeps transaction IDs stable for unchanged account data. In the QuickBooks Online sandbox test, re-uploading the same file didn't create duplicates. This is not a guarantee against overlaps with bank feeds or differently edited files; check those separately.
The CSV route (if you need it)
If you'd rather use CSV, QuickBooks Online accepts two layouts (Intuit):
- 3 columns: Date, Description, Amount (for bank accounts, money in positive and money out negative). Card exports use the card-specific CSV signs; check Spent/Received on the upload preview.
- 4 columns: Date, Description, Credit, Debit. Confirm on the upload screen which column QuickBooks treats as money in.
Intuit's help says the file must be 350 KB or less; split larger files by date range. Use one date format throughout, and pick that format on the mapping screen. Our bank statement PDF to CSV guide covers making a clean CSV.
Common problems and fixes
| Problem | Likely cause | Fix |
|---|---|---|
| Every expense shows as income | CSV columns mapped the wrong way round | Use .QBO, or verify the signed amounts and mapping in the CSV upload preview |
| Card purchases reduce the balance | File uploaded to a bank account instead of the card account | Upload the card's file to the credit card account |
| Dates in the wrong month | CSV date format didn't match the setting on the import screen | Use .QBO, or choose the matching format when mapping |
| Same transactions twice | Upload overlaps the bank feed or another statement | Trim to dates after the last one in QuickBooks; remove statement overlaps |
| Upload rejected | CSV file too large or malformed | Split by date range; check one header row and one transaction per row |
FAQ
Can QuickBooks Online import a PDF bank statement directly? The transaction upload uses CSV, QBO or QFX files. Intuit's help page lists PDF and image files separately, as accepted for account statements. Check what your version of QuickBooks does with a PDF before relying on it to create transactions. To get the transactions in reliably, convert the PDF to .QBO or CSV first.
What is a .QBO file? It's the QuickBooks Web Connect format: the file banks offer as a "QuickBooks download". It contains each transaction's date, amount, direction, payee, memo and a unique ID, which is why it doesn't need column mapping. PDFDrill leaves payee blank when the extracted source has no explicit payee, and keeps the description in the memo.
Does this work for credit card statements? Yes. Convert the card statement, then upload it to the matching credit card account in QuickBooks. PDFDrill checks card statements with the card's own balance rule before exporting.
Will this work in QuickBooks Desktop? This guide covers QuickBooks Online. PDFDrill's QuickBooks Desktop compatibility has not been verified; no Desktop compatibility is claimed.
Is it safe to upload client statements? With PDFDrill, files are stored privately. Source PDFs are deleted 7 days after the batch is created and extracted data after 30 days, and you can delete a batch at any time. Details are on the security page.
Turn PDF statements into QuickBooks-ready .QBO files, balance-checked and with overlaps removed. Try PDFDrill: free for 10 pages a month. QuickBooks exports are on the Pro plan.