ABBYY FlexiCapture for Invoices Training at #ABBYYSummit16

ABBYY TechnologySummit2016

ABBYY NAHQ, 2016

Peter Lang

© ABBYY Confidential

ABBYY FlexiCapture for Invoices

Two Hour Overview

Preparation for FCI

Certification Test

© ABBYY Confidential

Why ABBYY FlexiCapture for Invoices

– Ready-to-use. ABBYY FlexiCapture for Invoices is a ready-to-use solution that automates the processing of 70% of invoices out-of-the-box without a long deployment cycle.

– Flexible. Flexibility of the configuration allows you to:

● Improve the quality on the rest 30% (using training and vendor-specific FlexiLayouts)

● Meet the requirements of any project (additional fields extraction, additional business rules)

● Process invoices from different countries in one workflow

ABBYY FlexiCapture for Invoices. Overview 3

Key Functionality● Multi-channel capture from scanners,

fax, email and mobile devices

● Extracts header, footer and line items and validates the data

● Offers PO matching and straight-through processing

● On-the-fly training to improve data quality in production

● Supports US and European invoicesin many languages

● Extendable to new fields and document types

Multi-channel Capture

E-mail

Web-based scanning

MFP, local scanning

FTP

Mobile device

Fax serverFax

● 20% of organizations print electronic documents and process them manually or scan them into the capture process (AIIM, 2013)

● Processing of paper and electronic invoices in the same flow brings significant cost savings

5

6

Automatic Supplier And Buyer Identification

● Supplier and buying BU information is checked against your master data in the ERP

● Suppliers and buying BUs may be identified by name, address, phone number, website

● Multiple addresses and/or name spelling variationsfor the same supplier/buyer are allowed

Database Lookup

Pre-configured Extraction of Data Invoice number and date

Name and address of the buyer BU

Name and address of the supplier

Delivery date

Purchase order data

Line items: description of goods, quantity, unit and total price

Currency and total

7

Purchase Order Matching And Line Item Extraction• PO matching is done on a header and/or line item level

• Multi-level comparison is done with the master database (by number, total amount, vendor name, etc.)

• Invoice line items can also be visually compared to the purchase order details

• Line items can be extracted from non-PO invoices too

8

● Training by the administrator during setup

● For a proof of concept

● For the initial configuration of the system

● Training by the operator during production

● For improving data capture from new supplier invoices or invoices with changed design

● Can be controlled by the administrator or prohibited altogether

Training of the System (1 of 2)

Training Of The System (2 of 2)

• On-the-fly training allows the operator to refine data detection and teach the program to work with new suppliers

10

2. Click “Train” button

1. Select the correct area on the image

Demonstration


ABBYY FlexiCapture for Invoices. Overview

Focus on Functionality

• Product features

• Application scenarios

• Project setup


Variety of Invoices

• Reasons for the high variety of invoices:

– Types of invoices and processes related to them are diverse:• PO-based invoices

• Contract-based invoice

• Non-PO and non-contract invoices

– Vendor-specific layouts

– Invoice-like documents exist• Credit Notes

• Delivery Notes

• Receipts

13ABBYY FlexiCapture for Invoices. Overview

Invoice Capture Process


Recognition

• Recognition starts automatically after import

• The program has great room for customization, but all complexity is hidden from the end user


Custom

Extraction of BU/Vendor

Standard

Extraction of Main fields

Custom

Extraction of Additional fields

Ven

do

r-sp

ecif

ic t

rain

ing

Au

tom

atic

Ext

ract

ion

Invoice Project in ABBYY FlexiCapture

• A special type of project

• Contains a pre-defined

Document Definition


Steps to configure the project

• Integration with the ERP database– Connect the Vendor and

BU tables– Connect the PO tables– Configure export to

the ERP system

• Adding new fields to extract

• Vendor-specific training

• Fine-tuning of business rules


Country Settings

