QFX Import Problem

[aga]

Good work.

On 07/03/16 18:05, Greg wrote:
> Previously, I reported unusual behavior from a qfx file import of credit
> card transactions.  I believe that I have found the problem.  It's a
> rather bizarre problem that perhaps somebody could explain.  I not sure
> if it is a bug or KMM configuration problem.  Hopefully, my explanation
> helps an understanding of the problem because I certainly do not
> understand it.
>
> *_Summary of the Problem_*
> The problem was that KMM failed to show the proper payee information
> from an import of a qfx file.  Upon import the 'Pay to' field listed the
> single letter E as payee even though there were payee names in the qfx
> file (there were no payee names E).  To add to the confusion this
> occurred for most imported transactions but not all.

Just to be clear, when you say "(there were no payee names E)", I 
couldn't recocile that with your later comments.   Unless you meant 
"there were no payee names E in the QFX file"?  I think there must have 
been a payee E from the QIF imports.

In Payees view, how is matching set on payee "E"?
>
> The KMM version is 4.7.2 under Windows 10.  KMM was installed several
> weeks ago, and I have been testing how it works before I made it my
> personal finance program.  Currently, I am using Quicken 2015 so there
> are file imports.  My method to set up the KMM file consisted of
> creating a series of KMM files.  After each change to the KMM file I
> created a new file so that I had a series of KMM files representing the
> changes. Consequently, I could back up the process without much effort.
>
> *_The Cause of the Problem_*
> The apparent cause of the problem was that previously I imported several
> qif files, one of which had an errant payee name.  The payee name was E
> when it should have been Earnings.  It occurred in a single
> transaction.  This payee E was subsequently used in the qfx file import.
>
> _Why This __Was the Cause_
> Prior to importing the qfx file I had imported several qif files from
> old investment accounts; these accounts were closed and had only a few
> transfers.  This was done because I was learning how to import accounts
> from Quicken, and these files contained 'simple' transactions.  These
> qif file transactions were imported successfully, but I noticed in KMM's
> payee view that there was a payee name E.  There was a single
> transaction with the letter E for payee, and it came from the qif file
> (and Quicken).  Most likely, this was a typo from a long time ago.
> Afterwards when I imported the qfx files, most of the transactions had
> an E in the 'Pay to' field.
>
> *_Why I Believe This _**_Is the Problem_*
> _Test 1_
> If I reversed the sequence of file imports by initially importing the
> qfx files first, the payee problem disappeared.  The correct payee
> information was inserted into the 'Pay to' field in KMM for all
> transactions.  The problem is not in the qfx file.
>
> _Test 2_
> To further test this idea I restarted the file imports from scratch but
> modifiedthe errant transaction in the qif file.  The letter E was
> changed to Earnings in the qif file, and the qif files were imported
> successfully with no payee name E.  Next, the qfx files were imported,
> and the payee information was inserted correctly into the 'Pay to' field
> for all transactions.  The problem was corrected by merely changing a
> single transaction in a prior import.  Why would KMM use payee
> information from a prior import when the qfx file included payee
> information.
>
> _Test 3_
> I tested this idea by restarting the import process all over again but
> with the original files.  I imported the qif files without the corrected
> transaction and then imported the qfx files.  The letter E shows up in
> 'Pay to' field for most of the transactions but not all. I was able to
> replicated the problem.  But, why do some transactions import successfully?
>
> Greg
>

Allan