|
Posted by jo on January 16, 2008, 9:27 pm
Please log in for more thread options > Marc Auslander wrote:
> > sometimes I accidently accept a checking account transaction
> > which is
> > "new" because it didn't match correctly. =A0now I have the
> > reconciled
> > downloaded entry and the original unreconciled entry.
>
> > I'd love to force a match, of course, but its too late.
>
> > What are my options?
>
> > what i did this time was to delete the downloaded entry (with
> > the
> > warning that i was deleting a reconciled entry) and manually
> > marked
> > the real entry as reconciled. =A0is this safe?
>
> I can't tell you for certain whether it's "safe" or not because
> I don't reconcile to an "online balance", but to my "paper
> statement". =A0My guess is there is nothing major to worry about.
>
> But I can tell you what you lose: the "posting date" and the
> fact that the transaction was, in fact, "downloaded".
>
> Losing the posting date could create problems if you later
> decided to try to switch to reconciling to a paper statement.
> Losing the "downloaded" status means that the register
> transaction will remain a candidate for future "match"
> (including "Manual Match") attempts.
>
> You can overcome both drawbacks by noting the "posting date" of
> the downloaded transaction before you delete it, then modifying
> the remainging transaction to have that posting date.
>
> To view, or modify, the posting date: right-click the
> transaction; hold down CTRL while left-clicking "Copy
> Transaction".
>
> When you modify the posting date for the remaining transaction,
> you should also put a check mark in the "Downloaded" box.
>
> --
> John Pollard
> First initial underscore Last name at mchsi dot com
> Please reply to newsgroup- Hide quoted text -
>
> - Show quoted text -
Interesting. All this time and I never knew about there was a hidden
posting date and the download/ matching issues. Is this technique of
Ctrl + Copy documented in some obvious section? Thanks for bringing
it up.
jo
|