• Languages | languages of incoming invoices

• Tax Rates | tax rates of the country of BU that receives and pays the

invoices

• Currency | keywords for currencies, separators of decimal positions

• Keywords | keywords for certain fields: Total, Total Tax, Bank

Account, etc.

Countries and languages not supported out of the box can be added to the default Invoice Document Definition by the FCI Administrator.


What we just covered…

• Invoice processing is a part of the purchase-to-pay process

• FlexiCapture for Invoices – an easy-to-use, intelligent solution for capturing invoices

• Includes a special Invoice project

• On-the-fly training to improve data quality in production

• Extendable to new fields and document types


Extended setup


Content

• Invoice validation rules; document status

• Country settings

• Search algorithms for main fields – Line items

– PO matching

• Adding extraction of new fields

ABBYY FlexiCapture for Invoices. Extended setup 21

Invoice Validation Rules• What is checked:

– Legal compliance: if all national requirements to the compliant invoice are met

– Financial correctness: if the invoice is arithmetically correct and the taxes are appropriate

– Factual correctness: are the price, quantity and quality of goods is as expected/ordered

• Checking all this automatically saves time and money


Changing the Invoice Status• The status is assigned to the invoice automatically by the

validation rules– After errors have been corrected, the rules are checked again and a

new status is automatically assigned to the invoice

• Invoice status can be manually changed by the operator– to Valid – if the invoice does not satisfy some of the rules,

but can be exported and paid anyway– to Rejected or Exception – if the invoice formally satisfies

the rules, but must not be exported– A reason for changing the status must be selected

from a list or entered manually


Manual Changing of Status at Verification: Setup– Administrator can add new

reasons for a status change and modify the existing ones• E.g. to support messages in

different languages

ABBYY FlexiCapture for Invoices. Extended setup

● Operator may enter custom reasons, if allowed by the administrator

24

Disabling the Status– Status can be used to determine the export destination


● Status can be disabled● Rules will work the same way but will

not affect the status

● If status was used and then disabled:● Re-recognize the documents● Switch off the dependency of custom

export profiles on the status (if any)

● Status is disabled by default in the US invoice document definition

25

Filtering the Rules• To view all the rules that will be applied to invoices from a

particular country, use the filter– Show/hide rules that are not country-dependant by using the

“Always” option– Select “Overlaps with set” and a country value


General and Country-specific Rules• FlexiCapture for Invoices is shipped with the pre-defined rules that

include common rules for invoices as well as country-specific legal compliance rules

• You can disable, modify an existing rule or create a new one– Validation rules contain

launch conditions(based on the field value check)


• Based on the countries of the buyer and the vendor, FlexiCapture for Invoices makes certain assumptions that reduce the project deployment time

• Language (based on the vendor and buyer, plus English)

• Date and currency formats

• VAT rates (for EU countries)

• Currencies


Country Settings

• Languages | languages of incoming invoices

• Tax Rates | tax rates of the country of the buyer BU that receives and

pays the invoices

• Currency | keywords for currencies; decimal and position separators

• Keywords | keywords for certain fields: Total, Total Tax, Bank

Account, etc

• Formats | regular expressions for

formalized fields : VatID,

IBAN, Bank Code, etc.

(mostly for EU invoices)


Country Settings

Country Support• United States as well as a number of European countries are supported

• The following languages are supported:– English– French– German– Spanish– Dutch– Hungarian– Italian– Polish– Japanese– Czech

• Not supported countries and languages can be added and described manually

– Duplicate an existing country

– Add languages in the properties of the country


• Keywords for the invoice fields specified in the Country settings depend on the country (see Tax Rate, Currency and Keywords tabs)

– Country-specific keywords can be in multiple languages

– E.g. for Switzerland : French, German, Italian (+ default English)

• Language-specific keywords depend on the language and are the same across countries speaking this language


Keywords: Country and Language Settings

Currency

