Steps to connect ServiceTrade to QuickBooks:

Log into a ServiceTrade account (Your user must be an admin), click your account-Avatar (top-right of the screen) -> then click 'Account Settings'.

NOTE: This User MUST remain active in your ServiceTrade account in order for the integration to remain connected. It's recommended that you create a dedicated "integration user" that is solely in your account to keep the integration connected. You will lose all integration connections/settings if this user is ever deactivated in your account. Again, make sure this user is set up as an Admin.

2) On the right-side of this page, click the 'Add an External System' button.

3) Select 'QuickBooks' from the 'Type' dropdown menu

4) Enter a System Name & System Label, following the naming criteria described above these fields. (Example System Name = 'quickbooks' and System Label = 'QuickBooks'). Click Save.

5) On the next screen you'll select how to connect. For QuickBooks Desktop connections choose 'Connect using the WebConnector'

6) The next screen will present you with more steps for the connection. Please read through before you move forward. Once you've read through these steps click 'Download QWC'. This will initiate a download of the QuickBooks WebConnector ServiceTrade Application. If your computer prompts you to open the downloaded file, select 'open file'. if your computer does not prompt you, find the file on your customer and double click to open.

7) QuickBooks will open an authorization screen allowing you to tell QuickBooks you authorize the connection between ServiceTrade and your QuickBooks company file. Click 'OK'

8) QuickBooks will then ask you how and when you'd like for QuickBooks to allow ServiceTrade to access your company file. Choose 'Yes, always; allow access even if QuickBooks is not running' then click 'Continue...'

9) QuickBooks WebConnector will then open as it's own window and you'll see the ServiceTrade Web Connector application installed within.

9) Click back over to your browser with the connection steps. 'Step 8' has a password needed to complete the installation of the ServiceTrade WebConnector Application. Highlight and copy that full password.

10) Click back over to the WebConnector and Paste the password into the 'Password' area. hit Enter and it will prompt you to Save the password. Click 'Save'. (Right click and paste might not work on certain machines within the connector. If this happens click into the password area and type 'CRTL + V')

12) The WebConnector is now setup. After finalizing the settings in ServiceTrade you'll be able to send invoices. Click back over to your browser with the connection steps. Click the link in 'Step 9' to 'Refresh the page'.

14) Once you've chosen answers to the Sync setting questions and saved, you can test the connection. Click back over to the QuickBooks WebConnector. On the left side of the ServiceTrade installed application there is a check box. Check that box then click 'Update Selected' above the application column. This will run the WebConnector for the first time. (Depending on the size of your company file the first run of the connector could take 5-10+ minutes to run).

15) If the progress bars at the bottom of the WebConnector both reach 100% and the 'Last result:' shows 'Success' then you've completed the setup and ServiceTrade can now send invoices over to your QuickBooks company file.

16) The 'Send' Option on a invoice in ServiceTrade will now have an extra option. This option will be to send to QuickBooks.

(Some of these items may already be in place, and are for consideration only.)

1. Consider planned updates to your server or desktop PC running QBWC. Notify staff of when updates are to occur. Rebooting out of cycle for something truly critical.2, The server admin should understand that the QBWC must be re-opened after a server reboot. They should either do this, or notify an office user that the server has been rebooted so that he or she may re-open QBWC.3. The server should be pinging a monitoring service. It is fairly easy for IT to set up a system that listens for the server every, say, few minutes, and sends an email, SMS, or other notifications to interested parties in the event that it stops responding. Action can then be taken before your staff are significantly affected.