From a post from @dsfreddy
dsfreddy Member ✭✭November 2023 edited November 2023
Have not found an explanation by Simplifi of the purpose of its split functionality. I am not sure a one to one correspondence between the list of transactions in Simplifi (called the register by some?) and what I'd see at my banks website is a fundamental requirement. My request is that split transactions, when exported, inherit traits from their parent record. Here is what these look like now:
account | state | postedOn | payee | usage | category | tags | notes | amount |
|---|
Credit Card 1 | CLEARED | 9/28/2023 | Our Dentist | | SPLIT | | | $0.00 |
| | | | | Health:Dentist-Jack | | | -152.42 |
| | | | | Health:Dentist-Jill | | | -152.42 |
Checking 1 | CLEARED | 7/31/2023 | Atm Wthdrwl On 07/31 @ 11:09 Us Debitcard, Pos, Withdrawal, Processed | | SPLIT | | | $0.00 |
| | | | | Cash & ATM:ATM-Jack | | | -60 |
| | | | | Cash & ATM:ATM-Jill | | | -140 |
| | | | | | | | |
These child records should inherit account, state ("status" in transaction detail), postedOn ("date"), and payee from their parent record. It makes no sense to create a CSV file without that information. Displaying these child records in the transaction list is another matter. Not sure I care either way about that.
I would like to see this idea implemented without separating split transactions into individual/separate transactions.
Request is for child split records to inherit details from parent transaction records: account, state ("status" in transaction detail), postedOn ("date"), and payee
Original post below.
[edited title]