QuickBooks Enterprise cannot import a bank CSV. Convert your CSV or Excel export to a real .qbo Web Connect file in seconds, then import it through Bank Feeds.
No account needed for your first conversions. We never store your bank login.
Short answer: QuickBooks Enterprise cannot import a bank or credit card CSV. Enterprise reads exactly one banking file, a .qbo Web Connect file. So the working method is to upload your CSV or Excel export to the converter at the top of this page, download the .qbo it builds, then load it in Enterprise through Banking, Bank Feeds, Import Web Connect File. Last updated July 2026.
This trips up a lot of Enterprise controllers, because Enterprise is the biggest, most expensive edition Intuit sells, and people reasonably assume the most expensive edition can do what QuickBooks Online does for free. It cannot. The native CSV bank upload lives only in QuickBooks Online. Every Desktop edition, Pro, Premier, Accountant, and Enterprise alike, has the same banking import path: a Web Connect file with a .qbo extension. Enterprise's Import from Excel feature is a different thing entirely. It handles lists such as customers, vendors, items, and chart of accounts, not bank and credit card activity.
The gap matters more in 2026 than it used to. Intuit stopped selling new Pro Plus, Premier Plus, and Mac Plus subscriptions in September 2024, QuickBooks Desktop 2023 left support after May 31, 2026, and Desktop 2024 is the final non-Enterprise release. Enterprise is now the only Desktop edition Intuit still sells and updates with no published end date, so a steady stream of Pro and Premier companies is landing on Enterprise. They arrive with the same bank exports they have always used, and discover the CSV route they expected is not there.
Enterprise shops also tend to have the hardest version of the problem: several legal entities, a dozen or more bank and card accounts, and banks that never built a QuickBooks connection in the first place. Regional commercial banks, credit unions, treasury and lockbox portals, fuel card programs, and merchant processors mostly hand you a CSV or an Excel workbook and nothing else. Converting those files to .qbo is the only supported way to get that activity into Enterprise without keying it by hand or paying for a data services engagement.
The converter above reads .csv, .txt, .xls, .xlsx, and .xlsm in any column order. It normalizes mixed date formats, strips dollar signs and thousands separators, handles both the signed single amount column and the separate debit and credit layout, and writes a valid OFX-based .qbo with a unique ID on every transaction so Enterprise recognizes a re-import instead of duplicating it. You get the .qbo plus cleaned Excel and CSV copies in the same download, which is useful when a controller wants an audit trail of exactly what was loaded.
| Route into QuickBooks Enterprise | Accepts a bank CSV? | Works after Oct 30, 2026 | Typical cost | Best for |
|---|---|---|---|---|
| Convert CSV to .qbo, then Import Web Connect File | Yes, that is the point of the conversion | Yes | Free to try, paid plans for volume | Any bank or card that only exports CSV or Excel |
| Direct Connect bank feed | No | No, Intuit retires it Oct 30, 2026 | Bank fee, often $10 to $25 a month | Nothing going forward, it is being switched off |
| Web Connect download straight from the bank | No, the bank has to publish .qbo | Yes | Usually free | Large banks that still offer a QuickBooks download |
| Enterprise Import from Excel | No, lists only, not bank activity | Yes | Included | Customers, vendors, items, chart of accounts |
| Third party IIF import | Indirectly, via a converter | Yes | Varies | Journal style entries, not bank feed review |
| Manual entry in the register | No | Yes | Staff time | A handful of transactions a month |
Built for the CSV and Excel exports US banks and cards actually send, checked before it exports.
The converter adds up the transactions it parsed and matches that to your file 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.
Date, description, and amount are detected for you, so you skip QuickBooks' strict 3-column and 4-column CSV layout.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Mixed date formats, currency symbols, and stray commas that break a raw CSV import are cleaned up before the .qbo is built.
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 CSV, XLS, or XLSX export from your bank, credit card, or accounting tool. Any column order is fine.
Every transaction is parsed and checked against your file total. You see the 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, message us in chat.
Not for bank or credit card transactions. QuickBooks Enterprise has no native CSV bank upload in any year or edition, including Platinum and Diamond. Its only banking import is a .qbo Web Connect file. Enterprise does import Excel and CSV for lists such as customers, vendors, items, and the chart of accounts, but that tool will not accept bank activity.
Convert it first. Upload your CSV or Excel export to the converter above, check the parsed rows and the transaction count, and download the .qbo. In Enterprise, open Banking, then Bank Feeds, then Import Web Connect File, select the .qbo, and pick the account to load it into. The transactions land in Bank Feeds for review exactly like a normal feed download.
There are three supported routes. Download a .qbo from your bank if it publishes one, use a bank feed while it lasts, or convert the CSV your bank does export into a .qbo and import that. The third route is the only one that works for every bank, since it depends on your file rather than on whether your bank built an Intuit connection.
A .qbo file, also called a Web Connect file. It is Intuit's flavor of OFX and carries the account details, a date range, and one record per transaction with a unique FITID that QuickBooks uses to spot duplicates. Web Connect reads .qbo only. QFX files from Quicken, QIF files, and plain OFX will be rejected by Enterprise.
Yes. Enterprise supports Bank Feeds in Advanced Mode, Express Mode, and Classic (Register) Mode, switchable under Banking, Bank Feeds, Change Bank Feeds Mode. All three modes accept an imported Web Connect file, so a converted .qbo behaves the same as a live download once it is in. Advanced Mode gives you the Transactions List window for adding and matching in bulk.
Recent QuickBooks Desktop releases require an Intuit Account sign-in inside the program before a Web Connect import will run, and Advanced Mode bank feeds require it too. Sign in under Company, then My Company, or when the prompt appears. If sign-in keeps failing, switching to Classic (Register) Mode is the usual workaround while you sort the account out.
Enterprise has no small per file cap the way QuickBooks Online does. Online limits a manual upload to 350 KB and 1,000 rows, which is why multi year backfills fail there. Desktop Web Connect imports of several months, or a full year of activity in one .qbo, are routine. Enterprise is built for high transaction volume, so the practical limit is your file, not the import.
Yes, and that is the normal Enterprise pattern. Convert each account's export to its own .qbo, because a Web Connect file maps to one account, then import them one at a time into the matching account in Enterprise. Batch conversion and duplicate detection are on the paid plans, which is what firms running multiple entities use to close a month quickly.
No. Intuit stopped selling new Pro Plus, Premier Plus, and Mac Plus subscriptions in September 2024 and Desktop 2024 is the last non-Enterprise release, but Enterprise is still sold, supported, and updated with no published end date. That is why Enterprise is where most companies leaving Pro and Premier are going, and why its import limits are worth understanding before you migrate.
Intuit retires Direct Connect on October 30, 2026, and new enrollments already closed on April 30, 2026. Web Connect is not affected and keeps working. Companies losing Direct Connect switch to downloading a .qbo from the bank, or, where the bank offers only a CSV, converting that CSV to .qbo and importing it. Direct Connect bill pay ends with the service.
It should not. Every transaction in the generated .qbo carries a unique ID, which is the field QuickBooks checks when deciding whether it has seen a transaction before. If you import overlapping date ranges, Enterprise flags the repeats rather than posting them twice. Review the batch in Bank Feeds before you add anything to the register.
Upload a CSV or Excel export, get a QuickBooks-ready .qbo back in seconds. No card to try it.
Where to go next: run the same conversion for the cloud edition on the CSV to QuickBooks Online page, cover the Pro and Premier route on the CSV to QuickBooks Desktop converter, plan for the feed change with the Direct Connect alternative, load a backlog of accounts with the bulk CSV to QBO converter, wire it into a nightly job with the CSV to QBO API, or set up the feed itself using bank feeds in QuickBooks Desktop. Firms handling client files should start at the CSV to QBO converter for accountants, and if your export is a spreadsheet rather than a CSV the Excel to QBO converter covers it. For the exact column layout QuickBooks expects, use the QuickBooks CSV import template.
For the solo bookkeeper running a monthly close in QuickBooks.
USD / month
billed $288 yearly
For a firm or finance team converting across many clients and currencies.
USD / month
billed $888 yearly
For multi-bookkeeper firms managing many client books at scale.
USD / month
billed $2,988 yearly
