Document Validation Errors
Purchase Invoice Validation Errors
Purchase and Expense Invoices go through several validation checks. These include:
The invoice has not been assigned to a facility
Expense invoices must be assigned to a facility before they can be exported.
Shipping Charges on Purchase Order (x) do not match Invoice (y)
The detected shipping charges on the invoice differ from the values on the imported Purchase Order.
No ‘Line Details’ found on this invoice
No product lines have been detected.
Detected a quantity of 0 for at least one line
A product line has been detected, but the quantity is 0.
Line Extended Price (x) is out of tolerance (y) by z for Line No. w.
The total value for line (w) does not match the corresponding line on the Purchase Order and exceeds the configured tolerance value (y).
Line Detail Totals (x) do not equal Sub Total (y).
The combined total of all detected product lines (x) does not match the detected Sub Total (y).
No ‘Line Details’ found for Purchase Order (x)
The detected and linked Purchase Order does not contain any product lines.
Invoice could not be matched to a ‘Purchase Order’
The detected Purchase Order Number is not a valid or active Purchase Order.
A ‘Purchase Order Number’ could not be found on this invoice.
No text was found in the area where the Purchase Order Number is expected.
Quantity Invoiced (x) is greater than quantity received (y) for Line No. z.
More products are being invoiced than have currently been received into the connected ERP solution.
Invoice Total (x) is out of tolerance (y) by z.
The detected invoice total does not match the total from the Purchase Order and exceeds the configured tolerance value (y).
Invoice Total (x) does not equal Sub Total + Tax + Shipping Charges - Discount (y).
The combined total of the detected Sub Total, Tax, Shipping Charges, and Discount (y) does not exactly match the invoice total (no tolerance allowed).
Invoice Unit Price (x) is out of tolerance (y) by z for Line No. w. The detected Unit Price for product line w is not the same as the Purchase Order & is out by more than the configured tolerance value (y)
(x) Line item(s) not found on the Purchase Order. One or more (x) lines detected on the Invoice have not been found on the Purchase Order
Line No. (x) does not have a valid Expense GL Account set. The specified line has not had a Expense GL Account manually set & the associated vendor doesn’t have a default configured
Statement Validation Errors
Date on this statement is not a valid date.
The detected date could not be parsed.
No ‘Line Details’ found on this statement.
No statement lines have been detected.
No matching statement line for transaction with Invoice No. x.
A line on the statement could not be found for the outstanding transaction (x).
No transaction found for Invoice No. x.
A transaction could not be found for a line on the statement with Invoice Number x.
Transaction for Invoice No. x has an outstanding value of y but the statement value is 0 (Paid).
A transaction has been found for the statement line. However, the transaction has an outstanding value, but the statement is marked as fully paid.
Outstanding transaction value (x) does not match statement (y).
A transaction has been found for the statement line. However, the transaction and statement values (x, y) do not match.
Invoice No. x is overdue (by approximately y days) and has an outstanding balance of z.
A transaction has been found for the statement line. However, it has an outstanding balance and is past the detected due date by y days.
Transaction for Invoice No. x has been marked as paid but the statement value outstanding is y.
A transaction has been found for the statement line. However, it has been marked as fully paid, but the statement still shows an outstanding balance of y.