Improvements in position recognition
Recognition of multi-row table headers
Whereas previously only one header could be recognised, an unlimited number of headers can now be recognised for each table. A condition for this is that at least two different hints at interpretation concepts can be found in one row.
Definition of parameters and tolerances
Further, it is now possible to define certain parameters and tolerances per business partner within the position recognition matrix. This allows for the recognition to be finely adjusted to the documents of partners and for its further improvement. Currently, parameters for the influencing of the column calculation and running-text identification exist. This function will be expanded with additional options in future updates.
Business partner whitelist
Position recognition can now be activated for individual business partners. If the whitelist has been activated, position recognition is applied only to partners contained on it. The previous recognition logic will be applied to all others. Thus, it is possible to roll out the new recognition step-by-step. The whitelist is independent of the system and can be edited for each system without transport requests.
- Columns can now be allocated to several recognition concepts
- Data contained in a column is allocated to its applicable column heading
- Improved Regex generator
- Improved allocation of order positions to the recognised positions in the table
Expansion of the recognition logic of the talkENGINE
Multi-line Regex entries
Normally, it is assumed that lexicon entries and Regex patterns only appear in one line in the talkENGINE. With the addition of multi-line Regexes, it is now possible to find terms that are split across two lines. This enables, for example, the capturing of column headings exceeding one line.
Implementation of the foundation for the correspondence function
Fast and simple communication with suppliers or team members directly in SAP
Within the correspondence function, e-mails can be captured within a process. The processing of e-mails can be supported by customer-specific text templates and an attachment option. Replies are automatically allocated to the respective process. All e-mails are archived in .EML format and thus remain accessible at all times. The integration of a separate e-mail address in the SCOT in SAP, via which communication can be controlled, is required for this.
Implementation of the technical foundation
The dunningLINE can be linked to an existing scanning and archiving infrastructure via SAP® ArchiveLink. Through free-form recognition and the connected mapping of all pertinent information of a dunning notice, the dunningLINE records the values contained in dunning notices, which previously had to be done manually. Moreover, dunning notices and the original invoices are connected in the invoiceLINE, which fosters an homogenous and interactive interplay between dunningLINE and invoiceLINE.
Please note: The dunningLINE offers a solution for the automated processing of inbound dunning notices in the SAP® environment and should be considered an independent extension of the invoiceLINE that must be licenced separately.
Readiness for S/4HANA 2020
The coding of the invoiceLINE was adjusted to meet the S4/HANA 2020 readiness guidelines.
Notification “duplicate invoice”
Pop-up with more information concerning the notification “duplicate invoice” can now be opened via the notification box.
invoiceLINE processes can be converted in dunningLINE.
Support for multiple new ZUGFeRD (2.0 and 2.1) versions have been added.
Magic-byte assessment now supports multiple versions of the XRechnung. Further, the HTML visualisation for XRechnungen was equipped with multiple additional spaces for service duration and delivery information
Accounting upload via Excel files is now possible.
IBANs and VAT IDs can be memorised in manual learning processes.
There are new filter categories for the display of processes booked blindly. Further, filters now show the number of processes within a filter category.
Additional columns with tracking information can be displayed. Further, there is a new function for the pushing-back of a process into the team pool.
Company-code change can also be carried out in the return flow. Brief text templates can be stored for specific company codes. The documentation type of a process can be changed in the return flow.
All rights reserved. Transfer and duplication of this publication, in whole or in part, are prohibited for any purpose and in any shape or form without the explicit, written consent of the flowDOCS Software GmbH.
We approach our documentation with great care. Yet, it is impossible to entirely exclude the possibility of errors. The following documentation is thus provided without warranty for the correctness and completeness of the information given. The user alone assumes responsibility for the verification of the latter.
The flowDOCS Software GmbH only assumes liability for damages resulting from the use of this documentation – regardless of the legal basis – in case of intentional or negligent behaviour. The liability of the flowDOCS Software GmbH is otherwise foreclosed. The flowDOCS Software GmbH does not take responsibility for the content of third parties, which may be cross-referenced in this documentation.