Ethan on 03 May, 2021 01:44 AM
I'm not quite sure I understand. If you have a manually entered transaction, or one created from a reminder, or any source really, if you download a matching transaction from your bank, you should be able to merge that transaction with the existing one in the confirmation process.
I'm not yet a moneydance user, but I'm seeking clarification of this question before I get on board. Are transaction merges for similar/duplicates NOT possible after they have been added to the register? Is merging transactions in the register only possible in relation to transactions that are sitting in a queue reserved for related transactions that were just manually or automatically downloaded from a financial institution?
Merging works on any txns downloaded that have not yet been confirmed (or merged). Once they are confirmed (or merged) then that's it... But.... if you then download again (the same txns) then you can again do the confirm/merge... Does this help..
Put differently, you could for example, work manually for years, then download a OFX file from the bank and it will offer to confirm/merge all these downloaded...
That helps, but now I'm concerned that the workflow will be cumbersome when lots of transactions are involved with similar data. I'd prefer for existing and new transactions to just be sorted together by date order in the register so I can efficiently choose what matches with what, without bothering with a cumbersome interface with unnecessary little split-screens that wants to make questionable recommendations for me. Does that make sense? Can you share an opinion? Thanks.