QBO Sync — Duplicate Transaction Detection & Sync Anyway

QBO Sync — Duplicate Transaction Detection & Sync Anyway

Notes
Overview
LedgerSync automatically detects when a bank transaction about to be synced to QuickBooks may already exist in QBO as a manually entered entry. Instead of creating a duplicate, it holds the transaction back and flags it visibly so you can decide what to do. This prevents duplicate entries in QBO without requiring you to compare lists manually.

How Duplicate Detection Works

When LedgerSync attempts to sync a categorized transaction to QuickBooks, it checks whether QBO already contains an entry with a matching combination of:
  • Transaction date
  • Amount
  • Check number (if applicable)
  • Transaction description (compared intelligently, not exact-match)
If a likely duplicate is detected, the transaction is held back (not synced) and flagged in the Sync Status tab instead of being pushed to QBO.

What You See When a Duplicate Is Detected

  • The transaction row is highlighted in amber in the Rules Engine / Categorized view
  • A "Skipped" status appears in the Sync Status tab for that transaction
  • The Sync Status tab shows a Skipped count alongside the Synced and Failed counts so you can quickly see how many were held back

How to Resolve a Skipped (Duplicate-Flagged) Transaction

When you see a Skipped transaction, you have two options:

Option 1 — Confirm it’s a duplicate (do nothing): If the transaction genuinely already exists in QBO, leave it as Skipped. The transaction remains in LedgerSync’s history but is not pushed to QBO again.

Option 2 — Force-push it ("Sync Anyway"): If the transaction was incorrectly flagged as a duplicate (the QBO entry is for something else), click Sync Anyway on that transaction. LedgerSync will push it to QBO regardless of the duplicate signal.

When Does This Happen Most Often?

  • A bank transaction failed to sync, and the accountant manually entered it in QBO as a workaround
  • LedgerSync later re-pulls the same bank transaction and tries to push it again
  • The duplicate detection catches the second attempt and holds it, avoiding a double entry

Need Help?

Contact LedgerSync Support at support@ledgersync.com

Related Articles: