| Status | |
| Owner | |
| Stakeholders |
Issue
Syensqo's Currently use Readsoft for Invoice processing and this covers two areas of functionality
- Readsoft Process Director for Invoice Management: Processes and approves supplier invoices.
- Readsoft OCR: For scanning paper and PDF invoices into the system.
Situation: With the move to S/4 HANA Private Cloud, this setup needs review to see which tools work best for the future setup.
Recommendation
The recommended option is to
- Use Open|Text VIM (aka SAP IM) for Invoice processing as its better integrated to S/4 HANA Cloud editions and already has Fiori Apps.
- Use the OpenText OCR as using the same provider for both processing and scanning ensures better compatibility, easier upgrading/patching going forward and minimises licence costs
- ECC will continue to use Readsoft and as users switch over to the S/4 HANA they will use Opentext.
As the recommended SAP option for S/4 HANA Cloud - OpenText/SAP IM for Invoice Processing due to its greater compatibility with S/4 HANA Cloud editions.
replacing Readsoft to ensure smoother implementation and synchronised Upgrades & Patching
Background & Context
Invoice Management Tool and Invoice approvals
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 htem 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
- PO Based Invoices where there is a price discrepancy
- PO Based invoices where there is a quantity discrepancy or no GR has been entered
- Non PO Based Invoices that need to be coded to a cost object and approved by the cost object owner
Users will need a tool in S/4 HANA (essentially a Fiori App) to send invoices for processing and approval and for approving or rejecting the Invoices.
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. This should be available to work with the three invoice scanning centres.
OCR Tool
Technically both Readsoft and Open Text can supplier both or either component, but using differnt vendors (eg Readsoft for OCR and OpenText for Invocie Mgt) leads to a more complex system and incerased licence costs. So its 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 scanned (ie not EDI, Ariba Network, Govt Portal etc) will go through the OCR system.
Options:
- No Invoice Approval Tool:
- Continue with current OCR setup
- Likely impractical due to high invoice volume
- Non-SAP 3rd Party Tool:
- Not advisable
- Significant effort to integrate with S/4 HANA Cloud and Fiori
- SAP Recommended Tools:
a) Readsoft:
- Handles both scanning and invoice processing
- Currently installed globally - Syensqo has system experience and is currently integrated to many invoice flows
b) OpenText:
- Handles both scanning and invoice processing
- Not currently installed/integrated
- SAP's preferred option (marketed as SAP IM)
- Strategic agreement between SAP and OpenText
Key Points:
- Readsoft and OpenText offer similar functionality
- Both can handle OCR scanning and invoice approval
- Syensqo already already uses Readsoft
- Opentext currently is better integated to S/4 HANA Private Cloud Edition (uses Fiori Apps, cloud native architecture)
Assumptions
No Invoice Management Tool
The volume of invoices that will require some kind of approval will be too high for a purely manual process, so not having any invoicing tool is not practical
Non SAP Tool
A non SAP recommended tool is not viable due to the expected effort to integrate with S/4 HANA.
Different vendor 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
- Potential gaps with dataflows, error handling & workflows
- Custom integration/Middleware
- Compatibility issues
- More complex implementation
- More complex Upgrades & Patching
In addition OpenText gives both OCR and Invoice Processing as a single licence.
So there would be a cost implication to using Readsoft for OCR and OpenText for Processing.
Constraints
The Invoice Management tool should be
- Able to handle invoices coming into the system from a number of sources - eg eMail PDF scans, Government Portals, SAP Business Network, EDI Inputs
- Able to ID the correct approvers and transmit Invoices to them with minimal manual input
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.
Impacts
If the invoices are not processed and approved in a timely fashion then the suppliers of Syensqo may begin to refuse to supply Syensqo and so cause disruption to the business
If the Invoice Management tool cannot reliably receive inbound interfaces from all the inbound processes and networks then invoice payments may be delayed
If the Invoice Management tool is not reliable or does not integrate to SAP smoothly then invoice payments may be delayed.
If the tool is not reliably integrated with S/4 HANA Cloud then errors and lost data could occur causing disruption and delays to payments to suppliers.
Business Rules
All PO related Invoices that have differences outside of tolerance levels will require approval.
Invoice payments on time are tracked and monitored for compliance with local prompt payments standards so timely payment is a requirement.
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
Options considered
The following options were considered
Option A: Use Readsoft OCR and Process Director for Invoice Management
Use one of the tools already recommended by SAP and (where possible) approved or validated for working with S/4 HANA Cloud
Note that currently only OpenText is validated as the preferred tool for S/4 HANA Cloud - but the actual selection of Readsoft or OpenText can be handled at Detailed Design
Option B: Use OpenText OCR and VIM for Invoice Management
Use one of the tools already recommended by SAP and (where possible) approved or validated for working with S/4 HANA Cloud
Note that currently only OpenText is validated as the preferred tool for S/4 HANA Cloud - but the actual selection of Readsoft or OpenText can be handled at Detailed Design
Evaluation
Use SAP Readsoft Process Director & OCR | Use SAP OpenText VIM & OpenText OCR | |
|---|---|---|
Invoice Document Functionality MM Invoices FI Invoices DownPayments |
|
|
Non Invoice Documents Assets POs GRs Customer Orders/Payments |
|
|
| Syensqo Knowledge |
|
|
Other Functionality |
Customisable Workflows Reporting tools Code exists inside SAP
|
Customisable Workflows Reporting tools Code exists inside SAP
|
| Syensqo Integration |
|
|
| Adaptation to Cloud |
|
|
| Standard Fiori Apps |  Con Web based UI (not common look and feel with S/4 HANA Fiori, is developing Fiori Apps for Process Director |
|
Pro MM InvoicesSee also
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.
