Hi,

when importing transactions, kmm (using 4. automatically categorizes some transactions as splits if the last transaction for that Payee was a split.

Is there some way to turn this off? It is very annoying, since this practically never makes sense for me.

Thanks!

Unfortunately, I don't know of any way to turn this behavior off (except a change in source code of course). It will not happen once the previous transaction for the payee does not have more than one split. Does it help to select a default category for that payee (if feasible in your case)?

Thanks, that allows me to work around the issue a bit. Fortunately, only a few payees are affected, and I can just delete the corresponding imported transactions, assign the default category, and reimport.

It would be easier to edit the splits, clear them all and assign the category as usual. No need to re-import.

Not really - clearing the splits requires a lot of clicks, and this I have to do for each individual transaction. With the reimport method, it's very quick - I filter by erroneous data, then by one of the payees with incorrect splits, select all (can be dozens), delete, assign default category, reimport, done. I only need to do the reimport once I have deleted all the splits by different payees. Since I have transaction ids, only the deleted transactions get reimported, which is exactly what I want...

I did not know about those numbers of transactions. Then indeed it is easier to re-import, given only the deleted ones will be used.