Truist Statement to QuickBooks: Import Truist Transactions to QBO

Yes, but the connection is not always reliable. Truist can link to QuickBooks Online through bank feeds and to QuickBooks Desktop through Direct Connect, yet many users hit periods where transactions stop loading or the account will not connect at all. A new connection also imports only the recent window, usually about the last 90 days.

In QuickBooks Online, go to Transactions, Bank transactions, then Link account, search for Truist, and enter your online banking credentials. For QuickBooks Desktop Direct Connect, you first enroll your Truist accounts for Direct Connect in Truist online banking, then set up the bank feed in Desktop. Truist required Direct Connect re-enrollment after the SunTrust conversion, so if an old SunTrust link stopped working, re-enrolling the account is usually the fix before the feed will sync again.

Truist feeds break for a handful of reasons. Leftover SunTrust connections that were never re-enrolled for Truist Direct Connect simply stop pulling data. Beyond that, expired credentials, a security prompt QuickBooks cannot answer, or a bank-side outage halts the sync, and Truist has had several stretches where transactions would not load for many users at once. Truist also offers a manual export for recent activity, and our guide to downloading a QBO file from your bank shows where to find it.

When SunTrust became Truist, the old SunTrust bank feed was retired and accounts had to be reconnected under Truist. Many QuickBooks users saw the SunTrust connection stop downloading, duplicate transactions appear during the switch, or the account fail to find a match under the new name.

Sign in to Truist online banking, open the account, and go to the Statements and Documents section. Select the months you need and download each one as a PDF. Truist keeps your monthly statements there for several years, far longer than the roughly 90-day window a fresh bank feed imports.

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 Truist 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.

Use the Truist 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 Truist 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.