Would it make sense to change the category suggestion so that it suggests the last non-split category when entering a transaction?
I thought that's what it does. Unless I don't get what you're saying.
When I enter Publix the suggested category is groceries; the last category I used for Publix. Is that what you mean?
Sorry, I wasn't clear. The last time I entered a transaction for groceries it was a split transaction. When entering the next transaction, the split editor automatically popped up since the previous transaction for the payee was a split, instead of suggesting the category from the last non-split transaction.
Edit: I hope that makes sense, I'm not running on much coffee yet.
Got it.
I can see where the way it's working now would be helpful. For instance if you track your mortgage payment by splitting P&I with homeowners ins. This would be something you probably want to happen every time you enter your mortgage company as the payee. Of course these would mostly be regularly repeating transactions I would think and setting them up as scheduled transactions (when we get there) would set them up as spits each time then.
In everyday random transactions I can see where defaulting back to the non-split, last category would be more in line with what happens most of the time.
I think this is something I will defer to the payee management system (it would probably make sense to allow a manual category selection per payee).
Then you could just set the payee to use whatever you want for the category and it would stay that way (wouldn't change if you used a different category for the payee, etc).
Would the default behavior be the current suggestion method, with the option to manually override with a payee setting? I think that would be good.
I go to Meijer for groceries (splitting often) and occasionally for fuel. Setting to "groceries" manually as the default category would be nice since the transaction ratio is about 4:1 vs fuel.
Exactly 👍 🙂
Once we have scheduled transactions and payee management, this won't be an issue :)