Duplicate transactions when categorizing
I get duplicate transactions when I do the following:
1. Download the transactions for multiple accounts
2. Find a transaction in one account which is a transfer between two accounts, and categorize it as a transfer to the other account.
This happens with paying credit card bills, transfers from checking to savings, etc. Let's take savings/checking as an example. Each time I categorize a transaction in the checking account as a transfer to the savings account, MoneyDance adds a transaction in the savings account. But there is already a transaction in the savings account that represents that deposit. So I have to go and manually clean it up by deleting the deposit that was downloaded from the bank. Is there any way MoneyDance could be smarter in this regard? Like if it sees an existing transaction on the same day for the same amount it could recognize the association? Or even ask about it? This is really annoying.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by dwg on 20 Dec, 2024 11:04 PM
When using the confirmation process in Moneydance part of this process is the merge function and you use this to merge the transfer created and the downloaded transactions into one.
This ensures that you have the transactions linked between the two accounts as they should be and that any unique identifiers in the downloaded transaction are kept to prevent the transaction downloading again.
2 Posted by erik on 22 Dec, 2024 09:06 PM
OK I will pay more attention next time I have transactions to confirm, thanks.
Support Staff 3 Posted by Ethan on 23 Dec, 2024 03:20 PM
Just to add: You should temporarily have a duplicate transaction if you are confirming correctly. In the first account you confirm, once you set one of these transactions to the second account in the category field (or if Moneydance automatically guesses this based on past transactions), the 'other side' of this transaction will appear in the second account. Then when you go onto the second account, one of the options for confirming the transaction downloaded into that account should be to merge with the 'other side' of the previous transaction.
You can minimize the amount of time these potential duplicates are in your registers by going through the confirmation process for all of your downloaded transactions in all accounts shortly after downloading.
Ethan
Infinite Kind Support