Bank Feeds and Client OTPs: Who Should Connect the Account

When you set up a bank feed in QuickBooks Online, the connection often stops at a one-time passcode sent to the account holder's registered mobile number. This is not a fault in the ledger or the software. It is the bank's own multi-factor authentication, and it is doing exactly what it was designed to do. The passcode goes to the person who owns the bank login, and that person is your client, not you.

Why there is no workaround link you can send

QuickBooks Online does not offer a secure, forwardable link that lets a third party complete a bank connection on the client's behalf. The connection is treated as part of the account holder's banking credentials, so the authentication steps, including the OTP, must be completed by the account holder. That is a deliberate security boundary, not a missing feature.

The boundary also protects you. If you asked the client to share their bank username, password, or a received passcode, you would be handling credentials that were never meant to leave the holder. Most banks' terms prohibit it, and it puts you in the middle of any later dispute about unauthorised access. Never ask for them, and decline them if offered.

What the client needs to do

The client connects the bank from their own QuickBooks Online login. In broad terms, they open the Banking or Bank transactions area, choose to connect or link an account, search for their bank, and follow the bank's own prompts, including the passcode. If their bank is not listed, QuickBooks Online lets them request that the provider be added.

Your job is to make that easy for a non-accountant. Send short written instructions in plain language, tell them roughly how long it takes, and tell them what the screen will ask for. If they get stuck, a screen-share where they type their own credentials and passcode works well: you guide, they authenticate.

What to sort out on your side

Once the feed is live, the bookkeeping work is yours again. Decide which QuickBooks account the feed maps to, and check the opening balance the connection creates. Feeds typically import a starting balance and a window of history; confirm that window against the last reconciled statement so you do not duplicate transactions already entered.

Agree with the client who reviews and matches the downloaded transactions, and how often. A feed left unmatched for weeks turns a five-minute task into a reconciliation exercise. If the client will do the matching, keep the naming and category rules simple enough for them to follow.

When the OTP problem is something else

A passcode that never arrives, or a connection that repeatedly fails after the code is entered, can point to a problem at the bank's end or with the feed provider. That is different from an ordinary setup stumble. Note what happened and when, keep the client's bank connection untouched, and take it to someone who works on QuickBooks Online connection issues specifically. The same applies if a previously working feed starts failing authentication mid-year: preserve the reconciliation history before anyone disconnects and relinks the account, because a relink can change the opening balance and duplicate history.

Handled this way, the OTP stop is a small coordination task, not a blocker. The client authenticates once, and the clean feed does the rest.