Loading Profile...
Your Account is Currently up to Date
I get the following error when I attempt to update my accounts with T. Rowe Price Mutual Funds: "Your Account is Currently up to Date". I know it is not up to date as the last time I updated the account was in March from Microsoft Money (before I migrated to MD) and there are new entries on my online statement at the T. Rowe Price website. It appears MD is connecting to T. Rowe Price because if I enter either my ID or password incorrectly, I get a "Incorrect Username or Password" error instead. I have read reports on some forums that this error was encountered when importing an OFX file, but no one seems to have an answer. To set up online, I used the list from "New Connection"; I did not set up manually. Is this a bug? Anyone have any solutions?
I’m frustrated
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?The answer for OFX files was that there was duplication in the FITID (Financial Institution Transaction ID) - which is a unique transaction number for each account. When you upload a file or update an account, MD seems to remember all the FITIDs for that account, and if it sees another transaction with the same FITID, it won't update the account, saying that your account is already up to date.
I haven't found the original post, but you can see a similar problem here - http://moneydance.com/trac/ticket/1193. In my case, this was because my bank reset all the account numbers and seemed to start from 0 for some of the accounts. The developers at MD seem to be taking the stance that it's the bank's problem, so you should go to the bank to fix it. I would rather they provide some way for users to deal with problems that the bank won't fix, like allowing users to "forget" select FITIDs for accounts.
I fixed my problem by removing the FITIDs from my OFX files for the problem accounts so MD didn't have anything to compare the transaction to.
