just a user - yes it definitely happens, particularly if the field is blank and you load the MD+ entries. I haven't observed as much as you have about categories, but the way you describe it, it might be MD+ downloading the older transaction that would normally be called a "duplicate", but seeing the category difference, it may be used as a "new" download. (I do not say this definitively)
It's not really a bug with Moneydance and "technically" not a bug with MD+, it's the fact that both treat what you are downloading from the bank as primary information. I could see it being reversed, but I think that would be a suggestion versus a bug fix.
I disagree that this isn't a bug. This happens to old reconciled
transactions. I saw this again this morning on transactions from last
September. It changed the category to something different and after I did
the 'enter' to edit it reverted back to the category I had assigned. These
transactions do not show up as duplicate. You would never know that
something was changed unless you go back and check. And this doesn't happen
with all transactions, only some.
I haven't checked the reporting yet, but this is a major issue IMO.
Moneydance is proactively changing categories on old reconciled
transactions. How am I to trust that income/expense reports are correct if
MD is changing the categories for me?
I never saw this problem before subscribing to MD+, so I'm assuming it's
related. I wonder how far back MD goes when processing downloading
I hope somebody from Moneydance is paying attention to this thread. They
should confirm that MD doesn't touch transactions that have been reconciled.
Maddy on 28 Nov, 2022 02:16 PM
Is it possible that you have the Automatically Merge Downloaded Transactions feature checked, in the Network tab of your Moneydance Preferences?
If so, in order to limit the merge option, you should select Moneydance --> Preferences --> Network and set the option "Only match downloaded transactions when they are at most 'N' days apart" as outlined here. Change the N to 7 or less. This should help limit the possibility of any incorrect merges in future.
The easiest solution to correct a confirmation error would be to create a transaction to replace the one which has been 'merged' and therefore is missing from the register. You may have use your bank statement for the transaction information. Also, amending the settings as I mentioned earlier will help reduce any incorrect merges happening in the future.
I don't have *Automatically Merge Downloaded Transactions* enabled.
The 'easiest solution' you mentioned isn't the easiest, because
transactions are getting updated without me knowing about it. I don't have
any missing transactions in the register. An existing, reconciled
transaction is modified MD without any user input.
Moneydance is changing the category/memo field for a reconciled
transaction. That seems like a bug to me and should be fixed.
I’ve noticed that if you try to change the memo or category BEFORE you confirm a txn then it gets overwritten once you confirm a txn. I’ve learned that if I’m not merging a txn, to hit confirm or CMD-enter and then edit memo or txn.
I have also seen this type of problem with credit card transactions downloaded with MoneyDance+. When I download a transaction, change the memo and/or category, either or both will change when confirming the transaction. In response to two earlier posts, I do not have Automatically Merge... enabled and have changed the Only Match Transactions... set to two days.
I will try the suggestion from Stuart.
I consider this a serious bug. It requires time and attention that should not be necessary when using MoneyDance. In this forum, there are a number of other reports of what seem to be the same bug.
I am using MoneyDance 2022.5 4091 and macOS 13.1.