Salesforce and QuickBooks Integration: Complete Guide 2026
Connect Salesforce CRM and QuickBooks to create a more connected workflow between sales, customer management, invoicing, payments, and financial reporting.
Quick Answer
Salesforce and QuickBooks integration connects CRM and accounting workflows so that customer, sales, order, invoice, and payment information can move between systems with less manual data entry. Salesforce currently provides a QuickBooks Online Connector for Flow that can use QuickBooks Online as a data source or target, including actions such as syncing customers and creating invoices.
What Is Salesforce and QuickBooks Integration?
Salesforce is commonly used to manage leads, accounts, contacts, opportunities, customer relationships, and sales processes. QuickBooks is an accounting platform used for financial operations such as invoicing, payments, expenses, reporting, and bookkeeping.
When these systems operate independently, sales and finance teams may need to enter the same information multiple times. This can create duplicate records, inconsistent data, delayed invoicing, and limited visibility into customer financial status.
Integration creates a controlled data flow between the two platforms. Depending on the architecture, information such as customers, products, orders, invoices, payments, and account balances can be synchronized according to defined business rules.
The goal is not simply to connect two applications. A well-designed integration should establish clear ownership of data, secure authentication, predictable synchronization, error handling, monitoring, and processes for resolving failed transactions.
What Is QuickBooks?
QuickBooks is an accounting and financial management platform from Intuit. Businesses use QuickBooks products to manage areas such as income, expenses, invoicing, payments, financial reporting, and bookkeeping.
QuickBooks Online is particularly relevant for cloud-based integrations because external applications can connect to QuickBooks Online through supported APIs and integration mechanisms.
Benefits of Integrating Salesforce with QuickBooks
Connecting Salesforce and QuickBooks can improve visibility between sales and finance while reducing repetitive work. The exact benefits depend on which records are synchronized and how the integration is implemented.
Streamlined Data Flow
Reduce duplicate data entry by synchronizing selected Salesforce and QuickBooks records through automated workflows.
Better Customer Visibility
Give sales teams appropriate visibility into financial information such as invoice status and payment activity.
Automated Invoicing
A completed Salesforce sales process can trigger downstream invoice creation when the business workflow supports it.
Payment Visibility
Synchronize payment-related information back to Salesforce so teams can understand the financial status of customer transactions.
Financial Reporting
Bring relevant financial information closer to CRM data to improve operational reporting and decision-making.
Operational Efficiency
Automating repetitive cross-system tasks allows sales, finance, and operations teams to spend less time on manual reconciliation.
Scalability
A properly designed integration can support growing transaction volumes without relying on increasingly manual processes.
Data Consistency
Defined synchronization rules help reduce discrepancies between CRM and accounting records.
Planning a Salesforce Integration?
A successful integration starts with the right architecture, authentication model, data mapping, error handling, and synchronization strategy.
Salesforce and QuickBooks Integration Architecture
There are several ways to connect Salesforce and QuickBooks. The appropriate architecture depends on transaction volume, complexity, security requirements, required latency, integration ownership, and the systems involved.
Salesforce
CRM records, opportunities, accounts, contacts, products, orders, and business workflows.
Authentication
OAuth-based authentication and secure credential management for authorized API communication.
Integration Layer
Salesforce Flow, Apex callouts, native connectors, or middleware can orchestrate data movement.
QuickBooks Online
Accounting records such as customers, invoices, payments, bills, estimates, and sales receipts.
Salesforce’s current QuickBooks Online Connector for Flow supports QuickBooks Online as both a trigger/data source and a data target. Salesforce documents triggers for objects such as customers, invoices, payments, estimates, sales receipts, and other QuickBooks records.
Ways to Integrate Salesforce with QuickBooks
Salesforce Flow + QuickBooks Connector
Salesforce’s current QuickBooks Online Connector can be used with Flow to automate supported QuickBooks operations without building every interaction from scratch. The connector requires the applicable Salesforce integration capabilities and supported editions.
Direct API Integration
A custom integration can call QuickBooks APIs from Salesforce when the use case requires custom transformations, business rules, or API orchestration.
Middleware or iPaaS
Middleware can be useful when Salesforce and QuickBooks are part of a larger integration landscape involving ERP, billing, data warehouses, or other enterprise systems.
How to Integrate QuickBooks with Salesforce
The following workflow describes a custom OAuth-based integration approach using Salesforce’s current credential architecture. Salesforce now recommends the improved External Credential + Named Credential model rather than legacy Named Credentials.
Create a QuickBooks Developer Account
Start by creating or accessing your QuickBooks developer account. From the developer environment, create the application that will communicate with QuickBooks Online.
Create the QuickBooks App
In the QuickBooks developer dashboard, create an application and configure the appropriate application details and permissions.
The application credentials are used as part of the OAuth authorization process. Keep the client secret protected and do not expose it in Apex code, client-side JavaScript, or public repositories.
Configure OAuth Authentication
QuickBooks Online uses OAuth 2.0 for application authorization. Salesforce supports OAuth authentication through its external credential and named credential architecture.
Salesforce’s current OAuth setup involves an external authentication identity provider, an external credential containing the authentication configuration and principals, and a named credential that defines the endpoint and references the external credential.
Create the External Credential in Salesforce
In Salesforce Setup, create an External Credential and configure the appropriate OAuth 2.0 authentication protocol and principal.
Salesforce recommends the newer extensible External Credential and Named Credential framework because it separates endpoint configuration from authentication and provides explicit permission-based access to credentials.
Create the Named Credential
Create a Named Credential and associate it with the External Credential. The Named Credential represents the external endpoint that Salesforce will call.
Salesforce describes a Named Credential as a reusable definition of a callout endpoint and its associated authentication configuration, allowing Apex and other supported Salesforce features to use the connection without embedding authentication details directly into code.
Configure the OAuth Callback
Configure the callback or redirect URL required by the OAuth authorization flow in the QuickBooks application and the Salesforce authentication configuration.
The exact URL and configuration depend on the Salesforce authentication architecture and QuickBooks application setup, so use the values generated by the respective environments rather than hard-coding a callback URL from an older implementation guide.
Authenticate QuickBooks Online
Authenticate the Salesforce credential against QuickBooks Online and authorize the application to access the required company data.
Salesforce stores user external credentials and OAuth access tokens using its credential framework rather than requiring tokens to be embedded directly in Apex code.
Test the Connection
Before building business automation, test authentication and verify that Salesforce can successfully communicate with QuickBooks Online.
Test both successful requests and expected failure conditions, including expired authorization, insufficient permissions, invalid records, duplicate data, and API errors.
Call QuickBooks APIs or Use Supported Flow Actions
Once authentication is working, the integration can use the QuickBooks Online Connector, supported Salesforce Flow actions, or custom API callouts depending on the requirements.
For custom Apex integrations, the Named Credential can be referenced as the callout endpoint so that authentication and endpoint management remain separated from business logic. Salesforce documents this pattern as the recommended way to simplify authenticated callouts.
What Data Can Be Synchronized?
The exact records depend on the selected integration method and business requirements. Common integration scenarios include:
Account and customer information
Invoice creation and status
Payment and transaction status
Product and item information
Quote or estimate information
Receipt information
Salesforce’s current QuickBooks Online Connector documentation specifically lists supported triggers for customers, invoices, payments, estimates, sales receipts, bills, vendors, purchase orders, and other QuickBooks Online records.
Define Data Ownership Before Synchronization
One of the most important integration decisions is determining which system owns each type of data.
| Data | Possible System of Record | Integration Consideration |
|---|---|---|
| Customer / Account | Salesforce | Define matching and duplicate rules. |
| Invoice | QuickBooks | Synchronize status back to Salesforce. |
| Payment | QuickBooks | Avoid treating Salesforce as the financial ledger. |
| Opportunity | Salesforce | Use business events to trigger downstream processes. |
Security Best Practices for Salesforce and QuickBooks Integration
Financial information requires careful handling. Integration security should therefore be designed into the architecture rather than added after development.
- Use OAuth-based authentication where supported.
- Store credentials and tokens using Salesforce’s credential framework rather than hard-coding secrets.
- Use permission sets to control which users can access external credentials.
- Limit API scopes to the minimum required by the integration.
- Do not store client secrets in Apex classes, JavaScript, or public repositories.
- Monitor authentication failures and integration errors.
- Define retry and exception-handling procedures.
- Document data ownership and synchronization rules.
Salesforce’s current credential architecture supports permission-based access, encrypted user external credentials, and separation between endpoint configuration and authentication information.
Error Handling and Monitoring
A production integration needs more than successful API calls. It should also define what happens when a transaction fails.
Logging
Record integration events and failures without exposing sensitive credentials.
Retries
Retry transient failures according to controlled rules.
Alerts
Notify the appropriate team when critical synchronization failures occur.
Reconciliation
Provide a process for identifying and resolving records that did not synchronize correctly.
Sales Commissions and Incentivization
QuickBooks and Salesforce integration can also support workflows where sales performance, commissions, incentives, and financial outcomes need to be connected. If this is part of your Salesforce architecture, see our dedicated resource:
Salesforce Integration with QuickBooks: Sales Commissioning and Incentivisation
Connect Salesforce and QuickBooks With the Right Architecture
Whether you need a direct API integration, Flow-based automation, or a broader enterprise integration architecture, Kizzy Consulting can help design the right approach for your business.
Frequently Asked Questions
Can Salesforce integrate with QuickBooks?
Yes. Salesforce can integrate with QuickBooks Online using supported connectors, Flow, APIs, or middleware depending on the requirements. Salesforce currently provides a QuickBooks Online Connector for Flow that supports QuickBooks Online as a data source and target.
What is the easiest way to integrate Salesforce with QuickBooks?
The simplest approach depends on the Salesforce edition, required workflows, and available integration capabilities. Salesforce’s current QuickBooks Online Connector can simplify supported Flow-based integrations, while custom APIs or middleware may be more appropriate for complex requirements.
Can Salesforce automatically create QuickBooks invoices?
Yes, this can be automated depending on the integration architecture. Salesforce’s QuickBooks Online Connector includes capabilities for creating invoices, while custom integrations can also use QuickBooks APIs for invoice-related workflows.
Does Salesforce integration with QuickBooks require APIs?
Not necessarily. Salesforce’s current QuickBooks Online Connector provides a supported integration path for Flow-based automation. Custom API development is useful when the business requires functionality, transformations, or workflows beyond the capabilities of the available connector.
What are Named Credentials used for in Salesforce integrations?
Named Credentials define an external callout endpoint and connect it to the authentication configuration managed through Salesforce’s credential framework. They allow developers to make authenticated callouts without embedding authentication details directly into application logic.
Should I use the old Salesforce Auth Provider and Named Credential setup?
For a new implementation, Salesforce recommends its newer External Credential and Named Credential architecture rather than legacy Named Credentials. The current model separates authentication configuration, permissions, and endpoint definitions more cleanly.
What QuickBooks data can be synchronized with Salesforce?
Depending on the integration method, businesses can synchronize data such as customers, invoices, payments, estimates, sales receipts, bills, vendors, and other supported QuickBooks Online records.
Can QuickBooks payment status be shown in Salesforce?
Yes, payment information can be synchronized into Salesforce when the selected integration supports the required QuickBooks records and the business has defined the appropriate mapping and synchronization rules.
Want to Integrate Salesforce With QuickBooks?
Connect sales and financial workflows with a secure, scalable Salesforce and QuickBooks integration designed around your business processes.
Or email [email protected]
Conclusion
Salesforce and QuickBooks integration can connect two critical parts of a business: customer and sales operations in Salesforce and financial operations in QuickBooks. When designed correctly, the integration can reduce manual data entry, improve visibility, automate repetitive workflows, and provide teams with more consistent information.
The best integration approach depends on the organization’s requirements. Salesforce’s current QuickBooks Online Connector provides a supported Flow-based option for many use cases, while custom API integrations and middleware can support more complex business processes and enterprise architectures.
For custom integrations, Salesforce’s current External Credential and Named Credential architecture provides a more secure and maintainable way to manage authenticated callouts than embedding credentials directly into code.
The key is to define the business process first, establish data ownership, select the appropriate integration architecture, secure the authentication layer, and build monitoring and error handling into the solution from the beginning.
Kizzy Consulting
Kizzy Consulting helps businesses design, implement, integrate, and optimize Salesforce solutions across CRM, data, automation, and AI. Connect with our team at [email protected] or contact us.



