Select the validation rules that you want to apply to the current document type.

Determines whether the validation is performed in a workflow.

The validation rule is available for Swedish document types.

Performs length, identifier and checksum validations on the PaymentReferenceNumber field to ensure the validity of creditor reference numbers.

This validation makes sure that the date:

• occurs on or after today’s date.
• does not occur too far in the future.
• is a valid date. Note that English date formats are valid on all document types, including non-English document types.

Due-date limit (days) - Due dates are only valid if they do not exceed the current date plus the number of days you specify here.

Calculate due date from payment-terms master data - Uses payment terms master data to validate and optionally supply the due date.

• the supplier resending the same invoice by mistake or on purpose.
• the same invoice being scanned more than once.
• scanning software errors.
• an error in ReadSoft Online.
• original invoice attachments that are not recognized as an attachments and treated as separate invoices.

If a duplicate invoice is detected during verification or approval, the validation error is set on all relevant fields. For example, if Include invoice date and Include invoice amount are selected, and a duplicate invoice is detected, then the validation error is set on the invoice number, invoice date and invoice amount fields.

All relevant fields necessary for the duplicate invoice check are required. For example, if Include invoice date and Include invoice amount are selected, then invoice number, invoice date and invoice amount are all required in the document type. If any field is missing, the duplicate check will not execute.

The supplier number and invoice number are always checked when performing this validation, however, Include invoice date and Include invoice amount checks are optional and can be toggled in the Duplicate invoice check setting. If Include invoice date and Include invoice amount are selected, the invoice number, invoice date and invoice amount must all be the same as a previously processed invoice in order to be considered a duplicate. If you select Include invoice amount, the total amount field is used. However, if the total amount field is missing from the document type, the net amount field is used.

If a user overrides this validation, it is noted in the document history.

When you enable this validation, it utilizes existing data from previously processed invoices, so the validation works immediately. There is no need to wait for data collection that is specific to this validation.

The duplicate invoice check is performed per buyer, so it is possible to have invoices with the same invoice number, for example, if they are for different buyers.

Ensures that invoiced quantities match the quantities of goods received (3-way matching) by performing two checks:

• The quantity on the invoice must be equal to or less than the delivered quantity of the goods received on the purchase order:

  invoice quantity ≤ PO goods received quantity

• The quantity on the invoice must be equal to or less than the delivered quantity of the goods received on the purchase order minus the invoiced quantity on purchase order:

  invoice quantity ≤ (PO goods received quantity - PO invoiced quantity)

Invoices that fail this validation are automatically put on hold.

Automatic retry (days) - specifies the number of days ReadSoft Online will continue to automatically check the goods received quantity before sending the invoice to the next step. Automatic retry is only triggered if you override this validation during verification or approval and approve the invoice. Checks will be made automatically and continuously until the document passes validation or until the number of days you specify here passes, whichever comes first. If you change this setting, the new value is applied to invoices that are already on

If the document type contains multiple IBAN fields, all of the IBAN fields are validated.

This validation makes sure that the date.

• occurs before or equal to today’s date.
• does not occur too far in the past.
• is a valid date.

Invoice-date limit (days) - Invoice dates are only valid if they are not older than the current date, minus the number of days you specify here.

Process limit (days) - Invoices are stopped, if the invoice date is older than the current date minus the number of days you specify here. Unlike Invoice-date limit, you cannot override this validation error by pressing Enter during verification. The value you specify here must be greater than Invoice-date limit, unless you specify 0 to disable this setting (default value: 0).

This validation handles amounts up to 5 decimal places.

The validation compares the product of the delivered quantity and unit price with the total on each line item row. The validation is performed using two methods in this order:

1. The discount is applied to the total amount.

   LIT_VatExcludedAmount = (LIT_DeliveredQuantity * LIT_UnitPriceAmount) * (1 - LIT_DiscountPercentage) – | LIT_DiscountAmount|

