QuickBooks Desktop will not import a PDF at all, and QuickBooks Online only takes one under 350 KB, in English, through an AI review step. Upload your PDF statement and BankXLSX writes a QBO Web Connect file with the account, dates, descriptions, and amounts already mapped, so the transactions drop straight into QuickBooks. Start free, no credit card.
Last updated July 2026
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
Upload the PDF bank statement to BankXLSX and download it as a QBO file. The converter reads every transaction and writes a QuickBooks Web Connect file with the bank account, dates, descriptions, and signed amounts already mapped, so QuickBooks recognizes it as a real bank feed. In QuickBooks Online, go to Banking, choose the account, and use Upload from file. In QuickBooks Desktop, use File then Utilities then Import then Web Connect Files. QuickBooks Desktop cannot read a PDF at all, and QuickBooks Online caps a PDF upload at 350 KB and routes it through AI extraction you have to review, which is why the QBO step exists.
QuickBooks Online will now attempt a PDF statement with AI extraction, but only under 350 KB, only in English, and only after a review step. Desktop refuses a PDF outright. Here is what stops most bookkeepers.
The bank feed import accepts QBO, QFX, OFX, and CSV only. Hand it a PDF and there is no upload option at all, so the statement you downloaded is unusable as is.
A CSV upload works but lands as raw rows you must map column by column every time, with no bank ID, so QuickBooks cannot auto-match it to the right account.
Direct Connect and the live feed only reach back a few months. Older statements, closed accounts, and pre-conversion history come as PDFs you have to import yourself.
Many community banks, credit unions, and business accounts never offered a QuickBooks feed, so a converted QBO file is the only way to get their transactions in.
Typing a few hundred lines into the register by hand burns an afternoon and invites transposed amounts that throw off the reconciliation.
A CSV with the wrong date format or debits as positives reconciles to the wrong balance, and QuickBooks gives no warning until the numbers do not match.
Upload the PDF and the converter reads the statement, then writes a valid QBO Web Connect file QuickBooks treats like a real bank download, with every transaction dated, described, and signed correctly.
You get an actual .qbo file with the OFX structure QuickBooks expects, not a CSV you have to remap, so the bank feed accepts it on the first try.
Bank name, account type, and a transaction ID are written into the file so QuickBooks recognizes the account and avoids importing the same line twice.
Every transaction gets the correct date and a signed amount, debits negative and credits positive, so the register reconciles to the statement balance.
Need Quicken or another finance app instead? The same upload exports QFX and OFX, so one statement covers QuickBooks Desktop, Online, and Quicken.
When you would rather map columns yourself or just review the data, download a clean CSV or XLSX of the same transactions from the same conversion.
256-bit encryption in transit, and you can delete your uploaded files whenever you want.
No software to install and no credit card to start.
Drag your PDF bank or credit card statement into the box above. Scanned and image-only statements work too.
Tip: Several months in one file is fine.
Once the transactions are read, pick QBO as the download format. QFX, OFX, CSV, and Excel are there too if you need them.
Tip: Pick QFX for Quicken instead.
In QuickBooks Online use Banking then Upload from file; in Desktop use File, Utilities, Import, Web Connect Files. Pick the account and review.
Tip: Match the account before you add.
A QBO file is the fast path into QuickBooks, so the people converting one are usually catching up the books, onboarding a client, or importing history the bank feed cannot reach.
Import a year of client statements into QuickBooks as QBO files instead of keying every transaction into the register by hand.
Bring in pre-conversion history and closed-account activity that the live bank feed will not pull during a cleanup engagement.
Get statements from a bank or credit union that never had a QuickBooks feed into the books without paying for bookkeeping help.
Load historical transactions when moving to QuickBooks or switching banks, so the opening period reconciles cleanly.
A QBO file, also called a Web Connect file, is the format QuickBooks uses to receive bank and credit card transactions. It is an OFX file under the hood, plain text that carries the account details and a list of transactions with dates, amounts, and descriptions. The reason it matters is that QuickBooks treats a QBO import exactly like a download from your bank: the transactions land in the bank feed with the account already identified, ready to categorize and add to the register. A CSV gets you the same rows but with none of that mapping, which is why a QBO file is the cleaner import when QuickBooks supports it. Holding a .qbo already and needing it as a spreadsheet instead? That is the reverse trip, and the QBO to CSV converter reads the file in your browser.
Keying a statement into QuickBooks by hand is where reconciliation goes wrong. Independent research on manual data entry puts the numbers in perspective, and they explain why a mapped QBO import is worth the extra step.
| Metric | Manual entry into QuickBooks | Converted QBO import |
|---|---|---|
| Typical human data-entry error rate | 1% to 5% of fields, and 2.5% even in structured numeric fields | Amounts and dates read straight from the statement, not retyped |
| Error rate late in the day | Roughly doubles by the sixth hour of continuous entry | Same output at 4pm as at 9am |
| Firms reporting incorrectly entered data | More than 27% of accounting professionals | Account, sign, and transaction IDs mapped once by the converter |
| Time to import a month of transactions | An afternoon of keying and checking the register | Under a minute to upload the QBO file and review |
| Duplicate detection | None; a mistyped line can double-count silently | QuickBooks matches on the transaction ID in the QBO file |
The takeaway for a bookkeeper: the risk in hand-keying a statement is not one big mistake, it is a steady 1% to 5% of lines going in slightly wrong, and those small errors are exactly what break a reconciliation. A QBO import moves the transactions across without retyping them, so the numbers that land in QuickBooks are the numbers on the statement. Error-rate figures are from published data-entry research (Fluxygen, DocuClipper); Gartner separately pegs the average cost of poor data quality at 15 million dollars a year per organization.
QuickBooks Online can. You upload a PDF or image statement under Bank transactions, Upload from file, and its AI extracts the transactions for you to review side by side with the original. Intuit caps that upload file at 350 KB and requires English, and when the AI is unsure it may route your statement to Intuit reviewers before the transactions are ready. QuickBooks Desktop has no such feature and cannot read a PDF at all.
So the question is not whether a PDF can go in, but whether it should. A real bank statement often exceeds 350 KB, a scanned one nearly always does, and extraction you have to proof line by line is not obviously faster than a converted file that arrives already structured. A QBO Web Connect file also carries something the AI path does not: QuickBooks treats it as a genuine bank download, so it matches against existing transactions instead of duplicating them. For a deeper comparison of both routes, see the QuickBooks bank statement converter.
All three get transactions into QuickBooks, but they behave differently once they are in. The table below lays out when each one is the right pick.
| Format | Best for | What to know |
|---|---|---|
| QBO (Web Connect) | QuickBooks Online and Desktop | Carries the account mapping and transaction IDs, so it imports like a real bank feed and avoids duplicates. |
| QFX | Quicken | The Quicken variant of the same Web Connect format; pick this when the target is Quicken, not QuickBooks. |
| CSV | Any system, manual mapping | Universal but unmapped: you set the date, description, and amount columns yourself on every import. |
| OFX | Other finance apps | The open standard QBO and QFX are built on; works with GnuCash, Xero, and most apps that read bank files. |
The steps differ slightly between the online and desktop versions, but both finish in a minute once you have the QBO file.
Open Banking (or Transactions then Bank transactions), select the account you are importing into, click the Link account dropdown, and choose Upload from file. Pick the QBO file, confirm the QuickBooks account it maps to, and the transactions appear in the For review tab. From there you categorize each one and add it to the register, the same as transactions that come in over a live feed.
Go to File, then Utilities, then Import, then Web Connect Files, and select the QBO file. If the target account shows a lightning or strike icon for an active direct feed, deactivate that feed first under Bank Feed Settings so the import does not conflict. Pick the account, and the transactions flow into the bank feed center for review. Including the routing and account numbers in the file helps QuickBooks auto-match it to the right account.
The converter reads any US bank or credit card statement, so the same upload produces a QBO file whether the PDF came from a national bank, a regional bank, a credit union, or a card issuer. For a credit card, the Chase credit card converter and its siblings work the same way. Prefer a spreadsheet first? The general bank statement converter and the PDF bank statement to Excel converter produce the same transactions in XLSX or CSV.
Every bank fails QuickBooks in its own way. One charges a monthly fee for the connection, another retired Direct Connect outright, a third shows only 18 months of history, and a fourth simply will not sync anything older than 90 days. Each page below documents that bank's specific limit and the workaround, and every one of them converts the statement PDF to the same Web Connect file.
Two limits cut across all of them. QuickBooks will not download transactions older than 90 days through any bank connection, which is Intuit's rule rather than your bank's, and each upload is capped at 1,000 transactions and 350 KB. Both are reasons a converted statement, which has no date window at all, ends up doing the heavy lifting on a cleanup.
If your bank or converter only gives you a CSV, QuickBooks Online will still take it, but you map the columns by hand and it imports without an account ID, so duplicate detection is weaker. A QBO file skips all of that because the mapping is baked in. When you want the QBO path, this converter writes the file for you; when a CSV is genuinely simpler for your workflow, you can convert bank statements to QuickBooks as a mapped CSV instead. For the manual route start to finish, our guide on how to convert bank statements to QuickBooks (QBO) walks through both options.
Most teams do not stop at one statement. If you already have your transactions in a CSV from another tool, you can turn that straight into an importable file with a CSV to QBO converter. For any other business PDF you need as a spreadsheet, a general PDF to Excel converter handles reports and tables, and firms processing financial documents at volume can extract them with enterprise document OCR.
Upload the PDF statement to BankXLSX and choose QBO as the download format. The converter reads every transaction and writes a QuickBooks Web Connect file with the account, dates, descriptions, and signed amounts mapped, so QuickBooks imports it like a real bank feed instead of a document it cannot open.
No. QuickBooks Online and Desktop only accept QBO, QFX, and OFX files in the bank feed, with CSV as a manual fallback, and there is no built-in PDF importer. You convert the PDF to a QBO file first, then upload that, which is the workflow Intuit itself points users to.
A QBO file, also called a Web Connect file, is the OFX-based format QuickBooks uses to receive bank and credit card transactions. It carries the account details and a dated, signed transaction list, so QuickBooks treats the import exactly like a download from your bank rather than a raw spreadsheet.
Open Banking, select the account, click the Link account dropdown, and choose Upload from file. Pick the QBO file, confirm the account it maps to, and the transactions appear in the For review tab to categorize and add to the register, the same as live-feed transactions.
Go to File, then Utilities, then Import, then Web Connect Files, and select the QBO file. If the account has an active direct feed, deactivate it first under Bank Feed Settings so the import does not conflict, then pick the account and review the transactions in the bank feed center.
Use QBO when QuickBooks supports it, because the account mapping and transaction IDs are baked in, so it imports cleanly and detects duplicates. Use CSV when you would rather map the columns yourself or your workflow already runs on spreadsheets. BankXLSX exports both from the same upload.
Yes. The converter reads credit card statements the same way it reads bank statements and writes a QBO file with the same account, date, description, and amount mapping. That covers card history the QuickBooks feed will not reach for older or closed accounts.
Uploads use 256-bit encryption in transit, you can delete your files at any time, and your financial data is never resold or shared. The conversion runs in your browser without installing anything, so the statement stays under your control while it is processed.
Convert to OFX for other finance software.
Convert PDF statements to Excel or CSV.
From the same family of tools
Get started converting bank statements to spreadsheets.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
