Upload PDF bank statements to QuickBooks Online: what Intuit’s statement reader does and does not do

The short answer: can you upload PDF bank statements to QuickBooks Online?

Yes, in the US version. Go to All apps → Accounting → Bank transactions, open the Link account ▼ menu, choose Upload from file, and select the PDF or image. QuickBooks extracts the transactions, may pass the statement to Intuit’s reviewers if something needs a second look, then shows the statement and the extracted rows side by side so you can correct them and select Save. The transactions then wait on the Bank transactions page for that bank or credit card account, where you add or match them like any other upload.

Intuit described the feature on its Firm of the Future site in July 2025, as part of the new bank feed and Accounting Agent: users can upload a bank or credit card statement as a PDF, JPG or PNG, the agent extracts the transactions and presents them for confirmation “before they are added to the bank feed”, and statements its technology cannot read correctly go to human reviewers. The help page, updated in August 2026, adds HEIC images and the English-language rule.

What Intuit documents about the PDF statement upload

The useful way to read Intuit’s pages is to separate what they say from what they leave out. Both matter when you decide whether to rely on the feature for a client’s year of statements or just for last month.

How to upload a PDF bank statement in QuickBooks Online, step by step

Set up the account before you upload. If the bank or card account does not exist in the Chart of accounts yet, you can add it from the account dropdown during the upload, but it is better to create it first with the right account type and an opening balance dated the day before the first statement you plan to bring in.

1. 1Find the date of the oldest transaction already in that account in QuickBooks. Intuit asks that the statement start at least one day before it, so you are not filling a period QuickBooks already holds.
2. 2Go to All apps → Accounting → Bank transactions and select the account’s tile if one appears.
3. 3Open the Link account ▼ dropdown and select Upload from file. If the account has no bank connection, you may see “Or upload transactions manually” instead.
4. 4Drag in or select the PDF, or a JPG, PNG or HEIC photo of the statement.
5. 5Choose the QuickBooks account the statement belongs to and select Continue.
6. 6If QuickBooks says some items need review, wait. Intuit says it will tell you on the Bank transactions page when the statement is ready.
7. 7Check the side-by-side view of the statement and the extracted data. Correct any field that is wrong, then select Save.
8. 8Go to the account’s transactions on the Bank transactions page and categorize, match or add them.

Start from Bank transactions every time. QuickBooks Online has other places that accept files, such as receipt capture, and those treat a PDF as a document to attach rather than a statement to read.

Where the transactions land, and what that means

This is the most important difference between the native PDF upload and an app that “sends to QuickBooks”. Rows from a PDF upload arrive in the same review list as your bank feed, the For review tab of the Bank transactions page. Nothing is in your books yet. You still choose a category or match each row to an existing transaction, and your bank rules can help, because Intuit applies rules to transactions in For review.

• Good: nothing posts until you add it, so a misread row can be corrected or excluded before it touches a report.
• Good: QuickBooks suggests matches against invoices, bills and transactions already in the register, which catches some duplicates.
• Less good: a year of statements means a year of rows to review one screen at a time, after the side-by-side check you already did.
• Worth knowing: uploaded rows do not carry the bank’s transaction IDs. If a bank feed later downloads the same dates, QuickBooks has no ID to recognise them by, and you will see the activity twice unless you exclude one copy.

What the PDF upload does not do, or does not document

None of these are reasons to avoid the feature. They are the questions to answer before you rely on it for more than a few statements.

