The payee name starts with the actual order date followed by my credit card number. It's useful to retrieve the original order date, as opposed to the transaction date (although ideally I'd have a separate column for order date, but I suppose that's a limitation of the banking systems - could be extracted by an algo I guess). However since it's placed at the start of the payee name and the Payee column tends to be quite short (unless I play a lot with my columns and sacrifice the Notes column), so I can barely see the actual name of the payee.

(screenshot 1)

This is also true for mobile, although the column by default is larger since fewer columns are displayed.

(screenshot 2)

I was using Bankin' mobile app and it has a nice string parsing where it displays a simplified string in the quick transaction view.

(screenshot 3 & 4)

Basically the algo removes the date DDMMYY as well as credit card number and following comma and space, as well as the area code ZIP_CITY at the end. It also applies Name Capitalization but that's not what I need most (and it's not always valid since acronyms like NASA should be preserved).

Ex:

300826 CB1234567890 FISH RESTAURANT 75011PARIS

=> Fish Restaurant

So my suggestion is to have an option to either add a column to display the Payee name in Simplified form (read-only, derived from current Payee name) or to automatically edit the existing Payee name when importing a bank transaction. From what I see, the Payee column in Lunch Money can be edited and is actually a custom field that was copied from the original Payee name (always accessible in details), so it should be OK to modify it directly.

I don't know if this format is a French thing and that's why Bankin' (French app) knows it well, but I suppose different countries must have similar tricks anyway so it would be nice if LunchApp could detect format from various countries (and tell users to report if their country bank transaction format is not supported).

P.S.: meta issue: I noticed we can't multi-select images to attach in this very form, although it does support multi attachment (we have to select them one by one). Maybe be worth a separate meta issue for this forum.