OK, I get it. Manager is trying to be smart at avoiding duplicates even if description changes. What you have described was an edge case which Manager couldn’t handle properly (it picked incorrect transaction to import out of duplicate candidates). I was able to reproduce this issue and fixed this in the latest version (15.3.62).