Bug 279296 - Imported transactions from HBCI account appear in wrong KMyMoney account
Summary: Imported transactions from HBCI account appear in wrong KMyMoney account
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.5.3
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 14:35 UTC by Jan Essert
Modified: 2011-08-11 09:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Essert 2011-08-03 14:35:08 UTC
Version:           4.5.3 (using KDE 4.7.0) 
OS:                Linux

I have two accounts at a certain bank, and my girlfriend also has two at the same bank. We have been importing the transactions via HCBI for a long time and it has always worked.

Since one of the recent upgrades of kmymoney (can't tell you which, might have been 4.5.0), all imported transactions from one account show up in a kmymoney account associated to a different HCBI account.

Deleting the HCBI information and reassociating the accounts with the HCBI accounts did not help. In fact, the account associations are displayed correctly.

Please tell me which additional information I could give you to track this problem down.

With the same upgrade, the payee detection also got significantly worse, to the point that I have do double check everything via online banking, but this may not be related (and belongs to a different bug report).

Reproducible: Always




aqbanking version: 5.0.4
Comment 1 Thomas Baumgart 2011-08-04 07:21:03 UTC
I assume that both account numbers contain enclosed zeroes (e.g. 10005001 and 10005002). If that is the case, I can confirm the bug and let you know that it has been fixed and will be part of the upcoming 4.6.0 release.

Please confirm if that is the case or you see a different behavior. The problems you experience with payee detection might be a result of the above bug.
Comment 2 Jan Essert 2011-08-11 09:39:40 UTC
Thank you, this is indeed fixed in 4.6.0.

I did not have time to check whether the payee detection has improved. If not, I will file a separate (albeit vague) bug.