• The list of currency abbreviations can be specified in the properties of every country

– Currency abbreviation may be absent on the invoice

• Decimal and position separators for amounts are country-specific


SEARCH ALGORITHMS FOR THE MAIN FIELDS



Data Extracted from an Invoice

Invoice number and date

Buyer's name and address

Vendor’s name, address, VAT number (EU)

Currency, subtotal, total, as well as VAT rate and amount (EU)

Purchase order data

Line items: description of goods, quantity, VAT rate (EU), unit price and total price

34

Extraction Algorithm


Document DefinitionBuyer BU and Vendor detection

Built-in Technology

Matching the default fieldsMain FlexiLayout

Data Set

Invoice Settings

Matching the user-defined fieldsAdditional FlexiLayout

Results of all steps are merged together producing the full set of matched fields

35

CustomSettings

Full Text Recognition

& Objects Detection

Business Unit and Vendor Data• Automatic invoice processing starts with the

search for the Vendor and the buyer Business Unit fields

• Vendor and Business Unit groups of fields are very important!

– Vendor and BU both influence thematching of other fields (they define countries and through them – formats, keywords, tax rates)

– Business Unit: determines the set of validation rules for the invoice

– Vendor defines the Trained (specific) layout that will be used for matching (if it exists)


Data Fields for Business Unit

• Business Unit database columns:

– ID*

– Vat ID (EU)

– Name

– Street

– City

– State (US)

– ZIP

– Country Code*

37ABBYY FlexiCapture for Invoices. Extended setup

NameAddressVATID

IDCountry Code

Data Fields for Vendor• Vendor database columns:

– ID*– Business Unit ID– Name– Street– City– State (US)– ZIP– Vat ID (EU)– National VAT ID (EU)– IBAN (EU)– Bank Code (EU)– Bank Account (EU)– Country Code*


Unique IdentifiersName

Address

IDCountry Code

– Information in the database must match with the text on the invoice

The Key to Vendor and BU Detection


● Business Unit● small number of entities● can be added to the database

manually

● Vendors● many entities● other methods described

below can be used to improve the matching result

Business Unit Data


Real Life

ABBYY Group

ABBYY Solutions Ltd.

VATID_1

John Doe

Address:

Kyriakou Matsi Av. 61, CY 1082, Nicosia,

Cyprus

ABBYY Europe GmbH

VATID_2

ABBYY Italy

Some address here

ABBYY France

Some address here,

that is equal

to previous

FlexiCapture Model

Business Unit ID

VATID

Company Name

Address: Street, ZIP, City

Country

How To Fill In the BU Data Set?


HAPPY STARProduction LLC

HAPPY STAR Software LLC

Marketing Finance

Group of companies

CostCenter Legal

John Doe

Jane Roe

HR

Business Unit

Purchaser

Happy Star Group

BU Records in the Data SetBU ID Name Address…

1 Happy Star Group1 HAPPY STAR Production LLC1 HAPPY STAR Software LLC1 Marketing1 John Doe

BU ID Name Address…? Happy Star Group1 HAPPY STAR Software House LLC1 HAPPY STAR Software LLC2 HAPPY STAR Production LLC2 Marketing2 John Doe


Multiple variants– Information in database should be matched

with the text printed at invoice

– Multiple variants● Master Data can have the variants of values

● Admin can allow column to have variants, operator can add variant

● Records with equal ID in database will be collapsed to variants of one record in Data Set


Street

Robert-Bosch-Str

1

P.Box

Box 1533 Robert-Bosch-Str

1

Box 1533

Street

43

Data Base Dataset

Vendors Database


FlexiCapture Model

Vendor ID

Company Name

Address (Street, ZIP, City

Country)

Tax Identifiers,

Bank Detials

Typically about 10K Vendors in a database

Auto-Investigation of problems


ABBYY FlexiCapture for Invoices automatically looks for potential problems

