Even for the „old“ Navision!
You know the misery with standard bank statement import, where you try to recognize transfer texts with all sorts of tricks and more and more rules, and the import thus unfortunately only slower and slower, but not always better?
Use my automatic bank statement import!
-Note: Are you already using OP Plus? Congratulations. I can gladly help you with its setup/optimization as well, so that you also achieve minimum detection rates above 80% by means of it-
This attempts very successfully to recognize invoice numbers and customer numbers even when these no need are fully stated. And completely independent of any texts like „Invoice No.“ or „RG-NR.“ or „Customer No.“ or anything like that!
If a customer number has been learned from the invoice number or the customer number from the transfer text, OR entered manually, the link is saved. This way, Navision can now identify transfers from this customer in the future completely independently of the transfer text. In the future, it will not matter if the customer has entered any meaningful text at all in the transfer text!
This makes Navision technically far superior to bank statements in terms of recognition and pre-accounting. Since there are often very few open documents per customer, Navision can then also reliably identify the correct open item, again by reading or, if necessary, „guessing“ from the transfer text.
Customers and suppliers are recognized > 80%(typically: 90% ) automatically after training (one month's bank data can be read in one go), and the correct open items are then also typically assigned correctly to 80% .
As a side effect, most cost postings (e.g., pension fund, gas station statement) can also be assigned to the correct general ledger account. Overall, the time for booking bank statements is usually reduced by more than 50%, depending on the number of bank postings. With 100 postings a day, a time saving of over 80%is also possible.