How to Fix “Item Not Found in QBD” for Amazon Settlements
Category: Webgility Desktop
Intro
If an Amazon settlement report fails to post with the error “Order have item which not found in QBD,” Webgility is unable to match one of the settlement lines to an item in QuickBooks Desktop.
This usually occurs when an overpayment, refund, or fee item is not mapped to a QuickBooks item. Follow the steps below to correct the mapping and repost the settlement.
Causes of Issues
The error can occur when:
- An Amazon fee, refund, or overpayment line does not have a QuickBooks item mapped.
- The required QuickBooks item exists but is not linked to the corresponding Webgility item.
- The affected settlement contains a transaction type that has not been mapped previously.
Amazon settlement reports can contain multiple fee, refund, adjustment, and other transaction types that Webgility processes as individual lines.
Step-by-Step Instructions
- Update Webgility Desktop.
Go to Help > Check for Updates and install any available update. Learn how to update Webgility Desktop - Find the affected order.
Locate the order included in the settlement that failed to post.If the order is in Archive or another order queue, move it back to the main Orders section so you can view its details. - Find the item that is not mapped.
Open the order and check its line items. Look for the fee, refund, or overpayment line that does not have a QuickBooks item assigned. - Map the item to QuickBooks.
Open the item mapping option and select the correct QuickBooks item and account. Save the mapping.
Learn more about mapping products in Webgility Desktop - Post the settlement again.
Go back to the affected Amazon settlement and select Post. The settlement should now post successfully.
Note
Once the item is mapped, keep the mapping in place so future Amazon settlements with the same fee, refund, or overpayment can post without the same error.
If the issue continues after mapping the item, contact Webgility Support with the settlement ID, affected order number, and a screenshot of the error.