tag:infinitekind.tenderapp.com,2009-01-14:/discussions/problems/831-reports-transaction-descriptions-not-consistent-with-check-registerInfinite Kind: Discussion 2015-03-31T16:05:43Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-02-20T00:30:15Z2010-02-20T00:30:15ZReports - transaction descriptions not consistent with check register<div><p>Maybe not helpful, but are you viewing the register in 2-line
mode (right-click two-line mode)? Each transaction has a second
line called Memo below Description, and I think bank downloads can
put stuff in there too (and they seem to really like ugly ALL UPPER
CASE). If you were in one-line mode, you wouldn't see these
memos.</p></div>ljbtag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-02-20T04:23:28Z2010-02-20T04:23:29ZReports - transaction descriptions not consistent with check register<div><p>I'm having the same problem. The memo field is blank. There is
some data not being copied correctly. I have a suspicion its linked
to another problem i'm having where if i 'clean up the transaction'
before 'accept'ing it, regardless of what version I pick in the
dropdown before clicking the button, the downloaded text will
replace my cleaned up version.</p>
<p>MD ver2010r2 (735) on Mac OS X 10.6.2.</p></div>Johntag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-02-20T05:00:23Z2010-02-20T05:00:24ZReports - transaction descriptions not consistent with check register<div><p>Yep, mine acts the same as yours John. Seems VERY buggy. If MD
can fix those little bugs I think the program will be adequate for
all of my needs.</p></div>michaeltag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-02-20T19:39:11Z2010-02-20T19:39:11ZReports - transaction descriptions not consistent with check register<div><p>I believe this bug with the description reverting when the
unconfirmed transaction is accepted has been fixed in the latest
preview release. Please try downloading the latest preview from the
link below and let me know if it resolves the problem:</p>
<p><a href=
"http://moneydance.com/trac/wiki/Moneydance2010Beta">http://moneydance.com/trac/wiki/Moneydance2010Beta</a></p>
<p>Sincerely</p>
<p>Ben Spencer<br>
Moneydance Support</p></div>Ben Spencertag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-03T04:11:06Z2010-11-03T04:11:09ZReports - transaction descriptions not consistent with check register<div><p>I'm seeing the same thing problem the originator of this thread is seeing. I'm using 2010r3(751).</p>
<p>It looks like the reports are pulling data from some info that is listed inside the transaction details. I can see the original downloaded description and the new edited description when I select a transaction and Show Transaction Details.<br />
</p>
<p>The reports seem to be pulling data from the wrong tag in a transaction. The reports 'Detailed Cash Flow' and 'Detailed Income and Expenses' seem to be looking at the wrong metatag in the transaction detail.</p>
<p>Funny thing though, the 'Transactions' report appears to be pulling the data from the correct tags in all the transactions.</p></div>SteveHtag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-03T05:06:22Z2010-11-03T05:06:23ZReports - transaction descriptions not consistent with check register<div><p>By further search of the forms I stumbled upon <a href="http://help.infinitekind.com/discussions/problems/859-problem-replicatable-description-in-reports-not-matching-check-register">this post</a>. I found that I can fix the descriptions easily by double clicking an accepted transaction as if to edit, then press enter to save changes. The transaction would appear correctly in the Detailed Cash Flow report.<br />
I did a before and after on the transaction details. I found that the tag would not change content. However, the tag would change from the orignal downloaded content to match the earlier DESC tag under the PTXN.</p>
<p>Hope this helps to find a resolution.</p></div>SteveHtag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-03T05:12:38Z2010-11-03T05:12:39ZReports - transaction descriptions not consistent with check register<div><p>oops the system munged my post... the last paragraph should read</p>
<p>... I found that the PTXN-DESC tag would not change content. However, the PTXN-SPLITS-STXN-DESC tag would change from the original downloaded content to match the earlier DESC tag directly under PTXN.</p></div>SteveHtag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-06T15:37:00Z2010-11-06T15:37:00ZReports - transaction descriptions not consistent with check register<div><p>Steve,<br />
Thanks for taking a look at this. Its always nice to have users who like to dig into an issue and work to problem solve as much as we do.<br />
I'm not able to reproduce this error, and had hoped it was fixed earlier this year, would you be willing to send me a stripped down copy of you .md file that demonstrates this problem. Just a few transactions that show the issue is all that is necessary.<br />
Thank you much,<br />
Jon Hoover, Moneydance Support</p></div>Jon Hoovertag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-06T15:37:56Z2010-11-06T15:37:56ZReports - transaction descriptions not consistent with check register<div><p>My email is Jon 'at' Moneydance 'dot' com.<br />
Thanks,<br />
Jon</p></div>Jon Hoovertag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-08T16:04:48Z2010-11-08T16:04:48ZReports - transaction descriptions not consistent with check register<div><p>Steve,<br />
So the process that generates a useful file for me would be the following:<br />
Go to 'file -> save as' and save your Moneydance file under a different name.<br />
Now that you have an alternative copy of Moneydance go ahead and delete all your data that does not directly reflect this problem. This way you can send me your Moneydance file but not risk putting much of your information out there. So all that needs to be in the file is a few transactions that demonstrate this issue.<br />
Once you done that please save the file and pass it on to me and I can take a look at it.<br />
Thank you much,<br />
Jon Hoover, Moneydance Support</p></div>Jon Hoovertag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-09T04:11:22Z2010-11-09T04:11:22ZReports - transaction descriptions not consistent with check register<div><p>OK, here is a representative sample. I wish I could remember when I<br />
applied the updates, but I see the problem seems to have started about<br />
January this year.</p>
<p>Be sure to check the Detailed Cash Flow report.</p>
<p>Thanks, Steve.</p></div>Stevetag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-10T11:05:02Z2010-11-10T11:05:02ZReports - transaction descriptions not consistent with check register<div><p>Steve,<br />
It appears that the information you included did not get attached to your message. Could you try sending it to my private email <a href="mailto:Jon@moneydance.com">Jon@moneydance.com</a> ?<br />
Thanks,<br />
Jon Hoover, Moneydance Support</p></div>Jon Hoovertag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-11T12:01:54Z2010-11-11T12:01:54ZReports - transaction descriptions not consistent with check register<div><p>Steve,<br />
I can see that there is indeed a problem. When you clean up the descriptions by what process are you doing it? Are you doing this during the matching and merging or through some other means?<br />
Thanks,<br />
Jon Hoover, Moneydance Support</p></div>Jon Hoovertag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-11T13:20:40Z2010-11-11T13:20:40ZReports - transaction descriptions not consistent with check register<div><p>I can answer this. Simply by going into the register, clicking on the<br />
transaction, hitting enter (so you hear the cha-ching sound). This<br />
corrects the problem.</p>
<p>So every time I save a transaction in my register I essentially hit enter<br />
twice until I hear the cha-ching sound again.</p>
<p>On 11/11/10 6:03 AM, "Jon Hoover"<br />
<a>tender+d42637e5d3b74329f39f36607245128e1ec766495@tenderapp.com</a> wrote:</p></div>Michael Sledgetag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932010-11-11T20:48:48Z2010-11-11T20:48:48ZReports - transaction descriptions not consistent with check register<div><p>I'm able to fix my transactions as Micheal outlined. Open the<br />
transaction for edit, then simply save it back out.</p>
<p>Maybe something is amiss in the way I get my transactions. Here is how<br />
I do that.</p>
<ol>
<li>When I get my transactions from my bank, I download them as QFX
files with Firefox.</li>
<li>I'll then get a popup asking if I want to open with Moneydance or
save the file. I'll select the open with option.</li>
<li>I'll then get a popup from Moneydance asking if I want to import
an OFX file. I'll OK this.</li>
<li>I then get a popup to select the correct account and OK this.</li>
<li>I'll then go into the account and accept each transaction
individually. Usually I'm able to 'Categorize' the transaction
and sometimes 'Merge', rarely I'll edit and then 'Use Original'</li>
<li>Press "Accept" button.</li>
</ol>
<p>Today I noticed that I didn't hear ka-ching when I pressed accept. But<br />
I do when I save out a transaction that was opened for edit.</p></div>Stevetag:infinitekind.tenderapp.com,2009-01-14:Comment/10683932011-01-05T19:38:36Z2011-01-05T19:38:36ZReports - transaction descriptions not consistent with check register<div><p>Hi Steve</p>
<p>I am sorry I have not responded to you sooner.</p>
<p>When Moneydance offers a CATEGORIZE option for an unconfirmed
transaction what this means is that it has found another existing
transaction in your register that is similar to the one that is
unconfirmed, lets call that the match. When you click "Accept" with
the CATEGORIZE option the category of the match transaction is
applied to the unconfirmed transaction. However the description of
the unconfirmed transaction is also changed to be equal to that of
the match transaction. And it is slightly more complicated than
that as well. All transactions have at least two sides and a
transaction can have a different description on both sides. The
description from the source side of the match transaction is
applied to the description of the source side of the unconfirmed
transaction and the description on the destination side of the
match transaction is applied to the description of the destination
side of the unconfirmed transaction.</p>
<p>For example if you have an existing transaction in your checking
account called transaction A, which has the description "123" on
the source side and "XYZ" on the destination side and then you
download a transaction from your bank (transaction B).</p>
<p>You click on transaction B and you see the accept window at the
bottom of the register.<br>
Transaction A is a CATEGORIZE match for the downloaded transaction.
When you accept Transaction B with that CATEGORIZE option
Transaction B will not have the description "123" on the source
side and "XYZ" on the destination side.</p>
<p>I think what is going on in your case is that you are accepting
transactions with a CATEGORIZE match to a transaction that already
has different descriptions on source and destination sides. This
results in the accepted transaction taking on both description.</p>
<p>The only solution I can think of would be to manually make sure
all transactions in your register have the same description on both
sides before accepting any more transactions.</p>
<p>Sincerely<br>
Ben Spencer<br>
Moneydance Support<br></p></div>Ben Spencer