Invoice Processing functionality

The following issues were resolved in the Invoice Processing functionality of Kofax AP Agility.

ID

Issue

Solution

1990608

Invoice amount incorrectly extracted as negative because of " - " between amount and currency.

Improved the distance checks by taking the distance between previous and next words into account. If the distance to the previous work is similar a minus sign does not cause a negative amount or a credit note categorization.

1988612

Able to validate $0 Invoice Amount invoices with the lines deleted.

Zero value invoices can no longer be validated successfully without selecting the "Zero value invoice" invalid reason.

1988304

DOCUMENT_STATUS remains on state 8 (IP Validation) after rejecting a document with scan quality issue on the validation form.

Rejected documents that are sent for re-scan correctly show 'New' status.

1985904

Object Ref Error when there are No documents in the folder.

An error no longer occurs when there is an empty documents folder.

1982963

Change Default Capture Profile Field Settings Unit Price from 2 Decimal Places to 4.

The Unit Price field has been modified so that it supports more decimal places.

1975873

Credit memo exported with 0 as line total amount after pairing with SLPO approach.

Credit memos are sent to Line Pairing Correction activity before they are exported.

1975869

Company code extraction not certain despite a clear hit when address label references non-preferred address type.

Scores are no longer modified based on surrounding keywords if:

  • there is a single hit only.

  • no keyword for the preferred address type was found on the document.

1974736

Old password used in IP .NET actions after changing DB password.

Passwords are not cached.

1962070

"Line data does not correspond to PO lines" error after line pairing correction when setting line type for misc charges.

Misc charge lines or lines without a PO reference are no longer erroneously sent to the Line Pairing Error Handling activity.

1961621

Use of PO Type value to categorize matched PO as Service or Material fails.

The PO Type can be used to categorize a matched PO as a Service or Material PO.

1961614

Incorrect line pairing when having two lines with similar unit price.

For matching rules with tolerance, AP Agility tried to find exact matches. If this fails, it matches with tolerance.

When matching with tolerance a cross-check is made if there is another unpaired line remaining where an exact match would succeed. In that case the current match is rejected.

1958646

Issue with Amount Group Locator(AGL).

The subfields of the Amount Group Locator were updated to account for situations when there is a mismatch in the decimal separator position.

1954634

Invoice incorrectly categorized as Credit note because Total being wrongly extracted from text at the top of the invoice.

When a document has a low confidence, it is no longer incorrectly categorized to a certain document type due to several improvements to document type determination.

1952909

Arabic characters misinterpreted as "-" leading to invoice being categorized incorrectly as credit note.

The distance between a leading or trailing minus sign is now taken into consideration.

Due to this, if there is a minus sign with some distance between it and the nearest value, it is no longer flagged as a credit note.

1938340

ExtractionProcess.exe runs out of memory when processing large documents.

To reduce memory usage fewer alternatives for each document are retained. If a document has more than 20 pages, drawn lines are no longer detected.

This avoids loading binary images into memory.