Bank of America AmEx (legacy MBNA) duplicate x'action downloads on statement close
in [Quicken]
|
Prev: Bank of America AmEx (legacy MBNA) duplicate x'action downloadson statement close
Next: TT 2009 Deluxe -- Form 1116 Line 3e Bug
From: Gary B. Berns on 29 Mar 2010 20:40 I have been doing exactly what Bart says for sixteen years. I have never had a problem with any bank or charge account doing it that way. ----------------------------------------------- Gary ..
From: itk on 1 Apr 2010 11:22 Bartt Shelton <shelton.bartt(a)iname.com> wrote: >QB 2008 H&B. > >I'm seeing something puzzling with my BofA AmEx credit card >transactions. > >Typically, I enter transactions into my register, then reconcile them >against what One Step Update picks up. > >It works like a champ with every other account I've got. > >However, when my BofA AmEx statement closes, the transactions show up >again, en masse. This doesn't happen w/ any other accounts, some of >which are also at BofA. > >I don't use the card that much, so I haven't really dug into what's >happening until now. But it's been doing it for a long time. > >BofA just tried to tell me it's because I enter the x'actions into the >register ahead of One Step Update instead of just categorizing what >One Step Update downloads, which sounds absolutely ridiculous to me. >They told me to call Quicken Support (I know better than to do that). > >Any ideas? What BofA says is nonsense as long as you match the downloaded transaction with the one you entered, which it sounds like you do. If they are sending duplicate transactions, when the second one arrives it will look like a "New" transaction whether or not you originally entered it manually. I have BofA credit card that downloads with Direct Connect and once in a while see duplicated transactions; I haven't noticed that it happens on statement close, but could be. When I looked at what the bank was sending in the OFX log (Help / Product and Customer Support / OFX Log) I could see that they were sending the same transactions again with slightly different FITID values. That's an OFX no-no and causes Quicken to think it's a different transaction. It sure sounds like that's happening to you.
From: Bartt on 8 Apr 2010 10:19 On Apr 3, 9:01 am, "John Pollard" <8plus7...(a)gmail.com> wrote: > Oilcan wrote: > > I have direct connect on my last remaining BofA card (they forgot to > > remove it when I transferred my accounts to another FI). I get the > > transaction when it post to their system and I also get it when the > > statement closes. The second transaction will not match which means > > it must have a different transaction id being sent to me > > If the second transaction had the same Financial Institution Transaction > ID as the first, you should never see it at all: Quicken compares FITID's > and doesn't display downloaded transactions whose FITID has already been > Accepted into your Quicken data. > > You can verify for yourself by either saving the OFXlogs from both > downloads and comparing the FITID's of the two transactions; or by using > the QELLOG facility to display your current FITID's and check the FITID in > the OFXlog from the second download to see if you already have it. > > http://quicken.intuit.com/support/articles/getting-started/setting-up... > > -- > > John Pollard > news://<YOUR-NNTP-NEWSERVER-HERE>/alt.comp.software.financial.quicken > Your source of user-to-user Quicken help A couple of things: 1) What do you use to view the OFXLOG file? I tried to use NotePad, but that doesn't work. 2) I generated a QELLOG file & I can see at least one example where a x'action appears in the file twice. I'm not an expert in analysis of the info, but both appear to have the same FITID. There are some slight variations in the info in the records, but they're very close. One has a status "new" and the other is "processed"
From: John Pollard on 8 Apr 2010 12:05
Bartt wrote: > On Apr 3, 9:01 am, "John Pollard" <8plus7...(a)gmail.com> wrote: >> Oilcan wrote: >>> I have direct connect on my last remaining BofA card (they forgot to >>> remove it when I transferred my accounts to another FI). I get the >>> transaction when it post to their system and I also get it when the >>> statement closes. The second transaction will not match which means >>> it must have a different transaction id being sent to me >> >> If the second transaction had the same Financial Institution >> Transaction ID as the first, you should never see it at all: Quicken >> compares FITID's and doesn't display downloaded transactions whose >> FITID has already been Accepted into your Quicken data. >> >> You can verify for yourself by either saving the OFXlogs from both >> downloads and comparing the FITID's of the two transactions; or by >> using the QELLOG facility to display your current FITID's and check >> the FITID in the OFXlog from the second download to see if you >> already have it. >> >> http://quicken.intuit.com/support/articles/getting-started/setting-up... >> >> -- >> >> John Pollard >> news://<YOUR-NNTP-NEWSERVER-HERE>/alt.comp.software.financial.quicken >> Your source of user-to-user Quicken help > > A couple of things: > 1) What do you use to view the OFXLOG file? I tried to use NotePad, > but that doesn't work. You can view the OFXlog in Quicken: Help > Product and Customer Support > OFXlog But often it is easier to use an editor, or word processor (like Word); especially if your financial institution doesn't format the OFX nicely. To do that, "Save" the OFXlog while in Quicken ... that will create a Windows .txt file of the log, which you can then work with in an editor or word processor. > 2) I generated a QELLOG file & I can see at least one example where a > x'action appears in the file twice. I'm not an expert in analysis of > the info, but both appear to have the same FITID. There are some > slight variations in the info in the records, but they're very close. > One has a status "new" and the other is "processed" I haven't worked with the QELLOG to any meaningful degree, just generated a couple and took a quick look. My understanding is that there should not be two exactly equal FITID's for the same account with the same fi, in your Quicken data ... not even one in your account register and the other in the "Accept transactions ...." window. An FITID that is already in your data should prevent any transaction from the same fi for the same account, with that FITID, from ever getting as far as the "Accept transactions ...." window. It may be in the downloaded data (OFXlog), but it shouldn't appear in Quicken. I don't know what the distinction between "new" and "processed" in QELLOG represents in Quicken. If the FITID's (or accounts, or fi's) were different, I might think one transaction had already been "Accepted" ("processed"), and the other was in the "Accept transactions ..." window as a "New" transaction. But I'd just be guessing. Do you have an account where you have accepted some of the downloaded transactions, but there are still others which you have not yet "processed"? If you note the data in each QELLOG transaction, I would think you could locate the two transactions in your Quicken data ... and see what relationship they have to each other. If you were willing to post the data from the two transactions with the same FITID, in the Quicken Live Community (you could probably scrub any truly sensitive information first), the post might get Intuit's attention. You could provide the background of your original post in this discussion, explain you ran QELLOG and say you didn't think there should be two transactions in your Quicken data from the same account at the same financial institution with the same FITID, and ask what the meaning of "new" and "processed" is. Intuit might answer, and you and quite a few other people could get some useful info. Or not. -- John Pollard news://<YOUR-NNTP-NEWSERVER-HERE>/alt.comp.software.financial.quicken Your source of user-to-user Quicken help |