- Salesforce recommends MuleSoft Composer, a separate Salesforce product with a QuickBooks Online connector, for this pairing.
- AppExchange lists several QuickBooks Online apps from independent software companies. We didn't find one built by Intuit.
- The common goal is an invoice created from a won opportunity, with payment status shown back in Salesforce.
- Gaps show up around custom fields, partial invoicing, credit memos, sub-customers and duplicates.
- Check the app reaches live QuickBooks data the way Intuit expects, and that your Salesforce edition allows outside connections.
The closed deal that waits a week
A rep closes a deal on Thursday. The bookkeeper finds out on Monday, when someone forwards the signed order. They open QuickBooks, search for the customer, create them again because the name is spelled differently, and type in the line items.
Three weeks later the rep asks if the customer has paid. Nobody in Salesforce can tell.
That is the job most Salesforce and QuickBooks connections are bought to do: get the invoice out the day the deal closes, and show payment where sales can see it.
What's available
MuleSoft Composer. Salesforce's own page on QuickBooks integration names MuleSoft Composer as its recommended route. Composer is a separate, paid Salesforce product for building flows without code, and it includes a QuickBooks Online connector. MuleSoft's reference lists triggers such as new invoices and new customers, and an action to create an invoice.
AppExchange apps. Several independent software companies sell QuickBooks Online apps on AppExchange. Most create invoices from accounts, opportunities or orders and bring invoice and payment status back into Salesforce. Some are two-way, some one-way. We didn't find an app built by Intuit itself, so check who publishes and supports whichever you choose.
General automation tools. Tools like Zapier offer ready-made recipes, such as creating a QuickBooks invoice from a new opportunity. They suit low volume and simple rules.
For a small team with one product line and simple terms, a well-reviewed AppExchange app is often all you need.
Where it stops
- Custom fields. QuickBooks Online limits custom fields on sales forms by plan. MuleSoft's reference also notes that only the first three text custom fields come through to outside software. If your invoices rely on a project code or PO number, check it carries.
- Partial and milestone invoicing. One opportunity billed in three parts doesn't fit a one-deal, one-invoice rule. Check how each tool handles deposits and staged billing.
- Credit memos and refunds. Check whether they reach Salesforce, or only the original invoice does.
- Customers and sub-customers. QuickBooks requires unique display names. A parent company with several sites, or two accounts with similar names, is where duplicates start.
- Products and prices. Your Salesforce price book and your QuickBooks products and services list need to agree. Decide which one leads.
- Classes, locations and tax. If finance tags invoices by department or location, check whether the tool can set those fields.
- Your Salesforce edition. Some editions don't allow outside connections by default. Check before you buy anything.
Your three options
An AppExchange app as it comes. Fastest to start, maintained by its publisher and usually enough when billing follows one or two patterns.
MuleSoft Composer or another integration platform. Suits teams that already use it, want an admin to adjust flows without a developer and have someone to own them.
A custom connection. Suits companies whose billing rules are specific: milestone billing tied to project progress, approvals before invoicing, or invoices that combine Salesforce data with another system. Our invoice processing page shows the kind of work that usually pays off first.
What a custom connection usually adds
- Invoices created from a won deal on your billing schedule, including deposits and milestones.
- A check before an invoice is sent, such as a missing PO number or a discount that needs sign-off.
- Payment, overdue and credit status on the account, so reps can follow up without asking finance.
- One customer record per company, matched on rules you agree with finance.
- A short daily list of anything that didn't go through, in plain language.
If no one is doing a step by hand today, it probably doesn't need building.
Questions to settle before you buy
Before you compare apps, sit down with the person who sends invoices and answer these together:
- Does every deal become one invoice, or do some become deposits, milestones or monthly bills?
- Which system issues the invoice, and where are mistakes corrected?
- What has to be true before an invoice goes out: a signed order, a PO number, a manager's approval?
- Which QuickBooks fields does finance rely on: classes, locations, terms, custom fields?
- What should a rep see: sent, paid, overdue, credited?
- How many customers exist in both systems already, and how many are duplicates?
- Who checks for failures, and how will they know?
Then give each option the same test. Run last month's real deals through a trial and compare the invoices to what finance actually sent. The differences tell you more than any feature table. If the differences are small, buy the app and move on.
Who owns the access
Your QuickBooks admin connects the app to your company file. Your Salesforce admin creates the integration user and grants its permissions. Intuit asks every app that reaches live QuickBooks data to complete its app assessment, even a private one, so plan for that step with any custom build.
Our guide to when an integration needs the vendor's approval covers how that works.
What most guides miss
Clean the customer list first. Duplicates in QuickBooks get copied into Salesforce, and the reverse. An afternoon of cleanup saves months of confusion.
Decide which system issues the invoice number. Two systems counting invoices is how audits get awkward.
Ask your bookkeeper what they fix by hand. Those fixes are the real requirements.
Start one way. Invoices out of Salesforce and payment status back is a smaller, safer first step than syncing everything both ways. Add more once finance trusts what they see.
Plan for the year-end close. Finance may lock past periods in QuickBooks. Check what the connection does when it tries to change an invoice in a closed month, and who hears about it.
How we do it
We start with a free intro call and look at how a closed deal becomes a paid invoice today. Then we work alongside your Salesforce admin and bookkeeper, use an existing app where it fits, and build only what it leaves behind. More on our Salesforce and QuickBooks pages.
