QuickBooks only pulls about 90 days of bank feed history. Convert old PDF statements to .qbo and import historical transactions for catch-up and taxes.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF · Max 50MB
Uploading...
To import bank statements older than about 90 days into QuickBooks, you cannot rely on the bank feed. QuickBooks Online downloads roughly the last 90 days of history when you connect an account, some banks reach back up to 24 months but most do not, and anything older has to be added another way. The reliable fix is to convert each old PDF statement into a .qbo Web Connect file and upload it, so every historical transaction lands in QuickBooks with its real date, description, and amount.
Last updated June 2026. Bank feed history limits are set by each bank, not by QuickBooks; confirm the range your bank exposes inside QuickBooks.
This is the wall almost every catch-up, software migration, and year-end cleanup hits. You start a new QuickBooks company, connect the bank, and only the last quarter shows up. The eight, twelve, or twenty-four months you actually need for the books are sitting in PDF statements your bank already issued. The converter at the top of this page turns those statements into files QuickBooks imports the same way it imports a live feed, so you can backfill a full year in a few minutes per month instead of typing transactions by hand.
The same problem shows up when you switch accountants, file a prior-year return late, respond to an audit, or move books off a spreadsheet into QuickBooks for the first time. In every case the data exists; it is just trapped in PDFs the bank feed will not retrieve. Here are the four ways to get older transactions in, and why converting the statement to a .qbo is the cleanest for backfilling months or years at once.
| Method | How far back it reaches | Effort | Best for |
|---|---|---|---|
| Reconnect or update the bank feed | About 90 days (some banks to 24 months) | Low | Filling a recent gap only |
| Type transactions into the register | Any date, by hand | Very high | A handful of missing entries |
| Upload a CSV downloaded from your bank | As far back as your bank exports | Medium, you map the columns | Banks that still export old CSV |
| Convert each PDF statement to a .qbo file | Any statement you can download | Low, no column mapping | Backfilling months or years from PDFs |
Whichever method you use, work oldest to newest. QuickBooks builds the register balance as transactions arrive, so importing in date order keeps the running balance correct and makes a missing month obvious at a glance.
Built for the statements US banks actually send, checked before it exports.
The converter adds up the transactions it parsed and matches that to the statement total before you export, so nothing is silently dropped.
Valid OFX 1.02 with QuickBooks Web Connect headers. Online and Desktop import it as a standard bank feed.
OCR runs before parsing, so a scanned or photographed paper statement comes out the same as a digital PDF.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Enter the password on upload. Multi-column and multi-page statement layouts are parsed too.
One conversion, three files: the .qbo for QuickBooks, an XLSX to review, and a CSV for everything else.
Three steps. No column-mapping wizard.
Drag in a PDF, a scan, or a phone photo. Password-protected and multi-page files are fine.
Every transaction is extracted and checked against the statement total. You see the parsed rows before exporting.
Download the .qbo and import it as a Web Connect bank feed. Excel and CSV are in the same download.
The specifics that decide whether the import is clean. If your case is not here, email [email protected].
QuickBooks Online downloads about the last 90 days of transactions when you first connect a bank account. Some banks let it reach back up to 24 months, but most stop near 90 days. To bring in anything older you upload a .qbo or CSV file yourself, which a converted PDF statement provides for any date you have.
The 90-day cap is set by your bank, not by QuickBooks. When QuickBooks connects, it can only pull the history the bank's feed makes available, and most US banks expose roughly the last 90 days through that connection. QuickBooks cannot request older data the bank declines to send, so earlier months never arrive automatically.
Convert or download the old statements into a file QuickBooks accepts, then upload it manually. In QuickBooks Online go to Transactions, then Bank transactions, then Upload from file, and select a .qbo or CSV covering the older dates. Converting each PDF statement to a .qbo is the cleanest route because it needs no column mapping.
Connecting a bank only brings in recent history, so earlier transactions must be added by file. Convert each PDF statement from before your connection date into a .qbo Web Connect file and upload it under Transactions, Bank transactions, Upload from file. Import oldest first so the register builds its running balance in the right order.
Gather every monthly statement for that year, convert each one to a .qbo file, and upload them in date order through Upload from file in QuickBooks Online or the Web Connect importer in Desktop. Because each .qbo carries the real dates, the prior-year transactions post to the right periods and reconcile against the statements.
Open Transactions, then Bank transactions, then Upload from file, and pick a .qbo or CSV that covers the historical dates. Choose the matching bank account and continue. QuickBooks drops the transactions into For Review, where you categorize and match them. A converted PDF statement gives you a ready .qbo for any month the feed missed.
QuickBooks Desktop imports old statements through File, then Utilities, then Import, then Web Connect Files. It reads .qbo Web Connect files only, not PDF or CSV, so convert each old statement to .qbo first. Import the files oldest to newest, attach each to the correct account, then match the transactions in the Bank Feeds Center.
Yes. Last year's statements import fine as long as you give QuickBooks a file it reads. Convert each monthly PDF to a .qbo and upload it, and the transactions post to last year's dates, not today's. This is the standard way to finish a prior-year set of books for taxes or a late catch-up.
The oldest transaction date is the earliest entry already in your QuickBooks bank register. It matters because you want your historical upload to start one day before it, so you fill the gap without overlapping. Check it under the Gear icon, then Chart of Accounts, then View register, and scroll to the bottom of the list.
It can if the date ranges overlap with transactions already in QuickBooks. To avoid duplicates, note your oldest existing transaction date and convert statements that end just before it. QuickBooks also flags likely matches in For Review. If a duplicate slips in, exclude or delete it there before you categorize the rest.
Convert each monthly statement to its own .qbo file, then import them oldest to newest, one month at a time. The full catch-up bookkeeping workflow walks through the reconciliation order. Working in date order keeps the running balance correct and makes a missing month obvious. A dozen statements take a few minutes each, far faster than retyping years of transactions by hand.
QuickBooks Self-Employed accepts a CSV of past transactions rather than a .qbo Web Connect file. Convert your old PDF statement, use the CSV copy the converter produces alongside the .qbo, and import it through the transactions import option. Review the categories after the upload, since older imports come in uncategorized.
A .qbo file is usually better because it imports without column mapping and carries the bank identifiers QuickBooks expects, so transactions land ready to review. CSV works in QuickBooks Online too, but you map the date, description, and amount columns yourself each time. For QuickBooks Desktop, .qbo is the only one of the two it reads.
Upload a PDF, see every transaction extracted in seconds. No card to try it.
Still comparing tools? See our bank statement to QuickBooks converter comparison.
Once your historical statements are in, keep the workflow going: see how to convert a bank statement to QuickBooks Desktop, read the companion guide on how far back QuickBooks imports transactions, and learn the format in our QBO file and PDF to QBO converter explainers. Bookkeepers cleaning up several clients should see bank statement to QuickBooks for accountants, and old credit card history follows the credit card statement to QuickBooks steps. If your bank exports old activity as CSV, a CSV to QBO converter handles that file, a bank statement to Excel converter gives you a spreadsheet to review the year against, and you can digitize the matching old receipts and bills into a spreadsheet while you reconcile the catch-up.
Same converter, tuned for the layout each bank uses. Find yours:
For one bookkeeper running monthly close.
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 |
For an accounting firm or finance team with steady volume. Adds QuickBooks .qbo export and bulk conversion.
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 |
For lenders, audit firms and analysts running thousands of statements a month.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
