To import PDF bank statements into QuickBooks Desktop, first convert each PDF into a QBO file, because Desktop cannot read the PDF itself. Then bring each QBO file in with File > Utilities > Import > Web Connect Files, accept the lines, and check that the register's ending balance matches the statement.
Can QuickBooks Desktop read a PDF bank statement?
No. QuickBooks Desktop does not open a PDF statement and pull transactions out of it. A PDF is laid out for printing, and Desktop's bank import expects structured data. You need a conversion step that turns the printed lines into a file Desktop understands.
That surprises people because a PDF statement looks like a list of transactions. It is not one to the software. The dates, the descriptions and the amounts are placed on the page for a human eye, and nothing in the PDF says which number is a deposit, which is a fee and which is the balance.
Why "open with" and "print to" do not help
Two shortcuts come up often, and neither works. Opening the PDF in Excel gives you text scattered across cells, with wrapped descriptions split over rows and page headers repeated every page. Printing the PDF to a file does not change what it contains. Both leave you with a cleanup job that is longer than the import.
The two things a conversion has to get right
A converter has to read each line correctly and then write it in the form Desktop wants. The reading has to get the date, the description and the amount of each line, with money out marked as money out. The writing has to produce a Web Connect (QBO) file with a bank identification and a unique ID for each line. The details of the reading are in converting a PDF to a QBO file. This post covers what happens once you have the file.
What if your bank can give you a QBO directly?
Then skip the PDF. Many banks let you download recent activity as a Web Connect file. The PDF route is for months the bank no longer offers as a download, or for banks that offer no QuickBooks file at all. Check the bank's download screen for a QuickBooks or Web Connect choice before you convert anything.
Why does Desktop need a QBO file rather than a CSV?
Desktop's bank import is built around Web Connect files. It expects the QBO layout, with a bank identification and a unique ID on each transaction. A CSV has neither, so Desktop has no place to take a CSV for bank lines. A CSV made from a PDF therefore needs another step before Desktop can use it.
You can still make a CSV from the PDF. It is a good way to check the numbers in a spreadsheet before you commit them. But to get the lines into the bank register with matching, the CSV must become a QBO file. If you want the other ways in, importing CSV bank transactions into QuickBooks Desktop compares the routes and explains what each one gives up.
The case for a journal entry, and why it is rarely right
Typing each statement into a journal entry avoids the file problem but skips the bank register, so reconciliation has nothing to tick off. Journal entry imports that bypass the bank register explains what is lost, and why journals are best kept for adjustments.
What SimpleBankConvert does here
SimpleBankConvert is being built for this gap: you upload a PDF statement and download a QBO file, with the dates made consistent and money out shown as a minus. Accounts are not open yet, so Get started takes your email for when they are.
Importing a year of PDF statements into Desktop month by month
When you have a backlog of PDFs, import them in date order, oldest first, one month at a time. After each month, compare the register's ending balance with the statement before moving on. A month that does not tie is far easier to fix when it is the only thing you have changed since the last good check.
Why oldest first
The balance on each statement depends on the one before it. If you import March before January, the register balance on March 31 will be wrong until January and February arrive, and you cannot use it to prove anything. Importing in order means the register balance at the end of each import is a number you can compare to the printed ending balance.
Set the starting point first
Before the first import, make sure the account has the right opening balance. This is the balance at the start of the first statement, entered once. If the opening balance is missing, every later check will be off by the same amount, and the offset can look like a missing transaction when it is not.
A monthly checklist for a 12-statement backlog
This checklist assumes twelve PDF statements, January through December of one year. The dates and amounts are examples.
- Back up the company file before the first import, and again every few months of work.
- Enter the opening balance for the account as of the first day of January, if it is not there already.
- Convert the January PDF to a QBO file. Open the file once outside QuickBooks if you can, to see that the first and last dates fall in January.
- Import the QBO file and link it to the right bank account.
- Review the lines in the Bank Feeds Center, accept the matches and add the rest.
- Open the register and read the ending balance on January 31. Compare it to the ending balance printed on the January statement.
- If the two match, write "January done" in your notes and move on. If not, fix January before February.
- Repeat from step 3 for February, and so on through December.
- When all twelve months are in, run a reconciliation for December and confirm it ends at zero difference.
An example of why step 7 matters: January's statement ends at 8,410.00, and your register reads 8,650.00. The difference is exactly 240.00, which points to a single debit that did not come in. Found in January, that is a one-line search. Found in December, after eleven more imports, the same 240.00 is mixed in with everything else.
Keep one note per month
Write down, for each month, the file name, the statement's ending balance and the register's ending balance. A plain list is enough. If a later import brings a duplicate, the note tells you which file to blame.
Desktop statement imports that land in the wrong account
If you link a statement file to the wrong QuickBooks account, every line from that file lands there, and you must undo the damage by hand. Desktop does not offer a button to move an import. The safest cure is prevention: read the account prompt each time and check the first lines after the import.
How to spot a wrong-account import
Three signs give it away. The register for the account you meant to use is missing the month. The register for the wrong account has lines it should not have, with dates in the statement period. And the wrong account's balance now looks odd, such as a savings account that suddenly has hundreds of payments. Check the register straight after the import, not at the end of the week.
How to fix it
The prompts in a Web Connect import are described step by step in linking the Web Connect file to a Desktop bank account. Once a file is in the wrong account, you have two choices:
- Restore the backup taken before the import. This is the cleanest way and the reason the checklist starts with a backup. You lose any work done since, so keep the gap short.
- Delete the imported transactions from the wrong account, then import the file again into the right one. This is only sensible when the file brought in a few lines, because each line has to be deleted by hand.
Intuit's guide to importing and exporting data in QuickBooks Desktop states that an import cannot be undone, which is why a restore is the practical fix.
Guard against it next time
Name your accounts so they cannot be confused. "Checking" and "Checking 2" invite mistakes. A name with the last four digits of the account number, such as "Business Checking (4417)", does not. When you convert a PDF, also label the QBO file with the account and month in its file name, so the file in front of you tells you where it belongs.
Matching the Desktop register to the PDF statement balance
A statement import is complete when the register's ending balance on the statement date equals the closing balance printed on the PDF. That one comparison tells you whether any line was missed, doubled or given the wrong sign. If the numbers match, the month is done.
How to run the comparison
Open the account register and look at the balance on the last day of the statement period, not the last day in the register, which may include later entries. Compare that figure to the closing balance on the PDF. Both should be the same to the cent.
What a difference tells you
The size of the gap points to the cause:
- A gap equal to one line's amount. A line is missing or doubled. Scan the statement for that amount.
- A gap equal to twice a line's amount. A deposit was brought in as a payment, or the other way round. The sign is wrong on one line.
- A gap equal to the opening balance. The starting balance was never entered.
- A gap that fits nothing. Two or more problems cancel in part. Compare the register to the statement line by line, page by page.
Gaps that equal twice a line's amount are the signature of a sign problem, and they matter most for credit card statements, where charges and payments run opposite to a bank account. The fix is in the conversion, not the register.
Do the proof at the end too
After the last month, run a bank reconciliation for the final statement. Reconciliation looks at cleared items and the ending balance together, so it catches a problem that a month-by-month check missed. If it ends at zero difference, the year is in.