Verified feature request does not already exist?

• I have searched and found no existing issue

💻

• Would you like to implement this feature?

Pitch: what problem are you trying to solve?

Raised in #2668 (And by the looks of it in #2420) The Reconciliation function run on CSV manual import can cause unrelated transactions to be merged together if:

1. The transactions are within about week of each other.
2. The transaction dollar amount matches.

Some examples of regular transactions that may be caught by this:

• Go to the same cafe for the same coffee in the morning.
• Weekly rent payments
• Mortgage payments

This is done transparently and can cause confusion when account balances cannot be balanced correctly.

Describe your ideal solution to this problem

Data shouldn't be transparently modified or destroyed without user interaction.

As the Reconciliation function is actively useful the changes should be clearly exposed to users during the import cycle possibly with a second model dialogue.

Mock up:

As you can see in the above mock up the imported transaction, RETAIL PURCHASE for 16.39, is shown merging with the existing
transaction CORNER GROCERIES with the note Weekday shopping and the category of groceries.

Teaching and learning

This should open during CSV import workflow if any transactions merging will cause a data change (Date, payee ect.)