When your property is on the Premium accounting plan and connected to QuickBooks Online, URBI shows a small colored badge, the "sync pill," next to accounting transactions. At a glance it tells you...
Last updated
When your property is on the Premium accounting plan and connected to QuickBooks Online, URBI shows a small colored badge, the "sync pill," next to accounting transactions. At a glance it tells you whether a given transaction has made it into QuickBooks, is still on its way, ran into a problem, or was pulled in from QuickBooks rather than pushed out. This guide explains every state the pill can show and exactly what each one means.
Who this is for: Property managers, board members, and staff on the Premium accounting plan whose property has an active QuickBooks Online connection.
The sync pill shows up on individual accounting transactions, general-ledger (GL) rows and the detail drawers for journal entries, expenses, and invoices, so you can see the QuickBooks status of that specific transaction right where you are looking at it.
The pill is deliberately scoped to properties that use QuickBooks. If your property is not on Premium, or is not connected to QuickBooks, the pill does not render at all. This is intentional, so properties that do not use QuickBooks are never cluttered with a badge that would not apply to them. In other words, seeing the pill at all is itself a signal: it means this property is Premium and connected.
The pill can show one of six states. Each has its own label, color, and icon so they are easy to tell apart at a glance.
The transaction has been successfully written to QuickBooks, and URBI has confirmed the two records are linked. This is the "all good" state. Shown in a success (green) tone with a checkmark.
The transaction is queued or in progress, on its way to QuickBooks but not confirmed there yet. This is normal for the short window right after you post something. It typically clears to Synced within about a minute. Shown in an informational (blue) tone with a clock icon.
URBI tried to send this transaction to QuickBooks and QuickBooks rejected it, or QuickBooks could not be reached. The transaction is safe in URBI; it just has not landed in QuickBooks yet. This state usually resolves on its own after a retry (for example once you reconnect QuickBooks), but a persistent failure is worth investigating in the sync console. Shown in a danger (red) tone with a warning triangle.
URBI could not send this transaction because one or more of the GL accounts it touches has no matching QuickBooks account set up yet. QuickBooks needs to know which of its accounts corresponds to your URBI account before it can accept the entry. Once the account mapping is completed, the item can sync. Shown in a warning (amber) tone with an alert icon.
This transaction was pulled in from QuickBooks, not pushed out by URBI, and URBI is intentionally not sending it back. This is the visible face of the "echo suppression" design described in the two-way-sync guide: a payment recorded in QuickBooks is brought into URBI for your books, and URBI marks it so the sync queue skips re-pushing it (which would double-book it). Shown in a neutral (grey) tone with a download-from-cloud icon.
This state is distinct from "Synced" on purpose. "Synced" means URBI authored it and sent it to QuickBooks. "From QuickBooks" means QuickBooks authored it and URBI received it. Both are healthy, but they are different directions, so URBI gives them different labels, colors, and icons so you never confuse the two. A "From QuickBooks" item is not an error and needs no action.
There is no QuickBooks link for this transaction. This appears when a transaction has no sync record yet, or when it was deliberately skipped, or in any case where URBI simply has nothing to report about QuickBooks for that row. Shown in a muted (light grey) tone with a minus-circle icon. It means "QuickBooks is not tracking this one," which for some transaction types is perfectly expected.
The pill reads a single per-transaction sync status that URBI maintains for each transaction that participates in QuickBooks sync. It resolves the Premium-and-connected gate once for the whole page or drawer you are viewing (not once per row), then looks up the current status for the transactions on screen in one batched read. The mapping is straightforward:
You post a journal entry in URBI that moves money between two accounts.
Immediately after posting, the pill reads Syncing. URBI has queued the entry for QuickBooks.
About a minute later, the background worker sends it, QuickBooks accepts it, and the pill flips to Synced. You are done, no action needed.
Now suppose one of the two accounts in that entry has never been mapped to a QuickBooks account. In that case the pill would instead read Needs mapping, telling you the entry cannot go to QuickBooks until you finish the account mapping. Once mapped, it can proceed to Synced.
Separately, your bookkeeper records a resident's payment directly in QuickBooks. URBI pulls it in and applies it to the invoice. On that payment, the pill reads From QuickBooks, telling you it came from QuickBooks and URBI is correctly not pushing it back.
Why do some of my transactions have no pill at all? Either your property is not on Premium, or it is not connected to QuickBooks. The pill only appears for Premium-and-connected properties. Within such a property, a transaction with no QuickBooks status shows the muted Not synced state rather than no pill.
What is the difference between "Synced" and "From QuickBooks"? Direction. Synced means URBI created the transaction and successfully pushed it to QuickBooks. From QuickBooks means QuickBooks created it (a payment) and URBI pulled it in, and URBI is intentionally not sending it back. Both are healthy states.
My entry says "Needs mapping." What do I do? It uses a GL account that has no QuickBooks account mapped to it. Finish the QuickBooks account mapping for that account, and the entry can then sync.
A transaction says "Sync failed." Did I lose it? No. The transaction is fully intact in URBI. Only the copy to QuickBooks failed. It can be retried, and reconnecting QuickBooks often clears authorization-related failures automatically.
Does the pill update live on its own? It reflects the status as of when you opened or refreshed the view. Refresh the row or drawer to pull the latest status after you have made a change.