Quickbooks to Salesforce Integration 2026

How should you choose?

Start by evaluating available connectors if your requirements are standard. Consider middleware when several systems or complex transformations are involved. Choose custom API development when you need specific behavior, integration logic, or greater control over the end-to-end workflow.

Implementation note: confirm Desktop support before publishing a delivery claim.

The Web Connector and SDK are documented QuickBooks Desktop integration routes. However, the specific route Kizzy uses for a particular customer, supported Desktop version, hosting arrangement, and synchronization schedule must be confirmed with the delivery team. Do not present either route as Kizzy’s standard implementation until it is verified.

QuickBooks, developed by Intuit, is accounting software used by businesses to manage financial operations. Depending on the product and subscription, it can support invoicing, expense tracking, bank reconciliation, tax-related workflows, payroll integrations, inventory functions, and financial reporting.

• Customer invoicing and billing
• Expense tracking and reconciliation
• Financial reports and transaction records
• Customer and product or service information
• Cloud access in QuickBooks Online or locally managed workflows in supported Desktop editions

Step 1: Create a QuickBooks Developer Account

Create or access your developer account in the Intuit Developer Portal. Review the QuickBooks Online Accounting API documentation for the entities and operations required by your integration.

Step 2: Create an App in the Intuit Developer Portal

Create an application and configure its required API access and OAuth settings.

Step 3: Obtain the Client ID and Client Secret

Use the credentials provided for your application when configuring the supported authentication flow. Keep the client secret private and do not place it in public code or client-side scripts.

Step 4: Configure Salesforce Authentication

In Salesforce Setup, configure the supported external authentication mechanism for QuickBooks Online. Depending on the org and authentication model, this can involve an Auth Provider, External Credentials, and a Named Credential.

Step 5: Configure the OAuth Credentials

Enter the application credentials in the appropriate secure configuration. Set the authorization and token endpoints, scopes, and other required parameters according to the current Intuit documentation and the selected OAuth flow.

Step 6: Configure the Redirect URI

Use the callback or redirect URI required by the Salesforce authentication configuration. Register the matching URI in your Intuit application. The URI configured on both sides must match the supported OAuth setup.

Step 7: Register and Test the Redirect URI

Save the matching redirect URI in the Intuit application and test the authorization flow in a sandbox environment before using production credentials.

Step 8: Create a Salesforce Named Credential

In Salesforce Setup, create a Named Credential for the QuickBooks API endpoint and associate it with the appropriate external authentication configuration.

• Use the correct QuickBooks Online API base URL for the environment.
• Configure the required authentication and principal settings.
• Grant access to the integration user or execution context as appropriate.
• Use the Named Credential from Apex instead of embedding tokens in code.

Step 9: Verify Authentication and Configure Company Information

Complete the OAuth authorization process and confirm that the connection can make an authenticated API request. Store non-secret integration configuration in an appropriate configuration mechanism. For QuickBooks Online, the company identifier is commonly referred to as the realm ID; use the correct value for the authorized company and environment.

Step 10: Create the Apex Integration

Use Apex HTTP callouts to send authenticated requests to supported QuickBooks Online API endpoints. For example, a customer creation request uses the customer endpoint, while invoice creation uses the invoice endpoint. The request body must follow the schema required by the selected API operation.

• Endpoint pattern: callout:QB_NAMED_CRED/v3/company/{realmId}/customer or the appropriate invoice endpoint.
• Method: POST for creating supported records.
• Content type: application/json.
• Response handling: Validate HTTP status and parse the returned record identifier or error details.

Check the current QuickBooks Online API documentation for required fields, supported operations, version parameters, and endpoint requirements before deploying.

public class QuickBooksCustomerService {

    public static void createCustomer(String realmId) {
        HttpRequest req = new HttpRequest();

        req.setEndpoint(
            'callout:QB_NAMED_CRED/v3/company/' +
            EncodingUtil.urlEncode(realmId, 'UTF-8') +
            '/customer'
        );

        req.setMethod('POST');
        req.setHeader('Content-Type', 'application/json');
        req.setHeader('Accept', 'application/json');

        Map<String, Object> customer = new Map<String, Object>{
            'DisplayName' => 'Example Customer'
        };

        req.setBody(JSON.serialize(customer));

        Http http = new Http();
        HttpResponse res = http.send(req);

        Integer statusCode = res.getStatusCode();

        if (statusCode >= 200 && statusCode < 300) {
            System.debug('QuickBooks customer request succeeded.');
            // Parse the response and save the returned QuickBooks ID.
        } else {
            // Log a sanitized error and route it for investigation.
            System.debug(
                'QuickBooks request failed. HTTP status: ' +
                statusCode
            );
        }
    }
}

1. Configure OAuth 2.0

Follow Intuit’s current OAuth authorization flow to obtain an access token. Use a sandbox company for development and testing.

2. Configure the Postman Environment

Set up environment variables for the base URL, realm ID, and authorization values needed by your test requests. Use Postman’s supported secret or sensitive-variable features for credentials.

• baseUrl: QuickBooks API base URL for the selected environment.
• realmId: QuickBooks Online company identifier.
• accessToken: OAuth access token.
• clientId and clientSecret: Application credentials, handled securely.
• refreshToken: Refresh token, if required by your configured flow.

3. Obtain an Access Token

Complete the required authorization process and request a token according to Intuit’s OAuth documentation. Do not assume that a token from one company or environment will authorize requests to another.

4. Test a Customer or Invoice Request

Send a request to the appropriate API endpoint with a valid JSON payload and the required authorization headers. Use the customer endpoint for a customer test and the invoice endpoint for an invoice test.

5. Validate the Response

Check the HTTP status, response body, returned record identifier, and the resulting record in the QuickBooks sandbox. Test invalid input, expired credentials, duplicate submissions, and recoverable API errors as well.