Hi Jack
I suspect you are correct. I was hoping someone would recall the reasoning
so we could work on a fix with all the necessary info.
If the reason has been lost in the mists of time. Then I'll clean up my code
changes (which were very rough just to do the testing) and put it in for revie
I vaguely recall that this has come up before, with about the same
(lack of) remembered reason for the restriction. However, given that
you found multiple explicit checks, whoever developed that bit of code
must have had a reason, although perhaps we are lucky enough that it
simply doesn't
No Takers?
I have commented out the checks that prevent the matching of imported
transactions. KMM then correctly manually matched the transactions. I
haven't had the opportunity to test matching during import.
So the remaining questions is why was matching disabled on two imported or
two ma
Hey all
I am having an issue with imported transactions not being automatically
matched and manual matching is disabled.
both transactions are the result of seperate imports one from my credit card
statement the other from a bank statement
both transactions are for a payment from my bank ac
