[Bug]: YNAB4 import leads to malformed split transactions

Verified issue does not already exist?

• I have searched and found no existing issue
• I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

After migrating to Actual from a large YNAB4 install I found that my split transactions did not show up correctly:

There is evidence that the data was imported behind the scenes but is not displayed:

I suspect this is because YNAB4 [can] tracks payees for split transactions solely at parent transaction level, and does not require payees for the splits, while Actual computes the parent payee name from that of the splits?

This doesn't break the app but introduces the dangerous gotcha that these transactions will not show up in reports and filters based on Payee name.

Split transfers do not seem to be affected:

The repair split transactions tool seems to handle this correctly, but ideally the situation should not exist in the first place:

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Mac OSX