Mvelopes Feature Requests

Fix import transactions to eliminate duplicates

In Mv4, when you imported a .qfx file, Mvelopes automatically searched for already imported transactions (whether manual or automatic) and did not duplicate them. In Mv5, they duplicate. It's impossible to work with when you have an account that is not importing on its own correctly.

  • Ariana Bissky
  • Sep 25 2020
  • Shipped
  • Attach files
  • Guest commented
    13 Jul, 2021 04:58pm

    I have been fighting with this also. I have an account that forces me to download the full statement of transactions or all of the current activity.

    If you are brave you can export the file as a QFX file, make a copy of the file, and then change the extension on one of them to TXT so that you can open it up in a notepad program and delete the transactions you don't want brought in there. Transactions have this in front of each transaction <STMTTRN> and the end of a transaction has this code </STMTTRN>

    Then of course you save it and change the extension back to QFX

    I've only tried it on QFX files, but I do it all the time. I've had one account that has not functioned properly for over two years. I have found that the newest transactions are at the bottom of the QFX file and the oldest are at the top of the transactions. Now there's a bunch of header and footer information you don't want to mess with.

    Hope this helps somebody.