New features

Chinese VAT support improvements

The following improvements area available for processing Chinese VAT invoices:

Addition field extraction

Several additional fields are now extracted and validated when a Chinese VAT invoice is processes. These fields are also present on the Invoice Processing Validation activity form.

These fields include:

InvoiceCodeCN
InvoiceTypeCN
OriginCN
Payee
Reviewer
Drawer
BillToVATRegNo
VendorVATRegNo

Compliance checks

Chinese VAT invoices have specific compliance checks that must be met in order for successful invoice processing. Kofax AP Agility is able to detect any compliance violations so that they are exported and available for use downstream. For example, one rule is that an invoice number is present on a document twice. If Kofax AP Agility finds one invoice number only, the invoice is flagged. The Validation activity can override this to process the document, but the flag is sent downstream when the invoice is exported.

Custom fields for all AP Agility activities and processes

Three new custom fields are available for all AP Agility activities and processes. These fields appear on the Invoice Processing Validation activity form and during the AP Workflow activities. These custom fields are exported and included in Analytics for Kofax AP Agility reports.

Data from QR code

The information that is available in the QR code is used to improve extraction accuracy.

Chinese Golden Tax System framework

Invoices with a QR code are pre-registered with the Chinese Golden Tax System (GTS) by the vendor. It is possible to retrieve the invoice data from the GTS using a web service using the QR code data.

Kofax AP Agility provides a framework for easy integration with the GTS if needed.

Clean up master data

It is now possible to clean up previous master data that is no longer required when the AP Data Import process is run.

This is possible with the new Settings > Administration > Variables > Clean up Master Data variable. If this is set to True, the database is cleaned whenever the database is imported.

If you choose to delete the master data it is possible to delete any master data that falls outside the current date range for the ERP system that is configured in Settings > ERP Connections.

Company Code address extraction

The following improvements are available for the Company Code address:

Address type

It is now possible for the Administrator to specify the type of address that is expected on a document. The new Derive From setting in the Settings > Invoice Processing > Capture Profiles > Company Code enables an Administrator to configure whether the address that is used for the Company Code is listed as a Bill-to address, a Ship-to address, or any address on the document.

Train address location

During the Invoice Processing Validation activity it is possible to lasso an address on a document that is used for the Company Code. This document is added to the training documents and the Company Code address extraction results improve for subsequent invoices from that same vendor.

Configurable filenames for Agnostic ERP

It is now possible to configure the filenames of invoices for the Agnostic ERP. This is configurable when adding an Agnostic ERP Connection.

ERP connector framework

It is now possible to install ERP connectors that are released independently from Kofax AP Agility. These ERP connectors retrieve data required by AP Agility and send final invoice data and images back to the ERP system.

Kofax TotalAgility OPMT support

It is now possible to run Kofax AP Agility on Kofax TotalAgility in an OPMT environment. See the Kofax AP Agility On-Premise Multi-Tenant Installation Guide for more information.

MarkView integration improvements

The following improvements have been made to MarkView support.

MarkView supporting documents

A new scan form is available for MarkView organizations. On this new scan form, users can select a MarkView document type, which in turn, provides additional settings related to that invoice type. To use this form, update the Scan form in TotalAgility via the User Interface > Navigations for the Kofax AP Agility category to use the new Capture_Document_MV process.

If other ingestion methods are required, update these to use the CaptureDocumentMV process for the InvoiceProcessingAgility category as well.

MarkView support for subfield types

There is a new configuration form at Settings > Invoice Processing > Capture Profiles > Invoice Type Values.

Here, additional invoice types that are used by MarkView are available. Users can also add their own additional invoice types.

Parse MarkView bar codes to populate fields

A new setting on the Settings > Invoice Processing > Global Settings > General Settings form to enable users to process Settings > Invoice Processing > Capture Profiles > Invoice Type Values cover pages.

The cover page includes a bar code that is used by Kofax AP Agility to retrieve information from MarkView.

MarkView multi-tenant support

It is now possible to use MarkView in a multi-tenant environment.

One-time vendors

Kofax AP Agility now supports one-time vendors. On rare occasions, a document is encountered by Kofax AP Agility from a one-time vendor.

If an ERP system supports one-time vendors and processing documents from these vendors is wanted, ensure that any records in the master vendor data table have the OneTimeVendor value set to True for one-time vendors. Additionally, there is a new setting in the Settings > Invoice Processing > Capture Profiles > Vendor Settings to Enable One-Time Vendor Support.

If both of these are configured, a new button is displayed on the Invoice Processing Validation activity form to help users populate the vendor fields. If the vendor is know, some of the vendor details are filled in by the search. If the vendor is not known or a field is left blank by the search, the user populates the available vendor data manually.

Depending on the ERP system, the behavior of one-time vendors may differ. In SAP ECC or SAP S/4HANA Cloud ES ERPs, it is possible to reuse one-time vendor records.

Prefix stripping for PO numbers

A new setting in the Settings > Invoice Processing > Capture Profiles > PO Number Settings > PO Number Validation tab called Strip Prefixes enables Administrators to configure when to strip prefixes.

Return for data validation

It is now possible for Coders, Approvers, and Exception handlers to route documents back to the Invoice Processing Validation activity, along with a comment explaining why they routed the document.

For example, if a document is identified as a NON-PO but it is actually a PO and the PO number is not extracted, the Coder can send this document back to the Invoice Processing Validation activity with a message saying "This is a PO, please enter PO number."

Vendor subclass best practices

A new best practices guide is available that describes the recommended best practices when working with subclasses to improve extraction performance.