Skip to content
  • There are no suggestions because the search field is empty.

Webgility Desktop Settlement Report posting Issue due to QuickBooks Desktop connection failure

This article outlines the steps to troubleshoot and resolve connection issues between Webgility Desktop and QuickBooks Desktop that may prevent settlement reports from posting successfully.

Root Cause

This issue commonly arises due to one or more of the following factors:

  • Session timeout or expired authentication between Webgility and QuickBooks

  • Recent configuration changes in Webgility or QuickBooks Desktop

  • Network connectivity issues

Affected Sales Channel: Amazon

Resolution Steps

1. Verify the QuickBooks Company File Connection

  • In Webgility Desktop, navigate to:
    Connections > Accounting POS/ERP > Edit Connection.

  • Click Test QuickBooks Connection (applicable for QuickBooks Desktop users).

  • A successful test should return "Connection Successful/Successfully connected to quickbooks".

2. If the Connection Test Fails

  • Confirm the correct location of your QuickBooks company file.

  • Launch QuickBooks and ensure you are logged in as Admin.

  • Return to Webgility and reattempt the connection test using the verified company file path.

  • A successful connection will re-establish communication with the correct company file.

3. Reattempt Settlement Report Posting

  • Once the connection is successfully re-established:
    Go to Orders > Amazon > Settlement Reports.

  • Locate the failed or pending settlement and reattempt to post it to QuickBooks.

Following these steps should successfully resolve the settlement report posting issue caused by a connection error between Webgility and QuickBooks.