[Kmymoney-devel] [kmymoney4] [Bug 326100] Update always creates duplicate transactions

[Brendan Coupe]

I've been having the same problem with one of my banks for a while. I'm
running the latest version of KMM from git and this problem started a year
or two ago.

I only get duplicate transactions from one bank (Charles Schwab), it
happens with both accounts I have at Charles Schwab. My many other accounts
work as expected. I get the duplicates as long as the start date for the
download covers the transaction. I've shortened it to 3 days to minimize
the pain or deleting or constantly matching it to previous the previous
transactions. If I approve the duplicate match each time then the next time
it comes in matched (green) and if I approve the match it's ready for the
next duplicate. If I don't approve the match then I get a new transaction,
I have to approve the previous match, then I have to manually match the new
with the old and approve it. I hate using KMM for 3 days each month:-)

I have worked with Thomas Baumgart on OFX problems in the past and he told
me about a simple trick to make it easy to see the actual OFX files after
you download them. Make a directory called thb in /home and give your user
write access to it. If KMM sees /home/thb it will save the OFX files in
that directory (kmm-statement-0.txt, kmm-statement-1.txt...)

I finally took the time to do this and I think I found the problem. Charles
Schwab does not include a bankid with the transactions. Matthew, I'm
guessing your bank(s) may not include a bankid value. Everything else looks
the similar in the OFX that works and the one that does not work.

Charles Schwab does include a unique value in both the payee field and the
memo field, and they are the same value. For example:

BANK INT 091613-101513
BANK INT 081613-091513
BANK INT 071613-081513
BANK INT 061613-071513

This appears to be the category plus the date range of the interest payment.

I'm hoping there is a way to use this information to skip duplicate
transactions when there is no unique bankid provided.

*
----
Brendan*


On Wed, Oct 16, 2013 at 7:55 AM, Matthew Schultz <mattsch at gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=326100
>
> --- Comment #2 from Matthew Schultz <mattsch at gmail.com> ---
> (In reply to comment #1)
> > I believe that matching is based on a transaction id provided by the
> > bank/credit card.  Is there any chance your institution made any changes
> to
> > their system in the past month?  Also, does each transaction duplicate
> just
> > once, or does it create a new one each time you update the account?
> >
> > Additional question - how do you have your online settings for that
> account
> > set?  You can set how far back it tries to update each time it connects.
> > Setting it to the last time you updated might at least eliminate some of
> the
> > duplication.
>
> I'm not aware of any changes my bank has made with transactions.  What I do
> recall is as soon as I upgraded from 4.6.2 to 4.6.3, I immediately started
> getting duplicate transactions every time I click update.  This occurs
> every
> time on the same transactions assuming I do it again the same day and there
> hasn't been any new transactions.  It doesn't even matter if I previously
> accepted it, they will be marked as duplicates again on a subsequent
> update.
>
> I changed the setting so it checks the last 30 days instead of 60 days
> which
> has limited the number of duplicate transactions but this is still rather
> annoying since I still have to accept the last 30 days of duplicate
> transactions every time I update.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
> _______________________________________________
> KMyMoney-devel mailing list
> KMyMoney-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kmymoney-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kmymoney-devel/attachments/20131016/322c51c0/attachment-0001.html>