• No documented balance check. The side-by-side view puts the job of checking on you. Intuit’s page does not say that the extracted rows are tested against the statement’s opening balance, closing balance or printed totals.
• No documented limits for statements. Intuit gives no maximum file size, page count, number of months or number of statements per upload for PDFs. For a 40-page business statement or a three-month combined statement, you will only find out by trying.
• English statements only. A statement in Spanish or French, even from a US bank, is outside what the page supports.
• US help only. Canadian and UK users are told to convert PDFs, as of October 2026.
• A person may see the statement. When extraction needs review, Intuit says its global experts may review the statement. Some firms’ client agreements care about that; most individuals will not.
• One account per upload. You choose a single QuickBooks account. Intuit does not say what happens to a statement that prints checking and savings together.
• Not available in QuickBooks Desktop. Desktop still imports bank data as Web Connect (.qbo) files, or IIF.
• No file to keep. The upload produces transactions in QuickBooks, not a CSV or Excel file you can send to a client, a lender or another program.

PDF upload versus AI-powered reconciliation

Intuit has a second feature that also takes an uploaded statement, and the two are easy to confuse. AI-powered reconciliation lives under All apps → Accounting → Reconcile. You upload the statement (or use Statement Auto Import), QuickBooks fills in the ending balance and ending date, and its Insights tab compares the statement with what is already in QuickBooks: paired transactions, transactions still waiting in the bank feed, and extra transactions on the QuickBooks side.

Used together they make a sensible workflow on the plans that have both: bring missing months in with the statement upload, then reconcile each month against the same statement.

Check the upload against the statement before you add it

Since the side-by-side screen is the review step, use it with the statement’s own numbers rather than reading row by row. A statement prints everything you need to prove the extraction in under a minute: the beginning balance, the ending balance, and usually the total deposits and total withdrawals. Here is a made-up example that adds up.

1. 1Count the extracted rows. Fourteen deposits plus 52 withdrawals is 66 rows; if QuickBooks shows 65, one is missing, often a line at a page break.
2. 2Add the deposits and the withdrawals separately and compare them with the printed totals. A difference equal to one amount is a missing or doubled row.
3. 3Check that the beginning balance plus deposits minus withdrawals equals the ending balance: 6,412.90 + 9,875.00 − 8,960.35 = 7,327.55.
4. 4Check a few dates near the start of the month and the end of the year. Statements that print MM/DD without a year are where wrong years appear.
5. 5After adding the rows, reconcile the account to the ending balance and ending date. A Difference of $0.00 is the proof.

If a difference is exactly twice one transaction, that row came in with the wrong sign. On a credit card account, check the direction too: charges should reduce what you have and payments should increase it, seen from your side rather than the card issuer’s.

Avoiding duplicates when the account also has a bank feed

Most duplicate trouble with PDF uploads comes from two sources covering the same days. A bank feed downloads its own copy of each transaction, and Intuit’s connection page says feeds reach back anywhere from 90 days to 24 months depending on the bank. A PDF upload adds another copy, with no ID to match on.

• Decide where the feed starts. Use PDF uploads only for statements that end before that date.
• If you connect the feed after uploading history, Intuit recommends picking a start date immediately after the most recent transaction already in the account.
• Upload whole statements, end to end, oldest first. Statement periods meet exactly, so a gap or an overlap shows up straight away.
• If a duplicate is still in For review, exclude it rather than adding it. If both copies were added, delete one and reconcile again.

When QuickBooks’ own PDF upload is enough

For many readers, the honest answer is to try the native upload first. It is already part of QuickBooks Online, it keeps the statement inside QuickBooks, and the review list means nothing posts without you. It fits best when:

• You need a few months that the bank feed does not reach, for one or two accounts.
• The statements are in English and you are on the US version of QuickBooks Online.
• You are willing to check each statement against its printed totals yourself, as above.
• You do not need the data anywhere other than QuickBooks Online.

When converting the PDF first still helps

A converter earns its place when the volume, the checking or the destination goes beyond what Intuit documents. Converting does not change where the rows land if you upload the result: a .qbo or CSV goes through the same Upload from file screen and into For review.

Scanned and photographed statements are not on their own a reason to convert: Intuit accepts JPG, PNG and HEIC images. The reason to convert a scan is the same as for a digital PDF, wanting the result proven against the statement before it reaches your books.