FAQ

Conductor is a web service that securely connects your app to one or more QuickBooks Desktop instances. It provides a RESTful API and fully-typed client libraries that you can use to read and write data to/from QuickBooks Desktop.

Behind the scenes, Conductor uses the QuickBooks Web Connector, which is a Windows SOAP-based program that comes preinstalled with QuickBooks Desktop on your end-users’ computers. This program always runs invisibly in the background, waiting for requests from Conductor. When you send a request to Conductor, it forwards the request to the Web Connector, which then forwards the request to QuickBooks Desktop. The response follows the same path in reverse. Between each of those steps, there are many layers of error handling, validation, and data transformation.

Conductor abstracts away all of the complexity, idiosyncrasies, and fragility of working with QuickBooks Desktop so that interfacing with this criminally outdated technology is as easy and wonderful as using Stripe’s API.

Conductor leverages a program called QuickBooks Web Connector, which comes preinstalled with all versions of QuickBooks Desktop and runs invisibly in the background on the Windows computer to maintain the connection. To connect, the QuickBooks Desktop users will step through Conductor’s authentication flow, which has them download a config file that Conductor generates, open it in the Web Connector, authenticate, and connect to Conductor (and thereby to your application). Here is a demo of the auth flow.

Conductor is priced at $49 month for each active QuickBooks Desktop company file connection. A connection is considered active if both of the following conditions are met within the same monthly billing period:

1. Conductor receives a heartbeat from the QuickBooks Desktop instance.
2. Your application makes a Conductor API call to that connection.

NOTE: Connections used for testing and development are free. Connections using data from an active production environment are not.

Volume discounts are available for enterprises requiring a large number of connections.

Integrating with QuickBooks Desktop from scratch is a painful nightmare. It’s a decades-old API that hasn’t been modernized and is riddled with edge cases, idiosyncrasies, and bugs that are incredibly difficult to work with. Conductor solves all of these problems and takes only a fraction of the time to implement with none of the maintenance headaches. We have obsessed over the edge cases and performance. Beyond the significant time savings, Conductor preserves your team’s mental well-being.

No, every Conductor API call is a real-time direct request to/from QuickBooks Desktop. If you make a request when the end-user’s computer is off or QuickBooks Desktop is inaccessible, Conductor will return an error message with instructions for how the end-user can resolve the issue.

By design, Conductor has no cache layer because it causes all sorts of problems when data is out-of-sync. E.g., you modify data on one end that has already been removed on the other.

Ideally, the computer running QuickBooks Desktop is always on and accessible. If that is not possible for some end-users, this design has still worked well because if such an end-user triggers a sync while using your app, they likely did so from the same computer as where QuickBooks Desktop is already running.

No, Conductor does not retain any of your end-users’ QuickBooks Desktop data on a permanent basis. For operational purposes, API request logs, which includes QuickBooks Desktop data, are temporarily, securely stored in a SOC 2 and GDPR-compliant log manager for 14 days before permanent deletion. Access to these logs is strictly limited to authorized Conductor engineers, who use them solely for debugging, offering customer support, and product improvement purposes. This approach ensures both the confidentiality of your data and compliance with the highest standards of data protection.

No, Conductor’s APIs currently only support working with a single object at a time because QuickBooks Desktop itself only resolves requests serially. If you want to create 50 invoices, for example, you will need to call the create-invoice API 50 times. However, you can send multiple requests in parallel; for example, you can use await Promise.all([ ... ]) in JavaScript with multiple requests, but you cannot send multiple requests in a single HTTPS request.

The QuickBooks Web Connector is a Windows program that comes preinstalled with QuickBooks Desktop that Conductor uses to securely communicate with QuickBooks Desktop. This program runs invisibly in the background on the end-user’s computer, waiting for requests from Conductor. The only time your end-user should see the Web Connector is when they first set up their QuickBooks Desktop connection with Conductor; other than that, it should be invisible to them.

