Resolving Amazon Settlement posting Failures Due to incorrect order download or Tax Configuration
This article helps Webgility Desktop users in troubleshooting errors encountered when uploading or posting Amazon settlement reports, which often result from misconfigured Amazon channel settings or outdated tax configurations. It provides support teams with a clear, step-by-step process to efficiently identify and resolve these issues, ensuring accurate and successful Amazon settlement reporting.
Overview
When a customer encounters errors uploading or posting settlement reports, issues often stem from misconfigured sales channel settings or outdated tax configurations. This article outlines a step-by-step troubleshooting process for support teams to efficiently identify and resolve such errors.
Common Causes
- Non-Amazon sales channels disabled or not configured
- Inaccurate or incomplete tax settings
- Corrupted or outdated report files
Step 1: Enable Non-Amazon Sales Channels
- Log in to Webgility with elevated access.
- Navigate to Connections > Sales Channel > Manage Sales Channel.
- Review the list of available channels. Ensure that required non-Amazon sales channels are enabled.
- Click Enable next to any missing channels relevant to the integration.
- Save changes and record the modification.
Step 2: Verify and Update Tax Settings
- Access Connections > Accounting/ERP/POS > Sync Settings.
- Cross-reference tax settings with the customer’s sales channels and business requirements:
- Check that correct tax jurisdictions and rates are assigned.
- Validate any automatic tax calculation services are active if required.
- Apply necessary updates and save. Note changes for future reference.
Step 3: Instruct Customer to Re-Download Settlement Reports
- Generate and download fresh copies of their settlement reports after the above adjustments.
- Upload the new reports as per standard procedure.
Step 4: Validate Resolution
- Confirm with the customer whether the upload completes successfully.