Answered

What criteria does Import Transaction Duplicate Check use?

When importing Bank records into my account, although I have Detect Duplicates checked, after importing the records, for most if not all of my scheduled records I have a duplicate where the same entry exists in the bank data. The only difference that I can determine is the actual date of the transaction.

Leave a Comment

Comments (2)

photo
1

All fields are compared, including transaction date.

photo
1

I think that you may have to consider adding a date 'range' to the calculation (Maybe just for scheduled transactions) or allow the user to specify how they 'match' the import data.. The problem is that banks do not always process Direct Debits and Standing Orders on the 'scheduled' date. This means that most of my scheduled transactions get duplicated when I import my bank data. As the scheduled transaction contains important information such as Category etc, I have to go and 'find' the 'real' transaction to flag it as reconciled then delete the downloaded version. Additionally, for those who enter transactions into one of the 'mobile' versions of the app as they go along, often the bank's date for the entry is often different to that entered, so again duplication occurs. The situation is slightly exacerbated by the fact that you cannot 'see' the transactions that already exist in the desktop application because the import data box sits over the centre of the screen.