How to Resolve Errors While Posting Settlement Reports in Webgility Desktop
This article helps Webgility Desktop users address errors encountered when posting Amazon settlement orders into QuickBooks Desktop Enterprise through Webgility Desktop. Such errors are often caused by data mismatches, sync interruptions, or system issues that prevent proper order processing. The guide provides step-by-step instructions to resolve these errors and restore normal operations quickly.
Overview
If you are encountering errors when posting settlement orders in Webgility. These errors are often caused by data mismatches, sync interruptions, or system-related issues that prevent the order from processing correctly. This guide provides step-by-step troubleshooting to help you quickly resolve these errors and resume normal operations.
Common Causes
Settlement posting errors typically result from:
-
Incomplete or corrupted order data
-
Conflicts from recent or failed sync attempts
-
Temporary server, network, or application issues
Steps to resolve the error:
1. Note the Affected Order Number
-
Check the error message for the order number.
-
To copy the error message, click on the error, press Ctrl + C, then paste it into a Notepad file using Ctrl + V.
2. Search for the Affected Order
-
Go to the Dashboard in Webgility.
-
Search for the order in all relevant tabs like ‘Posted orders’ or ‘Archived’.
3. Address Affected Orders
-
If the order is already posted to QuickBooks, undo sync the order.
-
Select the order, do a right click and Re-download the order within Webgility.
4. Undo-Sync the Settlement Report
-
If the settlement report is partially posted, undo the sync.
-
Re-download the settlement report in Webgility.
5. Repost the Settlement Report
-
After completing the steps above, try to repost the settlement report. It should now post successfully.