Note! Schedule “Master Data Clean Up” phase in your project timeline

● Standard procedure can be enforced by you own script that checks each record

Deduplication


ID Name TaxID Address

100 The Best Company DE 789461233 Munich

200 The Best Company FR15 310378704 Paris

300 The Best Company DE 789461233 Dresden

400 The Best Company Ltd

DE 789461233 Munich

ID Name TaxID Address Currency

100 The Best Company DE 789461233

Munich EUR

101 The Best Company DE 789461233

Munich USD

ID

100

200

100

100

ID AdditionalInfo

Final ID

100 EUR 100

100 USD 101

● Printed at invoice or extracted by Vendor detection algorithm information is not enough to distinguish records in database

● A lot of similar records without clear understanding are they one vendor or many

Normalization– Information in the database

must match the text printed on the invoice

– Data is normalizedduring the comparison

– Text● “LIMITED” = “LTD”, “Boulevard” = “bld” (whole word)

● “<Project>\Templates\InvoiceData\<Name of Data Set>.Cache\Normalization.xml

– Alphanumeric code● “123 ABC” = “123ABC”

● “+7 (903) 721-12-73” -> “79037211273”


Manual correction of Vendor Data


The administrator can edit internal copy of Vendor data or even delete some records.This will not affect data ERP system and will be valid through the update process

Manually Modifying & Adding Records• The administrator may enable the operators to

add or modify records in the Data Sets – Changes will be made to the Data Sets stored in the project, not to the external

vendor and business unit databases

– By default, operators cannot add new records to Data Sets!


Adding New Vendors at Verification


• A new vendor can be added during invoice processing

• The record will only exist in the internal data set

• [Unknown] prefix and Exception status will be assigned

• The AP dept. should add the vendor to the master database

• Search for ABBYY KB article:– “How to update external database

for the Data Set?”

Connection to ERP

ABBYY FlexiCapture for Invoices. Extended setup ->demo environmental variable 51

• ODBC-connection– Specify connection string

as Environmental Variable– Use this variable to connect each Data Set to external Database– Map Data Set columns to external Database columns

• Connection via API– IDataSet is available in special script event to import and update data

// Get records from ERP. Then for each external record:IDataSetRecord record = DataSet.CreateRecord();record.AddValue(“VendorId”, “123”);record.AddValue(…);…DataSet.AddRecord(record);

Data Set Internals• Data Set is a SQLite database inside ABBYY FlexiCapture

<project>\Tempates\Attachements\DataSetName.Cache\db


● Main – copy of external data according to specified mapping rules

● Diff – contains all user editing, made via ABBYY FlexiCapture

Both contain some technical fields that allow to build final view of data and perform different tasks like data update without losing users editing

(Download DB Browser for SQL Lite to view - DB Browser for SQLite is an open source tool to create, design, view, and edit database files compatible with SQLite.)

Data Set Update• Updating a Data Set synchronizes it with the external database


● Update can be done:

● manually in the document definition

● automatically, if “Update period” option is enabled

Rules of data merge

Existing records: – all users’ editing made via FlexiCapture is preserved,

– changes from external Database are applied

New records– are imported from external Database,

– records added via FlexiCapture are deleted

Deleted records– excess records are deleted in Data Set;

– records, that were marked as deleted only in Data Set are preserver in the same state

Note! Validation check is performed on all records brought by Update. Invalid records are imported with special sign, that prevent them from using in processing. Administrator can resolve the situation in Data Set properties.

BU and Vendor ID Dependency

• If vendor databases are composed with databases of several Business Units, use BusinessUnitId field in the Vendor database


VendorID VendorName BU ID001 Kleine Wagen GmbH 01002 Jimmy Fox Inc. 01003 Happy Meal Ltd 01001 Happy Meal Ltd 02002 Autoservice Srl 02

Pair of Id and BusinessUnitId values is a unique key of the Vendor record!

