Relay to QuickBooks: Convert Your Relay CSV to a .qbo File

Short answer: Relay Financial has a native QuickBooks Online bank feed, but it does not connect to QuickBooks Desktop and it only pushes settled transactions. To get Relay activity into Desktop, or to fill a gap the feed missed, export the account as a CSV, convert it to a QuickBooks Web Connect (.qbo) file, and import it. Desktop reads it through File, Utilities, Import, Web Connect Files, and QuickBooks Online accepts the same file as an upload.

Relay has become the default banking platform for a lot of US firms running Profit First, and for good reason. One Relay account can hold up to 20 individual checking accounts, so the allocation you plan on a spreadsheet actually happens in the bank. Every one of those accounts turns into its own bank feed in QuickBooks Online, which is a genuinely good design for a bookkeeper. The trouble starts at the edges of that design.

Does Relay sync with QuickBooks?

Relay syncs with QuickBooks Online through a direct bank feed integration that runs every few hours. Relay's support documentation is explicit that it does not connect with QuickBooks Desktop at this time, and Relay does not offer OFX Direct Connect either. So Online users get a feed, and Desktop users get nothing automatic at all. For Desktop, the only supported route is a Web Connect file.

Why are my Relay transactions missing in QuickBooks?

Start with the two known causes before you go hunting. Relay pushes only settled transactions to the QuickBooks bank feed, so anything still pending simply is not there yet and will arrive when it clears. Separately, users on the QuickBooks community have reported the connection looking healthy on the Relay side while no transactions ever land in QuickBooks. If pressing sync produces nothing, stop retrying and import the period as a file.

Why can't I just upload the Relay CSV to QuickBooks Desktop?

Because Desktop does not read CSV bank transactions. The Bank Feeds Center accepts Web Connect files only, which means .qbo, .qfx, and .ofx. QuickBooks Online will take a CSV if you map the columns by hand, but Desktop will not take it under any configuration. This trips up a lot of people who assume a CSV is a universal format. Inside QuickBooks Desktop, the universal format for bank data is .qbo.

How to convert a Relay CSV to a .qbo file

The whole job takes about a minute per account.

1. Export one CSV per Relay checking account. Sign in to Relay, open the account, set your date range, and download the transactions as a CSV. Do not merge your buckets into one file. Each Relay account should map to its own QuickBooks register, and mixing them destroys the allocation you set Relay up to enforce in the first place.

2. Check where QuickBooks left off. Open the matching QuickBooks register and note the last transaction date already posted. Set your Relay export to start the day after that. This one habit prevents almost every duplicate-import headache.

3. Convert the CSV. Upload the file to the Relay CSV to QBO converter. It reads the date, description, and amount columns, normalizes the dates into the format QuickBooks expects, strips dollar signs and thousands separators, and signs deposits and withdrawals correctly. Check the parsed total against your Relay balance before you download the .qbo.

4. Import the .qbo. In QuickBooks Desktop, go to File, then Utilities, then Import, then Web Connect Files, pick the file, and choose the matching Relay register. In QuickBooks Online, open Transactions, then Bank transactions, select the account, and upload the file. Either way the transactions appear for review before anything posts.

How do I set up Relay's 20 checking accounts in QuickBooks?

Mirror the structure exactly. Create one QuickBooks bank account for every Relay checking account you actually use, name them the same way, and keep them separate forever. A typical Profit First layout runs an operating account, an owner pay account, a tax account, and a profit account, sometimes with a payroll bucket alongside. The whole value of the method is that you can look at a register and know that money is already spoken for. Collapsing the buckets into one QuickBooks account for convenience gives that away, and you will not get it back without a painful re-split later.

When you import, do it account by account: one Relay CSV becomes one .qbo becomes one register. Reconcile each against its own Relay statement at month end. It sounds like more work than a single import, and it is, by about two minutes per account.

How do I import historical Relay transactions?

Bank feeds only ever look forward from the day you connect them, so anything from before that has to arrive as a file. Export the older date range from each Relay account, convert each CSV, and import each .qbo into its register. If you are onboarding a client mid-year and need to catch up six months across five buckets, that is 5 files, not 30, because a Web Connect import is not limited the way a raw CSV upload to QuickBooks Online is.

If the client also hands you PDF statements from a prior bank rather than clean exports, deal with that first: you can turn the PDF statements into a spreadsheet and then bring the resulting file through the same conversion path.

Will I get duplicates if the feed comes back on?

QuickBooks matches incoming Web Connect transactions against what is already in the register and flags likely duplicates for review rather than posting them blindly, so a careful import is fairly safe. Still, the discipline that matters is the date range. Import files only for the periods the feed never covered. If the Relay feed for an account is healthy from March onward, your converted files should stop at the end of February for that account. Overlapping ranges are what create the mess, not the file format.

Is Relay a bank?

Relay is a fintech platform rather than a chartered bank, with banking services provided by a partner bank. That is not a knock on it, but it explains the QuickBooks behavior. Fintechs almost never offer OFX Direct Connect, the old protocol QuickBooks Desktop uses to pull transactions automatically, because standing that up means running OFX infrastructure with the bank. So the fintechs build a modern API integration with QuickBooks Online and leave Desktop users to import files. Mercury, Brex, and Ramp all land in the same place, for the same structural reason.

The practical setup

If you are on QuickBooks Online and the Relay feed is working, use it, and keep converted files as your tool for history and for the accounts the feed skips. If you are on QuickBooks Desktop, files are the whole workflow, so build a monthly habit: export each Relay account, convert, import, reconcile. It is the same three minutes every month, and the register that comes out of it is a clean one.

More on this: the Relay CSV to QBO converter handles the file, the CSV to QuickBooks Desktop guide covers the Web Connect import in detail, and if you carry several clients on fintech banking, the CSV to QBO converter for accountants is built for that volume. Same pattern, different platform: Mercury to QuickBooks.