Validation

Add behavior before or after the Validation activity that influences how validation is performed or data is processed.

For example, use the before process to assign an invoice to a custom resource group. Use the after process to track an invoice in an external application.

Parent process: Validation

Customizable processes:

• IP Custom Before Validation

• IP Custom After Validation

Executes when one or both of the following variables are set to TRUE.

• Customized Before Invoice Validation

• Customized After Invoice Validation

Extraction

You cannot modify the actual extraction, but you are able to add behavior before an invoice goes to the ClassifyExtract process. Similarly, you are able to add behavior after an invoice is extracted.

For example, you can add bar code extraction using a separate project before an invoice is passed to the ClassifyExtract process. After the ClassifyExtract process, you can use a User Exit to do something with that bar code data, such as populating a custom field.

Also, use the before process to poll for additional information from an external source or process non-image formats such as custom XML. Use the after process to perform invoice tracking in an external application.

Parent process: InvoiceProcessingAgility

Customizable processes:

• IP Custom Before Extraction

• IP Custom After Extraction

Executes when one or both of the following variables are set to TRUE.

• Customized Before Invoice Coding

• Customized After invoice Coding

Processing

Add behavior before Kofax AP Agility starts processing a document for extraction, validation, line pairing, etc. Add behavior after this processing is complete.

For example, use before process to perform page separation or perform tracking in an external application such as a CMS.

Parent process: InvoiceProcessingAgility

Customizable processes:

• IP Custom Before Processing

• IP Custom After Processing

Executes when one or both of the following variables is set to TRUE.

• Customized Before Invoice Approval

• Customized After Invoice Approval

LPR Correction

Add behavior before the Line Pairing Correction activity as well as after the Line Pairing Correction activity.

For example, use the before process to configure a custom resource group assignment for an invoice after it is processed in the Line Pairing Correction activity.

Parent process: LinePairingCorrection

Customizable processes:

• IP Custom Before LPR Correction

• IP Custom After LPR Correction

Executes when one or both of the following variables is set to TRUE.

• Customized Before Invoice Exception

• Customized After Invoice Exception

Export

Extend the standard export processes or with your own custom processes. You can create a separate export operation to an external system or provide additional handling and notifications.

For example, extend the standard export functionality by saving the processed invoice and its image to a database.

Parent process: DocumentExport

Customizable processes:

• IP Custom Before Export

• IP Custom After Export

Executes when one or both of the following variables is set to TRUE.

• Customized Before Invoice Export

• Customized After Invoice Export

Rejected Document

Extend the standard HandleRejectedDocuments functionality with your own custom processes.

For example, you add a new entry to the list of rejection reasons called [CUST] Missing Attachments. By default, the rejected reason is saved alongside the invoice, but nothing else happens. Create the corresponding process so that custom behavior is performed each time this rejection reason is selected.

Parent process: HandleRejectedDocuments

Customizable processes:

• IP Custom Rejected Documents

Executes when the following variables is set to TRUE.

• Customized IP Reject Documents