THIS NOTE REFERS ONLY TO THE MAC VERSION OF THE APPLICATION.

As a footnote to my July observations I was recently required to reclassify a number of transactions for tax purposes. This exercise took me back over three years. So I went, record by record and made all of the changes to the various expense accounts. Some of the changes necessitated foreign exchange rate adjustments.

Then I found NONE of my bank accounts or credit cards balanced any more.

So I went back record by record getting those to balance again.

Now my extensively reworked expense accounts have changed.

This is stupid game that could go on forever. The issue lies with foreign exchange of course (if you don't use ForEx you can ignore this review) and have to do with which account the entry was first posted to. Assuming all entries are first posted to bank or credit card accounts uses the value from the statement and applies an exchange rate to get a foreign exchange value.

If later you spot that the foreign currency expense value is wrong and change it there it assumes for the foreign value is sacrosanct and uses the new rate to change the bank/credit-card (primary currency) value. MAD.

So you need to know which was the source account for each entry.

The only way to discover that is to try to write a memo; if you can then you've got the source entry. If not then you need to use the See Other Side of the transaction option.

Only this does not work if the other side of the transaction is a split transaction. At this point MD returns you to the first row of the split.

Hours upon hours upon hours gets wasted with this application.

So my observations a reinforced; way and above the JAVA issues MD is simply unable to resolve on the OSX platform, there is much easier software for reconciling your pocket book and much better software for doing your accounts.

Do not even consider using MD for foreign currency accounts on the Mac.