- Introducing ABBYY FlexiCapture
- Installing and running the program
- ABBYY FlexiCapture architecture
-
Program settings
- ABBYY FlexiCapture Setup
- Multitenancy
- Creating a project
-
Document Definitions
- Creating fixed Document Definitions
- Creating Document Definitions for semi-structured documents
- Document Definitions without automatic fields extraction
- Document sets
-
Document Definition fields
- Text entry fields
- Checkmarks
- Checkmark groups
- Barcodes
- Pictures
- Tables
- Field group
- Service fields
- Index fields
- Link to an existing field
- Fields without a region
- Creating a field with a non-rectangular region
- Fields with several instances
- Fields with several regions
- How to change a field name
- Copying, moving, deleting fields
- Exclusion of a region from recognition
- Document Definition Wizard
- Editing and publishing a Document Definition
- Creating Document Definitions
- Document Definition properties
- Properties of a Document Definition section
- Rule validation
- Export settings
- Configuring data presentation in the document window
- Testing Document Definitions
- Localizing a Document Definition
- Classification
- Field extraction training
- Operating a configured project
-
ABBYY FlexiCapture for Invoices
- Features of ABBYY FlexiCapture for Invoices
- How to capture invoices
-
How to set up an invoice capture project
- Country and language settings
- Connecting vendor and business unit databases
- Data export settings
- The status of documents in ABBYY FlexiCapture for Invoices projects
- Training ABBYY FlexiCapture for Invoices
- Rules
- Capturing additional invoice fields
- Purchase Order Matching
- Enabling additional program features for operators
- Using multiple Document Definitions
- Editing invoice processing settings in XML files
- Updating the Document Definition for invoices
- Tax systems
- Specifications
- Capturing receipts
- Capturing purchase orders
- Using NLP to process unstructured documents
- ABBYY FlexiCapture interface
-
Appendix
-
Using scripts in ABBYY FlexiCapture
- Specifics of scripts written in .Net languages
- External assemblies
- Object model
-
Scripts for customizing processing stages
-
Types of scripts
- Script rule
- Autocorrection script
- Export script
- User script (custom action)
- Document assembly script
- Custom recognition script
- Stage rule
- Processing scripts
- Data set update script
- Data set validation scripts
- Document classification script
-
Event handlers
- Batch created
- Batch deleted
- Batch parameter change
- Batch structure change (page added/page deleted/document added/document deleted)
- Pages moved
- Batch opened/closed
- Batch integrity check
- Document parameter changed
- Document state changed
- Export completed
- Script that is run after rule checks
- Before matching
- Field verification request
-
Objects
- IActionResult
- IAssemblingError
- IAssemblingErrors
- IBatch
- IBatchCheckResults
- IBatchItem
- IBatchItems
- IBatchTypeClassifier
- IBatchTypeClassifierResult
- IBinarizationParams
- IBoxedBoolean
- ICharacterParams
- ICharactersParams
- ICheckmarkGroupValue
- ICheckmarkValue
- IDataSet
- IDataSetQuery
- IDataSetRecord
- IDocument
- IDocuments
- IDocumentExportResults
- IDocumentsExportResults
- IDocumentDefinitionInfo
- IDocumentDefinitionInfoArray
- IEditablePictureObject
- IExportFieldsToRedact
- IExportImageSavingOptions
- IField
- IFieldRegion
- IFieldRegions
- IFields
- IFlexiCaptureTools
- ILocalContrastParams
- IMatchedSectionInfo
- IMatchingInfo
- IPage
- IPageClassificationResult
- IPages
- IPictureObject
- IPictureObjectsInfo
- IPrincipal
- IPrincipals
- IProcessingCallback
- IProject
- IProperties
- IProperty
- IPropertyModificationInfo
- IRecordCheckResult
- IRecordset
- IRect
- IRects
- IRoutingRuleResult
- IRuleContext
- IRuleError
- IRuleErrors
- IRuleTag
- IRuleTags
- IScriptBinaryAttributes
- IScriptDefinitionContext
- ISectionDefinitionInfo
- ISectionDefinitionInfoArray
- IShadowsHighlightsParams
- IStageInfo
- IUserAttachment
- IUserAttachments
- IUserSessionInfo
- IValue
- IVARIANTArray
- TAssemlingErrorType
- TBatchItemType
- TColorToFilter
- TExportFieldType
- TExportType
- TImageCompressionType
- TPageClassificationType
- TPdfAVersion
- TPdfDocumentInfoType
- TPdfTextSearchAreaType
- TPrincipalType
- TProcessingPriority
- TPropertyType
- TRuleErrorType
- TStateType
- Sample scripts
- Internal names of recognition languages
-
Types of scripts
-
Scripts for processing interface events
-
Event handlers
- On Document Closed
- On Project Closed
- On Activate Document
- On Field Control Activate
- On Return From Task
- On User Command
- On Field Control Deactivate
- On Closing Document
- On Task Close
- On Closing Project
- On Region Change
- On Task Window Mode Changed
- On Open Document
- On Task Window Create
- On Task Reject
- On Region Control Draw
- On Task Send To Stage
- On Text Field Validating
-
Objects
- IBoolean
- IBoxedFieldControl
- IDocumentEditor
- IDocumentItem
- IDocumentItems
- IDocumentsCollection
- IDocumentsWindow
- IDrawContext
- IErrorControl
- IErrorControls
- IErrorsWindow
- IFieldControl
- IFieldRegionControl
- IFieldRegionControls
- IFormWindow
- IImageWindow
- IMainMenu
- IMainWindow
- IMenu
- IMenuItem
- IPageControl
- IPageItem
- IPageItems
- IPagesCollection
- IPoint
- ISelection
- IShellRational
- IShellRect
- IShellRects
- ITaskWindow
- ITextEditor
- IToolbar
- IToolbarButton
- IToolbars
- TCommandBarType
- TCommandID
- TDockingType
- TDocumentState
- TErrorType
- TSelectionType
- TTaskWindowMode
- TTextSize
- TUserRole
- TWorkWindowType
-
Event handlers
- User scripts for the Web Verification Station
- Creating a machine-readable form
- Hot keys
- Additional options
- Description of Processing Server commands
- ABBYY FlexiCapture sample projects
- Supported recognition languages
- Supported classifier languages
- Fonts for correct characters rendering
- Supported text types
- Supported barcode types
- Supported input formats
- Processing PDF files
- Export file formats
- Date formats
- Alphabet used in regular expressions
- Patents
- Third-party technologies
- Glossary
- Technical support
- How to buy ABBYY FlexiCapture
- End-User License Agreement (EULA)
-
Using scripts in ABBYY FlexiCapture
Enabling additional program features for operators
The administrator may enable additional features for operators that will be processing invoices. Note that these additional features are always available to users with administrator permissions.
Training the program while processing invoices
If the results of automatic field extraction are below the expected standard, the operator can additionally train ABBYY FlexiCapture for Invoices while processing invoices. In the process, new FlexiLayouts are created which can then be used instead of the regular FlexiLayout. See Training ABBYY FlexiCapture for Invoices for details.
To enable the additional training feature, complete the following steps:
- In the main window of the Document Definition editor, select Document Definition → Document Definition Properties....
- In the dialog box that opens, click the Document Definition Settings tab.
- Click the Edit... button next to the Additional Fields and Features group to open the Document Definition Features dialog box.
- Select the Training during processing option.
Note: To disable the additional training feature for operators (if enabled), clear the Training during processing option.
If a verification operator changes the field mark-up on a document image, then, at the training stage, this document will be copied into the training batch used for this document variant. Every first and second document thus added will be assigned the "For training" status, and every third document will be assigned the "For testing" status.
Note: Training is done independently for each document variant. Invoices from the same vendor are regarded as the same document variant.
The quality of the newly trained model will be tested on the documents which have the "For testing" status. The program will compare the number of fields that have been correctly matched. If the newly trained model delivers more correctly matched fields than the reference model, the new FlexiLayout will be saved and will be subsequently used for this document variant (i.e. for processing invoices from this particular vendor). See Training while processing documents for details.
Modifying and adding vendor and business unit records
When setting up your invoice capture project, you connected vendor and business unit databases to the corresponding data sets of the project. These data sets specify the structure of data and store a copy of the data inside the project, periodically synchronizing them with your external database. See Using vendor and business unit databases.
Invoice recognition starts with finding the vendor and the business unit. These field groups can be found on an image only if they are present in the data set. It is important that the program find the vendor and the business unit because these data are used to select the country of the invoice, which determines the tax rates used in finding the Amounts fields on the image and the choice of validation rules.
As a rule, all vendors and business units will be already included in the corresponding data sets. However, if you get an invoice from a new vendor which is not in the database, the group of Vendor fields will not be detected. Depending on the business process, adding the new vendor to the vendor database and synchronizing it with the data sets may take a long time, and the program will not be able to process invoices from that vendor until it finds the vendor in the data set.
A further example involves the change of address or account number of an existing vendor. Updating the vendor database and synchronizing it with the data set may take a long time, and the Operator needs the up-to-date information to be able to process invoices.
To resolve the above issues, 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.
If an Operator adds a new vendor to the data set, the program will be able to detect the Vendor group of fields on subsequent invoices from that vendor, just as if there was a record for the vendor in the external vendor database. However, the validation rules will detect that the vendor is missing in the external database and assign the Exception status to the invoice.
Next time the data set is synchronized with the external database, all vendors added by the Operators will be replaced with the appropriate records from the database or removed from the data set. See Updating data sets for more about updating data sets.
By default, Operators cannot edit or add new records to data sets. To enable this feature for Operators:
- In the main window of the Document Definition editor, select Document Definition → Document Definition Properties....
- In the dialog box that opens click the Data Sets tab.
- Select a data set from the list and click the Set Up... button.
- Enable the Operators can add records and/or Operators can edit records option.
If you do not want Operators to add or edit data sets, make sure these options are disabled.
3/2/2021 8:10:42 AM