|
Posted by Joe McDermott on December 22, 2007, 6:44 pm
Please log in for more thread options Ken,
Very good explanation. In previous versions of Quicken I would just make a
global edit of the qif file with notepad and then import it. I took a look
at the qfx file format and its not as easy to edit it with notepad. I was
hoping there were some programs floating around out there that could do this
or that maybe I was missing something.
I try to pay for everything with my credit card because it gives me a good
record of my spending so I have a lot of rules to write.
> John Pollard wrote:
>> Joe McDermott wrote:
>>> When I download credit card transactions from my bank in Quicken
>>> 2007, the Payee field contains the word "Purchase" and the payee info
>>> is in the memo field.
>>>
>>> Is there some way to write a rule that would move the contents of the
>>> Memo field to the Payee field whenever the word Purchase appears,
>>> regardless of what is in the memo field.
>>
>> Or something almost as good: see Quicken "Renaming Rules" (in the Online
>> Menu).
>>
>> You can have Quicken rename your downloaded payees (before they are
>> Accepted) based on the contents of the payee name or memo fields.
>>
>
> John,
>
> No offense, but I think you missed the point here.
>
> Unfortunately, I have a credit card like the first poster where EVERY
> purchase shows up with the payee field named, (I love this), "payee".
>
> Then, in the memo field, they have the actual name of the place where the
> credit card was used. Along with the date of the transaction, which store
> number, and anything else that whoever the processor was could think of.
>
> Discover, on the other hand, actually does put into the Payee field the
> name of the place where the card was used (Borders, Ye Olde Friendly
> Restaurant, etc.).
>
> In Quicken 2006, I ended up having to cut and paste the payee from every
> downloaded transaction from the memo field to the payee field. A pain, but
> the card in question wasn't my primary card, and I could live with it.
>
> In Quicken 2008, the first version of Quicken in which I had the naming
> rules turned on, Quicken happened to see the first "payee" transaction and
> promptly used the renaming rules to change the payee to the name of a
> local Chinese restaurant I frequent. Every single transaction after that
> (thinks of Frankenstein's Monster clumping down the street) got renamed to
> that Chinese restaurant. At this point I finally read up on the renaming
> rules and discovered that the rule was that if Payee = payee, the Chinese
> restaurant was substituted in.
>
> So, for about 50 or so payees, now, I have rules. Every new one that comes
> in that Quicken hasn't seen before infects the whole process, because
> Quicken, by preference, seems to think the right thing to do when it sees
> that "Payee", is to substitute in the Memo field name - and then use that
> particular self-generated rule for all the rest of the transactions!
>
> As the original poster points out, what would work better is a method in
> the renaming rule where if the "Payee" field has something in it that the
> user sets, the Payee field becomes set to what's in another field - like
> the "Memo" field contents. And maybe >then< run the renaming rules on the
> new Payee field contents.
>
> The second poster is basically doing just that, by swapping the contents
> of the Payee and Memo fields, then letting Quicken doing its thing. Which
> works better, when the Payee field (which it appears to favor) has at
> least a piece of the actual payee.
>
> Oh, well.
>
> Ken Becker
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap