QuickBooks Desktop Integration

The desktop counterpart to the QuickBooks Online integration. Vision reaches QuickBooks Desktop through the QuickBooks Web Connector — so setup and timing work differently, even though the data that syncs is the same. This screen explains the difference and generates the connector configuration.

Online vs. Desktop — how they differ

Both integrations sync the same QuickBooks objects. The difference is entirely in transport and setup: QuickBooks Online is a live cloud API Vision calls directly; QuickBooks Desktop is reached through the QuickBooks Web Connector, which runs beside the company file and polls Vision on a schedule — Vision can never initiate the connection.

Aspect	QuickBooks Online	QuickBooks Desktop
How Vision connects	Cloud REST API — direct calls	Web Connector + qbXML — runs on the QB machine
Who starts the exchange	Vision, any time	The Web Connector polls Vision on a schedule
Authentication	One-click OAuth "Connect"	Generated .qwc + password, authorized once inside QuickBooks
Timing	Real-time / on demand	Batch — on the connector’s poll interval
Where it runs	Anywhere (cloud)	The Windows machine hosting the company file
Customer setup	Click Connect	Download .qwc → import → paste password → Allow in QB
Data model	QuickBooks objects (REST)	Same objects, expressed as qbXML

Sync behavior — two independent controls

Desktop sync has a push side (records into Vision’s staging area) and a pull side (the connector sending them to QuickBooks). You control them separately.

Push to staging

Records stage only when a user clicks "Post to QB Desktop." Full control over when GL data leaves Vision.

Pull cadence (connector poll interval)

minutes

How often the Web Connector checks Vision for new records. Minimum 1 minute; 15 recommended. Shorter means fresher data, but each poll opens a QuickBooks session — more load and possible contention with users working in QuickBooks. Longer is lighter but adds latency. Vision bakes this into the generated .qwc; the customer can still adjust it in the connector.

Automatic push + a short interval is as close to hands-off as desktop allows — records queue the moment they are created and reach QuickBooks on the next poll. It is never instant like Online, because Vision cannot initiate the connection.

Pushing while QuickBooks is pulling is safe. Vision stages each document (a journal and all its lines) in a single transaction, and the connector claims a fixed batch at the start of each poll. Records created mid-poll simply stay pending and go on the next run — the in-flight batch never changes underneath the connector, so there is no partial read or double-send.

Connector configuration

Vision generates the Web Connector configuration for you — credentials, identifiers, poll schedule, and the .qwc file — so there is no server config to hand-edit and no IT ticket.

Web Connector — not configured

Generate a per-tenant connector configuration to begin.

Setup on the customer machine

Install the QuickBooks Web Connector on the machine running QuickBooks Desktop (it usually ships with QuickBooks).
Download the .qwc file below and double-click it — the Web Connector opens and imports the Vision application.
When prompted, paste the connector password shown below (Vision generated it; it is not stored in the .qwc).
In QuickBooks Desktop, approve the Vision application when the authorization prompt appears — choose "allow even when QuickBooks is not running" for unattended sync.
Leave "Auto-Run" enabled — the connector then polls on the interval below. On the first run Vision pulls your GL, customer, vendor, and item lists to seed the mapping.

About this demo: the configuration and .qwc download above are real and correctly formed. A live sync additionally needs QuickBooks Desktop and the Web Connector running on a Windows machine pointed at this endpoint — which can’t run inside this cloud demo. The point here is to show the desktop setup experience and how it differs from the one-click Online flow.