Amazon Settlement Stuck at Refund Posting
This article helps Webgility Desktop users resolve "Error while creating credit memo, the query request has not been fully completed. There was a required element that could not be found in QuickBooks." This issue usually occurs when Amazon settlements get stuck at the refund posting stage in Webgility Desktop. It explains that the error typically occurs due to missing, inactive, or incorrectly mapped items in QuickBooks Desktop, and provides troubleshooting steps to enable logging, review debug logs, and fix item mapping to complete the settlement posting.
Possible Reason
This error generally occurs if the item in the credit memo is not downloading into the Webgility Desktop database, the item is inactive in QuickBooks Desktop, or the item is not mapped to the correct item.
Troubleshooting errors while creating credit memo
-
Enable the logger, go to the location C:\Webgility\UnifyEnterprise\XML and open API Config in a notepad, check for the node <Logger>False</Logger> set it to True. Save the API Config file.
Follow the steps in this helpful article on: How to enable or disable logs
-
Restart Webgility Desktop as well as Scheduler (if running).
-
Go to the ErrorLog folder C:\Webgility\UnifyEnterprise\ErrorLog and delete old logs.
-
Post the settlement to regenerate the error.
-
Go to the ErrorLog folder C:\Webgility\UnifyEnterprise\ErrorLog and check the Debug logs.
-
Check the Debug log to find the item and fix the mapping.
Follow the steps in this helpful article on: How to Map Products or Inventory in Webgility Desktop
-
Once the above steps are done, try posting the settlement report again.