Why do QuickBooks Desktop syncs work differently than other platforms?

Last updated: April 15, 2026

Overview

QuickBooks Desktop (QBD) syncs function differently than other platforms Rutter supports due to the unique nature of the QuickBooks Web Connector.

How most platforms work

For cloud-based platforms:

  • API requests from Rutter to the platform may be asynchronous, but are processed immediately

  • Incremental syncs to pull data from the platform into Rutter happen on a regular scheduled interval

How QuickBooks Desktop works

QuickBooks Desktop requires the Web Connector application to facilitate communication between Rutter and QBD. All data exchange, in both directions, can only occur when the Web Connector is running.

This means:

  • API requests from Rutter to QBD are queued and only processed during the next Web Connector run

  • Incremental syncs to pull data from QBD into Rutter only happen when the Web Connector runs (either manually or via the configured auto-run schedule)

  • The end user must initiate the sync by running the Web Connector, Rutter cannot trigger it remotely

  • Rutter's incremental sync endpoint does not work for QBD connections

  • Backfill requests will be queued and processed during the next Web Connector session

What this means for sync timing

A single Web Connector session processes:

  1. All queued write requests from Rutter to QBD (creates, updates, deletes)

  2. All new or updated data from QBD since the last sync

This bi-directional processing can cause syncs to take longer than expected, especially if there are many queued operations or significant changes in QuickBooks Desktop since the last run.

For best performance, ensure the Web Connector is configured to run automatically at regular intervals.