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

How to Fix “Date or Amount Does Not Match” Errors During Amazon Settlement Posting in Webgility Desktop

This article helps Webgility Desktop users in resolving the error message “Date or amount does not match with the payment transaction attached with Invoice,” which commonly occurs during Amazon settlement report posting due to mismatches between Amazon settlement report data and payment transaction details even when transaction GUIDs appear to match. The article provides a step-by-step process to identify and fix the issue.

Overview

The error message 'Date or amount does not match with the payment transaction attached with Invoice' typically occurs during settlement report posting when there is a mismatch between the settlement data and the associated payment transaction details, even if the transaction GUIDs appear to match. This article outlines a step-by-step process to resolve this error and provides context for escalation or follow-up.

Common Causes

  • Discrepancies between settlement report and payment transaction data despite matching GUIDs
  • Synchronization issues between systems (e.g., ERP, payment gateway)
  • Data corruption or overwrites during automated sync

Troubleshooting Steps

1. Undo the Sync

  • In Webgility, locate the affected order/invoice.
  • Use the Undo Sync function. This will break the association between the settlement report and the payment transaction.

2. Redownload the Order

  • Trigger a manual download/import for the order or invoice from the sales channel.
  • Ensure the latest data is pulled in, including payment transaction details.
  • Confirm that the GUIDs still match after download.

3. Retry Posting the Settlement Report

  • Attempt to post the settlement report again after the data refresh.
  • Validate that the posting proceeds without the 'date or amount does not match' error.

4. Confirm Resolution

  • Check the settlement report and associated invoice for successful posting status.
  • Review transaction history or audit logs as needed for compliance.