Download a CSV, QFX, or OFX file of transactions from your bank, go to Transactions, click the dropdown next to Link account, and choose Upload from file. Map the columns if you're using a CSV, select or create the matching account, and the transactions land in For Review exactly like a live bank feed would. This is the fallback for when your bank doesn't offer a direct connection, not a replacement for one that does.
1. Confirm you actually need this. Most banks connect to QuickBooks directly through Link account, pulling transactions in automatically with no file involved. File upload exists for the ones that don't, or for a connection that's temporarily broken, so check the direct option first.
2. Download the right file from your bank. Most banks offer CSV, QFX, or OFX for a given account and date range. QFX and OFX carry more structure already built in; CSV is the most common but needs manual mapping on the QuickBooks side.
3. Go to Transactions, then click the Upload from file option. It's under the dropdown next to Link account on the main Banking screen, easy to miss since the default flow pushes you toward connecting a bank live.
4. Match it to the right account. Select the existing QuickBooks account this data belongs to, or create a new one if it doesn't exist yet. Getting this wrong routes real transactions into the wrong register.
5. Map the columns, if it's a CSV. QuickBooks asks you to tell it which column is the date, which is the description or payee, and which is the amount (or separate debit and credit columns, if your bank exports it that way).
6. Check the date range against what's already there before you finish. Overlapping an upload with transactions QuickBooks already has, from a prior upload or a live feed that's since reconnected, creates duplicates that someone has to find and remove by hand.
7. Review and categorize as normal. Once imported, the transactions sit in For Review exactly like anything from a live connection, waiting to be added or matched.
For a bank that genuinely never offers a live connection, which does still happen with smaller or regional institutions, file upload isn't a one-off fix, it's the ongoing way that account's data gets into QuickBooks every single period. Someone has to remember to log into the bank, export the right file, and run it through QuickBooks, on a schedule, indefinitely.
The duplicate risk gets worse the longer this runs. Each upload needs to pick up exactly where the last one left off, and a missed week, or an overlap nobody caught, means hunting through the register later for transactions that showed up twice or didn't show up at all.
None of that actually requires a person in the loop every time. If a bank or processor can be reached directly, even without an official QuickBooks connector, the same data that someone's exporting and uploading by hand can often be pulled and formatted automatically on the same schedule, without anyone touching a file.
For an account with no live Online Banking support, we build a direct pull from the bank or processor that formats and lands transactions in QuickBooks on a schedule, so nobody's exporting a file and running it through the upload screen every month.
Every import checks the date range and transaction details against what's already in QuickBooks before anything gets added, so an overlapping upload doesn't create the double entries someone would otherwise have to track down by hand.
Those are two ways this gets fixed. Tell us which bank or account it is and how often you're doing this, and we'll tell you if it can run on its own.
Tell us which account doesn't connect directly, and how you're getting its data in today, and we'll tell you whether that step can disappear entirely. And if it's not bank transactions that are the real time sink, that's fine too; the same question applies to anything else in the business that's still running on someone's manual effort.
Let's talk →Go to File > Utilities > Import > Web Connect Files for a QFX or OFX file, or use Banking > Bank Feeds > Import Web Connect File depending on your version. Desktop generally expects the bank's own export format rather than a generic CSV, unlike Online, which accepts CSV with manual column mapping.
This is the same action as importing transactions: export a CSV, QFX, or OFX file covering the statement period from your bank, then use QuickBooks' file-upload option (Online) or Web Connect import (Desktop) rather than trying to import a PDF statement directly, which neither version supports.
The same file-upload process works for a credit card account as for a checking account. Pick the credit card account when prompted to match the upload to an existing account, rather than accidentally routing the charges into a bank account.
Save the Excel file as a CSV first; QuickBooks' transaction file upload expects CSV, QFX, or OFX, not a native .xlsx file. That's a different tool from QuickBooks' own Excel import feature, which is built for customer, vendor, and product list data rather than bank transaction history.