| Status | |
| Owner | |
| Stakeholders |
Syensqo currently use Readsoft's solutions for Invoice processing. This covers two areas of functionality:
Situation: With the move to S/4 HANA Private Cloud, this setup needs review to see which tools work best for the future setup.
The recommended is to:
Additionally it appears that OpenText's solution will be more cost-competitive compared to the existing ReadSoft product being used today.
All Supplier Invoices have to be processed by the Invoice Management tool - it validates the invoice data and runs any approvals queries etc for Supplier Invoices before posting them in the SAP Accounts Payable module for payment.
Invoices flow from suppliers into the Invoice Management tool from a number of sources

All of these processes will need to continue to flow into the Invoice Management Tool regardless of whether Readsoft or OpenText is used.
Supplier invoices coming into Syensqo will need a process to approve invoice in the following scenarios
Users will need a tool in S/4 HANA (essentially a Fiori App) to send invoices for processing and approval and for approving/rejecting the Invoices.
OCR (Optical Character Recognition) is used to scan PDF and paper invoices into the Invoice Management Tool. Whilst an increasing number of invoices will be received via interfaces and so not need OCR scanning, there will always be a residual requirement to bring paper and PDF invoices into the after some kind of OCR processing.
Readsoft and OpenText supply both OCR tools & Invoice Management tools and these can be deployed independently, e.g. using the combination of Readsoft for OCR and OpenText for Invoice Management. This leads to a more complex system and increased licence costs. So it's recommended that the same vendor be used for both
The more important decision is the invoice processing - as all invoices that come in will need to go through the processing, but only invoices that are not in a digital machine-processable format (e.g. paper or PDF) will go through the OCR system.
There are two common choices; these will be evaluated in this document.
Different vendors for Scanning and Invoice Management
Whilst its technically possible to use a scanning tool from one supplier and an invoicing processing tool from another it does cause issues.
The use of two different systems run by different vendors means there are:
The Invoice Management tool should be able to:
Local governments can mandate the use if an Invoice Portal for all invoices to be passed through - so the system will need to be compatible with this.
The system should be able to receive inbound invoices from multiple sources - eg Portals, SAP Business Networks, EDI etc
The system should be certified as compatible with S/4 HANA Cloud Private edition.
If the invoices are not processed, approved and paid in a timely fashion then the suppliers of Syensqo may begin to refuse to supply Syensqo and so cause disruption to the business.
This means that the Invoice Management tool must not have errors or lost data due to unreliable inbound interfaces from all the inbound processes and networks.
The following options were considered. Both of these are part of "Option 3" in the Background and Context section above. The choices of not using any processing tool, or using a tool not certified by SAP for integration, were discounted from consideration.
Continue the use of ReadSoft OCR and ReadSoft Process Director, but integrate these with S/4HANA. Most probably this would require a re-implementation of ReadSoft Process Director due to the different configuration and processes inside the S/4HANA system as compared to Syensqo's existing ECC-based implementation.
Implement OpenText VIM for the invoice processing functionality inside S/4HANA, and supplement this by implementation of the OpenText OCR component to parse incoming PDF invoices. This would cause the ReadSoft solution to be discontinued in parallel with the ECC system where it is implemented today.
Use SAP Readsoft Process Director & OCR | Use SAP OpenText VIM & OpenText OCR | |
|---|---|---|
Invoice Document Coverage |
|
|
Non-Invoice Documents |
| |
| Syensqo Knowledge |
|
|
| Integration |
|
|
| Adaptation to Cloud |
|
|
| Standard Fiori Apps |
| |
| Licence Costs |
|
|
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
