QuickBooks Salesforce Integration: Which Route Fits, and What Each One Misses
Neither Intuit nor Salesforce ships a sync you can just switch on. You choose between an AppExchange connector, a Zapier-style tool, or a custom integration against both APIs. The right one depends on a narrow question: what does each team need to see from the other system, and how fast?
An AppExchange connector. Several exist, Breadwinner and DBSync among them. They install inside Salesforce and cover customers, invoices and usually payment status. Pick this first if your deals use standard products and pricing.
Zapier or another low-code tool. Good for one trigger and one action, such as a won opportunity creating a QuickBooks estimate. It gets fragile once you need line items, error handling or a sync that runs both ways.
A custom integration. Built on the Salesforce and QuickBooks Online APIs, it syncs exactly the fields your teams use, including custom objects, partial payments and your own pricing rules. That's the route n-frames builds.
Start from what each team is missing
Most companies need one or two of these, not all of them. Pick the row that hurts most and build from there.
Run these through any connector trial
Install it in a Salesforce sandbox, point it at a QuickBooks Online test company, and push real deals through it, not the demo data.
Close a deal with three products, one discounted. What lands in QuickBooks?
You want three lines with the right items and the discount where your accountant expects it. A single total line means finance still fixes every invoice.
Record a partial payment in QuickBooks. What does the rep see?
If Salesforce only knows paid and unpaid, reps will keep asking finance about the half-paid ones.
Rename an account in Salesforce. Does QuickBooks follow, or create a second customer?
Duplicate customers are the most common mess these syncs leave behind, and they're slow to clean up.
Make a sync fail on purpose. Who finds out, and where?
A connector that fails quietly is worse than none. Someone should get an alert that names the record.
Does it read our custom fields and objects, or only the standard ones?
If your opportunity data lives on a custom object, many packaged connectors can't see it at all.
A distributor whose reps had to ask finance
Wholesale distributor · Salesforce for sales, QuickBooks for the books
A rep would mark a deal won and move on. Whether the customer had paid was a question for finance, who got it five or six times a week, usually with nothing more than an invoice number to go on.
Invoices were keyed into QuickBooks by hand from the closed opportunity, so typos in the CRM came along with them.
A closed-won opportunity now creates the matching QuickBooks invoice on its own, with nothing retyped.
Payment status flows back the other way, so the Salesforce record shows the invoice is paid as soon as it clears.
Reps check payment status for themselves before they call a customer, and finance stopped fielding the question.
Put QuickBooks payment status where your reps already work
n-frames builds the integration between Salesforce and QuickBooks Online around the fields your teams actually use: invoices created from won deals with the right lines, payments and balances on the opportunity, and one owner for customer records. If a packaged AppExchange app already covers your deals, we'll set that up instead of building one.
Put paid status in Salesforce →Questions people ask
Does Salesforce integrate with QuickBooks?
Not on its own. Neither company ships a built-in sync for the pair. You connect them with a third-party app from the Salesforce AppExchange, a low-code tool like Zapier, or a custom integration built on both systems' APIs.
Does it matter if I use QuickBooks Online or QuickBooks Desktop?
Yes. QuickBooks Online has a REST API that connectors and custom builds talk to directly. QuickBooks Desktop needs a go-between such as the Web Connector running on a machine with QuickBooks open, so the sync stops whenever that machine does. Fewer AppExchange connectors support Desktop. More on that in our QuickBooks Desktop API guide.
What data actually syncs between QuickBooks and Salesforce?
It depends on the route. Nearly every setup syncs accounts and customers so both systems agree on who the customer is. From there you choose: invoice and payment status into Salesforce, won opportunities into QuickBooks as invoices or estimates, or both. A custom integration can also carry custom objects, contract terms and partial payments that packaged connectors don't map.
Should the sync run one way or both ways?
Usually both, but each record type should have one owner. Opportunities and customer details start in Salesforce. Invoices, payments and balances start in QuickBooks. Two-way edits to the same field are where syncs start overwriting each other.