MD refuses to match downloaded transaction
(I moved this from Questions)
When I download from my bank (web downloaded OFX file), MD refuses to recognize a matched check transaction.
It matches the transaction, I "Merge" it, everything Reconciles. Next time I download, that same transaction shows up again, it is matched, I Merge it again, and the same thing happens next time I download. I have looked at the transaction in the .OFX using TextEdit and it seems to be similar to other checks.
Any suggestions?
I did find this problem posted a while back, but could not find a solution.
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 Ben Spencer on 03 Mar, 2011 04:16 PM
OFX files have a unique ID for each transaction applied by the bank. This is the FITID field in the OFX file on each transaction. This field is used by Moneydance to determine if the transaction is a duplicate. The OFX specification requires that this ID should be the same each time the transaciton is downloaded it might be that your bank is not consistently giving this transaction the same ID. Can you verify that the FITID on this transaction is the same every time you download the OFX file?
SIncerely
Ben Spencer
Moneydance Support
2 Posted by davet65 on 03 Mar, 2011 06:53 PM
Ben,
Not only is the FITID field the same on two different downloads, but I can import a download file, Merge the transaction, re-import the same .OFX file and get that particular transaction appearing again. None of the other transactions in the download appear.
This problem will soon go away since the default download from this institution begins just over 1 month before the current date, and the problem transaction is dated 2/4/2011 in the download file. But I would like to know why this is happening.
For what it's worth, the transaction that I originally entered, and that successfully matches [if I have the matching time limit set high enough], is dated 12/04/2010.
And just in case this issue is related to another download problem I posted about, I call your attention to my recent post in Problems: "investment transactions Imported from Schwab rarely have correct price".
Thanks for your help.
3 Posted by Pete Linley on 04 Mar, 2011 07:50 AM
I have just seen this having posted a separate question on this issue. I am having exactly the same problem!
4 Posted by Ben Spencer on 05 Mar, 2011 03:02 PM
I have never seen this reported before. Could one of you attach the OFX file that contains the transaction in question. You might want to edit the file in a text editor first to obscure the account number.
Ben Spencer
Moneydance Support
5 Posted by davet65 on 06 Mar, 2011 01:20 AM
Ben,
Attached is the key part of the .ofx file. I am a "nervous novice" about sending banking files, so I stripped my account number and all other transactions except the problem one, Check #999, and one other check transaction, Check #1007, that is behaving normally. All deleted transactions are also behaving normally.
I verified that this particular download continued to show up the problem transaction even though that transaction has been Merged numerous times from earlier downloads.
The bank is ESL, Rochester NY.
6 Posted by Erica Carter on 06 Mar, 2011 04:16 AM
I had this problem too with American Express and First Republic (I still can't get First Republic to download again . . . .).
7 Posted by Pete Linley on 06 Mar, 2011 04:43 AM
Hi Ben. Ignore my earlier email. I now attach a file showing the same transactions but downloaded on different dates in OFX. Seems like it is the FITID which is causing the problem. Looks to me like the bank is assigning a different FITID to the same transaction. Let me know your take on it. Thanks
8 Posted by davet65 on 06 Mar, 2011 09:53 PM
I have done some searching on this problem, and see #3026 by stevewi which seems to be the same or closely related issue.
I have a suggestion: Why not give me the ability to "Discard" a downloaded transaction which I get and I don't want because it is a duplicate or whatever, and then MD will not show that downloaded transaction again?
I think there is a similar need in the downloads into Investment accounts. From what I can see, the only choice there is to Accept the transaction - and then delete it separately. But at least in some cases, it will download and show up next time. I have posted on this problem in #12, Home → Problems →
investment transactions Imported from Schwab rarely have correct price.
9 Posted by Ben Spencer on 08 Mar, 2011 06:56 PM
Indeed the same transaction in both files does not have the same FITID. It would be great if we could discard a downloaded transaction and say we never want to see this downloaded again and the problem is that without the FITID being consistent there is no way that Moneydance can know for sure that it is the same transaction. This could lead to false positives and the possibility of very similar transactions being discarded incorrectly. I think the best course of action would be to contact your financial institution and tell them they are not in compliance with the OFX specification.
Sincerely
Ben Spencer
Moneydance Support
10 Posted by Peter Linley on 08 Mar, 2011 08:14 PM
Thanks Ben. I will will be doing that now that we have identified the
problem. Appreciate your help.
Peter
On 8 March 2011 20:56, Ben Spencer <
[email blocked]> wrote:
Ben Spencer closed this discussion on 08 Mar, 2011 08:33 PM.