Jack, On Monday 14 December 2015 13:32:11 Jack wrote:
> Good - things are much better now. > > On 2015.12.13 04:53, Thomas Baumgart wrote: > > On Saturday 12 December 2015 12:36:02 Jack wrote: > > KMM uses AqBanking and you can setup an account mapping for it. The > > first step would be to create a user/account in AqBanking. Use > > Settings/AqBanking Settings in KMyMoney and the 'Create Account' > > feature to select the backend. (see attached screenshot). I don't > > know what needs to be done then as I have never used that path. Also, > > I am not sure if you need to setup a user before to get things > > working. > > Once I upgraded aqbanking and recompiled KMM to use it, since the > aqbanking user and account were setup when accessed from gnucash, KMM > just used the same user and account; all I had to do was to map the > aqbanking account to the KMM account and it worked. > > My only (minor) problem is that aqbanking doesn't seem to import the > memo, so where transactions don't match to KMM payees, there is no > information imported I can use to make that match. I haven't looked > through all the configuration settings yet, so I'll be glad for any > hints. At least I can now access my Chase account again, no thanks to > any help (or lack of it) from them. Hm, that could be a problem in AqBanking, more specific the OFX backend. The HBCI backend provides the memo and it gets imported into KMyMoney. -- Regards Thomas Baumgart GPG-FP: E55E D592 F45F 116B 8429 4F99 9C59 DB40 B75D D3BA ------------------------------------------------------------- Early bird gets the worm, but the second mouse gets the cheese. -------------------------------------------------------------
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
