Categorize history is lost while in import
During a normal creation of a transaction, several histories,
both of the description and category, are offered.
If I do an import of transactions (from a bank), and the
description and category that I want aren't already there, and I
try to change it, Moneydance can't access the history. For instance
the bank creates a transaction for banking fees that always comes
something like this "CHECK IMAGES IN STATEMENT FEE" which I change
to bankfees. If bankfees isn't in the list for import, and I try
edit it, Moneydance can't provide the history it otherwise would
offer. Is this a bug or....
Comments are currently closed for this discussion. You can start a new one.
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 -Kevin N. on Dec 27, 2010 @ 03:19 AM
Hi agabhart36
If I understand you correctly, look to File > Preferences > Network tab, put a check mark next to 'Automatically Merge Downloaded Transactions' This will tell Moneydance to 'Learn' similar imported transactions and in time MD will offer up those entries (Descriptions & Categories) that you made in previously entered transactions.
HTH -Kevin N.
2 Posted by agabhart36 on Dec 27, 2010 @ 02:58 PM
You are correct. I didn't have that check mark. Now, I say it should be accessing the other payment history, instead of building a second payment history. For instance, I have several utilities that I and most everyone pay every month. This new history couldn't access that old history, I had only made a payment 1 month before, so it incorrectly tried to categorize it. If I had written it by 'hand', the category would've been matched correctly and for as many years as I have in my register - not the 90 days in this history. Another case is I have only needed to pay the I.R.S. once per year. With this payment history system, it wouldn't find that record. I am also wondering why you don't make the history more universal. Why not reduce the redundancy?
3 Posted by Tom Freeman on Jan 05, 2011 @ 08:59 PM
When you down load transactions from a bank and edit the description file, Moneydance remembers both the banks description and edited one.
When you import from another program or hand enter transactions the descriptions are not remembered.
Keeping tract of description histories is somewhat complicated. The bank uses a simplified and consistent description that Moneydance can easily track. On an import, the original banks descriptions don't import over. So the history log starts over. Its a complex algorithm that is finely tuned. It works well in some situations but not in all situations.
Tom
agabhart36 closed this discussion on Oct 24, 2013 @ 04:36 PM.