Understanding QuickBooks Sync States and Errors: A Glossary
This reference is for property managers, board members, and staff using URBI's QuickBooks Online integration (a PREMIUM feature). It's a lookup, not a how-to: use it to quickly check what a badge,...
Last updated
This reference is for property managers, board members, and staff using URBI's QuickBooks Online integration (a PREMIUM feature). It's a lookup, not a how-to: use it to quickly check what a badge, label, or status word means when you see it in the sync console, then jump to one of the linked how-to articles if you need the fix. You don't need to read it start to finish.
Section 1: Connection status badges
These appear on the QuickBooks drawer's Connection tab and describe the health of the link between URBI and QuickBooks itself, not any individual transaction.
| Badge | What it means | Action needed? |
|---|---|---|
| Active | The connection is healthy and syncing normally. | None. |
| Renewing soon | QuickBooks' authorization for this connection is due to expire in roughly the next two weeks. URBI renews it automatically in the background. | None, this happens on its own. |
| Reconnect needed | QuickBooks rejected URBI's automatic renewal outright, most commonly because access was revoked or the connection was cancelled on the QuickBooks side. Nothing syncs to QuickBooks until the connection is reconnected. | Yes. See Reconnecting a Broken QuickBooks Connection. |
Note: If a connection could technically show more than one of these at once, Reconnect needed always takes priority and is the one displayed.
Section 2: Failed Transactions badges and terms
The Failed Transactions section lists individual records (invoices, expenses/bills, payments, journal entries) that URBI tried to sync to QuickBooks and didn't succeed. Each row shows the record type, the operation attempted, a badge, an error message when relevant, and when it was queued.
"Failed" badge
A sync attempt for this item did not succeed. The error message shown on the row (in red) explains why. A Retry button is available on the row so you can queue another attempt, unless the connection itself is currently broken (see Section 1).
"Voided" badge
The URBI record this item was trying to push (the invoice, expense, or journal entry) has since been voided inside URBI. There's nothing left to sync, so no Retry button is shown for it.
Note: There's one exception. If the failed item's own operation is the attempt to notify QuickBooks that something was voided, it keeps showing Failed with a Retry button instead of Voided, because that notification still needs to go through.
"Attempts: N"
A running count of how many times URBI has tried to sync this specific item. This only appears once an item has been tried more than once, so you won't see "Attempts: 1" on a first-time failure.
The error message
The red text on a failed row is the actual message returned by QuickBooks (or, in some cases, by URBI's own validation before it even reached QuickBooks). Read it as a literal explanation of what went wrong, not a generic label.
If the same error keeps appearing after you retry, that's a signal the issue usually needs a person to look at rather than one that will resolve itself with more retries alone; common examples are a missing account mapping, a QuickBooks-side validation rule being tripped, or a duplicate record. For the retry workflow itself, see Using the Sync Console and Retrying Failed Transactions.
Section 3: Attention (drift) badges and terms
The Attention section surfaces "drift": a value that no longer matches between URBI and QuickBooks because it changed on the QuickBooks side sometime after URBI originally sent it. URBI detects drift automatically with a periodic background check; it's never something staff create directly.
Restorable drift vs. informational-only drift
There are two broad categories of drift, and they behave differently:
- Restorable drift: a QuickBooks-side edit to a value that URBI originally authored and pushed. This is the one kind of drift with an action button, Re-push to restore, which sends URBI's original value back to QuickBooks. Full detail in Handling Drift: Re-Push to Restore.
- Informational-only drift: everything else. This covers several other situations, such as items that were created directly in QuickBooks and don't match anything in URBI, bank-reconciliation conflicts, items pulled in from QuickBooks that can't be matched to a URBI record, coverage gaps, and a handful of bill-payment-specific cases. These show up so staff know something diverged, but there's no button to click; if action is needed, it happens manually, outside the sync console.
Note: Don't expect a Re-push option on every Attention row. If a row doesn't have one, that's expected: it's informational-only by design, not a bug.
"Digested" badge
Appears once a drift item has already been included in an earlier summary. The exact timing or cadence of when that happens isn't precisely fixed, so treat this simply as "already surfaced previously" rather than assuming a specific schedule.
The field diff
Each Attention row shows exactly what changed, field by field: the field name, the old ("before") value, an arrow, and the new ("after") value. This lets you see the full change without needing to open QuickBooks yourself to compare.
Section 4: Sync History log statuses
The Sync History tab is the raw, unfiltered log of every sync operation URBI has attempted, separate from the curated Failed Transactions and Attention sections. Each entry shows the operation name, the record type, a timestamp, and how many records were involved. You can filter the log by status:
| Status | What it means |
|---|---|
| Success | The operation completed and is reflected in QuickBooks. |
| Error | The operation failed outright. The raw QuickBooks or URBI validation error is shown in red on that entry. |
| Pending | The operation is still queued or in progress; it hasn't resolved either way yet. |
Section 5: Quick glossary table
| Term | Where you see it | Plain-English meaning |
|---|---|---|
| Active | Connection tab, health badge | The connection is healthy and syncing normally. |
| Renewing soon | Connection tab, health badge | QuickBooks authorization expires in about two weeks; renews automatically. |
| Reconnect needed | Connection tab, health badge | Automatic renewal was rejected by QuickBooks; nothing syncs until reconnected. |
| Failed | Failed Transactions, row badge | A sync attempt for this item didn't succeed; a Retry button is available. |
| Voided | Failed Transactions, row badge | The URBI record this item was pushing has since been voided; nothing left to retry. |
| Attempts | Failed Transactions, row label | How many times URBI has tried to sync this specific item (shown once it's more than one). |
| Digested | Attention, row badge | This drift item was already included in an earlier summary. |
| Attention | Section name | The list of items where a value diverged between URBI and QuickBooks (drift). |
| Drift | Concept, used throughout Attention | A value URBI sent that was later changed on the QuickBooks side, or otherwise diverged. |
| Re-push to restore | Attention, row action | Sends URBI's original value back to QuickBooks, overwriting the QuickBooks-side change. Only available for restorable drift. |
| Retry | Failed Transactions, row action | Queues one more sync attempt for that single item. |
| Retry all | Failed Transactions, section action | Queues another sync attempt for every currently failed item at once. |
| Sync Now | Connection tab, action | An on-demand "check for anything new to sync" trigger, separate from retrying specific failed items. |
| Backfill | Post-connect setup | The one-time initial import of a property's existing QuickBooks data (accounts, existing balances, and so on) that runs when first connecting. |
| Account mapping | Its own section in the console | Matching URBI's chart of accounts to the corresponding QuickBooks accounts, available to revisit at any time. |