Previously Confirmed Transactions No Showing Up as Unconfirmed

Kenny's Avatar

Kenny

27 Jun, 2020 12:07 PM

Good Morning,
I have been using Moneydance for many years and love it. I regularly manually download transactions from my Credit Union Checking Account and I confirm each new transaction. The last 2 times I have downloaded my transactions all the transactions back to November, 2018 are showing as "Unconfirmed". The first time I figured it was a one-off mistake and I reconfirmed all of the transactions. This morning I downloaded the transactions and the same thing happened. Has something changed? I need to resolve this problem quickly. I appreciate any assistance you can provide.
Regards,
Kenny

  1. 1 Posted by davet65 on 27 Jun, 2020 02:09 PM

    davet65's Avatar

    I saw this problem when I upgraded to MD 2020v1913, using Mac OS 10.13.6. It just looked like I had a mess. So I was suspicious of the update, and I went back to 2019v1899 only to find the file updated to the mess, so went to a backup file. I'm using v1899 and am waiting for this to settle down before going to any update.

    I see there is another problem with the file windows not opening at all after the update on Mac that is addressed by 2020v1915, but I will continue to wait.

    As a side nuisance issue, is there a clean way to rename the backup file to the original file name? The backup file reopens with the archive date in the file name. I fumbled around and somehow did manage to get my original file name to show up. I don't know exactly what I did ?!?

  2. 2 Posted by Dan P on 27 Jun, 2020 02:46 PM

    Dan P's Avatar

    davet65:
    I recently had the same issue after restoring from a backup - how to change the name. It's really very simple. Just rename the file. Here's IK's answer:
    https://infinitekind.tenderapp.com/kb/file-locations-and-changes/re...

  3. Support Staff 3 Posted by Ethan on 27 Jun, 2020 06:40 PM

    Ethan's Avatar

    Hello Kenny,

    Can you clarify which file type you are importing into Moneydance (QFX, OFX, QIF, etc)? Have you changed which format you are importing recently?

    Ethan
    Infinite Kind Support

  4. 4 Posted by Kenneth Shann on 27 Jun, 2020 07:12 PM

    Kenneth Shann's Avatar

    Hi Ethan,
    Same thing happened with both OFX and QFX.
    Regards,
    Kenny

  5. 5 Posted by davet65 on 13 Jul, 2020 02:15 AM

    davet65's Avatar

    Ethan,

    Are you there? Would really appreciate an answer on the confirmed transactions --> unconfirmed in v1913 [that version for me at least].

    I would really like to update to solve the Citi download issue that I am also having [Private Discussion with Maddy]. But that is less serious than the confirmed --> unconfirmed situation.

  6. 6 Posted by sth on 14 Jul, 2020 12:55 AM

    sth's Avatar

    You can rename the file by opening the folder where the file is. Either in the default location through Help->Documents Folder, or if you keep the data file in your own Documents folder go there. Then close MD. (important, do this). Then rename the file using the Finder or File Explorer, do NOT get rid of the .moneydance extension.

  7. 7 Posted by davet65 on 19 Jul, 2020 11:39 PM

    davet65's Avatar

    Another week has gone by with no response on download issue :-( !!

  8. 8 Posted by sth on 20 Jul, 2020 02:56 AM

    sth's Avatar

    This can be a whole host of reasons, your bank may have changed something and be reporting older transactions once again. Somehow the processing of dates in the range that MD requests is not being respected. The connection to the bank got reset.

    You can check some of this by opening the console window and then connecting to the bank in question. It will show some details of the connection.
    (Not IK Support)

  9. 9 Posted by davet65 on 20 Jul, 2020 11:55 AM

    davet65's Avatar

    I don't know whether Kenny, the original poster, had just updated or which version he updated to or was using. But my experience clearly points to a bug, not something I nor my bank did.

    I had been using v1899 for months. I updated to v1913 and the FIRST TIME I downloaded transactions, using Download All Accounts, I had the experience I described - hundreds of previously confirmed transactions, across multiple bank and credit card accounts, showing up as unconfirmed. I didn't mess around as I immediately suspected a problem with v1913 and reverted to v1899 and a backup file [which brought up my question about the proper way to change the file name of the backup]. I have not had the download problem since doing that, and have been reluctant to go to v1915 until I hear that the problem/bug has been fixed.

    I guess it is possible that I - and Kenny - did something wrong, or have some strange situation that v1913 didn't like. But I expected some acknowledgement that there was, or wasn't, a problem. I have been using MD for 10 years and multiple upgrades and never run into this situation before.

  10. 10 Posted by sth on 20 Jul, 2020 12:56 PM

    sth's Avatar

    And I have moved from version to version and not seen this. That points to something external to MD and that is why I gave a whole host of reasons.

    I suggested a way to look more deeply at the communication with your bank and see what is happening. Other than that, there isn't much for the developer to go on. Acknowledge that there is 1% of the users who had this problem? Is it correlated with specific version to version updates? Correlated to specific banks/brokerages? Not updating the bank connection information recently? There isn't enough data to acknowledge anything, much less fix it.

    Even posting the log (with window open) as I suggested when this occurs would help narrow it down.

    Unless you have a specific repeatable case that you are willing to send to IK, I don't see much that can happen. What kind of response are you demanding (message 7)?
    (not IK Support)

  11. 11 Posted by davet65 on 20 Jul, 2020 05:37 PM

    davet65's Avatar

    Since I was not the only one to report this, and since the problem totally went away and has never returned when I went back to v1899, I was hoping to have support tell me that there WAS a bug in v1913 that had been corrected, and that I could safely go to v1915.

    Based on the change list, v1913, a preview version, was a significant update that was then upgraded 2x within a week to v1915. And I am told "Please report any problems to us using our help page" which is what I did. All I was really asking was to be told if a bug that could have caused my problem was fixed before I tried v1915, another Preview. And v1899 is also a Preview, but has proven pretty stable.

  12. 12 Posted by sth on 20 Jul, 2020 06:40 PM

    sth's Avatar

    That is great and reporting bugs is fine. i do it as well, and some are unrepeatable and some are unique to my setup etc.

    However "All I was really asking was to be told if a bug that could have caused my problem was fixed before I tried v1915, another Preview." is not possible unless there is more data, either more folks experiencing it and/or more exact information on the cause. The fact that only 2 folks have this problem and have worked around it and moved on, means there is no way the developer can assure you it is fixed. That's all I was trying to communicate.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

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