TD Bank CSV to QBO Converter: Convert TD Bank CSV to QuickBooks

Sign in to TD Bank online banking or TD Business Direct on a desktop browser, open the account, and download your activity as a CSV for the date range you need. Upload that CSV to the converter at the top of this page. It detects the date, description, and amount columns, checks the parsed total against your file, and hands back a .qbo you import into QuickBooks. QuickBooks Online reads the .qbo directly, and QuickBooks Desktop imports it through Bank Feeds, so the same file works in either version.

Sign in at td.com, open the account, and use the download or export option on the account activity page, then choose the comma-separated values (CSV) format and your date range. On TD Business Direct, open the account and use the export function to select CSV. Use the desktop website rather than the TD mobile app, since the app does not offer the full transaction export that the converter needs.

Error 105 means the problem is on the bank side, usually TD website maintenance or server issues that break the connection, and Intuit has escalated TD error 105 to its development team. Error 106 means QuickBooks cannot locate the account on TD's site, an issue TD Business Direct customers have hit repeatedly. While the feed is down, downloading a TD Bank CSV and converting it to a .qbo gets your transactions in without waiting for the connection to be fixed.

TD Bank and TD Business Direct offer a QuickBooks Web Connect (.qbo) download for some accounts, but users regularly report TD .qbo files failing to import cleanly, with formatting and Bank ID mismatches that need manual editing. Intuit's own guidance is to download the Web Connect file straight from your bank and confirm it is a .qbo. Converting a plain TD CSV to a .qbo produces a clean Web Connect file when the bank's own download is missing or broken.

A TD Bank CSV often has extra columns, no running balance, and debits and credits that QuickBooks Online's three or four column mapping reads the wrong way, so descriptions go missing or amounts flip sign. Converting the CSV to a .qbo builds a clean description and applies the correct sign for each transaction, so the import lands right the first time instead of needing row-by-row cleanup after the fact.

No, QuickBooks Desktop cannot import bank transactions from a raw CSV file. Desktop only imports a Web Connect .qbo through File, then Utilities, then Import, then Web Connect Files. When TD's own .qbo download errors out or an account only offers CSV, converting your TD Bank CSV to a .qbo first is the reliable way to get those transactions into QuickBooks Desktop.

TD Bank online banking typically shows around 18 months to two years of activity, and the direct QuickBooks feed reaches back roughly 90 days. To catch up a longer stretch, download each available range as a CSV, convert each one to a .qbo here, and import them in order. The accuracy check on every file means nothing is dropped when you piece a long history together.

Yes. TD Business Direct activity downloads as a CSV the same way personal account activity does, and the converter handles business exports, including split debit and credit columns. You get a .qbo that imports into the matching QuickBooks account, which is exactly the workaround Business Direct users reach for when the direct download returns error 106.

QuickBooks caps a single CSV upload at 350 KB, which is roughly 1,000 transactions, so a long TD Bank export can fail when uploaded as a CSV. Converting to a .qbo and, where needed, splitting by month or quarter keeps each file inside that limit. The converter checks every batch against your file total, so nothing is dropped when you split a long TD Bank history across several files.

Direct Connect is being retired industry wide on October 30, 2026, and new enrollments already closed on April 30, 2026. That is not a TD specific decision, it applies across banks, and individual institutions have moved earlier than the industry date. If TD publishes its own cutover notice, that date outranks the industry one.

What this means in practice is that a TD Bank connection you set up years ago has a shelf life, and the replacement is not automatic. Intuit's own QuickBooks Desktop bank feeds documentation lists exactly two connection types, Direct Connect and Web Connect, so Express Web Connect is not a guaranteed Desktop replacement when Direct Connect goes away. Converting your TD activity export to a .qbo file is the method with nothing to expire, because there is no live connection involved at any point.

Use the feed for ongoing daily activity and convert a CSV whenever you need history the feed will not give you. A newly connected bank feed commonly pulls only about 90 days, so if you are catching up on a backlog, opening a prior year, or onboarding a client mid year, the feed simply cannot reach far enough back and the CSV export can.

The other case for converting is a broken feed. Error 102 and 105 both point at the bank side rather than at your file, error 185 means the bank wants more than a user ID and password, and error 324 means QuickBooks cannot find the account. None of those are fixable from inside QuickBooks, and all of them leave you needing transactions today. Downloading the activity and converting it keeps the month closing on schedule while the connection gets sorted out.

Because a CSV carries no transaction identifier and a .qbo file does. Every OFX and .qbo transaction includes a FITID that is unique within the account and never reused, and QuickBooks skips any FITID it has already seen. Upload the same TD Bank CSV twice and you get every row twice. Import the same .qbo twice and the second pass is ignored.

There is a detail worth knowing before you try to fix a duplicate mess by deleting. QuickBooks remembers a FITID even after you delete the transaction, so deleting a batch and re importing the identical file will not bring it back. If you need to redo an import, change the date range or pull a fresh export rather than reusing the same file.

Almost always a date format problem introduced between the download and the import. The most common cause is the Intuit help article Google surfaces most often on CSV formatting, which is the global edition and recommends a day first date order. That is wrong for a US company file, and the effect is silent: the first through the twelfth of every month posts to the wrong month with no error message at all.

Excel adds two more traps. Two digit years resolve as 00 to 29 meaning 2000 to 2029 and 30 to 99 meaning 1930 to 1999, so an old export can land decades away. And Windows Excel defaults to the 1900 date system while Mac historically used 1904, a difference of four years and one day, which shows up when a file moves between machines. Converting the CSV rather than hand editing it in Excel avoids all three, because the dates are written into the .qbo as unambiguous YYYYMMDD values.

Three diagnostics narrow almost every case in a couple of minutes. A difference that divides evenly by nine means transposed digits. A difference equal to exactly twice a transaction means a sign flip. A difference that matches one transaction exactly means a row that did not convert, or one that was accepted twice.

Sign flips are the usual culprit on a bank export. QuickBooks reads a single Amount column as positive for money in and negative for money out, and it wants a minus sign rather than parentheses. Plenty of exports render negatives in parentheses, which Excel treats as text, so the values look right on screen and reconcile backwards. Credit card accounts invert the meaning again, so a TD card import that appears perfect can still be the wrong way round.