[Bug]: Splitting a transaction that is a transfer to another account off budget does not match up
Verified issue does not already exist?
- [x] I have searched and found no existing issue
What happened?
I split a transaction that is a transfer to an off budget account.
In the off budget account, it does not allow you to link to the transfer, but ends up adding 2 transactions.
These 2 transactions then cannot be marked as transfer, so there is the $3000 transaction and the split transactions showing up separately causing an additional $3000 to show up in the off budget ledger.
How can we reproduce the issue?
I would expect that the split would exist on both accounts and not show up as 2 new transactions that is not markable as transfers.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome
Operating System
Linux
What process are you using to get to this state?
I am using simplefin bridge to sync with my bank accounts.
Bank account A - Sending account and on budget Bank Account B - Receiving account and off budget
It would seem that:
- First sync, only Bank Account A saw the transactions.
- I split the transaction on Bank Account A. In Bank Account B, these now show up as 2 different transactions instead of the split.
- Bank Account B, the transfer posted, but now I can't mark as a transfer since it was split into 2 transactions instead of 1 single transaction with a split.
Can you elaborate on what your use case is? Why do you want the transaction to be a split, but then both splits go to the same place? Is it just to divide up the categories?
So you can fix the account B side by 1) selecting the two transfers and saying "make split" then 2) merge the unmatched, imported transaction to the split.
@youngcw I'll try that next time, however, it does seem a painful process to have to put the split in on both sides.
If this is the solution though, we can close this bug.
It would be nice to have that happen automatically, but I don't know how that would be done in the code where each of the split lines are treated as separate transactions on the backend. Ill leave this open for now
Does it become a feature instead of a bug then? :) It sounds like actually a new feature disguised as a bug.
It could be a feature request. If you want to change this to be a feature request that would be fine.