This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Differentiating payees to categories?

Tags: None
(comma "," separated)
dasbooter
Registered Member
Posts
5
Karma
0

Differentiating payees to categories?

Fri Sep 03, 2010 12:14 am
When importing statements I find that the categories do not match the payees. For example my local gas station where I purchased fuel will be classified as food:groceries instead of transportation:fuel. Opening the .qfx file shows that in my statements the name is always listed as:"Point Of Sale Withdrawal" and the memo seems to actually contain the name of the payee.

here is an example:

<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20100828000000[-7:PST]
<TRNAMT>-89.87
<FITID>628
<NAME>Point Of Sale Withdrawal
<MEMO>COSTCO
</STMTTRN>
<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20100828000000[-7:PST]
<TRNAMT>-20.00
<FITID>626
<NAME>Point Of Sale Withdrawal
<MEMO>COOPGAS
</STMTTRN>

So gas and food are categorized the same under food or gas but not seperated. What am I doing wrong here. To fix things seems to require alot of manual intervention which I think should not be required?
User avatar
Hei Ku
Registered Member
Posts
784
Karma
3
OS
When doing the matching, you have an option to use the memo field to identify the payee.


Hei Ku, proud to be a member of the KMyMoney Development Team since January-2008
User avatar
ipwizard
KDE Developer
Posts
1359
Karma
6
OS
Yes, but that is only available for HBCI online banking and not for OFX. Guess we need it as a general option if banks providing OFX access introduce the same set of problems.

That would make a nice wish list item on bugs.kde.org. Any volunteers?


ipwizard, proud to be a member of the KMyMoney forum since its beginning. :-D
openSuSE Leap 15.4 64bit, KF5
dasbooter
Registered Member
Posts
5
Karma
0
Sorry for the latency of my reply.Although I am not in front of my computer at home with kmymoney installed I do remember looking at matching options but did not see anything in regards to matching by memo's.In your post it seems this is an option only available to ofx users which is a system as I understand it of directly integrating information from your bank directly into kmymoney. I believe that this system isn't available to me and right now and I am importing .qfx(quicken) files on a monthly basis(downloaded from the banks site). Is it correct to state that I will have to live with manual correction of categories for entries in my ledger or is there anything I could do?
User avatar
ipwizard
KDE Developer
Posts
1359
Karma
6
OS
QFX is Quicken's idea of OFX files. So they are the same. The memo-to-payee conversion is only implemented in the HBCI (a German online banking protocol) plugin called 'KBanking'.

A possible workaround would be to pre-process the file before you import it into KMyMoney and move the payee into the payee field.


ipwizard, proud to be a member of the KMyMoney forum since its beginning. :-D
openSuSE Leap 15.4 64bit, KF5
dasbooter
Registered Member
Posts
5
Karma
0
Thanks I had thought of that, I suppose and text editor search and find all and replace would work.

Does anybody think that my banks practice is unusual. I guess I should think about putting in a feature request but if I am the only one with the problem it seems silly. Anyways thanks for giving replies as this isnt always the case in many forums.
User avatar
Hei Ku
Registered Member
Posts
784
Karma
3
OS
File a feature request. The feature is already there, but only for HBCI. We should "just" move it to a more general place, so OFX can use it too.


Hei Ku, proud to be a member of the KMyMoney Development Team since January-2008
User avatar
ipwizard
KDE Developer
Posts
1359
Karma
6
OS
In the meantime, I received an interesting statement from an OFX implementor:

If the strange behavior is the observation that the content
of the NAME and MEMO tags are opposite of what they should
be ... this is likely a poor implementation by this
particular institution. This should of never happened by
the financial institution delivering this OFX but because
OFX implementations vary widely in how "correct" they are
per the OFX specification ... this stuff occurs. The
commonality, if there is any commonality to other
institutions, would likely be that they are using the same
"back ends". When the OFX server are mapped to those back ends ...
they end up getting content into those NAME and MEMO tags that
is backwards from what it should be. That is my best guess.

I don't know if that helps or not, but ideally what would
happen is the financial institution would fix this because
its simply wrong, but that is probably not likely to ever
happen .. forcing you to come up with yet another work
around for this particular financial institution (which of
course undermines the whole reason for a standard like OFX).


From past experience we got in other issues where we had to deal with institutions I doubt that they will fix it. So it's time to create that wish list item/enhancement request on bugs.kde.org.


ipwizard, proud to be a member of the KMyMoney forum since its beginning. :-D
openSuSE Leap 15.4 64bit, KF5


Bookmarks



Who is online

Registered users: Bing [Bot], daret, Google [Bot], Sogou [Bot]