2. The discount is applied to the unit price.

   LIT_VatExcludedAmount = LIT_DeliveredQuantity * (LIT_UnitPriceAmount * (1 - LIT_DiscountPercentage) – |LIT_DiscountAmount|

Note that the absolute value of the discount amount is used. Fields in bold must be selected (enabled) in the Document type dialog in order for the validation to work properly.

The validation also uses two different margins of error when comparing the calculated value with the row total. An absolute tolerance of 1 and a relative tolerance (the row total times 0.01) is used.

The validation compares the sum of the amount fields and the total sum of all line-item rows with the total amount.

InvoiceTotalVATIncludedAmount = SumOfTotalNetAmountFromLineItems + InvoiceTotalVATAmount + DeliveryCost + DeliveryCostPackaging + DeliveryCostInsurance + DeliveryCostToll + DeliveryCostPostage - InvoiceDiscountAmount

• Maximum total amount limit - Makes sure that the total amount field (InvoiceTotalVATIncludedAmount) does not exceed the value you specify here. If you do not use the total amount field, the net amount field (InvoiceTotalVATExcludedAmount) is checked instead.

If the total amount is greater than the value you specify here, the field is marked with a warning icon, but you can override the validation.

• Process limit (amount) - This validation works like the Maximum total amount limit, however, you cannot override the validation. Therefore, if you receive an invoice that exceeds the process limit, you must increase the value of this setting to continue, or delete the invoice.

You can only enable this validation for Swedish document types.

You can only enable this validation for Swedish document types.

Default cash-account number - The default cash account to use when you specify Entry only as the payment type.

See also:

• Processing Danish invoices with E-conomic.
• Processing Norwegian invoices with E-conomic
• Processing Swedish invoices with E-conomic
  Note If you use this validation, you must select Verify and Workflow.

You can only enable this validation for Swedish document types.

Ensures that the invoiced quantities match the quantities on the purchase order (2-way matching) by performing two checks:

• Quantities on the invoice must be equal to or less than the quantities on the purchase order.

  invoice quantity ≤ PO quantity

• The quantity on the invoice must be equal to or less than the purchase order quantity minus the invoiced quantity on purchase order.

  invoice quantity ≤ (PO quantity - PO invoiced quantity)

Purchase order over-quantity tolerance (percent) - Determines how much the quantity on the invoice can exceed the purchase order quantity.

For example, assume you type 10 in this setting to allow a tolerance of 10%. You have a purchase order with a line-item quantity of 20 items. The matching invoice line, however, has a quantity of 22. Because 20 plus 10% is 22, the quantity is within the tolerance and passes validation. If the matching invoice line had a quantity of 23, it would exceed the 10% tolerance and fail validation.

Ensures that the invoiced unit prices match the unit prices on the purchase order (2-way matching).

The unit prices on the invoice must be equal to or less than the unit prices on the purchase order to pass this validation.

invoice unit price ≤ PO unit price

Purchase order over-price tolerance (percent) - Determines how much the price on the invoice can exceed the purchase order price.

For example, assume you type 10 in this setting to allow a tolerance of 10%. You have a purchase order with a line-item price of $20. The matching invoice line, however, has a price of $22. Because 20 plus 10% is 22, the price is within the tolerance and passes validation. If the matching invoice line had a price of $23, it would exceed the 10% tolerance and fail validation.

Ensures that the total amount matches the total sum of all line-item rows when verifying line items on remittance advices. In other words, InvoiceTotalVATIncludedAmount must equal the sum of all LI_InvoiceTotal fields. The totals can differ by +/- 0.5 to account for rounding.

Example: If the total amount is 200.00, the validation will pass if the sum of all line-item rows is between 199.50 and 200.50.

Example: If the total amount is 200.00, the validation will fail if the sum of all line-item rows is 0 or if no line-item rows are found.

This validation is only available for remittance advice document types.

• IBAN
• ESR Ref, ESR No and ESR Amount
• PC Account, BLZ, BICSwift and Bank account

Checks the validity of QR references found in QR-IBAN numbers.

This validation handles amounts up to 5 decimal places and supports a margin of error that you specify in the Maximum difference allowed setting. This is a two-step validation.

1. The first step compares the sum of the amount fields with the total amount.

   InvoiceTotalVATIncludedAmount = InvoiceTotalVATExcludedAmount + InvoiceTotalVATAmount + DeliveryCost + DeliveryCostPackaging + DeliveryCostInsurance + DeliveryCostToll + DeliveryCostPostage - InvoiceDiscountAmount

   Note that the absolute value of the discount amount is used. Fields in bold must be selected (enabled) in the Document type dialog in order for the validation to work properly. The other fields are optional.

2. The second step compares the calculated VAT rate with the invoice VAT rate.

   InvoiceTotalVatRatePercent = 100 * (InvoiceTotalVatAmount / SummedAmountFields)

   All three fields must be selected (enabled) in the Document type dialog in order for the validation to work properly.

Maximum difference allowed

Specifies the margin of error (plus or minus) that is permitted when comparing the total amount field with the calculated total amount.

Example: If you specify 0.5 here and the total amount on the invoice is 23.00, the validation will pass if the calculated total amount is anywhere between 22.50 and 23.50.

InvoiceTotalVatAmount = InvoiceTaxAmount1 + InvoiceTaxAmount2 + InvoiceTaxAmount3 + InvoiceTaxAmount4

At least one of these fields must be selected (enabled) in the Document type dialog in order for the validation to work properly:

• InvoiceTaxAmount1
• InvoiceTaxAmount2
• InvoiceTaxAmount3
• InvoiceTaxAmount4

Maximum difference allowed

Specifies the margin of error (plus or minus) that is permitted when comparing the total tax field with the sum of the other tax fields.

Example: If you specify 0.5 here and the total tax on the invoice is 23.00, the validation will pass if the sum of the other tax fields is anywhere between 22.50 and 23.50.

0.0;12.5;25.0

This validation handles amounts up to 5 decimal places. The margin of error between the captured rate and the calculated rate cannot exceed 0.005.