Form Recognition
Introduction
Use Form Recognition for processing incoming PDF files and structured email information.
Setup
To start Form Recognition a transport location is required. This can either be a mailbox or a file storage location (SFTP, Azure File Storage and so on). DataHub needs access to that location, with permissions for read/write/delete.
To post in messages from DataHub, access needs to be granted. Think of whitelisting as well.
Processing Purchase Invoices
Setup Matching Codes
The Matching Code (refered to by Vendor Card as Mapping Method) needs 2 functionsets. One for Mapping, one for Creation.
Mapping functions
MatchOcean: matching to existing Cost Lines
004: No matching to existing Lines
Creation functions
003: creation of Purchase Invoice Lines for related Cost Lines
004: creation of Purchase Invoice Lines for (derived) fixed General Ledger Account
Default General Ledger Account can be derived by using functionset
005: creation of Purchase Invoice Lines for Services.
Service will be obtained in following ways:
Search Services by Code and Service Description (either with entire Line Description or with first x characters)
Search Services by using DI Mapping
Default service, can be derived by using functionset
Setup DC Key Values
DC Key Values are used to relate particular keys from Form Recognition to Table Fields of BC365.