Accounts & Billing Contacts
One Salesforce account can hold many contacts, but QuickBooks needs one customer with one billing address. Autymate fills the invoice from the billing contact you name.
Salesforce QuickBooks Integration
Turn won Salesforce deals into QuickBooks Online invoices, estimates and sales receipts that finance can trace back to the deal.
Salesforce already reaches QuickBooks Online through MuleSoft for Flow, its Starter and Pro Suites, and AppExchange apps. Autymate builds and runs a Salesforce QuickBooks Online integration that works alongside them and takes over the jobs finance still does by hand: deciding which Closed Won deals get invoiced, getting every line item onto the invoice, and matching each deal to the right customer. QuickBooks is one of the 300+ tools we connect.
- Source system
- Salesforce
- Destination system
- QuickBooks Online
Does Salesforce Integrate With QuickBooks Online?
Yes, you can integrate Salesforce with QuickBooks Online using Autymate. Salesforce also has its own Salesforce QuickBooks connector through MuleSoft for Flow and prebuilt QuickBooks integrations in Starter and Pro Suite, and AppExchange lists third-party apps. Autymate builds the Salesforce QuickBooks integration around your billing rules: which deal event creates the invoice, how an account matches a customer, which company each entity posts to, and how Autymate checks each invoice against the deal.
Salesforce Flow → QuickBooks Online
- Create or update customers, items, estimates and invoices from a Flow.
- Record payments, credit memos and sales receipts.
- Write custom fields on invoices, estimates, credit memos and sales receipts.
- Look records up again with Get and List actions.
QuickBooks Online → Salesforce Flow
- Start a Flow when an invoice, estimate or customer is created or updated.
- Start a Flow when a payment or credit memo is recorded.
- Use that event to update whichever Salesforce record your team chooses.
- Runs on the MuleSoft for Flow: Integration add-on; Professional Edition also needs API access.
What Can a Salesforce QuickBooks Integration Use?
Most invoice problems start in six places in Salesforce, from the account and stage to the line items.
Opportunity Stage & Amount
Stage, amount and close date mark a deal as won. Many teams bill later, on a signed contract, an activated order or a delivery milestone, so Autymate invoices on the field your finance team approves, set before the first invoice is created.
Opportunity Line Items & Price Books
Each line carries a product, quantity, sales price and a discount stored as a percentage. In QuickBooks the item decides the income account, and discounts usually sit on a line of their own. Autymate maps each line to its QuickBooks item and writes its discount the way your accountant wants.
Quotes & Orders
An opportunity can hold several quotes but syncs with only one, and an order moves from Draft to Activated. Autymate turns only the synced quote into the QuickBooks estimate and invoices on activation if that is how you bill, so rejected quotes and draft orders stay out of the books.
Custom Objects & Fields
Projects, subscriptions, packages and billing milestones often live in custom objects, and the PO number or contract reference sits in a custom field. QuickBooks Online allows four custom fields per sales form on Essentials and Plus and twelve on Advanced, so Autymate carries the ones your team needs on every invoice.
Currency, Tax & Entity
A Salesforce org has one corporate currency; each QuickBooks company has its own home currency. US Automated Sales Tax recalculates tax on the invoice. Autymate routes each deal by its entity and currency fields, and the tax recalculation explains why an invoice total can differ from the quote.
Plan for Multiple QuickBooks Companies and Business Entities
Each QuickBooks Online company is its own subscription, so one Salesforce org selling for several entities needs a routing rule.
Each Entity in Its Own QuickBooks Company
A legal entity, business unit or record type field on the account or opportunity decides the destination, and Autymate posts each entity to its own QuickBooks company file. The destination never depends on the customer's name or the rep who owns the deal.
One Mapping Template Across the Group
The same product-to-item, tax and class rules serve every company file, with approved adjustments where one entity sells something the others do not. A new entity starts from the template instead of a blank map.
Home Currency per Company
A US company and a UK company sold from one org post in different home currencies, and QuickBooks will not change a customer's currency once it is set. Autymate checks the currency before it creates a customer in a company file.
Sales Made for Another Entity
QuickBooks Online has no built-in intercompany entry, so when one entity books a deal another delivers, Autymate records that balance the way your accountant sets it, the same way on every run.
Translate Salesforce Activity Into Your QuickBooks Structure
A Salesforce QuickBooks invoice integration from Autymate maps each record to one QuickBooks destination in your own structure.
| Source | Destination | Example |
|---|---|---|
| Salesforce Account | QuickBooks Customer | Matched on the QuickBooks customer ID kept in the mapping, never on display name. QuickBooks names must be unique across customers, vendors and employees. |
| Billing Contact | Customer email and billing address | One named billing contact per account fills the invoice; other contacts never create customers of their own. |
| Opportunity at the approved stage | QuickBooks Invoice | Closed Won, a signed contract or an activated order: whichever event finance approves. |
| Salesforce Quote | QuickBooks Estimate | Only the quote synced to the opportunity becomes the estimate; superseded and rejected quotes stay in Salesforce. |
| Activated Order | Invoice or Sales Receipt | Invoice when the customer pays on terms; sales receipt when payment is taken at the time of sale. |
| Opportunity Line Item | QuickBooks Item on the invoice line | Product code to item, so revenue lands in the item's income account. |
| Line discount (percent) | Discount line or net line rate | 10% off a $5,000 line becomes a $500 discount line, or a $4,500 line, by the rule you choose. |
| Product family or record type | QuickBooks Class | Class can be set per line, so one invoice can split services and software revenue. |
| Region or territory | QuickBooks Location | Location is one per transaction, so it comes from the deal header, not the line. |
| PO number or contract ID | Invoice custom field | Carried into a sales-form custom field so the customer's accounts payable team can match the invoice. |
| Entity field | QuickBooks company file | US Inc. deals post to the US company, UK Ltd. deals to the UK company, each in its own home currency. |
| Salesforce record ID | Reference on the QuickBooks entry | Each posted invoice carries a reference back to its Salesforce record. |
What Explains the Gap Between a Salesforce Deal and the Cash in QuickBooks
Autymate ties six figures together, from what sales booked to what finance collected.
Deal Amount
Start from the opportunity amount the rep closed, in the opportunity's currency, on its close date.
Lines and Discounts
Rebuild it from the line items: quantity times sales price, less each line's percentage discount, item by item.
Tax as QuickBooks Calculates It
Add the tax QuickBooks applies to the invoice. With Automated Sales Tax on, that figure can differ from the quote, which is often the whole of the gap.
Invoice Total
The total on the QuickBooks invoice should equal lines, discounts and tax. Autymate flags any difference that none of them explains, so your team looks there first.
Payments and Credits Applied
Subtract payments and credit memos applied to that invoice. An overpayment sits in QuickBooks as an unapplied payment until someone applies it.
Open Balance
What remains answers the question sales keeps asking finance: is this deal paid? Paid, partly paid or open, as recorded in QuickBooks.
How Exceptions Are Handled in a Salesforce QuickBooks Sync
Deals change after they are invoiced. Autymate holds anything uncertain for your team's decision instead of guessing.
| Situation | What it means in QuickBooks | How Autymate handles it |
|---|---|---|
| A deal is edited or reopened after its invoice posted | The invoice no longer matches the opportunity, and a naive rerun would create a second invoice. | Autymate holds the change for your team's decision, with the reason, so the deal is never invoiced twice. |
| Two accounts look like the same company | "Acme Inc" and "ACME Inc" can become two customers with split balances, or invoices land on the wrong one. | Autymate matches on the QuickBooks customer ID and holds any new account that would duplicate a customer name for review. |
| A product has no QuickBooks item | The line has no income account to post to. | Autymate holds the invoice with the reason and the product to map, instead of posting to a guessed account. |
| Line items come from a custom object | Lines the integration does not expect are left off the invoice, so the total is short. | Autymate reads each line from the object you bill on, so packages, milestones and subscriptions bill as lines. |
| A customer pays more than the invoice | The extra sits as an unapplied payment or credit. | Autymate follows your QuickBooks "Automatically apply credits" setting and flags any unapplied amount for your team. |
| Renewals close in a month-end burst | API calls count against Salesforce's daily allocation and QuickBooks' per-minute limit. | Autymate paces runs within both limits and reprocesses a run as a batch if one stops partway. |
Five Controls Before a Deal Posts
Salesforce QuickBooks automation that finance can trust checks each deal at five points.
Trigger Gate
Only deals that meet the approved billing condition, such as a signed contract or activated order, create accounting records.
Identity Match
Accounts and products match on the IDs kept in the mapping, so a renamed account still reaches the right customer.
Mapping Validation
Every line is checked against the approved item, tax code, class and company before it posts.
Duplicate Prevention
A rerun finds the invoice already posted for that deal, so the same deal is not invoiced twice.
Monitoring
Autymate's team monitors your runs and catches exceptions early.
Salesforce Connector, Suites, AppExchange, an In-House Build, or Autymate?
Each path reaches QuickBooks Online. They differ in who owns the accounting rules afterward.
| Path | Best fit | What your team still owns |
|---|---|---|
| Salesforce QuickBooks connector (MuleSoft for Flow) | Admins who build Flows and need QuickBooks triggers and actions inside Salesforce | The MuleSoft for Flow add-on, every Flow, the field mapping, testing, reconciliation and support. |
| Starter or Pro Suite prebuilt integration | Small teams on Starter or Pro Suite who want guided setup from templates | Fitting their billing process to the template; Suites include two connections and two flows. |
| Salesforce QuickBooks AppExchange app | Teams whose objects and billing match what a packaged app already syncs | The app's configuration and subscription, often an add-on for more than one company, and month-end checks. |
| General automation tool (Zapier, Workato, Tray) | A simple handoff, such as one invoice per Closed Won deal | Building and fixing each recipe, duplicate checks on edited deals, line items, and multi-company routing. |
| In-house Salesforce QuickBooks API integration | Companies with developers who can own both APIs long term | Authentication, rate limits, retries, duplicate control, logging and every change to either system. |
| Autymate | Finance teams that want the accounting rules designed, run and supported for them | Approving the blueprint and deciding held items; Autymate builds, monitors and supports the run. |
When Salesforce's Own QuickBooks Path Is Enough, and When to Add Autymate
Keep Salesforce's Own Path When...
Closed Won is your billing moment, each account is one QuickBooks customer, one company file takes every deal, and an admin is happy to own the Flow, the mapping and the month-end checks.
Add Autymate When...
Billing starts at a contract, order or milestone; several entities or currencies sell from one org; products, discounts and tax need finance's rules; or you want one partner accountable for every run.
If Salesforce's connector already works for you, keep it. Autymate works alongside Salesforce's QuickBooks path where the accounting result, the controls or the scale call for more, with each record assigned to one system so nothing posts twice.
From Salesforce Activity to a Monitored QuickBooks Workflow
Six steps take a Salesforce QuickBooks Online integration from blueprint to monitored runs.
Map Your Current Setup
Record your Salesforce edition and API access, whether a MuleSoft QuickBooks Salesforce connector (MuleSoft for Flow), a Suite integration or an AppExchange app already runs, your custom objects and each QuickBooks company.
Decide Who Owns Each Fact
Autymate assigns one owning system to each of customers, products, prices, invoices, payments and credits, so nobody edits the same fact in two places and nothing posts twice.
Name the Billing Trigger
Name the exact stage, quote, order, contract or milestone that creates an estimate, invoice or sales receipt, and Autymate bills on that event alone.
Build the Mapping Blueprint
Map accounts, billing contacts, line items, discounts, custom fields, entities, tax, currencies and classes to QuickBooks.
Run a Real Quote-to-Cash Cycle
Test representative deals end to end, including an edited deal, a credit, a part payment and a retry, and check the books after each one.
Go Live and Monitor
Autymate turns on the automation with held-item review and duplicate control, and Autymate's team monitors every run and keeps it current as your Flows and fields change.
A Better Fit When CRM-to-Accounting Workflows Need More Control
These teams sell in Salesforce and bill on rules a simple sync cannot express.
B2B and Professional Services Firms
Deals close in Salesforce, but billing follows a signed statement of work, a deposit or project milestones. The Salesforce accounting integration invoices each milestone as it is reached, not the whole deal at Closed Won.
Membership and Event Organizations
Renewals, sponsorships and registrations are sold as opportunities and then chased as invoices. Each renewal is invoiced to the member's existing QuickBooks customer, so their history stays on one statement.
Groups With Several Entities
One Salesforce org sells for a US company and an international one, or for several brands. Each deal posts to its own QuickBooks company in the right currency.
Finance and RevOps Teams
Finance stops retyping invoices from deal records, and RevOps stops maintaining a set of one-off Flows nobody else can read. Both work from one documented blueprint.
Built for Accounting Integrations That Need to Keep Working
Salesforce stays your CRM and QuickBooks stays your accounting system. Autymate runs the work between them.
Built for Your Billing Rules
Autymate builds every integration around your business: your trigger, your matching rules, your items and classes.
Unsure Items Wait for You
Anything Autymate is unsure about is held for your team's decision, with the reason and what to check, and support is on hand.
Traceable to the Deal
Every QuickBooks invoice carries a reference to the Salesforce record that created it, and mapping changes are versioned.
Watched After Launch
Autymate's team monitors your Salesforce QuickBooks automation through its logs and catches exceptions early, as your Flows, fields and company files change.
Salesforce QuickBooks Integration FAQs
Yes.
You can connect Salesforce to QuickBooks with Autymate, and Salesforce offers two paths of its own: the QuickBooks Online Connector for Flow Builder through MuleSoft for Flow, and prebuilt QuickBooks Online integrations in Starter and Pro Suite since August 2026. AppExchange adds third-party apps. A Salesforce QuickBooks integration through Autymate adds your billing rules, routing and checks.
Salesforce's QuickBooks Online Connector can start a Flow when a QuickBooks customer, invoice, estimate, payment, credit memo or sales receipt is created or updated, and it can create, update, get or list those records from a Flow.
Invoices, estimates, credit memos and sales receipts also have custom-field actions. Which Salesforce record drives each action is up to the Flow you build.
It can be.
The MuleSoft for Flow connector works as both a trigger and an action, and Salesforce describes the Starter and Pro Suite integrations as two-way. Intuit's separate CRM connection in QuickBooks Online Advanced and Intuit Enterprise Suite is one-way: it brings Salesforce leads, deals, customers and products in for sales reporting and creates no invoices.
The one your finance team bills on.
Closed Won is the common default, but it is often too early for deals billed on a signed contract, an activated order or a delivery milestone. A Salesforce Flow QuickBooks Online action can fire on any of these; Autymate invoices on the one you choose and tests it on real deals, including reopened and edited ones.
The connector's payment trigger can start a Flow that updates the opportunity, the account or a custom invoice record.
The hard part is finding the specific record the paid invoice belongs to, so teams stamp the QuickBooks invoice number on the opportunity when the invoice is created. Autymate writes the QuickBooks invoice number onto the opportunity when it posts the invoice, then updates that same record when the payment lands, so sales can see which deals are paid.
For Salesforce's own QuickBooks Online Connector in Flow Builder, yes: it needs the MuleSoft for Flow: Integration add-on, and Professional Edition also needs the API access add-on.
Starter and Pro Suite include their own prebuilt connections. Autymate is a separate route that connects through your Salesforce org's API access, confirmed before anything is built, and AppExchange apps carry their own requirements.
Intuit's "Salesforce Connector by QuickBooks" app left the QuickBooks App Store around November 2023, and an Intuit moderator acknowledged its disappearance in the QuickBooks Community.
Options now include the MuleSoft for Flow connector, a Salesforce QuickBooks AppExchange app, or a managed integration such as Autymate.
Yes, with a routing rule.
QuickBooks Online is one company per subscription, so a field on the account or opportunity, such as legal entity or business unit, decides which company file each deal posts to. Autymate applies one mapping template across every company file, with approved adjustments for any entity that needs them.
By matching on IDs, not names, which is the core of any Salesforce QuickBooks invoice integration.
Autymate keeps the QuickBooks customer ID for each Salesforce account in the mapping, and every posted invoice carries a reference back to its deal. A rerun then finds the existing record instead of creating a second customer or invoice.
Yes, at volume, for any Salesforce QuickBooks API integration.
Salesforce allocates API calls per 24 hours by edition and license count, and QuickBooks Online throttles requests per company per minute. Month-end renewal bursts are when both are felt, so Autymate paces runs within both limits and Autymate's team monitors them through those peaks.
It depends on the path.
Salesforce lists Starter Suite from $25 per user per month, billed monthly or annually, and Pro Suite from $100 per user per month, billed annually, both with prebuilt QuickBooks Online integrations. The MuleSoft for Flow: Integration add-on is sold through Salesforce sales, and AppExchange apps carry their own subscriptions. Autymate quotes your integration from a blueprint call that maps your trigger, entities and volumes.
Salesforce's connector gives you building blocks for a Salesforce accounting integration; someone still has to design the billing trigger, customer matching, company routing, discount and tax handling, and support.
Autymate does that work and stays accountable for it, for QuickBooks Online and the 300+ other tools a finance team may run beside Salesforce.
Get a Salesforce → QuickBooks Integration Blueprint
- Trigger Gate
- Identity Match
- Mapping Validation
- Duplicate Prevention
- Monitoring
Tell us how you connect Salesforce to QuickBooks today: your billing trigger, products, entities and company files. We will map your Salesforce QuickBooks Online integration before anything is built.
Intuit Gold Partner
SOC 2 Type II
1,000+ Five-Star Reviews