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

Resolving Payout Posting Error

This article helps users of Webgility Desktop resolve payout posting errors that occur when integrating with QuickBooks Desktop. These errors typically stem from orders linked to a payout that have either not been downloaded or not posted to accounting. When this happens, users may encounter a message stating: "Some of your orders are still not downloaded or posted to accounting. So the payment was not created for those order-related payment amounts." Such issues can disrupt the payout posting process and cause discrepancies in accounting records. The step-by-step instructions provided in this article guide users through resolving these errors and restoring proper payout synchronization.

 Error Message: 

"Some of your orders are still not downloaded or posted to accounting. So the payment was not created for those orders-related payment amounts."

Overview:​

This issue can prevent the successful posting of payouts from Webgility Desktop to QuickBooks Desktop and may result in confusion during the reconciliation process.

 

Resolution Steps:

1). Update the Customization Node:
Open the apiconfig file located on the system (if you do not find it in drive C, right click on the app and click on Open file location):

  • Navigate to C:\Webgility\Unify enterprise\XML\apiconfig

  • Copy the node and paste it in the apiconfig file <CustomizationNode>SHOPIFY_SHOPCASH_CHARGE_ADJUSTMENT_AMOUNT</CustomizationNode>


​2). Modify the Customization Node:
Ensure that the customization node is correctly configured. This will update the necessary settings for your payouts.​

3). Redownload the Payout:
After updating the apiconfig file, proceed to redownload the payouts. This step ensures that all necessary data is correctly fetched for processing.​

4). Repost the Payout:
Once the redownload process is complete, try reposting the payout again. With the updated configuration and data, the payout should post successfully without the error message.

Note: Ensure that the apiconfig file is modified correctly, as improper changes may lead to further issues.