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 manually entered transactions. There was checks to prevent it in at
least 3 different locations.
Is there a subtle bug that creeps in if these checks are removed?
If there is no (remembered) reason to prevent the matching of imported files
then I suggest this "feature" be removed. Though this feature is documented
there is no documentation I could find that gives a hint as to why.
Chris
On 25/04/2014 10:13 AM, Chris wrote:
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 account to the credit card
Both are on the same date with the same amount the only differences are
the memo and payee fields
They should have automatically matched. but didn't and I assume because
they are both imported I cannot manually match them.
Questions
1/ How can I correct this?
2/ What is the thinking behind disabling the matching when both are
imported or manually entered?
documentation is here..
http://docs.kde.org/stable/nl/extragear-office/kmymoney/details.ledgers.match.html
_______________________________________________
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
