Salesforce QuickBooks Integration: Options, Setup and Pitfalls

What a Salesforce QuickBooks integration should do

Sales lives in Salesforce. Invoices, payments and taxes live in QuickBooks. Without a connection, someone in accounting retypes every closed deal, and a sales rep emails finance to ask whether a customer paid.

The integration closes that loop, usually called quote-to-cash:

1. Deal closes in Salesforce. The opportunity is marked Closed Won, with products and amounts.
2. QuickBooks gets a customer and an invoice. The account becomes a customer (or matches an existing one), and the opportunity lines become invoice lines.
3. Payment status comes back. When the customer pays, all or part, Salesforce shows the balance and status on the account and opportunity.

Everything else is optional. Teams that try to mirror all of QuickBooks inside Salesforce spend months on it and end up with two sets of books.

Your integration options compared

Neither Intuit nor Salesforce offers its own connector for QuickBooks Online today. Intuit’s own Salesforce connector for QuickBooks Online is no longer listed in the QuickBooks app store, so the choice is between third-party products and your own build. That leaves four routes:

A quick note on the main apps. Breadwinner is a Salesforce-native app: according to its AppExchange materials, it creates invoices from accounts, opportunities, orders or custom objects and brings payment status back in real time. DBSync connects Salesforce with both QuickBooks Online and Desktop, and runs syncs from Salesforce buttons or on a schedule. Both list on AppExchange; check the current listing, reviews and pricing before you buy, because plans change often.

A fifth route exists if QuickBooks is already straining: replace it with an accounting system built on Salesforce, such as Accounting Seed. That is a finance migration, not an integration project, and needs your accountant’s buy-in.

QuickBooks Online vs QuickBooks Desktop

Most of this guide is about QuickBooks Online, because that is where new US companies are. According to Intuit, new US subscriptions to QuickBooks Desktop Pro Plus, Premier Plus and Mac Plus stopped after September 30, 2024; existing subscribers can renew, and Desktop Enterprise is still sold.

If you are on Desktop and planning a move to Online within a year, build the integration after the migration. Rebuilding mappings twice costs more than waiting.

Object and field mapping

Every reliable integration starts with one decision per object: which system is the system of record, the one where edits happen. The other system gets a read-only copy.

The last row matters most. Matching by name or email works until two customers share one. Store the QuickBooks ID on the Salesforce account, and the Salesforce account ID on the QuickBooks customer if your tool allows a custom field, and every later sync is exact.

How to set up the integration, step by step

These steps follow the most common path, an AppExchange app with QuickBooks Online. The order is the same for iPaaS and custom builds.

1. Agree on ownership with financeSit down with your accountant or controller for an hour. Decide which object each system owns (use the table above), what triggers an invoice (Closed Won, an approved order, a signed contract) and who fixes sync errors.
2. Clean both sides firstMerge duplicate accounts in Salesforce and duplicate customers in QuickBooks. Make the Salesforce product list match the QuickBooks products and services list, or plan to pull products from QuickBooks. Dirty data copied by an integration becomes twice the cleanup.
3. Create a dedicated integration userDon’t connect the app with an admin’s personal login. In Salesforce, use a dedicated user; supported editions such as Enterprise, Unlimited and Performance come with a limited number of free API-only Salesforce Integration user licenses, according to Salesforce. Give it a permission set with only the objects the sync touches. In QuickBooks, authorize the app with a company admin account that finance controls.
4. Install in a sandbox and connect a test companyInstall the app in a Salesforce sandbox and connect it to a QuickBooks Online test company, not your live books. Load a copy of a few real customers and products.
5. Map customers and matching rulesMap account fields to customer fields, and set the rule for existing customers: match on the stored QuickBooks ID first, then on an exact field you trust, and send everything else to a review queue instead of creating a new customer.
6. Map invoices, lines, items and taxMap opportunity products to QuickBooks items, set terms and due dates, and let QuickBooks calculate sales tax. Decide what happens to discounts and to products that don’t exist in QuickBooks yet.
7. Set up the return flowBring invoice number, status, balance and due date back to Salesforce, plus payments. Put them on the account and opportunity page layouts, read-only.
8. Test the awkward casesRun ten real deals through the sandbox: a new customer, an existing one, a deal with five lines and a discount, a tax-exempt customer, a foreign-currency customer, a partial payment, a credit memo. Have finance check each invoice in QuickBooks.
9. Go live in stepsConnect production, sync only new deals from a cut-off date, and watch the error log daily for two weeks. Backfill old invoices only if sales really needs the history.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

What not to sync

An integration that copies everything is slower, costs more API calls and leaks financial detail to people who don’t need it. Leave these in QuickBooks:

• The general ledger and journal entries. Sales doesn’t need debits and credits, and posting accounting entries from a CRM is how books get corrupted.
• The full chart of accounts. The income account belongs on the QuickBooks item. Salesforce only needs to pick the right item.
• Bills, vendors, payroll and bank feeds. None of it helps a sales rep, and some of it is sensitive.
• Tax calculations. Send the customer’s address and tax-exempt status; let QuickBooks calculate the tax.
• Historic invoices beyond what sales uses. Twelve to twenty-four months of history is usually enough for renewals and collections.

Pitfalls and how to fix them

When a custom integration makes sense

Apps fit most teams. A custom integration on the QuickBooks Online API pays off when:

• Billing follows rules an app can’t express: milestones, usage-based lines, prepayments, revenue split across several QuickBooks companies.
• Volume is high enough that per-user app pricing costs more each year than a build.
• Salesforce is heavily customized, and the deal data lives in custom objects the apps don’t support well.
• You need the same quote-to-cash logic in other systems, such as a customer portal or a billing platform.

A typical custom build covers OAuth 2.0 with automatic token refresh (Intuit now caps refresh tokens at five years and rotates them, so the service must always store the newest one), a customer matching service, invoice creation with idempotency so a retry never creates a second invoice, QuickBooks webhooks for payments, a retry queue, and an error dashboard for finance.

For cost ranges by integration type, see our API integration cost guide. Building a larger data platform around the CRM? Read the cost of data integration.

Salesforce Xero integration in brief

Xero follows the same pattern: closed-won deal to invoice, payment back to Salesforce. The options are similar too. Breadwinner for Xero is listed in both AppExchange and the Xero app store; Zapier, Make and the iPaaS platforms have Xero connectors; and the Xero API supports custom builds.

Two differences to plan for. Xero’s API limits are tighter per organization: Xero’s developer documentation lists 60 calls per minute and 5,000 per day per connected organization on paid app plans, and 1,000 per day on the free Starter plan introduced in March 2026, so large backfills take days. And Xero calls customers “contacts”, shared with suppliers, so the same duplicate and ownership rules apply.

Go-live checklist

FAQ

Next steps

Connecting more than QuickBooks? The Salesforce integration guide covers the patterns that repeat across every system, and the Salesforce NetSuite integration guide covers the move up when QuickBooks no longer fits.

If your billing logic needs more than an app, Gilzor’s engineers can map the data flow between Salesforce and QuickBooks, build the integration and support it after launch. See our Salesforce integration services.