editing "Near match" downloaded transactions?

I don't know how to prevent it.

But to work around it, you can alter the transaction date of the register transaction that is the "near match" to a date well in the future, forcing the downloaded transaction's Status to change to New, accept the downloaded transaction, then modify the pre-download register transaction back to its correct transaction date.

fjfino wrote in news: snipped-for-privacy@z14g2000yqa.googlegroups.com:

What I have is a repeating transaction that gets inserted in the register automagically. It then is a question of guessing at the date for the transaction, and when you download do the following: When you have started the download and comparison/clearing steps, if date, or other info of the download does not completely match the transaction, you have to edit the transaction to correct this before accepting the transaction. I think that should work.