The current bank rules only so simple string matching.
With for example the Dutch tax agency, you cannot use this, as the string differs in between:
(basically: tax return (some digits) vat, or: tax return (some digits) wages)
This could be fixed by either allowing wildcards tax return * vat, or regular expressions.
I know most people don’t really understand regular expressions, but there’s another case for this:
If I receive a transaction with the description INVOICE20190029, I think it makes sense to allocate this to debtors -> debtor -> matching invoice
With regular expressions we can use a (named) capture group. When using names, we can use different specifiers for this:
Payment for INV20190123 regarding something
Another thing I’d like to add is the source / destination bank account (With my .sta files it’s not imported, so I’m not sure if this would actually help anyone). For this, I could use a capture group with the IBAN of the debtor. something like debtorIban.
The different kinds of matching methods should have a dropdown with the type (normal, wildcard support, regex) to be backwards compatible and still easy to use