Where a tagging rule is not configured, Insights offers a solution based on previous actions (“A similar transaction to this was previously tagged…” prompt). This is good. Where a purchase invoice exists, and there is no tagging rule, the prompt “One or more unpaid purchase invoice matches this amount” is shown. This is also very good. But when there is a matching bank tagging rule AND a pre-existing purchase invoice, there is no indication that this purchase invoice is a potential match. The tagging rule should check whether there are any potentially matching purchase invoices that also match the tagging rule, and display that as a first option. Otherwise a duplicate purchase invoice is created.
Tagging Insights is a very good new feature but it’s now the case that the old bank tagging rules are often counter-productive when there is a conflict. The workaround is to turn off all rules for which there may be pre-existing invoices, and make use of Insights (that match more intelligently). It would be good if that wasn’t necessary, case by case.