Are you considering invoice automation but don’t want to limit your options for going from E-Business Suite to Fusion ERP Cloud down the road? Conversely, if the decision has already been made to make that shift to the cloud, what are the next steps when it comes to invoice automation? Does your current solution integrate with Fusion ERP Cloud? If so, is that integration certified? Do you want to take this opportunity to upgrade or replace your existing invoice automation solution? What have you considered in terms of process change?
To keep things simple, yes there is an integration change between E-Business Suite and ERP Cloud (Fusion). Many connections to Oracle E-Business Suite could be done at the database level with a DB Link and then methods for getting invoices in varies from inserting records into the Open Interface Tables to provision of a flat file that needs to be uploaded. Oracle ERP Cloud still provides those integrations for inserting invoices, they are just via an API, which can be a two-way integration or using the FBDI (File Based Data Import) function to load records, one-way integration.
The main difference though between EBS and ERP Cloud is that you no longer have direct access to a database. The data extraction method is different, and this is a key factor that needs to be overcome by the solution that you are considering. There are ways to automate this integration and a solution can be connected within hours to your ERP Cloud environment. The key thing to look for when you integrate your Invoice Automation solution is whether the application has a certified integration. How can you check this?
Depending on when you implemented your existing invoice automation solution, it could be that it has reached the end-of-life stage. If you implemented the solution in the past 3-4 years it could be that you are already running a SaaS invoice automation solution.
If the solution is currently on-premise then you have a more important decision to make. Is the current solution worth upgrading to the provider’s latest solution, which you would hope is cloud-based, or do you implement it with a new solution that is available in the cloud?
With legacy on-premise applications our view would be that you cut and run, don’t waste time in trying to take your existing hardware and solution and try to connect it to your new SaaS ERP Cloud environment. The market has changed and keeping on-premise applications that were often resource heavy doesn’t reflect current standards.
The likelihood is that you are running a capture application for scanning, an OCR application to read and index the document and then finally a workflow and document management application to route and store the document. This is overly complex and only benefits businesses with high volumes. New models are available and the starting point for purchasing such a solution requires a lower volume.
It’s easy to think that ERP Cloud was based on E-Business Suite and therefore there won’t be many differences. From an invoice automation perspective, there are many differences. See our blog on whether IDR works for you to see some of those differences and challenges. There are some data differences or nuances when it comes to ERP Cloud. Is your solution provider aware of these? Have you considered line descriptions on invoices that need to match the PO for insertion into ERP Cloud?
This is why our recommendation is to always ensure you are working with a provider that has specialist knowledge of your ERP. Be wary of any provider that says “We integrate with everything”. There is a difference between connecting with an ERP and integrating with an ERP. The former tends to mean a one-way “integration”. The latter will be a two-way connection with a proper handshake between the applications in the event there is ever an issue with resolving an invoice.
Too often issues occur with an invoice that requires a resolution in the open interface causing an invoice to be ”stuck” or “lost”. Ensure the solution you implement can feedback when an invoice is rejected by the ERP.
Going to a new ERP will inevitably mean that you have the opportunity to change your business process, you can even take the opportunity to onboard a new solution. Review whether No PO No Pay could be introduced to get a closer hold on spending. Reduce the number of blanket Pos with reversed Quantity and Unit Price. Process change is inevitably harder than trying to implement what you did before, however, too often companies are restricted by a department’s lack of willingness to change.