Group a recurring transaction
K
Karan Lyons
If you, for example, have a recurring service transaction for which tipping is appropriate, you may end up with two charges: one for the service itself, and another for the tip.
It would be ideal then to be able to make some semantic connection between these two charges. Typically the tool for doing so in LM is groups.
But you cannot add a transaction that is recurring to a group of transactions. It would be great to lift this limitation, as from a data model perspective there shouldn’t be a great difference between a standard transaction and a recurring one: the latter presumably has a many-to-one relation with some “recurrences” entry (or this information is denormalized) but is otherwise the same as a normal transaction and could as well have a many-to-one relation to a “group” entry.
Log In
J
Jonathan Lovelace
This is one of my biggest pain points currently. Many of my recurring transactions are via PayPal, which causes a debit transaction in the PayPal account, a debit transaction in the underlying credit card or bank account, and (once I manually add it) a "Transfer From Bank Account" credit in the PayPal account. These are all logically one transaction, and so should be grouped, but if LM sees any of them as "recurring," it won't let them be included in a group. This also causes budgets' "actual" figures to be off if the "transfer to PayPal" transaction is picked up as recurring but the other two are not, since (as I complained in another issue) all transactions in a group are forced to have the same category, which in this case then becomes counted as zero.