duplicate payment analytic<\/a><\/strong>. It now uses artificial intelligence to improve the quality of the results.<\/p>\nThe liberal search strategy and false positives<\/h2>\n
In the mentioned analytic, we put great emphasis on not overseeing any true duplicate payment, that’s why a liberal search strategy<\/strong> is necessary. This has the disadvantage that many so-called false positives are found. These are found duplicate payments, which actually turn out to be none.<\/p>\nVarious attempts to filter out false positives based on rules have failed because the defined rules were too static.<\/strong><\/p>\nAn example:<\/strong> If one would like to exclude invoices of recurring payments (e.g. for rent or garbage fees) from the result, it would be reasonable to apply the following rule: If for several invoices the vendor and the amounts are identical and the dates (in the document date) are either 30 or 31 days apart, then it is not a duplicate payment.<\/p>\n In short:<\/strong><\/p>\nVendor identical & amounts identical & document dates 30 or 31 days apart -> No duplicate payment\u00ad<\/em>\u00ad<\/p>\nThe problem:<\/strong> In general, real duplicate payments exist that meet these conditions.<\/p>\nThe example illustrates how difficult it is to define generally valid rules.<\/p>\n
\u00a0<\/p>\n
Using AI in your duplicate payment analysis<\/h2>\n
Whenever defining rules causes problems, it makes sense to think about using an AI<\/strong>. The result of our analytic so far has shown a ratio of true duplicate payments to false positives of:<\/p>\n\u00ad1 to 10<\/strong><\/p>\nSo on average only every 11th finding<\/strong> is an actual duplicate payment.<\/p>\nIn order to provide our customers a better analytic, we have added an AI to the analytics. It reduces the number of false positives by more than 70%. This results in a ratio of:<\/p>\n
1 to 3<\/strong><\/p>\nOn average, every 4th finding<\/strong> is a direct hit.<\/p>\nThus, we save our customers more than 70% of work, because most of the manual reviewing is eliminated.<\/p>\n
\u00a0<\/p>\n
How does the AI work?<\/h2>\n
The mentioned AI learns on a training pool<\/strong> which consists of previously found and labeled duplicate payments and is located exclusively at the customer’s site. That is, each customer of ours trains its own AI on its own data<\/strong>. The mentioned pool is continuously growing, so that the training takes place on an increasingly larger amount of data. As a result, we will be able to improve the stated ratio of 1 to 3 once again in the future and thus offer an even more comfortable result, because a decreasing number of false positives will have to be reviewed.\u00a0<\/p>\nTackle your duplicate payment analysis with dab<\/h3>\n
Are you interested in an analytic that reliably identifies double and multiple payments? Then please feel free to contact us.<\/p>\n\n\n