Huntington CSV to QBO Converter: Convert Huntington CSV to QuickBooks

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.

Direct Connect for QuickBooks is being retired across the industry on October 30, 2026, and new enrollments already closed on April 30, 2026. This is not one bank's decision, so it applies regardless of which institution you are with, and several banks moved earlier than the industry date. Bank of America ended its Direct Connect service on September 30, 2025. Treat any notice from Huntington itself as authoritative over the industry date, because your bank's own timeline is the one that will actually cut you off.

The practical consequence is worth planning for now rather than in October. On QuickBooks Desktop, Intuit's own bank feeds setup documentation lists exactly two connection types, Direct Connect and Web Connect. When Direct Connect goes, Web Connect is what remains, and Web Connect reads .qbo files and nothing else. Express Web Connect is a QuickBooks Online feature and is not a guaranteed Desktop replacement. That is the whole reason a Huntington CSV to QBO conversion matters for Desktop users: it produces the one file format the surviving connection type accepts.

No. Import posted transactions only. A pending transaction can still change its amount, its date, or its description before it settles, and card authorizations in particular often post for a different figure than the one that was held. If you import a pending row and then import the posted version later, you get two transactions for one purchase and a reconciliation that will not close.

The safe habit is to download and convert through the last fully posted day rather than through today. If you convert on the 3rd of the month, take the file through the end of the prior month and leave the first few days for the next run. Non overlapping date ranges are the cleanest way to work, and they matter more than usual when the same account is also feeding QuickBooks through any other route.

The same way, with one thing to watch: the sign convention flips. QuickBooks reads a single Amount column as positive for money in and negative for money out, expressed with a minus sign rather than parentheses. On a bank account that is intuitive. On a credit card account, a purchase increases what you owe, so the sign that means an expense on the card register is the opposite of the sign that means an expense on the checking register.

Check one known transaction after the first import rather than assuming. Find a purchase you remember, confirm it increased the card balance rather than reducing it, and you have validated the whole file in about thirty seconds. If every amount landed backwards, the fix is a sign flip on the column before reconverting, not a manual correction of hundreds of rows.

Three arithmetic checks narrow almost every discrepancy before you start scrolling. If the difference divides evenly by nine, you are looking at transposed digits, two figures entered in the wrong order. If the difference equals exactly twice a transaction on the statement, a sign is flipped somewhere. If the difference matches one transaction exactly, that row either did not convert or was accepted twice.

Only after those three come up empty is it worth comparing line by line. Start with the first and last dates in the imported period and confirm they match the Huntington statement, because a date that shifted at the edges of the range is the most common cause of a period that is short by a handful of transactions. Two digit years resolve as 00 to 29 meaning 2000 to 2029 and 30 to 99 meaning 1930 to 1999, which is enough to silently move a December transaction into the wrong year.

Convert one file at a time and produce one .qbo per account. That is not a limitation to work around, it is how QuickBooks expects bank data to arrive: a .qbo file carries the account it belongs to, and QuickBooks matches transactions and blocks duplicates within that account. Merging checking, savings and a card into a single file removes the boundary that makes the duplicate protection work.

Keep the files separate and named by account and period, for example huntington-checking-2026-08.qbo, and import them in date order. If you are running a full year across multiple accounts, work newest to oldest and reconcile each account for each period before moving on, so an error surfaces while you still remember which file produced it.