How do I integrate Salesforce with QuickBooks?

Your deals close in Salesforce and your invoices go out from QuickBooks. In between, someone retypes the client's name, billing address and amounts, and partners who want to know whether a client has paid have to ask the bookkeeper. The obvious fix is to connect the two, and the first surprise is that there is no simple built-in switch to do it.

The short answer: Salesforce does not ship its own QuickBooks connector. You have three realistic routes: a dedicated app from Salesforce's AppExchange that installs inside Salesforce, a general automation platform such as Zapier or Make, or MuleSoft Composer, which Salesforce itself recommends but which is priced for larger organizations. For most 10 to 50 person firms, the choice comes down to whether you want accounting data visible inside Salesforce (an AppExchange app) or a few targeted flows such as "deal won creates an invoice" (Zapier or Make).

Route 1: an AppExchange app

Several vendors sell QuickBooks integrations that install directly into Salesforce from the AppExchange. They typically sync customers, invoices, payments and products, and show QuickBooks balances on the Salesforce account record so the sales team can see who owes what without logging into accounting.

One widely used example is Breadwinner, which describes itself as a native Salesforce app with real-time QuickBooks sync. Its pricing page lists QuickBooks plans from $310 a month, as listed in October 2026, on annual subscriptions with tiers that add line items, payments, multi-currency and custom field mapping. Other publishers on AppExchange offer similar apps at different price points; compare them on the same checklist:

• Which objects sync, and in which direction?
• Does it support QuickBooks Online, QuickBooks Desktop, or both?
• Can you map custom fields, and on which tier?
• How does it handle multiple QuickBooks companies or currencies?
• Which Salesforce editions does it support?

Choose this route when the main goal is visibility: account owners seeing invoices, payments and balances in Salesforce, and finance staying in QuickBooks.

Route 2: Zapier or Make

Both Zapier and Make have Salesforce and QuickBooks Online connectors, so you can build specific flows: when an opportunity moves to Closed Won, find or create the customer in QuickBooks and raise a draft invoice; when an invoice is paid, update a field on the account and notify the owner.

Two requirements catch firms out:

• Zapier treats Salesforce as a premium app. According to Zapier's Salesforce help article, you need a paid Zapier plan, a supported Salesforce edition (it lists Essentials, Professional, Enterprise, Unlimited and Performance), My Domain configured, and Zapier approved as an External Client App in your org. Paid plans start at $19.99 a month billed annually for 750 tasks, as listed on Zapier's pricing page in October 2026.
• API access depends on your Salesforce edition. Salesforce's developer documentation says API access is included in Enterprise, Performance, Unlimited and Developer editions, while Professional Edition orgs can add it as a paid add-on. Check this before you plan around any platform that connects through the API.

Make offers the same pattern with a visual builder and credit-based pricing. Whichever you choose, the flows run in your account and you maintain them.

Choose this route when you need a handful of event-driven steps rather than a full mirror of accounting data in Salesforce.

Route 3: MuleSoft Composer

On its small business integrations page, Salesforce names MuleSoft Composer as the recommended solution for QuickBooks. Composer is a no-code tool inside Salesforce with a QuickBooks Online connector. According to MuleSoft's documentation, that connector covers invoices, customers, items and estimates, and the QuickBooks Online API only returns the first three custom fields of type string.

The catch is cost. As listed on the Composer pricing page in October 2026, the Starter edition connects up to three supported apps with 250,000 integration tasks, the Plus edition connects unlimited apps, and both are "contact for pricing". For most small firms that puts Composer out of proportion to a CRM and accounting link, but if you already license it, use it.

Which route fits

A fully custom integration built on both APIs is possible but rarely the right call at this size. It makes sense only when volumes are high or the logic is genuinely unusual.

Set it up without creating duplicates

Most failed Salesforce and QuickBooks integrations fail on data, not technology. Before you connect anything:

1. Decide the source of truth for each record. Typically Salesforce owns accounts and contacts until a deal is won; QuickBooks owns invoices, payments and balances. Write it down.
2. Clean both sides. Merge duplicate accounts in Salesforce and duplicate customers in QuickBooks. A client spelled two ways becomes two clients after the sync.
3. Know QuickBooks' naming rule. Intuit's Customer API documentation says a display name must be unique across customers, vendors and employees. A flow that blindly creates customers will hit errors when a name already exists.
4. Store the link. Save the QuickBooks customer ID on the Salesforce account so every later step looks the record up instead of creating a new one.
5. Pick one place to raise invoices. Editing the same invoice in both systems is how numbers drift apart.
6. Test with a few records, then review the sync log weekly for the first month.

Check with your accountant before changing how invoices, tax codes or revenue are recorded; the integration should follow their chart of accounts, not reshape it.

Our broader guide to integrating a CRM with accounting software goes deeper on source of truth and one-way versus two-way sync, and the HubSpot and Xero guide shows the same principles on a different stack.

How Flow Mesh helps

Our fixed-fee stack audit (€1,500) reviews Salesforce, QuickBooks and the rest of your tools, gives each a verdict (keep, configure, consolidate or replace) and writes up which records should flow where and through which route. If you want us to build the integration, it is scoped and quoted in writing after the audit and built inside your own accounts.

Key takeaways

• Salesforce has no built-in QuickBooks connector; the routes are an AppExchange app, Zapier or Make, or MuleSoft Composer.
• AppExchange apps suit visibility of invoices and balances in Salesforce; Zapier or Make suit a few targeted flows.
• Check your Salesforce edition's API access and Zapier's premium app requirement before you plan.
• MuleSoft Composer is Salesforce's recommendation but is quoted on request and sized for larger organizations.
• Decide the source of truth, clean duplicates and store the QuickBooks ID on each account before you switch anything on.