Ability to group records with different categories, (i.e, sub-records within one main transaction)
I frequently record shopping mall/department store purchases. Such purchases contain items from many different categories, such as "groceries", "electronics/accessories", "kitchen", "home and garden", etc. Now, if I've paid by card, I want to enter it as a single transaction for consistency and comparison purposes (with bank statement, etc.), but at the same time, it's difficult to select one category for the whole transaction, which I care about doing accurately because "Expenses by Category" are pretty important to me in statistics.
I feel this is a use-case that many if not most users would have, which is why I propose that it would be generally beneficial to add a feature (more of a re-design, really) with the following (non-exhaustive) details:
1 (a) - A single transaction should be able to have sub-records, and
1 (b) - transactions with sub-records should be easily distinguishable from single-record transactions , say with an icon displayed in every multi-record transaction in records view.
2 (a) - Single-record transactions (which are the only kind possible right now) should be the default (of course), but,
2 (b) - there should be a straightforward, easily accessible option for creating a multi-record transactions while creating a new record, and also for grouping multiple (existing) records into one transaction.
3 (a) - All records within one transaction should (compulsorily) share the same value for the following attributes: Account, Currency, Type (i.e., Income/Expense) Date, Time, Payee, Payment Type, Status, Place, and Confirmation Status, but,
3 (b) - each record within one transaction should be able to have its own value for the following attributes: Amount, Category, Note, Labels, Warranty, Attachments, and also,
3 (c) - for the following attributes, it should be possible to have a group value associated with the overall transaction as well as (and separate from) the individual values: Note, Labels, Attachments, but,
3 (d) - the following attributes should be strictly associated with the individual records only, with no group value: Amount (which should just be the sum of the individual amounts), Category, and Warranty, however,
3 (e) - please note that all the suggestions under number 3 come from a real-world-mapping perspective based on only my knowledge of use-cases, so they may or may not apply.
4 - It should not be possible to create multi-record transactions of a Transfer type, or to attach such a transaction to a debt. This suggestion is mostly because that would make things very convoluted from a usage perspective, but I suspect also from a development perspective.
5 - Search and filter should match on values of both group and individual attributes, with no need to implement a way to match values of only group or only individual.