Your company file, reachable from the route.
A small connector agent runs on the machine that holds the company file, keeps the QuickBooks session open and calls out to us. Thirteen record types cross — including sales orders, price levels and field reps, which QuickBooks Online has no object for at all.
- No inbound port
- 13 record types
- Pro, Premier, Enterprise
How a desktop company file is reached at all
QuickBooks Desktop has no public API of its own. This is the part every other answer glosses over.
Everything that crosses, and which way it goes
The actual sync matrix — entity for entity, arrow for arrow.
The details that decide whether you trust it
How the awkward cases behave, which is what you actually need to know.
You decide what syncs, one record type at a time
Sync rules is the screen where a direction is chosen per record — and it can only offer what QuickBooks Desktop can actually do, because the list comes from the connector itself.
The other integrations
Same connector framework, different ledger on the end of it.
Frequently asked questions
Do we have to open a port in our firewall?
Does the QuickBooks machine have to stay on?
Which editions are supported?
What happens if a rep edits a customer QuickBooks owns?
Does it sync our price levels?
Can it handle sales orders?
See it against your own company file.
The agent installs in minutes on a copy of your file. We would rather show you your own data crossing than talk about someone else’s.