Predefined Vendor and BU– The vendor or the business unit can be determined in

advance, for example● If there is only one BU

● If the BU is identified by the mailbox

● If the vendor is identified by the email sender

– Use registration parameters to define Vendor/BU prior to the processing

● fc_Predefined:InvoicePredefinedVendorId

● fc_Predefined:InvoicePredefinedBusinessUnitId


Invoice Header Information• Invoice Type

– InvoiceDate, InvoiceNumber

– Vendor, BU

– Amount

– CreditNoteKeywords, InvoiceIdentifiers

• Invoice Number

– HighConfidenceLabels Invoice/Credit 123

– LowConfidenceLabels Document No: 123

– InvoiceNumberExcludePrefixes Invoice No: 123

• Invoice Date

– InvoiceDateLabelsNearCity MANCHESTER, 1 March 2014

– InvoiceDateLabelsNearInvoiceNumber 123, dated 1/03/2014

– InvoiceNumberWithDateLabels Invoice No/Date: 123/1.03.2014


How to improve recognition?

• Vendor-specific training

• Adding new keywords


To add or edit keywords, go to Invoice Properties/Countries and Languages.Edit the Language to seeand add keywords associated with fields.

Amount Detection on US Invoices • Total

– Using keywords• Geometry (usually end of the page)• The number is the sum of numbers listed above

– If system is not confident about detecting the total, the Total field is highlighted in red

Note: Tax amounts are not extracted out of the box

• Currency is searched after the Total– near Total– by Keywords (EUR, Euros, etc.)


Line Items Extraction

• System searches for line items using● Special keywords (located elements) to detect the columns titles

● Type of content

● Mathematical expressions


● Rules help to validate the data:● Verify net total against order items

● Check amount per each line item

● Check line items against order items

Extraction of the Purchase Order Number

• Using a PO database (must provide it if they want to extract PO numbers) the end-customer

• If the PO database is not used– Extract PO numbers using regular expressions that are defined in the

InvoiceSettings.XML file

– E.g. for SAP: 4500[0-9]{8}


See the Alphabet in a Help file

256[0-9]{5}

PO Matching• Invoices that match a PO can skip verification and approval

• Multiple purchase orders can be detected

• Comparison methods:– you can compare the number and amount of the invoice with those in the

purchase order (header-level comparison) • For each PO found on the invoice, a group element will be displayed that will consist of

fields Order number, Total and the Details... button for viewing the order items from the data set

– you can compare the line items of the invoice with those in the purchase order (line item-level comparison)


Help File

• For more details please refer to the Help File

– ABBYY FlexiCapture for Invoices > Specifications > Detecting the main fields

– ABBYY FlexiCapture for Invoices > How to set up an invoice capture project> Capturing additional invoice fields > How FlexiLayout matching results are merged


mk:@MSITStore:C:/Program Files/ABBYY FlexiCapture 11 Stations/FCDistributedAdministrator0.chm::/InvoiceReader/IR_TitleTopic.htm

mk:@MSITStore:C:/Program Files/ABBYY FlexiCapture 11 Stations/FCDistributedAdministrator0.chm::/InvoiceReader/IR_Specifications.htm

mk:@MSITStore:C:/Program Files/ABBYY FlexiCapture 11 Stations/FCDistributedAdministrator0.chm::/InvoiceReader/IR_TitleTopic.htm

mk:@MSITStore:C:/Program Files/ABBYY FlexiCapture 11 Stations/FCDistributedAdministrator0.chm::/InvoiceReader/IR_HowToAdjustProject.htm

mk:@MSITStore:C:/Program Files/ABBYY FlexiCapture 11 Stations/FCDistributedAdministrator0.chm::/InvoiceReader/IR_OptionalFieldsExtraction.htm

ADDING EXTRACTION OF NEW FIELDS


Additional Pre-Defined Fields and Features

Invoice Features dialog allowsto enable/disable additional fields search:– Due date, Delivery

