StatusPairingsReconciliationNeeds Auth

QBO Connection Reconciliation

Every Qount client that does not cleanly tie to a QBO company file

Loading...

Pinned = this Qount client is this QBO file; we lock the Realm ID so renames never break the match again. Rolls up into parent = books live inside another entity's QBO file; shows as "covered by parent" and leaves the connection chase list. Not on QBO = R365 or manual books, should not carry the Tech:QBO label. Dropped client = terminated, Viktor revokes and deletes the token. Needs connection = genuinely missing, keep chasing. The two dropdowns are different lists: parent lists every Qount client (connected or not), while the QBO file list only has files whose token is authorized in Viktor - so a client can be missing from the file list and still show up as a parent option on other rows. Rows marked Two QBO files on one client mean one client has two authorized QBO files: pick the live one and Viktor revokes the other.
0
Exceptions
0
Decided
0
Remaining
0
Unsaved
Signed in as ...
# Client / QBO file Viktor's read Decision Parent / QBO file Note
Loading...