[Bug]: YNAB4 import leads to malformed split transactions

[mullermn]

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

[MatissJanis]

👋 Hi. Could you upload a sample ynab export that we could use to reproduce the issue? Thanks

[aa-hr]

My Budget~100D554C.ynab4.zip

Hi, sorry for the delay. I started by trying to prune down my real budget to produce a real world sample without too much personal data in it but that proves to be borderline impossible due to the size of it, sorry. I have made this one, which is a brand new budget and does demonstrate the visual issue with Payees not showing up on splits.
YNAB4:

Actual:

The parent transaction in this example DOES seem to show up in filters in Actual, so either I was mistaken about that or that was a consequence of something else in my real budget data (I can't check now, having run the 'fix splits' process). However, I think this visual bug would be worth fixing in its own right as it is a bit ugly and confusing.

I have also created a second transaction (after I took those screenshots) with a transfer as one of the splits. The transfer element seems to get imported correctly, so it looks like the missing behaviour is just to take the payee at parent level in YNAB and apply it to any non-transfer splits.

Edit: Sorry, I am the original reporter, just uploaded this while logged in on a work account by mistake.

[youngcw]

I think this is also happening with nynab imports