When a transaction is split (eg. in 3 ways), it will immediately display all 3 split transactions in the table, yet they will actually be treated individually (not associated with one another).

If the page is refreshed, they are then treated as expected... but if actions are done to them without refreshing the page, it means that an individual split transaction can be deleted by itself. The delete dialog doesn't mention the need to split it first as part of the deletion process. If deleted, that individual split transaction goes into a "void" and cannot be seen or accessed, but remains in the database.

The remaining two split transactions in this example will still display in the table. If the page is refreshed, the two split transactions will then correctly display as associated with one another, and can be unsplit or deleted. If unsplit, the original value returns (including that of the deleted transaction), but if it's deleted, then only the two are deleted, and the third remains in the "void".

Adding the same transaction through CSV prompt a warning saying it's a duplicate transaction, as it's comparing it with the transaction in the "void".