Adding transactions by OFX which have already been added and deleted duplicates them
Hi,
This is causing me much pain now. On Moneydance 2019.3 (1880) if you download and import a .ofx file into a bank account, if you've already added transactions to that bank account, it restores the ones that were deleted plus adds the new ones. It's impossible to sort through them. This looks like a major bug to me.
Regards,
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by melissa.heuser on Jul 16, 2019 @ 07:16 PM
This comment was split into a new private discussion: Adding transactions by OFX which have already been added and deleted duplicates them
I had major problems when I imported transactions last month. They didn't match the existing transactions because they were downloaded wrong - charges downloaded as credits and vice versa. I had to restore a backup, and couldn't use the import file at all. Need a fix for this!!
2 Posted by dwg on Jul 16, 2019 @ 10:09 PM
I'm a fellow user.
Elliot.
I can understand getting duplicate transactions if you are not using the confirmation process to merge transactions.
Are you using the process as outlined in:
https://infinitekind.tenderapp.com/kb/online-banking-and-bill-pay/confirm-downloaded-data
3 Posted by Elliot on Jul 17, 2019 @ 06:29 AM
The problem is there are now five transactions that look exactly the same on any given day. Some are duplicates which are simple to discern. Some are two different transactions at the same place but for the same amount and with the same description. With over 250 transactions to go through spanning two months, it’s impossible to decide whether to merge or confirm these transactions when they could be any of the options above.
Really regret upgrading and paying for a new licence. Totally unusable now!! Why did they change what was working so well!
4 Posted by Elliot on Jul 18, 2019 @ 09:57 PM
Any support staff able to help on this?
5 Posted by kara.desmarais on Jul 19, 2019 @ 12:17 AM
I am having a similar problem, but only with transactions from Capital One. My other accounts are importing data as expected. EVERY transaction has a negative dollar value and dates that I did not ask for are coming in, meaning that I am getting double the transactions.
6 Posted by Elliot on Jul 20, 2019 @ 07:05 PM
It appears that when you delete a transaction - Moneydance isn't deleting it. Whenever you do a new import, it rea-dds all the transactions you've already deleted.
Really disappointed by the support staff's silence in these forums. By the looks of the other topics that have gone unanswered it seems like this isn't the best channel to contact them on.
7 Posted by dwg on Jul 20, 2019 @ 09:46 PM
I'm a fellow user.
It appears that the support staff do not see it as a priority to post on the public forums. I can only suggest at this stage you try the "private Issues" forum.
8 Posted by Elliot on Jul 23, 2019 @ 02:24 PM
So delving in, it seems that Barclays are now not closing some tags on their OFX. Moneydance must see these open tags and get confused, importing transaction that were previously deleted (and not even in the OFX file) as a result.
Running through an XML Validator solves this. For anyone having issue with Barclays OFXs as a result of their website changed, I've created a python script that one can run to resolve these issues.
9 Posted by pat.callahan1 on Aug 19, 2019 @ 07:41 PM
This is a bug. You will never get all banks to provide correct xml.
You need to handle the situation correctly. Restoring previously deleted transactions is not a good solution to a bad xml file.
If I delete something there's usually a very good reason for doing so. It should stay deleted, especially if i re-import it.
-Pat
10 Posted by Elliot on Aug 27, 2019 @ 07:49 PM
Ultimately, it's the most frustrating thing having support staff supposedly on these forums, but none actively reading through the reported bugs to fix them.
11 Posted by Elliot on Aug 27, 2019 @ 08:18 PM
In honesty - it's just terrible. It now adds transactions which aren't even in the same date range. It's completely unworkable
12 Posted by kara.desmarais on Aug 28, 2019 @ 01:09 PM
Agree. My Cap One download is so riddled with issues. The problem with having positive amounts coming in as negatives has stopped, but the duplicate and 'outside of date range' transactions that come in the OFX file are still problematic. I still believe this is a bank problem since none of my other accounts have had issues. BUT, I am baffled that no support for this issue has been received by Moneydance. I have even sent in 3 or 4 requests for assistance that have not received a response. Disappointing...
13 Posted by derekkent23 on Aug 28, 2019 @ 04:15 PM
I am not support staff, just a user.
The following does not fix you issue but may help to establish what’s going on.
The OFX files should contain a "Unique Transaction ID" (FITID) for each transaction. Moneydance uses this ID to prevent duplicates.
The following is an extract of one transaction from my credit card downloaded OFX file. Note the FITID number.
I am running Moneydance 2019.4(1884). It does not matter how many times I import this file the transaction only appears once.
Worth opening your OFX file from your bank in a text editor to make sure they have included for each transaction a FITID.
Also, if you right click on a transaction imported via a OFX file and select “Show transaction details” it should include the FITID
Hope this helps.
14 Posted by Elliot on Oct 01, 2019 @ 09:54 AM
Can any Moneydance support staff confirm a fix is in place for this? Moneydance is just completely unusable. You can't undo an import so this is completely messing up everything
System closed this discussion on Dec 31, 2019 @ 10:00 AM.