Overview
Sometimes, after sending an Invoice or Credit Note which contains lines relating to weighted products, Suppliers will receive a “Core XSD Validation Error” message which contains the following:
There can be several reasons for this. This article details an example of this issue, and explains why it has occurred.
Example Validation Error
The validation error will look similar to that shown in Fig.1.
In this instance, a Supplier has sent an Invoice to a customer via Purchase to Pay with the following values for one of the product lines. These are the numbers contained within the file that was transmitted from their system.
Weight Sold (quantity)=1.90g
Unit Price=£17.15
Invoice Price=£32.52
If we multiply the quantity (1.90) by the unit price (17.15), then we actually get 32.585. This is different to the Invoice Price provided – out by 6 pence - and this is the cause of the validation error.
What happened in this instance is as follows:
The Supplier originally had the quantity as 1.896, which when multiplied with the unit price (17.15), gives the expected Invoice Price of 32.52. However, before the Invoice file was transmitted, the quantity value was rounded to 2 decimal places, meaning that 1.90 is what was actually in the file. The Invoice price did not change though, causing the validation error to occur.
Fourth's Purchase-to-Pay solution will always calculate and validate the Invoice Price by using the following equation:
Sometimes, after sending an Invoice or Credit Note which contains lines relating to weighted products, Suppliers will receive a “Core XSD Validation Error” message which contains the following:
“The total value on line X does not match the unit value multiplied by the quantity.”
There can be several reasons for this. This article details an example of this issue, and explains why it has occurred.
Example Validation Error
The validation error will look similar to that shown in Fig.1.
Fig.1 - Core XSD Validation Error - Document Type: Invoice
In this instance, a Supplier has sent an Invoice to a customer via Purchase to Pay with the following values for one of the product lines. These are the numbers contained within the file that was transmitted from their system.
Weight Sold (quantity)=1.90g
Unit Price=£17.15
Invoice Price=£32.52
If we multiply the quantity (1.90) by the unit price (17.15), then we actually get 32.585. This is different to the Invoice Price provided – out by 6 pence - and this is the cause of the validation error.
What happened in this instance is as follows:
The Supplier originally had the quantity as 1.896, which when multiplied with the unit price (17.15), gives the expected Invoice Price of 32.52. However, before the Invoice file was transmitted, the quantity value was rounded to 2 decimal places, meaning that 1.90 is what was actually in the file. The Invoice price did not change though, causing the validation error to occur.
Fourth's Purchase-to-Pay solution will always calculate and validate the Invoice Price by using the following equation:
unit price x unit(s) sold = invoice price
So, it is important to ensure that all Invoice Prices in outbound files transmitted to Fourth are correctly derived from this calculation and, if any rounding takes place, that the Invoice Prices are updated to reflect this.
Comments
Please sign in to leave a comment.