In the world of QuickBooks Desktop, a “company file” is the main local file for all the financial data for a specific company. Typically, a QuickBooks Desktop user will have only one company file: the one they use to manage their business. However, some users manage multiple company files on one computer and actively switch between them. For example, an accounting firm might manage the books for multiple clients, each with their own QuickBooks Desktop company file.

Each Conductor connection is tied to a specific company file. If you need to connect to multiple company files, you will need to create multiple EndUsers in Conductor, each with their own connection. See this guide for more information.

Conductor supports every version, variant, and edition of QuickBooks Desktop since 2018, including:

• QuickBooks Enterprise Solutions - any version or year
  • Any edition: Accountant, Contractor, Manufacturing and Wholesale, Nonprofit, Professional Services, Retail.
• QuickBooks Premier (Plus) - 2018 or later
  • Any edition: Accountant, Contractor, Manufacturing and Wholesale, Nonprofit, Professional Services, Retail.
• QuickBooks Desktop Pro (Plus) - 2018 or later
• QuickBooks Accountant Desktop (Plus) - 2018 or later

No, QuickBooks Desktop is not being discontinued.

1. Ongoing Support: Intuit continues to support all existing versions of QuickBooks Desktop for current customers.
2. Continued Sales: Intuit is still actively selling “QuickBooks Enterprise”, the main version of QuickBooks Desktop tailored for medium to large businesses, to new customers.
3. Product Changes: Intuit will soon cease sales of “QuickBooks Desktop Pro/Premier Plus” – a less popular variant primarily used by small family businesses – to new customers (existing customers will still be supported).

While Intuit has encouraged users to migrate to QuickBooks Online, Desktop users consistently tell us that it doesn’t fully meet their business needs. Consequently, the base of existing QuickBooks Desktop users, including both “Enterprise” and “Pro/Premier” versions, remains robust. Conductor continues to support these users and their ongoing reliance on QuickBooks Desktop.

Yes, you can set up Web Connector connections on multiple computers for the same QuickBooks Desktop company file. This is applicable if your company shares the same company file across multiple computers on your office network. This setup can serve as a backup in case one computer is offline. However, we haven’t seen any Conductor users needing this approach so far, but we have confirmed that it works.

No, there is no way to access QuickBooks Desktop instances when the user’s computer is off because QuickBooks Desktop data is not stored online. Instead, QuickBooks Desktop is a local application that runs on a user’s computer. As a result, this means an active Conductor connection is always direct and real-time. Conductor intentionally avoids using a cache layer to prevent potential data conflicts when data is out-of-sync.

While this may seem limiting to many developers, we find that typical QuickBooks Desktop users do not mind:

1. User Availability: When a user is interacting with your application that syncs data with QuickBooks Desktop, they are typically at their computer anyway, which means that QuickBooks Desktop is accessible.

2. User Control: Many QuickBooks Desktop users are protective of their data and prefer to manually initiate data syncs rather than rely on automatic background processes. This approach gives them greater control over their data and ensures that no syncs occur without their explicit consent.

No, QuickBooks Desktop does not need to be actively open. As long as the computer itself is powered on, Conductor can send a request to QuickBooks Desktop, which will then automatically launch in the background, process the request, and close itself once completed.

Important Note: Launching QuickBooks Desktop in the background adds approximately 30 seconds to the request processing time due to the software’s startup process. For optimal faster response times, we recommend keeping QuickBooks Desktop open while using Conductor.

Yes, please see this guide for more information.

Yes, Conductor is fully compatible with Rightworks. Users can establish the connection just as they would with a typical Windows instance running QuickBooks Desktop.

However, there is an important consideration: Rightworks users must sign in to their remote desktop session each time they wish to sync with QuickBooks Desktop. This requirement exists because Rightworks terminates inactive instances once the connection is closed, preventing background processes from running when the user is signed out. Despite this, most users find this process manageable because signing in to Rightworks is a routine part of their workflow. It is worth noting that, based on our experience, remote QuickBooks Desktop hosts like Rightworks account for fewer than 2% of all QuickBooks Desktop companies.

Please see this guide for setting up a Conductor connection with a Rightworks QuickBooks Desktop instance.