Invoice validation is part of the AP Agility Workflow and ensures that the extracted invoice data is accurate before an invoice is displayed to a user. This validation process occurs automatically and differs from the Invoice Processing Validation Activity.

There are two steps to the AP Agility Workflow validation process.

1. Verification that all required fields in the invoice header are valid.

2. Check for possible duplicate invoices.

All validations are recorded in the Kofax AP Agility VALIDATION_HISTORY database table. Any failed validations are stored in the VALIDATION_ERRORS table.

An invoice is considered as fully validated if all of the following information is extracted correctly.

• Business unit is specified.

• Vendor is specified.

• Invoice number is not empty.

• Invoice date is not empty.

• Invoice date is valid. For example not in the future.

• Invoice amount is not empty.

• Invoice type is not empty and has a valid value.

• Document type is not empty and has a valid value.

• Invalid reason code is empty.

• PO headers table has a record with the corresponding PO number value from the validated invoice header. For PO invoices only.

• Invoice total must equal the total of the invoice lines.

  This check is performed in the Exception Activity and only if Lines are changed. For example, the Coding Activity was performed by the exception processor or a line was added, removed, or modified.

• Invoice currency exists in the Kofax AP Agility database.