Xero Sync Error Message - Payment amount exceeds the amount outstanding on this document

Accounting IntegrationsUpdated 18 Nov 20262 min read

The purpose of this article is to explain the cause of the  "Payment amount exceeds the amount outstanding on this document" error that can occur with a Xero sync.

Xero sync log entry showing a failed sync with the message that the payment amount exceeds the amount outstanding

This issue relates to the amount that is currently outstanding on the invoice in Xero.

For example if the payment is for $200.00 and the is only $100.00 owing on the invoice in Xero, you will receive this error. Most often the cause of this error is the invoice has been paid in Xero and then paid again in Workshop Software. So there is $0.00 outstanding on the invoice and a payment for $100.00 is trying to sync. Xero wont allow the payment to sync. 

To resolve this, you will need to have a look at the invoice number in Xero. In the example error above, the invoice number had been highlighted.

Workshop Software screen showing in the example error above, the invoice number had been highlighted

Open the invoice and take note of the amount outstanding on these invoices.

If the invoice is fully paid, you have two choices.

Steps

  1. Either void the payment in Xero, then void the payment in Workshop Software and enter it again.
    1. Workshop Software does not resend a payment Xero has refused with this error, so the new payment is the one that syncs and pays the invoice off again.
  2. Alternatively, you can void the payment in Workshop Software, press the Xero button, and the invoice should update to paid in Workshop Software.

Our advice is to void the payment in Xero as the integration is quicker at sending information from Workshop Software to Xero.

If the the amount outstanding is more than $0.00, take note of the amount outstanding. Find the payment from Workshop Software for the invoice and compare the 2 amounts. Either the payment amount in Workshop Software or in Xero will need to be amended to resolve this issue.

Also Explore

Was this article helpful?