Reconnecting a Broken QuickBooks Connection

A guide for property managers, board members, and accounting staff on a PREMIUM property to understanding QuickBooks connection health, what breaks a connection, and how to fix it.

The three connection health states

Every QuickBooks Online connection shows a Status badge on the Connection tab. There are three states:

Note: "Reconnect needed" always takes priority over the other two states. If a connection is broken, you will see "Reconnect needed," not "Renewing soon" or "Active," even if a renewal was also due around the same time.

What "Renewing soon" means (and why you don't need to do anything)

URBI automatically renews its authorization with QuickBooks behind the scenes, roughly every hour, for as long as the connection stays healthy. "Renewing soon" simply means that renewal is coming up shortly. It is purely informational. URBI handles the renewal itself, and the badge will quietly return to Active once it happens. You do not need to click anything or take any action when you see this badge.

What actually causes "Reconnect needed"

This is the part worth understanding, because it is easy to assume the worst when you see a red banner.

URBI's authorization with QuickBooks needs to be automatically renewed roughly every hour to keep working. Most of the time this renewal happens invisibly and nothing changes on your end. "Reconnect needed" only appears when one of those automatic renewal attempts is flatly rejected by QuickBooks, for example because access was revoked, or the authorization was cancelled on the QuickBooks side. It is a hard rejection, not a maybe.

Note: A single network hiccup or a brief QuickBooks outage does not cause this state. Temporary or technical failures are retried automatically on the next renewal pass about an hour later, and the connection stays marked Active the whole time. You will only ever see "Reconnect needed" after a definitive rejection from QuickBooks itself, not from an ordinary blip.

Once a connection is marked "Reconnect needed," it stays that way until someone reconnects it, it does not clear itself on its own.

What stops syncing when a connection is broken

While a connection shows "Reconnect needed":

• Nothing pushes to QuickBooks. New invoices, expenses, and payments queue up but do not go out.
• Retrying failed transactions is disabled. See Using the Sync Console and Retrying Failed Transactions for what that looks like from the Sync History tab.
• Restoring drift items is disabled for the same reason. See Handling Drift: Re-Push to Restore.

Both of those actions stay grayed out with a reconnect hint until the connection is fixed, since neither can succeed while there is nothing on the other end to receive the push.

The weekly reminder

Once a connection breaks, URBI does not let it fail silently forever. Every Monday, URBI checks for properties with a broken connection and sends a reminder, an email plus an in-app notification, to the staff responsible for that property. This follows URBI's standard escalation order: it goes first to anyone specifically assigned to this kind of alert, and if no one is assigned, it goes up through the property's admin and board management chain.

The reminder email states how many days the connection has been broken, explains plainly that new invoices, expenses, and payments are not syncing, and includes a Reconnect QuickBooks link that takes you directly back to the property's settings.

Note: These weekly reminders stop after about 8 weeks of a connection staying broken (roughly 8 reminders total). Silence after that point does not mean the connection fixed itself. URBI simply stops nagging about it, the connection is still broken and still not syncing. Staff should still check the Status badge periodically and reconnect if needed, rather than assuming no news is good news. If a connection breaks again later after being fixed, the weekly reminder cycle and the 8-week cap both start over fresh.

Reconnecting is what stops the reminders. There is no separate "dismiss" action, once the connection is fixed, the following Monday's check will no longer find it broken and simply will not send another one.

How to reconnect

1. Go to property Settings.
2. Open the QuickBooks Online panel.
3. If the connection is broken, you'll see a red banner with a Reconnect button. Click it. (If you are connecting for the first time instead, click Connect to QuickBooks instead.)
4. A QuickBooks sign-in popup window opens.
5. Sign in to QuickBooks and approve access.

Note: If nothing appears to happen when you click Reconnect, check that your browser did not block the popup window. Allowing popups for the site is a reasonable first thing to try, though a blocked popup is not the only possible reason a reconnect might not visibly respond.

What happens automatically right after you reconnect

Once you successfully sign in and approve access, URBI does not just resume syncing new activity going forward. It automatically catches up on everything that was missed during the entire outage, in both directions:

1. Anything URBI had queued to send to QuickBooks while the connection was broken (pending invoices, expenses, payments, and entries) gets sent now.
2. Anything that changed on the QuickBooks side while the connection was broken gets checked. If something relevant happened there while you were disconnected, it will show up as a new item in the Attention section for your review.

You do not need to manually trigger a resync or click anything further after reconnecting. This catch-up happens automatically in the background.

Reconnect after an outage vs. a deliberate Disconnect

These are not the same thing, and the difference matters:

In short: reconnecting after an unplanned outage is a quick fix that drops you right back where you were. Choosing to disconnect is a bigger action than it might sound, because reconnecting afterward is not a one-click return to where you left off, you walk through setup again.

How to disconnect

If you want to deliberately stop syncing to QuickBooks:

1. Go to property Settings and open the QuickBooks Online panel.
2. Click the Connection tab.
3. Click Disconnect.
4. A confirmation dialog appears, asking you to confirm before anything happens.

What disconnecting does and does not do:

• It stops all future syncing to QuickBooks going forward.
• It does not delete anything already synced. Entries already sent to QuickBooks are unaffected and stay exactly as they are.
• It does not delete your sync history.
• It does not delete failed-transaction records.
• It does not delete drift or Attention records.

All of your historical data stays intact and viewable inside URBI even after you disconnect. Nothing already sent to QuickBooks is undone.

FAQ

Will I lose data if I disconnect? No. Disconnecting only stops future syncing. Everything already sent to QuickBooks stays there, and all of your sync history, failed-transaction records, and drift records stay visible inside URBI.

What if I reconnect the wrong QuickBooks company by mistake? When you reconnect, QuickBooks itself walks you through its own sign-in and company selection during the popup, so double-check the company name shown before approving. Afterward, confirm the company details shown on the Connection tab match the company you intended to connect. If you connected the wrong one, disconnect and reconnect again, selecting the correct company this time.

Do I need to redo my account mapping every time the connection breaks and I reconnect? No. A repair-reconnect (fixing a broken "Reconnect needed" connection) drops you straight back into the normal sync console, your existing account mapping stays in place. Only a deliberate Disconnect resets the setup wizard, requiring you to review account mapping again the next time you connect.

What is "Renewing soon" and do I need to do anything? No action needed. It just means URBI's authorization with QuickBooks is due for its regular automatic refresh soon. This happens on its own, and the badge returns to Active once it completes.

Related articles

• Using the Sync Console and Retrying Failed Transactions
• Handling Drift: Re-Push to Restore
• Understanding QBO Sync States and Errors