Overview
Verifying your client's data just became easier with the Audit Sight and QuickBooks Desktop integration! Simply send the connector link to your Client Contact that has admin access to the account and the connection can be enabled.
Refer to Knowledge Base Article: Client account set-up to learn how to set up your Client Contact.
The QuickBooks Desktop connector is designed to work in single-user environments only, where one Windows user logs on to the computer they use to access QuickBooks. It is not designed or supported for use in multi-user or hosted environments.
Audit Sight follows Intuit’s service discontinuation policy for QuickBooks Desktop and fully supports the following versions, version tiers, and special editions:
Follow the steps below to connect the Client’s account to Audit Sight.
Step 1: Navigate to the Client screen
Send an email inviting your Client Contact to connect. You can resend the email if your Client Contact did not receive it the first time. Alternatively, if you have the login credentials to the account, you may login directly via “Add Direct Connection”.
Step 2: Audit Sight emails the Client Contact
The Client Contact will receive an email similar to below inviting them to connect their account:
Step 3: Client Contact selects their accounting software
In this article, we will show the steps for QuickBooks Desktop
Step 4: Download the QuickBooks Desktop Connector
After selecting QuickBooks Desktop as their accounting package, the Client Contact will be prompted to download the QuickBooks Desktop Connector.
The connector is a .exe file. Its file name includes your company name so it is recognisable by the user. The file is also signed using an Extended Validation Code Signing Digital Certificate issued by GlobalSign to increase trust when downloading.
The connector operates on a user level, meaning it does not require administrator rights to run on most systems. Some stricter corporate policies may require admin rights to run; in these instances, users should be familiar with their internal process for requesting permission from their IT department.
Install the connector on the computer you normally use when working with QuickBooks Desktop
Copy down your license key to use in the next step.
Step 5: Launch the connector and enter the license key
The user must run the downloaded file to start the connector. They will then be prompted to enter their license key obtained in the previous step.
Step 6: Select your region and initiate the link
The user should select which region they are in (Canada, UK or US) and click Link. The connector will initiate the connection with QuickBooks which will then prompt the user to grant access.
If QuickBooks is not open (or there is more than one copy of QuickBooks open) when you click Link, you may be shown an error explaining that you need to ensure there is only one copy of QuickBooks running and that you are logged in.
Step 7: Authorize connector to access QuickBooks
In QuickBooks, the user is prompted to allow the application to read and modify the QuickBooks company file. Any of the Yes options allow the connector to work but we suggest users choose Allow access even if QuickBooks is not running for the best experience.
Options may vary between QuickBooks versions but are similar to:
-
No
-
Yes, prompt each time
-
Yes, whenever this QuickBooks company file is open
-
Yes, always; allow access even if QuickBooks is not running.
In all cases, we recommend choosing the option that allows the most access to QuickBooks so that you can sync data as easily as possible.
Step 8: Wait for the connector to complete first link
Once access to QuickBooks has been granted, the connector will process the datasets you have chosen to fetch on the first link. Upon completion of the first link, a message will be shown to the user confirming that their data has been synchronized.
Going forward, the connector will minimize the system tray and periodically process any dataset syncs or pushes you have queued using the Audit Sight portal. The connector will also be set to automatically start when the system reboots.
