|
Posted by BCFD36 on February 27, 2008, 12:35 pm
Please log in for more thread options > BCFD36wrote:
> > I didn't find this addressed anywhere in the group. Perhaps
> > someone
> > has run across this before.
>
> > I am runningQuicken2006 - R6 for Macintosh. On occasion,
> > when I
> > download the latest transactions, some of the transactions
> > will not
> > show up to be further processed. In fact, over the last 7 or
> > so
> > months, 4 paychecks have not been recorded. However, when
> > looking at
> > the .qfx files, the transactions are there.
>
> > Has this been seen before? Is there a fix? Is there a way to
> > reimport
> > the .qfx file. This last doesn't seem to work.
>
> I know nothing aboutQuickenfor the Mac ... except that it is
> quite different fromQuickenfor Windows.
>
> But my guess is that the Mac version may use some of the same
> underlying approaches for handling the same situations. In any
> event, the following all pertains to what I know aboutQuicken
> for Windows.
>
> Quickendetermines whether a downloaded transaction has been
> downloaded previously by checking the financial institution
> transaction id (<FITID> in OFX speak, I believe). IfQuicken
> believes that a transaction with that id has been downloaded
> before, it will not present it in the "Accept" transactions
> window.
>
> I believe it has already been noted by a few users that
> financial institutions sometimes do download a transaction with
> a previously used transaction id ... causingQuickento ignore
> the more recent transaction.
>
> At least one user was able to work around the problem by
> modifying the QFX file, changing the FITID for the transaction
> in question to be unique from any previous (or future) FITID for
> that financial institution. [Often the FITID includes a
> date/time stamp plus other identifying info ... with a bit of
> thought, those id's can be modified to something that has not
> occured before, and will not occur again.]
>
> I'm not clear whether this is a labor-cost effective approach,
> since one can always manually enter transactions, and since many
> users already have scheduled transactions setup for their
> paychecks. It might hinge on the number of "missing"
> transactions.
>
> If one wanted to manually enter such transactions, it would
> probably be a good idea to fib toQuickenand tell it they were
> actually downloaded ... by right-clicking the transaction, then
> holding down CTRL while left-clicking "Copy transaction", then
> entering a meaningful "Posting date" and checking the
> "Downloaded" box.
>
> The only "fix" is to get the financial institution to avoid
> re-using FITID's; good luck Mr. Phelps.
>
> --
> John Pollard
> First initial underscore Last name at mchsi dot com
> Please reply to newsgroup
Appreciate the input.
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap