How to Resolve Duplicate Transaction Errors When Posting Amazon Settlement Reports in Webgility Desktop
This article helps Webgility Desktop users address issues caused by duplicate transactions that prevent successful posting of Amazon settlement reports from Webgility Desktop to QuickBooks Desktop. It covers common symptoms, pre-resolution checks, and step-by-step instructions to resolve and prevent sync errors and operational delays.
Steps to Resolve Duplicate Transaction Errors
1. Update Webgility to the Latest Version
Keeping Webgility up to date ensures access to the latest bug fixes and sync improvements.
-
Open Webgility Desktop.
-
Navigate to Help > Check for Updates.
-
Install any available updates.
2. Identify Duplicate Transactions
Use Webgility’s error reporting tools to locate duplicate transaction entries.
-
Go to Home > Orders or Error Logs.
-
Look for errors related to duplicate transactions during settlement report sync.
3. Remove Duplicate Entries from QuickBooks
Resolve the conflict by removing redundant entries in QuickBooks.
-
Open QuickBooks and the relevant company file.
-
Use the Find feature to search for the transaction ID or reference number.
-
Review both entries:
-
Check for differences in date, amount, or type.
-
Cross-check against reconciliation records to determine which entry is correct.
-
-
Delete the duplicate(s), ensuring one accurate record remains.
4. Resync Webgility with QuickBooks
Once duplicates are removed, resync the affected settlement report(s).
-
Return to Webgility.
-
Go to Orders > Amazon > Settlement Reports
-
Initiate sync for the settlement report(s) that previously failed.
-
Monitor for any new sync errors or duplicate messages.
5. Confirm Successful Posting
Validate the corrected sync and settlement report posting.
-
In QuickBooks, locate the affected settlement report transaction.
-
Ensure:
-
The transaction has posted without errors.
-
No new duplicates have been introduced.
-