CSV Importing

Currently, when importing transactions, there is an option to skip duplicates entirely, but no option to choose which version of a duplicate to keep. It would be helpful to have the option to replace existing transactions with imported duplicates or to choose which version to retain (similar to deduplication tool). This would be especially useful when importing historical data from another source, such as a spreadsheet, where the imported transactions may already have been cleaned up, reviewed, and categorized.

When importing a CSV or PDF where the date is only MM and DD, the year currently defaults to 2001. Instead, have it default to the current year.

Since Canadian banks doesn't like to allow apps to sync data automatically, I have to use CSV files to import transactions. But unfortunately it is required to have the category on the csv file, and there is no autocategorization as we have in Bank Sync. I think that it would be great if Lunch Money included this feature into CSV Importing.

In some cases, banks only provide the month and day for transactions and if there are transactions extending over two different years or more, the existing "Override Year" feature doesn't help as it sets the same year for ALL transactions. It would be great if you could override the year for a select group of transactions, instead of all of them.

For CSV files with amount types defined by keywords other than "Credit" and "Debit", having a step to review the Amount Type field and map the CSV values to "Credit" or "Debit" would be helpful. At the moment, it requires replacing the Amount Type values in the CSV file before uploading.

On the 'Review Accounts' step of the CSV/PDF import, it would be helpful to see both account names and display names listed in the drop-down menu. This makes it easier to match the accounts' names from the files to the account names in Lunch Money.

When uploading a CSV / PDF, the dropdown shows "Amount" as a required field, BUT - you can also use the inflow (amount) and outflow (amount) instead. Users shared how they were confused at first, because they didn't have a single Amount field and needed to use inflow/outflow, but that meant not using a required field. Perhaps we can add a note in the blue information box at the top? Eg. "If you have your debits and credits in separate columns, you can use the "inflow (amount)" and "outflow (amount)" attributes instead of the Amount"

I would like for the .ofx and .qif formats to be supported within Lunch Money for manually transaction imports if possible.

Currently, if the Amount field is formatted in Google Sheets (i.e. "– $ 187.44"), Lunch Money fails to read the amount correctly. It would be great if Lunch Money automatically ignored the dollar sign and recognized debits and credits correctly. This also fails if the amount field includes currency symbols. Also, add support for the leading dash / en dash (−100,00), as it currently only supports the hyphen-minus sign (-100,00). See screenshots.

When manually importing transactions to a synced account that is experiencing sync issues, it would be great to have an option to set the 'Earliest import date' at the end of the process. This way, once syncing resumes, it will prevent duplicates. The option could display on the final step of the import process, after inserting the transactions.