We have enabled this new feature and are trying to evaluate this usefulness. It may be too soon to tell since the model has not had time to train much. Nevertheless, it seems to be giving a lot of false positives which is creating work without solving problems. Here is what we are seeing:
- Invoices and Journals are identified as having the incorrect amount. This seems to be based solely on previous invoices for the same vendor or journals for the same bank account. While this would make sense for a vendor or journal that was consistently the same amount each month and suddenly the amount changes, but for the most part, the amounts vary from invoice to invoice which is completely expected. Having to clear these as exceptions is not helpful.
- Many invoices and payments are identified as missing. In some cases this makes sense and we can see that we've received invoices every month for a vendor and then there is no invoice for the current month. However, the vast majority of the exceptions are for vendors where it simply isn't detecting the latest invoices and payments. For example, the view details for the exception show invoices from March-August and the exception is that there are not invoices for September and October, but a review of the vendor transactions shows that there were indeed invoices and payments for September and October. Again, this is creating work without benefit.
Should I open a support ticket for these issues? Should I expect this to improve based on my marking the transactions as "No action need"?