I agree completely with this. I might be fuzzy on who
agrees with whom here, so bear with me as I offer my
$0.02 (US).
The reconciliation process, if it exists, has to be
very comprehensive. There is a lot to learn from
Quicken here, where the user can enter the statement's
start/end dates, the beginning/ending balance, and
"clear/unclear" transactions as they are found to be
posted or not on the current statement. In addition,
the ability to enter and "adjustment entry" if the
balances don't match is also useful, given that user
error in entering information will always occur
(especially if we are talking about importing data and
if the user inadvertently deletes/changes a
transaction).
I agree with Michael here, and I think his description
of what is needed is a good one. I also appreciate
those who are putting aside how they personally use
MD, and are rather engaged on the best, most clear way
to accomplish the task. Reconciling accounts isn't a
difficult concept, so it shouldn't be a difficult
implementation.
On the issue of the "diamond=clear" issue, I agree
that there should be separate indicators for "cleared"
and for "reconciled". If "diamond"=clear, then
downloaded transactions should all have the diamond,
and when reconciled, these should be "checked" by
default (though the user should have the option of
"unchecking" them). When reconciling, the user would
have the option of either importing new data or
manually checking (AND ADDING TRANSACTIONS ON THE
FLY)tansactions until the reconciled difference is
$0.00.
Again, this would help bring MD into the mainstream as
a replacement for households' financial management.
Marcelo
Post by Mailing ListsPost by Jon WalthourSo I have to remove the diamonds from the
transactions that have
Post by Jon Walthourcleared the bank, but are not on the statement
that I'm trying to
Post by Jon Walthourreconcile.
This is expected behavior and not a problem with
Moneydance per se. It
Post by Jon Walthourcomes from you downloading transactional data from
your bank between
But it certainly is not user-friendly behavior on
MD's part, and I would
also consider it a 'problem' with MD. Sure it isn't
fatal, but why
should the computer get away with dictating WHEN a
person has to stop
downloading from the bank and wait for the statement
to arrive? Or
punish a user who wishes to download from the bank
AND reconcile to a
paper statement? From my Quicken experience, this
combination can work
very well if the software 'does the right thing',
(1) let you enter the 'statement date' (read right
off the statement, no
need to memorize it!) and use that as a cutoff for
considering 'cleared'
items as 'reconciled'. This is what Quicken does,
and it makes things
'just work' most of the time. For the rest of the
time, if only the
(2) let you remove 'cleared' items from the
reconciliation that are
within the date range but do not appear on the
statement, so as to
balance with the statement. But DON'T forget that
the item has
'cleared', so those items would helpfully be
included in the next
reconciliation without a human having to remember to
re-check them.
Quicken bugs me with its shortcoming here every now
and then.
That would be a more helpful program. Wouldn't that
be more friendly
for everyone?
Just because there is a rationale to how computers
work ('expected
behavior') doesn't make it right. Nor is it
necessarily right just
because it works the way YOU want to work.
--
Mike Casteel
_______________________________________________
moneydance-info mailing list
http://moneydance.com/mailman/listinfo/moneydance-info
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new Resources site
http://smallbusiness.yahoo.com/resources/