Convert a Huntington Bank CSV export into a QuickBooks .qbo file. Huntington Commercial accounts cannot link to QuickBooks Online, so import a file instead.
No account needed for your first conversions. We never store your bank login.
Short answer: Download your Huntington activity as a CSV, upload it here, and the converter returns a QuickBooks Web Connect (.qbo) file. QuickBooks Online imports the .qbo directly and QuickBooks Desktop reads it through File, Utilities, Import, Web Connect Files. Huntington Commercial customers sign in with a company ID, a user ID, and a password, a three field structure QuickBooks Online's bank connection form cannot accept, so for those accounts a converted file is not a workaround. It is the only route.
It handles exports from Huntington personal checking and savings, Huntington Business Checking, and the Huntington Commercial and treasury accounts used across Ohio, Michigan, Pennsylvania, Indiana, Illinois, West Virginia, Kentucky, Minnesota, Wisconsin, and Colorado.
The bank feed is where Huntington Commercial customers get stuck. A Huntington Commercial login is not a harder version of a personal login. It is a different credential shape, and no amount of retrying the connection will make QuickBooks accept it.
| Method | Works with QuickBooks Online | Works with QuickBooks Desktop | Works for Huntington Commercial | Best for |
|---|---|---|---|---|
| Convert the Huntington CSV to a .qbo (this tool) | Yes, upload the .qbo | Yes, Import Web Connect file | Yes | Any Huntington account, any date range, and history older than the feed window |
| Upload the raw CSV to QuickBooks Online | Yes, with manual column mapping | No native CSV transaction import | Yes | One small file, once you map columns and fix the date format |
| Huntington bank feed connection | Yes, for retail online logins | Yes, with Direct Connect | No, the company ID login is not supported | Hands off daily sync on a personal or retail business login |
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.
Sign in to Huntington online banking on a desktop browser, open the account, and use the download or export option above the transaction list. Choose your date range and select the CSV format. Upload that CSV here. The converter reads the date, description, and amount columns, checks the parsed totals against your file, and returns a .qbo ready to import.
Because the credentials do not fit. Huntington Commercial customers sign in with a company ID, a user ID, a password, and often a token or PIN. QuickBooks Online's bank connection form asks for a single username and a single password, so there is nowhere to put the company ID. Intuit's own community threads point commercial customers at a separate retail online login, or at importing a downloaded file. Converting the CSV to a .qbo is the file route, and it works on the first try.
Not through the bank connection. You can add the account manually in QuickBooks and then feed it transactions by importing files, which is what most Huntington Commercial bookkeepers end up doing. Create the account in your chart of accounts, download the CSV from Huntington, convert it to a .qbo, and import it against that account. The transactions land exactly as a live feed would deliver them.
Log in at huntington.com on a desktop browser, open the account, and look for the export or download icon near the transaction history. Pick the date range you need and choose the comma separated values option, then save the file. The export is on the full site rather than the mobile app, and it is available on commercial accounts even though the QuickBooks connection is not.
No. QuickBooks Desktop has no native CSV transaction import. Its only transaction import path is Web Connect, which accepts .qbo files, so a Huntington CSV has to be converted first. QuickBooks Online will take a CSV, but it asks you to map columns on every upload and it will not repair Huntington's date formatting or the way debits and credits are split.
Huntington CSV exports include columns QuickBooks does not expect, such as a running balance and a transaction type. QuickBooks Online accepts either a three column layout of date, description, and amount, or a four column layout that splits credit and debit, and it caps a single upload at 350 KB. The converter drops the extra columns, normalizes the dates, and writes each amount with the correct sign.
Huntington has published QuickBooks conversion instructions for Web Connect in the past, but the download options available inside online banking vary by account type, and commercial customers routinely find only spreadsheet formats. If a .qbo option appears for your account, use it. If it does not, or if the file QuickBooks receives is rejected, converting the CSV produces a clean Web Connect file that both QuickBooks versions read.
Huntington online banking keeps a long window of activity available for export, well beyond what a bank feed will sync. A connected feed typically reaches back about 90 days no matter which bank it is. To rebuild older books, pull a CSV for each range you need and convert each one, since importing a .qbo file carries no date restriction at all.
QuickBooks caps a single CSV upload at 350 KB, roughly 1,000 transactions, which is why a busy quarter fails to upload as a spreadsheet. A .qbo file has no equivalent cap. If you are converting several accounts or a full year of history, run them together with the bulk CSV to QBO converter instead of uploading files one at a time.
Upload a CSV or Excel export, get a QuickBooks-ready .qbo back in seconds. No card to try it.
Yes, and the accuracy check is the point. Before the .qbo downloads, the converter adds up every transaction it parsed and compares that total to the total in your Huntington CSV. If a row is missing or misread, you see it in the preview rather than during reconciliation. Working from another bank? Use the CSV to QuickBooks Online converter for any account, follow the Desktop path on CSV to QuickBooks Desktop, turn a spreadsheet into a .qbo with the Excel to QBO converter, or weigh the options on the best CSV to QBO converter roundup. Regional neighbors are covered by the Fifth Third CSV to QBO converter and the KeyBank CSV to QBO converter. For the long form walkthrough, read Huntington CSV to QuickBooks, and for the import step see how to import a QBO file into QuickBooks.
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
