Linking Payments to QuickBooks Online Blocks Refunds on Older Charges

QuickBooks Online users who bring along an existing QuickBooks Payments account keep hitting the same wall. Once the two accounts are connected, charges processed before the connection can no longer be refunded. We walked through the accepted guidance on this connect flow. Its advice is blunt: settle everything first, because the link is one-way on that point.

Who runs into this

Most affected users signed up for card processing inside another QuickBooks product, most often the GoPayment mobile app. When the books later move to QuickBooks Online, the accounts do not link themselves. That connection is manual, and it carries strings. Users who signed up for Payments from inside Online skip the problem entirely, since their accounts connect automatically. The rule applies to any account born outside Online, not just GoPayment.

Can you refund a charge made before the connection?

No. That is the hard rule in the accepted answer. A transaction processed before the link cannot be refunded afterward, and the guidance offers no workaround for it. The reasoning is not explained, only the limit. What matters is sequence: refund every open transaction while the accounts are still separate, then connect. Anyone holding disputed charges or pending returns should treat that as the first checkpoint.

Recurring payments have to be switched off first

Subscription-style billing adds a second chore. The guidance says to sign in to Merchant Services and turn off any recurring card payments before the connection begins. Those schedules do not survive the link. Once the accounts are joined, you can rebuild them as memorized sales receipts in QuickBooks Online, which is the accepted replacement path.

The GoPayment app resets during the link

GoPayment users should expect the mobile app to come back looking factory-fresh. The connection resets app settings. It removes the in-app transaction history and wipes receipt customizations. Nothing is destroyed outright; both live on in the Merchant Service account.

The app also adopts your item list. Items and descriptions set up in GoPayment are replaced by the ones from your company file, so the two stay consistent. One more quirk: with multiple customers tracked in GoPayment, some of their identifiers may be dropped during the connection.

Connecting the accounts, in order

The steps require an admin sign-in, since the connection changes company-level settings. From there the sequence is short:

1. Open Settings, the gear icon, and choose Account and settings.
2. Select the Payments tab, then choose to connect your QuickBooks Payments account.
3. Pick the account you want to bring over.
4. Select the accounts where customer payments should deposit, then choose Connect.
5. A confirmation window appears, labeled “Changes you might not expect”. Select “Yes, I understand” to proceed.
6. Sign out of QuickBooks Online and sign back in.

That mid-connection warning window is where the caveats get acknowledged. Reading it beats clicking past it.

Does the connection change where money lands?

Partly. During setup you pick the accounts where customer payments deposit, and that choice carries through your day-to-day processing. If the first pick turns out to be wrong, the deposit account can be changed afterward rather than relinking everything. The connect screen is the moment to get it right, though, since money routing is easier to set than to untangle.

After the link goes live

Two follow-on changes land once the connection completes. Your QuickBooks Payments user IDs replace your QuickBooks Online user IDs, so the credentials that governed card processing become the ones that govern the books. Team size matters here, so check the user limits on your plan before the swap. The guidance closes with a sign-out and a fresh sign-in, after which the new user IDs take over.

The recurring payments you switched off earlier can now be rebuilt as memorized sales receipts.

The short version

Stage the connection and it behaves. Refund what is open, pause what recurs, and expect the GoPayment app to look wiped. Skip the staging and you may meet an old charge you can no longer refund, plus an app you no longer recognize. The data survives either way; the convenience does not.