How to Import Relay Transactions into QuickBooks (Including Desktop)

Short answer: If you use QuickBooks Online, connect Relay's bank feed and it will sync settled transactions automatically every few hours. If you use QuickBooks Desktop, there is no integration to connect, because Relay states plainly that it does not connect with QuickBooks Desktop at this time. In that case, and for any period from before you connected the feed, download the Relay statement, convert it to a .QBO file, and import it through Upload from file or Web Connect Files.

Relay is built for bookkeepers, and it shows. The QuickBooks Online sync is genuinely reliable, and Relay is confident enough to say the sync does not break and does not skip or duplicate transactions. So this article is not a list of complaints about a broken feed. It is about the two places the feed does not go, and what you do instead when you land in one of them.

Does Relay integrate with QuickBooks?

Yes, with QuickBooks Online. Relay syncs your transaction data to QuickBooks Online through a direct bank feed integration, and it pushes settled transactions across automatically every few hours. Two details are worth knowing before you rely on it. Only checking and savings accounts sync through bank feeds, not card accounts. And you need to be an Administrator or Manager in Relay to set the connection up at all, which is a common stumbling block for a bookkeeper who was given view-only access.

Does Relay connect with QuickBooks Desktop?

No. Relay's help center answers this in a single sentence: it does not connect with QuickBooks Desktop at this time. There is no app to install, no connector to enable, and no setting buried in a menu. If your firm runs QuickBooks Desktop Pro, Premier, Enterprise, or Accountant, the feed is simply not an option, and no amount of troubleshooting will produce one.

This affects more people than it sounds like it should. A large share of established US bookkeeping practices still run Desktop, and Intuit's modern replacement for Direct Connect, Express Web Connect, does not serve Desktop either. So for those firms, importing a file by hand is not a fallback. It is the supported path, and it is the only one.

Method 1: the QuickBooks Online bank feed

If you are on QuickBooks Online and you only need activity going forward, use the feed. It is the right tool.

1. In Relay, make sure you are an Administrator or Manager on the account.
2. Open the QuickBooks integration panel in Relay and connect to QuickBooks Online.
3. Create the matching bank account in your QuickBooks chart of accounts, so Relay transactions land somewhere sensible and reconcile properly.
4. Map each Relay checking or savings account to its QuickBooks counterpart.

One warning that Relay itself raises, and that is easy to shrug off until it bites. If you connect a client's Relay account to QuickBooks Online using your own login credentials, that client will be able to see the other bank feeds attached to those credentials. Have the client connect using their own credentials instead. It costs five minutes and prevents a genuinely uncomfortable conversation with a different client later.

Method 2: convert the statement to a QBO file

This is what you do for QuickBooks Desktop, and for any month the feed never saw. Relay lets you download statements as a PDF, a CSV, or an OFX, and keeps them available for as long as your account is open, which is usually far further back than any feed will reach.

1. In Relay, open Accounts, then Statements. Pick the account and the month, and download the PDF.
2. Upload it to the Relay statement to QBO converter and choose QBO as the output format.
3. In QuickBooks Online, go to Transactions, then Bank transactions, and choose Upload from file under the Link account dropdown. In QuickBooks Desktop, use File, Utilities, Import, Web Connect Files.
4. Map the file to the right Relay account and review the transactions in the For review tab.

Why can't I just import Relay's OFX file?

Because an OFX and a QBO are not the same file, even though they are closely related and the names suggest otherwise. QBO is Intuit's own flavor of the OFX standard, and a Web Connect file carries an Intuit bank identifier that tells QuickBooks which financial institution produced the data. A plain OFX has no such identifier. QuickBooks Desktop will typically reject it outright or refuse to map it to an account.

Relay knows the shape of this problem. In its own documentation about other platforms, it tells Quicken users to download their statements and convert them to the required format before uploading. That is exactly the pattern here, aimed at QuickBooks rather than Quicken.

Why does QuickBooks only show 90 days of Relay transactions?

Because of a QuickBooks rule, not a Relay one. Intuit's bank-feed guidance states that transactions older than 90 days cannot be downloaded and have to be added to QuickBooks manually. It does not matter how much history Relay holds, and Relay holds plenty. The connection itself is not permitted to reach back further than three months.

This is why a mid-year client handoff almost always needs a file import. You take on the client in August, you connect the feed, you get a summer's worth of data, and January through May sits in the statement archive with no way to walk into QuickBooks on its own. Converting those statements is the walk.

Reconciling a Profit First setup

Relay is the official platform for Profit First Professionals, and most plans allow up to 20 checking accounts, with the Scale plan going to 50. That is the whole point of the method, and it also means one business can carry ten or more registers in QuickBooks.

Keep the separation intact all the way through the import. One Relay account, one statement, one QBO file, one QuickBooks account. QuickBooks maps a single Web Connect file to a single account, so merging your income, profit, owner pay, and tax allocation accounts into one import is the fastest way to turn a tidy Profit First structure into a day of untangling. While you are in there, remember that Relay card spend does not arrive as its own feed, because only checking and savings accounts sync. Card activity shows up inside the checking account it draws from.

How do I avoid duplicate transactions?

Load history behind the feed, never on top of it. Open the register in QuickBooks, find the oldest transaction the bank feed brought in, and make sure your converted file ends the day before that date. QuickBooks does attempt duplicate detection on a Web Connect import, but it matches on amount, date, and reference, so a description that reads a little differently or a posting date that shifted by a day will slide straight through and land twice.

One more Relay quirk that causes phantom problems: renaming an account in Relay does not rename it in QuickBooks. If the two drift apart, you will eventually map a file to the wrong register. Fix the names in both systems before you import anything.

A note on what Relay actually is

Relay is a financial technology company, not an FDIC-insured bank. Banking services and FDIC insurance are provided by Thread Bank, Member FDIC, with customers insured up to $3,000,000 per business through an insured cash sweep program. For bookkeeping purposes none of this changes anything: the statements are ordinary account statements and they reconcile like any other. It matters only when a lender or an auditor asks who holds the deposits.

Putting it together

Use the feed for the present and a converted file for the past. If you are on QuickBooks Online, connect Relay and let it run. If you are on QuickBooks Desktop, skip the feed entirely, because it does not exist for you, and build your workflow around monthly statement conversion instead. Either way, the periods before the connection went live come in from the statement archive, one QBO file per account.

Once the transactions are in and categorized, the rest of the month-end close gets easier: you can match receipts to card spend with proper expense management software, and reconcile each allocation account against its own statement. If you would rather work in a spreadsheet than in QuickBooks, the Relay statement to Excel converter gives you the same data as XLSX or CSV. And if the 90-day wall is what sent you looking in the first place, why QuickBooks only imports 90 days of transactions explains exactly what each type of connection can and cannot reach.