The most obvious match would be to match any Transfer Accounts in the data to gnu Accounts, even if the result needs to be verified.
Other comments: 1) User's rapid clicks can unintentionally select the wrong account, mapping invalid data 2) Seems there could be an opportunity for user to re-run a process to recreate map and prune the useless matches David refers to ( dates, connectors (a, and, the etc.), transaction amounts ?). With enough transactions this should be pretty good. 3) I assume the table is updated with merged accounts, _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
