Understanding and Resolving Settlement Report Posting Errors
This article helps Webgility Desktop users addressing Amazon settlement report posting errors that can delay account reconciliation or prevent final transaction settlements. Common causes include account mismatches, outdated report versions, and data entry errors such as typos, formatting issues, or missing fields.
Overview
Settlement report posting errors can arise when there's a mismatch or technical issue during the upload or processing of your reports. These errors can delay account reconciliation or prevent final settlement of your transactions.
Common Causes of Posting Errors
-
Account mismatch: The report doesn’t match the account details on file.
-
Outdated report version: Using an older or incorrect version of the report.
-
Data entry errors: Typos, formatting issues, or missing fields in the report file.
Step-by-Step Resolution Guide
1. Check the Error Details
Carefully review the error message displayed during the posting attempt.
-
Identify whether the error occurred during uploading, matching, or posting.
-
Take note of any specific codes or messages for troubleshooting.
2. Verify Account Information
-
Log in to your Webgility dashboard.
-
Go to Orders > Amazon > Settlement Reports.
-
Confirm that the account number and report version align with your current account records.
3. Use the Most Recent Settlement Report
-
Download the latest report directly from your eCommerce or accounting platform.
-
Ensure the report date and version are current.
-
Avoid using previously submitted or duplicate files.
4. Check Report Formatting
-
Review all required fields for accuracy.
-
Remove any extra spaces, symbols, or unsupported characters.
-
Save the file in a supported format, such as
.csv
or.xlsx
.
5. Re-Upload the Corrected Report
-
Go to Orders> Amazon > Settlement Reports > Get reports > Manual Import.
-
Select and upload the updated file.
-
Wait for confirmation that the report has been successfully posted.