TD Bank Statement to QuickBooks: Import TD Bank Transactions to QBO

Partly. TD Bank can connect to QuickBooks Online through bank feeds, but the link has been unstable: TD temporarily suspended automated Direct Connect to QuickBooks during a security upgrade, and many users still hit connection errors. Even when the feed works, a new connection usually imports only about the last 90 days.

Sign in to TD online banking (EasyWeb or the US TD Bank site), open the account, and go to the Statements and Documents section. TD keeps up to seven years of monthly statements there as PDFs. Select the months you need and download each one. TD also offers a transaction download, but that export covers a much shorter recent window, often around 18 months or less, which is why the PDF statement is what you use for anything older.

TD Bank feeds break for a few specific reasons. TD suspended automated Direct Connect to QuickBooks during a security upgrade, so that path has been unavailable or intermittent. On top of that, expired online banking credentials, a multi-factor prompt QuickBooks cannot pass, or connection errors like OL-301 stop the sync.

When TD's direct download is working, you can pull recent activity straight into QuickBooks, but it only reaches the short window TD makes available for export. Our guide on how to download a QBO file from your bank shows where TD puts that export and what to do when the QuickBooks format is missing. This gives you the same dated, described, and totaled transactions the feed would, without depending on a connection that TD has repeatedly taken offline.

To import a file into QuickBooks Online, go to Transactions, then Bank transactions, then Upload from file, and choose the file. In QuickBooks Desktop the path is File, Utilities, Import, Web Connect Files. The file can come from three places: a .qbo or .qfx download from TD Bank online banking if it offers one, a QIF export from Quicken converted with the tool above, or a CSV you map by hand. QuickBooks Online does not accept QIF in any version, which is the step most people miss; the QIF to QuickBooks Online page walks through that conversion, and QIF to QuickBooks Desktop covers the Web Connect route.

In order of least work: a .qbo Web Connect file if it is offered, because QuickBooks reads it with no column mapping and it carries a unique ID on every transaction, so repeat imports are caught. Then .qfx or .ofx, which behave the same way. Then a QIF export from Quicken, converted to .qbo first. CSV last, because it has no transaction IDs and you map the columns yourself on every upload.

TD Bank keeps up to seven years of monthly statements as PDFs in online banking, far beyond the roughly 90-day window a fresh bank feed imports and the limited 18-month export window. For anything older than the feed window, a file import is the only way in, whether that file comes from the bank or from an old Quicken export.

Use the TD bank feed for going-forward activity when it is actually connecting, because it keeps QuickBooks current with little effort. The file import route above covers the periods a live feed will not reach.

Accuracy matters more than speed here, because a converter that drops or misreads a transaction from TD Bank costs far more time than it saves. The error usually surfaces during reconciliation, sometimes weeks later, when you are chasing a few dollars across a long register. The converter parses every transaction in the QIF, resolves the date format once so the whole file is consistent, and shows you the parsed rows in a preview before you export.

Match the file to the gap and stop it the day before the feed's earliest transaction. .qbo, .qfx and .ofx files carry a unique ID on every line, so QuickBooks can recognize a transaction it has already seen and flag the repeat. A CSV carries no such ID and will happily import a second copy of a month you already have. If duplicates do land, review them in the For review tab before accepting rather than deleting them from the register afterward.

Check whatever software was tracking the account at the time. A Quicken file holds every transaction it ever downloaded, including accounts you closed and banks you left, and it keeps them long after the bank stops serving them. Export the account from Quicken with File, File Export, QIF File, then convert that QIF to a .qbo here and import it. Microsoft Money, Moneydance, Banktivity and SEE Finance all export QIF as well, so the same route works for those.

Import one period at a time and reconcile it before loading the next. Open the account register, compare the closing balance against the last line of the matching statement, and only then move on. Working period by period keeps a mismatch contained to a few weeks of activity instead of leaving you to hunt for one wrong figure across a year. If a period will not tie out, check for a transaction that arrived twice from an overlapping file before assuming the import dropped something.