![]() Registered Member ![]()
|
Is it possible to allocate a category automatic, if new transactions from the aqbanking plugin (HBCI) become available?
In the Moment I must allocate manual the category for every new transaction downloaded from the banking house. |
![]() Registered Member ![]()
|
it is certainly possible to allocate a category to a particular payee if that is what you want.
John Hudson, proud to be a member of KDE forums since 2008-Oct.
|
![]() Registered Member ![]()
|
Thanks, I have see this option and I have test it, but I think this is not the option I am looking for. I guess that "allocate a category to a particular payee" add the category if you make a new transaction with kMyMoney. But I’m looking for an automatism which add a category to this transaction that are transmitted from the aqbanking plugin. I'm sorry for my poor English, I hope you understand, what I try to say. |
![]() Registered Member ![]()
|
Maybe this is what you mean: Go to the account ledger and use the Search option to find all transactions with a given payee. If the list in the display looks OK, select everything (CTRL-A should work) and click the "Edit" button. Assign a category and click "Enter".
|
![]() KDE Developer ![]()
|
If I read this with my German glasses on, you are looking for an automatic category assignment during transaction download. Once you have some data in the ledger this should happen behind the scenes. Also, KMyMoney tries to match scheduled transactions against downloaded ones. So in case you pay your rent you simply setup a monthly scheduled transaction and KMyMoney will detect it if the date is in a given time frame. If it does not, you can also match a downloaded transaction with a manually entered one as long as the value is identical. Check the manual for more details. http://kmymoney2.sourceforge.net/kde4/o ... match.html
ipwizard, proud to be a member of the KMyMoney forum since its beginning.
![]() openSuSE Leap 15.4 64bit, KF5 |
![]() Registered Member ![]()
|
Yes!
Aha. OK, you mean the filter, which sort the incoming transactions to categories, learns witch every manually assigned category to an previously downloaded transaction? Is that correct? Did have the "Transaction Matching Settings" in the payees list an additional influence to the sorting procedure? My understanding is that the "Transaction Matching Settings" are only active, if you start a transaction from kMyMoney. zebulon, your Idea is exactly the manually way, I do it in the moment. |
![]() Registered Member ![]()
|
So what you are looking for is not "Suggest a category" under "Default Account" in the "Payee" menu?
|
![]() Registered Member ![]()
|
I'm not sure, therefore I ask ipwizard if the "Transaction Matching Settings" in the payees list have an additional influence to the sorting procedure. Because the German localized (translated) name for"Payee" suggest, that this list is only important for outgoing transactions. |
![]() KDE Developer ![]()
|
I expect you refer to the "Zuordnung" tab of the payees. In fact, that part is used to map a name found in a downloaded statement to an existing payee. Some shops add a message or random number to their name and the entries on this tab can be used to eliminate them.
Sometimes, the name of a payee is given as 'firstname lastname' and sometimes as 'lastname, firstname' but both refer to the same payee. Again, this tab can help you with the mapping and automatic conversion. Although you can map payee's and payer's names here it is not related to auto assignment to categories. In case you want to have all transactions with a certain person to show up in a specific category, use the 'Standard Konto' tab to simply do that.
ipwizard, proud to be a member of the KMyMoney forum since its beginning.
![]() openSuSE Leap 15.4 64bit, KF5 |
![]() Registered Member ![]()
|
Thank you for all the help!
![]()
OK, now I understand: Every changes, you made in the payees section is not relevant for automatic assignment to categories during download new transactions!? Everything you do here, is only for sorting and administrate your payees list.
OK, if I want to assign a payee to a category, I must first define a default konto, because the box is grayed out on the other way. But all these things in the payee section have not an effect on the automatic assignment to categories during download. If this is correct, the problem is solved for me. |
![]() KDE Developer ![]()
|
You cannot assign a payee to a category. You can define a category for a payee such that if that payee is used, the category will be pre-filled. This feature is used when importing transactions w/o category information.
In case there is no automatic assignment of a category, the following logic applies (comment from the source code):
ipwizard, proud to be a member of the KMyMoney forum since its beginning.
![]() openSuSE Leap 15.4 64bit, KF5 |
![]() Registered Member ![]()
|
I check how kmymoney manage this things next weeks, if new transactions via download become available.
In the moment, it is too complicated for me to understand all. Thanks |
![]() Registered Member ![]()
|
Just in this moment a new transaction becomes available: AND IT WORKS
![]() The category was automatic assigned! Thank you all for your help and for this great tool. |
![]() Registered Member ![]()
|
Hi,
I know this is an old topic, but it seems the logic is still the same. I'd like to ask whether it is planned to add more sophisticated logic to category assignment. For example, gnucash uses some Bayesian matching algorithm. With the current version, I have the problem that it can get thrown off quite easily. For example, I categorize practically everything bought from the local supermarket under "supermarket". But sometimes I buy a toy there, and split the transaction to list the toy separately under a "toy category". If this happens to be the last transaction after an import, the next import will split off something under "toy" for ALL my purchases at this supermarket, which is clearly not intended! I know I can assign a default category under "Payees", but I am sure this can be handled more elegantly! Thanks! |
Registered users: Bing [Bot], Evergrowing, Google [Bot], q.ignora, watchstar