Huntington keeps up to 24 months of statements in online banking, where they can be viewed, printed or downloaded. Transactions download over a date range you choose, as a CSV file or for Quicken and QuickBooks, and Business Online exports account reports to CSV, Excel, BAI and Quicken or QuickBooks. Statements older than 24 months are requested from Huntington. For the last two years of activity on a live Huntington account, that export is all you need.
A Huntington bank statement to Excel job gets harder at the edges of that window. Since 2021 Huntington has converted three other banks' customers onto its systems: TCF in October 2021, Veritex in mid-January 2026 and Cadence in June 2026. For a client who came through any of them, part of the history sits on statements issued under another bank's name, in another layout, under an account number that no longer exists. Those statements, and any Huntington statement past the 24 months, are PDFs, and the work is converting PDFs from more than one bank into a single sheet.
The sheet worth building has the bank, the account number and the statement period on every transaction row, and its opening and closing balances checked statement by statement, including at the point where one bank's statements hand over to the next.
How Far Back Huntington Statements Go, by Banking Tier
Which window applies depends on how the client banks with Huntington. Personal online banking, Business Online and commercial reporting each have their own terms:
| Tier | How far back online | What it exports | Older periods |
|---|---|---|---|
| Personal online banking | Statements for 24 months, to view, print or download | Transactions as CSV, or for Quicken or QuickBooks, over a custom date range | Statement copies requested from Huntington |
| Business Online | Statements for 24 months | Account reports to CSV, Excel, BAI, or Quicken and QuickBooks | Statement copies requested from Huntington |
| Commercial Advanced Reporting (treasury) | Standard: 13 months of transaction history. Comprehensive: 24 months | Reports within treasury management | Comprehensive adds a Long-Term 7 Year Archive |
A seven-year figure for Huntington statement history does circulate, and the table shows its source. The Long-Term 7 Year Archive belongs to Comprehensive reporting, a treasury management product for commercial clients. A household or a small business on ordinary online banking or Business Online has 24 months of statements, and anything older is ordered from Huntington.
The 24 months roll forward a statement at a time, so in November 2026 the window reaches back to about November 2024. A former Cadence or Veritex client's 2026 statements fall inside it, where Business Online carries them; everything from the TCF era sits years outside it.
The practical rule follows from the table. Inside the window, take the export or download from the client's login. Go to the PDF statement instead when:
- The period is older than the window. Ordered copies or the client's own saved PDFs are the record.
- The statement was issued by Cadence, Veritex or TCF before its accounts moved to Huntington.
- The figures have to tie to printed balances. A statement prints an opening and a closing balance for a fixed period. A transaction export covers whatever dates were picked and has no period to tie to.
Three Conversions Behind the Other Banks' Names in a Huntington File
A client who says they bank with Huntington may have opened the account somewhere else. Three conversions since 2021 put other banks' statements into Huntington clients' files:
| Former bank | Accounts moved to Huntington | Where its clients are | The job it usually creates |
|---|---|---|---|
| Cadence Bank | June 22, 2026 | Mississippi, Texas, Alabama and the South | A 2026 tax year split across two banks |
| Veritex | Mid-January 2026 | Texas | A short January stretch on a final Veritex statement |
| TCF Bank | October 12, 2021 | Michigan, Minnesota, Illinois, Colorado | A multi-year look-back for a loan file or an audit |
In all three, the statements from before the conversion carry the old bank's name, its layout and its account number, and the client's Huntington login may show only part of that history, or none of it.
The work itself takes one of three shapes. There is the 2026 return, where the year runs across two banks. There is the look-back, where a lender (Huntington is itself a large small-business and SBA lender), an auditor or a buyer wants two, three or more years of statements in one schedule. And there is the catch-up, where a client arrives with a year or more of unreconciled activity and the statements are the only complete record, the usual starting point for tax-season catch-up bookkeeping from client statements.
Huntington is not the only bank whose clients' files now run through a predecessor's statements. The same problem comes up with Fifth Third and Comerica statements across the 2026 conversion, and with U.S. Bank statements, including Union Bank's from before its conversion.
Cadence to Huntington in June 2026: A Year on Two Banks' Statements
Huntington announced on February 2, 2026 that its merger with Cadence Bank had completed, adding 390 branches across Texas and the South. Cadence accounts kept running on Cadence's systems for the next four and a half months. Ahead of the switch, customers received new account and routing numbers, and the Cadence numbers continued to work for a period afterwards.
The switchover itself came in June. According to WTVA's report on the Cadence switchover, Cadence accounts officially moved to Huntington Bank on Monday, June 22, 2026, and Cadence online and mobile banking stopped on Thursday, June 18. Customers were told to download or save credit card statements, payment history and payee information before Cadence online banking turned off. Huntington's second-quarter 2026 results record the systems conversion as completed in mid-June.
For a business client, Huntington says Cadence statement history is available in Business Online, and that migrated statements are listed by their statement end date. Look for a month by the date it ended: a statement for March 1 to March 31 sits under March 31, and one that ran from mid-February to mid-March sits under its March date, not its February one. Huntington's transition pages do not say how many months of Cadence statements moved across. Whatever Business Online does not show comes from the PDFs the client saved before June 18, or from copies requested from Huntington.
Take a former Cadence business client, a Mississippi contractor with one operating account, whose CPA needs every 2026 transaction for the return. With statements that run by calendar month, its year arrives in three parts:
- Monthly Cadence statements from January through May, in Cadence's layout, under the Cadence account number.
- A final Cadence statement covering June up to the switchover, the shortest document in the file and the easiest to miss.
- Huntington statements from late June through December, in Huntington's layout, under the new account number.
One account, then, but two statement layouts and two account numbers, and a single seam where the closing balance on the last Cadence statement should meet the opening balance on the first Huntington statement. Those two statements are also the only place both account numbers sit side by side in the client's own records, so keep them as a pair.
Veritex Statements: Two Weeks of January 2026
Veritex went first. Huntington's first-quarter 2026 earnings exhibit, filed with the SEC, records the systems conversion of Veritex Holdings as completed in mid-January, and Huntington's Veritex pages say the Veritex online statement history transferred with the accounts. For a former Veritex client in Texas, check the Huntington login for Veritex months before asking the client for PDFs.
The 2026 year is where Veritex trips people up. Its first couple of weeks sit on a final Veritex statement, under the Veritex account number and in Veritex's layout, and that statement looks like the tail end of 2025 rather than the start of the new year. Gather the year as "the Huntington statements" and it gets left out. The Huntington run then begins in mid-January, its first opening balance is not the balance on January 1, and the year will not tie to the prior year's closing figure.
A Veritex bank statement to Excel job for 2024 or 2025, for a loan file or a prior-year review, is simpler: every statement is Veritex's own, under one account number, and converts like any other bank's.
TCF Statements and a Look-Back Into 2019 to 2021
TCF accounts converted to Huntington on October 12, 2021, and for business clients little of their history came with them. Huntington's treasury transition guide gave most Business Online users about a year of TCF statement history. Five years on, that carried-over year has itself aged out of Huntington's 24-month window.
So the arithmetic for a former TCF client in Michigan, Minnesota, Illinois or Colorado is blunt. Anything before the October 2021 conversion is a pre-Huntington statement, and it exists as a PDF the client kept or as a copy ordered from Huntington. The early Huntington months, from late 2021 until two years ago, are past the online window too, and need ordering or the client's own files just the same.
That matters most for the jobs that reach furthest back: a lender's request for five or more years of statements, an audit of a period that spans the conversion, a buyer's due diligence, a dispute over an old payment. The file mixes TCF statements under TCF account numbers with Huntington statements under the new ones, and whoever reads it checks that the periods are continuous. Before converting a single TCF statement to Excel, list every month the request covers for each account, tick each one off against a statement in hand, and order the gaps from Huntington before the schedule is built.
Converting a Mixed Stack of Huntington, Cadence, Veritex and TCF PDFs
The stack comes from three places. The Huntington bank statement PDF for each month inside the window downloads from online banking or Business Online. Add the Cadence, Veritex or TCF PDFs the client saved, and the copies ordered from Huntington. A statement that survives only on paper can be scanned and added as a PDF, JPG or PNG.
For the Mississippi contractor, that is around a dozen PDFs for the operating account's 2026: five monthly Cadence statements, the final Cadence statement, and the Huntington statements from late June on. A Veritex client adds one January statement; a TCF look-back adds years.
Two banks' layouts do not mean two jobs. You can convert the PDF statements to Excel in one batch, Cadence's and Huntington's in the same task, without setting up either layout: the prompt describes the spreadsheet you want, and the AI reads each statement for itself. A seven-year TCF look-back goes in the same way, as one task, since a task takes up to 6,000 files.
The ready-made bank statement prompt gives one row per transaction. For a file that spans banks, add the columns that keep the banks and accounts apart. A plain request does it: "One row per transaction. Columns: Bank (as named on the statement), Account Number (last four digits as printed), Statement Period, Date, Description, Debit, Credit, Balance, Opening Balance and Closing Balance as printed on each statement."
Those three columns do the work in this file. The contractor's January to June rows carry the Cadence account number and the Cadence name; the rows from late June carry Huntington's name and the new number. Filter on Bank and Statement Period and each statement's run of transactions stands on its own; pivot on Statement Period and the year reads in order across both banks. Anyone checking a row against its PDF sees the bank and number that statement printed. If the books treat the account as one account throughout, a further column that gives every row the current Huntington number can be added to the prompt.
The result downloads as Excel, CSV or JSON. In Excel, numbers come through as numbers and dates as dates, so a pivot or a SUMIFS works straight away, and the CSV is the format for an import. Every row carries a Source File column with the file and page it came from. A panel of AI agents has to agree on every value, and a value or a row it cannot agree on is flagged as Review Needed, with what to check. In the results viewer, clicking the file name on any row opens the page it came from beside it.
Checking the Cadence-to-Huntington Seam, Then Importing to QuickBooks
Two checks prove the sheet holds every transaction, and both run on the balances each statement printed.
Each statement ties on its own. For every account and statement period, the opening balance plus the period's credits, minus its debits, should equal the closing balance. With Opening Balance and Closing Balance on the rows, that is a formula grouped by Account Number and Statement Period, not a walk through the PDFs. A period that misses by an amount usually points to one transaction left out or read wrong. The Source File column takes you to the statement page, where the difference can be found.
The seam ties across the banks. The closing balance on the contractor's final Cadence statement should equal the opening balance on its first Huntington statement, where the balance carried across at the conversion. A gap at that join means a statement or a run of transactions is missing between the two banks' records, and the final Cadence statement is the first suspect. The same check applies wherever a file crosses a conversion: Veritex's January statement against the first Huntington statement of 2026, and the last TCF statement against the first Huntington one in October 2021. Then read down the Statement Period column for gaps, since a missing month can hide between two periods that each tie on their own. The method is the same as reconciling bank statement balances at any single bank; the conversion just adds a join to check.
Once every period ties, the sheet goes into the books. For the recent window on a live account, Huntington's own QuickBooks download covers it. The converted history before that, the Cadence months included, goes in through QuickBooks' bank transaction upload, one file per account, each to the QuickBooks account it belongs to. Cut a copy of the checked sheet down to one account and the upload's columns. Where the upload file is the goal from the start, a Structured Prompt fixes the column headers in the order the upload expects (Date, Description and Amount, or Date, Description, Debit and Credit), and once the Review Needed rows are settled, the Source File and Review Needed columns can be left out of downloads in Preferences. End the converted history the day before Huntington's own download begins, so no month comes in twice. The file imports; nothing is posted to QuickBooks for you, and the matching and categorizing stay there. The column requirements and the duplicate-transaction traps are set out in the guide to importing bank statements into QuickBooks.