![]() ![]() ![]() Then the development team can onboard additional vendors and increase the amount of non-PO invoices that can be automatically processed by a bot. This allows the team that had been processing invoices manually to have the bandwidth to manually check only the invoices the bot can not process. By analyzing the process to find which non-PO invoices require the most time, they can be targeted to be automated first. Their workflow is designed to handle a variety of Non-PO Invoices and do as much of the task as possible, if the bot is unable to continue processing an invoice it can defer the invoice for manual processing.īy designing the bot with a failsafe, like manual processing, the bot can be designed and deployed quickly to address the bulk of the issues. With this automation TCS estimates it would reduce invoice processing time by 60% by removing the repetitive, no-value-added tasks. The TCS team developed a bot to automate Non-PO Invoicing in Ariba. In our third post we will spotlight the use case from Tata Consultancy Services (TCS). Over the next few weeks I will be sharing use cases in a series of use case spotlights. This Hackathon challenged partners to design and develop a use case for automation with Ariba. You can view the summary of that Hackathon in this blogpost from the Co-Innovation Lab. In early December we had a Hackathon with SAP partners that was focused on using SAP Intelligent RPA with SAP Ariba.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |