According to this whitepaper, a typical medium-sized organization loses $300,000 per year because of invoices that are paid twice. Most ERP systems try to prevent this by not letting you enter the same invoice reference twice for the same vendor.
What if the vendor exists twice in the master data with a slightly different name? Or a typo is made when entering the invoice? Or your OCR software reads a 7 as a 1?
For a lot of organizations this means you’re out of luck, and unless the accounting department manually finds out the invoice is a duplicate, you might be paying twice.
In this blog post I will show you how to use fuzzy matching to find duplicates using the Celonis Intelligent Business Cloud (IBC) and Python. If you have your Accounts Payable process in the IBC, this becomes very easy by just following these five steps:
1. Filter out irrelevant invoices
Using Process Analytics, we can quickly select the most relevant invoices. In the image below, you could select the activity “Pay Invoice,” so that invoices that are still being processed are ignored. Furthermore, we can select invoices with a value >€100, since we still need to do some manual work to verify whether results are true duplicates. (We only want to check them if the manual work is worth it.)
To narrow down further, we can remove things like:
3. Run the duplicate checker in Python
Finding the duplicates using default settings is as simple as running nine lines of Python code:
Anyone who knows the basics of Python can use this package. To give a brief overview of what happens:
3b. (Optional): Specify search patterns and similarity algorithms
This piece is a bit more technical; feel free to skip it!
By default, the duplicate checker finds duplicates by:
4. Check whether results are really duplicates
After running and fine-tuning the duplicate checker in Python, it’s time to verify and act on true duplicates. In Celonis Process Analytics, we can analyze the groups of potential duplicates, find cases with a high potential savings value and either drill down or directly go into the ERP to take action.
5. Take action
Using the Celonis Action Engine, relevant accounting employees can be notified directly of a potential duplicate in their business area. From there, they can be linked to the relevant transaction in the ERP to reject the invoice—preventing the duplicate payment from happening before it takes place. They can also mark it as a false duplicate. After doing this for a while we can use this information to make the duplicate checker more accurate.
Celonis customers have already saved millions by taking action on duplicate invoices. If you are an existing Celonis customer and interested in using the Celonis Duplicate Checker, please contact your customer success manager. If you are new to Celonis and interested in seeing how the IBC and Duplicate Checker can benefit you, please get in touch today!
Maybe others you know will also find it helpful.