date– Purchaser name, PO

details– Line items


Custom Fields• Each project requires its own specific set of fields,

e.g.– Department / Factory of the buyer– Cost Center– Name of the buyer– Project Number– Account Number– Customer ID– Project ID– CapEx Number, etc,

• Custom fields can be added to the Invoice definition– By training (for each vendor separately)– By an additional FlexiLayout (for all vendors)


Additional FlexiLayout• Expands the functionality of the

project and provides a means of controlling the search mechanism that detects standard and custom invoice fields (vendor-independent!)

• Can be created from scratch or based on the Main layout matching results– Basing it on the Main

layout is recommended


The additional layout is loaded to the Invoice document definition

66

Export the Matched Invoice to FLS• Results of the Main FlexiLayout

match (regions and values) can be useful for creation of relations and accessing data sets– Recognize a batch in FlexiCapture

(in case of a server project save it locally first!)

– Export the documents with matched regions and other information from the batch to the FlexiLayout project

• In FLS, you can see the matched regions on all images, inherited from the FlexiCapture batch

ABBYY FlexiCapture for Invoices. Extended setup -> add a field export demo 67

Additional FlexiLayout Project Features• In the exported project you can:

– create new custom fields (fields are described once and work for any vendor)

• create elements describing the search and a block with a unique name

– change the way the program searches for default invoice fields• create elements describing the search of necessary standard fields; create blocks

and name them after the appropriate standard invoice fields!

– specify search logic based on relationships with standard fields• regions of standard fields can be used in relations parameters or advanced

relations

– use values from the data set of the document definition, create rules specific to Vendor IDs, Business Unit IDs and other parameters

• these values can be accessed by special functions and parameters used in advanced relations (language expressions)


Working with the Invoice DefinitionABBYY provides configured Invoice Document Definition out-of-the-box– Extraction of main fields– Country and languages support– Wide-spread laws support– Common business-rules support


● Each customer provides his own unique requirements. You can change and configure the Invoice Definition accordingly.

● To be current with ABBYY releases, you always have an option to update customer’s definition with template available in newest release

Localization of Invoice Definition

• Huge companies can use geo-distributed invoice processing using one solution

• Not only UI, but also Document Definition can be localized to operator’s language:– Name of fields– Names and messages from rules– Messages from scripts


You can export all messages for localization within one txt file, send it to a translator, get the translation back and build into the document definition

File format:StringID, "Translation“ // “Default value"

Several Document Definitions

● Processing invoices with different fields

● Several Document Definitions can be used in one project

● Use different Batch Types for each Document Definition


Please, note!

It is not possible to use Document Definitions for invoices and for other documents in the same project

Let’s Recap…• Invoice document definition includes pre-defined validation rules

• The status of an invoice is determined automatically by the validation rules

• Country settings affect the way the data is extracted and validated

• The resulting set of fields is obtained by merging the results from different FlexiLayouts

• ABBYY FlexiCapture for Invoices offers line items extraction

• It is possible to extract PO numbers using a database and/or regular expressions

• Custom fields can be added in the Invoice document definition

• Additional FlexiLayout allows modifying the logic of search for the default fields and describe new custom fields


Training


Content

• Training: – by Operator– by Administrator

• Trained FlexiLayout:– Export/Import– Disabling/Deleting

• Manual development of FlexiLayout Variant

• Merging of FlexiLayouts


Training

• FlexiCapture is shipped with a Document Definition that contains a Generic FlexiLayout– this layout is able to extract data from the majority of

invoices

• On-the-fly training helps to improve data detection on invoices of particular vendors– specific invoice design or various formats of data

• Both the Trained FlexiLayout Variant and the Generic Layout are used for the document recognition to achieve the best quality of data extraction


How to Train: Training by Operator

1. Open the page

2. Correct the location of fields

3. Click Train button– Important! Before you hit the Train button, each field region must be

correctly located on the document image• Incorrect field marking can considerably decrease the overall quality of matching

4. Train the regions on at least 3 samples for each Vendor


Training Batch• Is a description of the particular vendor’s layout

– Contains the set of images added for training

– (after training) contains the trained layout based on the marking of sample images; the layout can be accessed by being exported to FLS

• Is named automatically after the Vendor's name

• The results of the training are stored separately for each Vendor (Vendor ID) in a project


Sample Images

• At least three invoices from the vendor must be trained

• Training works for all fields on the page, so all regions must be specified correctly!

• Each sample image in the training set may be in one of the following three states:

– Unused - the sample image is not used

– For training - the sample image is used for training and testing the layout

– For testing - the sample image is used only for testing the layout


Note: Training on many pages with various design and contradictory positions of fields may worsen the quality of the layout!

78

How To Train: Training by Administrator during the Project Setup

1. Add sample invoices form a particular vendor for training– Switch to the Training Batches view , create a batch for the

vendor– Add images for training

2. Specify correct regions for all the fields on sample pages

3. Select the Training Batch, click Train

4. Assess the recognition quality on the batch with invoices– Lock the layout if results are satisfactory– Modify the set of images and train again

if quality should be improved

ABBYY FlexiCapture for Invoices. Extended setup -> demo 79

Merging of FlexiLayouts. Generic FlexiLayout


BU/Vendor detection

Main FlexiLayout

Additional FlexiLayout

Merging of FlexiLayouts

ABBYY FlexiCapture for Invoices. Training 81

Generic FlexiLayout

Trained FlexiLayout Variant

● Processing speed does not depend on amount of FlexiLayout Variants

Export/Import of the Trained FlexiLayout

• To improve a trained FlexiLayout Variant or develop your own:– Export the trained layout as an FLS project

(optional)

– Modify the FlexiLayout in FLS to improve the detection of fields, or develop your own FlexiLayout from scratch

– Import it back to the training batch

Important!

• Trained FlexiLayout exported from one project should NOT be imported to another project! Use “Import training batches ” command to reuse training results

• A manually developed FlexiLayout for a vendor can be used for this vendor in all projects


Disable/Delete the Trained Layout

• If the results of the training are not satisfactory and the training process needs to be started from scratch:– Delete the Training batch (folder with the trained images)

– Start again with the training of one page in the verification mode and then continue training in the Training Batches view

• If only the matching of the generic layout needs to be tested:– Disable the Training batch


Training results can be re-used1) Export source project from the Application serverStore image samples if you want to continue training in new project


2) Open target project and import Training batches from source project

● Enable “Preserve Vendor ID” if both project share the same database of Vendors

● Select Document Definition you want to apply training results to

Links of Training Batch• Training batch should be linked with:

● Vendor from Data Set● Document Definition

• On import Training batches try to connect to Vendors by unique identifiers like TaxID number or IBAN

• You can specify associated Vendor and Document Definition manually

Use import Training Batches functionalityto share the same set of batches between two Document Definitions


Additional Fields and Features• Training during

invoice processing• Is enabled by default


Training… or Layout Development from training batch? Consider:

• Training for one vendor takes few minutes, developing FlexiLayout can take a few hours – might be best to start with training

Develop FlexiLayout Variant manually:

• In cases when you contend with:– repeatable items (except Line Items)– groups of changeable structure, e.g. Amount with

different tax groups (except Line Items)– field that has a lot of different locations even for one

vendor


Summary

• On-the-fly training helps to improve detection of the data on invoices

• FlexiLayout Variant can be trained or created manually

• Trained FlexiLayout can be exported, imported, disabled, or deleted

• ABBYY FlexiCapture for Invoices searches for the fields using a combination of FlexiLayouts



Date post:	08-Feb-2017
Category:	Technology
Upload:	abbyy-usa
View:	477 times
Download:	27 times