USAA Script to fix the broken download issue
Need to reconnect to USAA? I have written a (run one-time only) script to make USAA download to Moneydance work again. All it does it fix your connection profile. You simply run once, and then use standard Moneydance. It's not needed again.
This is now the IK recommended fix as they are working on 'medium and long-term' improvements to ofx connections
You must be on MD version 2019.4 (build 1904) or newer (if older, you must upgrade, else usaa will never work again).
[@@ UPDATE Oct 2021: This script is now built into the Toolbox extension (MD2021 onwards) under the Online Banking menu and it also works with MD2022 too. Further, we have worked with Moneydance so that once you have ‘primed’ MD with your USAA specific ClientUID number(s), the standard Moneydance Online Setup will work. Further again, there is now an even simpler way to get the connection working (which we haven’t documented: In Toolbox run the USAA ‘Prime’ option and then just use standard MD Online Setup. Lastly, if you need to get multiple UserIDs working, then Toolbox / Online Banking / OFX Authentication / Edit Multiple UserIds. NOTE: if you still just want the script, it’s still available, read on…. @@]
Following these simple, but complete, PDF instructions will make USAA download to your Moneydance file.
My python script creates a new USAA profile in Moneydance to replace the broken USAA profile. It has been used since Feb 23 by more than 100+ users successfully 😃
This script will allow you to download USAA transactions again. It isn't rocket science, really. You don't have to wait for IK/MD to fix the problem, nor will it stop you from embracing the Moneydance fix if/when it happens. I just fix the connection profile.
NOTE: usaa have changed their download data (content, format). If you get some data duplication afterwards, this is NOTHING to do with the script, it's what usaa are now sending. You simply need to do a one-time cleanup, keep the new data, and that's it.
DISCLAIMER: I have no affiliation with Moneydance. It's entirely possible that this won't work for you. Pretty much the worst that can happen is that your bank logon / service profile won't work - but then it's not working anyway.. You can always just delete the profile and start again, if you wish.
PLEASE ALWAYS BACKUP YOUR DATA FIRST!
The first thing to do is read the walk through PDF guide: ofx_create_new_usaa_bank_custom_profile.pdf
The latest PDF guide (now version 8a) is always here:
[https://github.com/yogi1967/MoneydancePythonScripts/raw/master/sour...]
The latest zip file containing the script to fix USAA/Moneydance is at: [https://github.com/yogi1967/MoneydancePythonScripts/raw/master/usef...]
FYI - When you click these links, you may see a blank screen (depending on your browser) and the file(s) will auto download to your downloads folder
You need to unzip this file. The script is called: ofx_create_new_usaa_bank_custom_profile.py
Quick Details:
- Make a backup first.
- Read the instructions.
- Once you run the script, Moneydance takes over with the new profile.
PS - If you get issues ensure a) you are connecting from a USA IP; and that any PiHole, Blockers etc are not getting in the way..
If you have problems, post - We love to solve problems.
CREDITS and thanks: @dtd and @hleofxquotes
I am not support, just a fellow user and creator of the very free and most-excellent Toolbox 🧰 extension for Moneydance.
The latest useful_scripts.zip package and Toolbox are on my site: [https://yogi1967.github.io/MoneydancePythonScripts/]
Showing page 9 out of 22. View the first page
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
241 Posted by Stuart Beesley ... on 15 Mar, 2021 07:07 PM
@PaulG - I have updated the script to properly handle userid and passwords with % sign included. There is no length issue (on my side). The latest useful_scripts package has been uploaded (script is now build 6). If your profile is already working, then you do not need to run this new script. It's only if you have a % in your credentials. HOWEVER, as far as we are aware, we think the quicken credentials generated on the usaa website are shorter than you specify, so are wondering if you are using the correct details? Let me know? Thx...
242 Posted by dwk on 15 Mar, 2021 09:41 PM
What is the latest version of the user-generated USAA issue pdf that you and Stuart are continuing to improve? I do not see a version update number in the title or the pdf text. Here is the link I presently have:
https://infinitekind.tenderapp.com/discussions/online-banking/18363-usaa-scripts-to-fix-the-broken-download-issue
Thank you both for this work ...
dwk
243 Posted by Stuart Beesley ... on 15 Mar, 2021 09:44 PM
.
244 Posted by dwk on 15 Mar, 2021 09:53 PM
Thanks, Stuart.
In my email I sent the name of script file I would use. Is this correct? I am not sure about your wording
> "
> useful scripts zip file using the links
>
> "
> Was not the script name correct? Why do you say ' links ', instead of ' link ' ? It is a single link to a single script document.
>
> From: Stuart Beesley - JUST A FELLOW USER
>
> I think it’s 6f. But regardless if you download the useful scripts zip file using the links then you will get the latest.
>
> dwk
>
>
>
> =========
>
>
>
245 Posted by dwk on 15 Mar, 2021 09:55 PM
To dtd as well:
========
Thanks, Stuart.
In my email I sent the name of script file I would use. Is this correct? I am not sure about your wording
246 Posted by Stuart Beesley ... on 15 Mar, 2021 10:01 PM
.
247 Posted by dtd on 15 Mar, 2021 10:21 PM
@dwk - in the first post of the link you posted, there is a long post on how to fix usaa.
Specifically, there is a pdf file (Version 6f) that you download and read in its entirety before you begin to get a concept for what you will be doing.
Second, there is a "useful_scripts.zip' file to download that has the script.
Once you have read the pdf file, and downloaded the script file, read the pdf file again, carefully following the steps. If you don't understand something, I'd love to know that via email - dtd at tbg3.com - as I continue to try to make the pdf instruction file clear for everyone.
Good luck.
248 Posted by dwk on 15 Mar, 2021 10:34 PM
Thanks. Will begin the process soon. I have one checking acct that is small and not too important. I intend to ensure that it has various kinds of transactions prior to using it to test them out, e.g., bill pay, transfer of funds, and deposit, all of which with a low $ amount.
249 Posted by Stuart Beesley ... on 15 Mar, 2021 10:43 PM
I would recommend you just set up 1 normal account first (not bill pay setup) and then when that’s working, add the accounts / bill pay using the standard moneydance online setup menu.
250 Posted by P. Gilmore on 16 Mar, 2021 01:58 AM
SUCCESS @stuart beesley
You really went above and beyond.
Comedy of errors on my part.
1) I used my password and not the Quicken access - which is what caused the % issue
2) reset passwords 2x and locked myself out of the account
3) I deleted the Quicken access not realizing it was needed
4) proceeded to use the Wrong access Id I transposed
5) Finally able to concentrate recreated Quicken authorization with corrected access id and bada boom.
Thanks everyone including
@dtd
@dwk
For assisting.
251 Posted by gnuite on 16 Mar, 2021 02:35 AM
Hm. After a week or so of successful use, I just now got the following error message when downloading one of my USAA accounts:
Strangely, however, retrying worked fine - I am now unable to reproduce the problem, despite multiple attempts.I did not make any changes (like resetting) that would obviously have caused this. Probably this has to do with my dual-USAA-account situation, and for now, it doesn't seem to be a problem anymore. So, maybe don't worry about it for now - I'll let you know if it happens again.
252 Posted by dtd on 16 Mar, 2021 02:38 AM
@paulg Fantastic. Glad it is now working! Stuart will certainly do another +1 soon.
As the writer of the pdf instruction file, what did I miss to make you pursue a different direction vs. the instructions to gather the quicken access information vs. your web information? Knowing that will help me make the documentation better.
253 Posted by dtd on 16 Mar, 2021 02:43 AM
@gnuite - some comments
A 2003 error is a successful connection. So you are connecting, somehow usaa doesn't think the account was there (for a moment0
At this point, whatever the issue is, it is not a script fix issue (i'm sure you know that) - and it may be your mutiple account issue. So, we're into Moneydance connection issues - and yes, given this is a specialty profile, i don't think moneydance support will help, so not surprised you came here...
my thought, if it happens again (and remember i'm the multi account chase guy) --- try to change and set it up again, and hopefully the account login issue will work for you... moneydance still needs to work on that.
254 Posted by Stuart Beesley ... on 16 Mar, 2021 05:32 AM
@PaulG +1 (=34)
255 Posted by Stuart Beesley ... on 17 Mar, 2021 09:23 AM
All, to clarify for everyone. The script works and 35+ people reconnected thus far. Read post 1 and the PDF carefully.
256 Posted by ik on 17 Mar, 2021 11:34 AM
The script worked great for several accounts (checking, savings, and credit card) but one account gets a 400 error. Have tried recreating the OnLIne setup and rebooting with no luck.
Error:
A communication or parsing error occurred. This could be the result of a network problem, a proxy error, or misconfigured server.
Error Description: java.io.IOException: HTTP Error:400
257 Posted by Stuart Beesley ... on 17 Mar, 2021 11:55 AM
@ik +1 (=35)... I've never heard of error 400.. Can you try rebooting and try again? If it fails, please Help>Open Console and leave console. Then download that account again and post the console output..... thx
258 Posted by ted on 17 Mar, 2021 02:31 PM
Genius - worked so well, of course i had over 1000 entries to verify, but it's nice to have things back.. Only part i don't like is the data added to the memo field, but small price to pay.
259 Posted by Rand on 17 Mar, 2021 02:45 PM
A 400 error would be a bad request, not super helpful by itself, but sometimes there will be an additional message. Restarting the app and trying again will probably solve the problem. 爛
260 Posted by Stuart Beesley ... on 17 Mar, 2021 03:36 PM
@ted +1 (=36). FYI - the extra memo data is nothing to do with the script or MD, usaa have changed the download format)
261 Posted by Charles Schell on 17 Mar, 2021 03:40 PM
Just as a side note once again, this is one of five identical account types that I have and this is the only one experiencing this problem. If they made a change on their end, it should be affecting all of them, but for some reason it is not.
262 Posted by dtd on 17 Mar, 2021 05:55 PM
This probably bears restating:
Given you have successfully connected, the normal Moneydance Online/Setup Menu items work properly again for USAA.
i.e.. Once you've successfully completed step 4 of the documentation (i.e. ran the script) anything beyond that in the documentation has to do with Moneydance, and the script is finished.
Still we want to help, so we included step 5 and step 6 as a "putting it all back in place" but you are now using Moneydance to do that.
Still, we aim to please, so Stuart is pleased to answer questions post- script success.
But I thought it would be good to distinguish the script working versus encountering the new world of (successfully) downloading from USAA. (like new download data, zeros in check number fields, and new errors) - Quicken users deal with all this - as it is the new download and account structures. Yes, they complain about it.
263 Posted by dtd on 17 Mar, 2021 06:00 PM
@Charles Schall - there are mitigating factors even for identical accounts. One that has defiinitely been seen are "missing accounts" - i.e. they don't appear in the linking list.
So, far those have been mostly inactive accounts - but still some are missing, some are not. In this case, the "inactive" part seems to be the pivotal point, and doing a small transaction brings them to life.
As for your 400 error - Stuart hasn't seen that, but there is probably something about that account that is unique. Still has to be solved, (by MONEYDANCE, or Stuart being his helpful self) but, it's probably not an all or nothing thing.
264 Posted by Stuart Beesley ... on 17 Mar, 2021 06:21 PM
Need to see the console log. It might be a html error 400 which would indicate a transitory issue with the usaa server... restart/reboot and try again... Let us know?
265 Posted by ik on 17 Mar, 2021 06:27 PM
@dtd
I have seven or so USAA accounts. All of them were put through the process, all of them are active, five of them are checking accounts just like this one. I have been able to individually do the online update with each of the accounts, and just hit my download everything button and everything works fine except for this one account.
When I set up the online for this account, it was on the linking list of accounts. I verified all the set up in the account etc.
The error message appears almost immediately when it starts To process the account.
266 Posted by ik on 17 Mar, 2021 06:28 PM
@Stuart
I posted this this morning, but for some reason is not showing in the timeline. Here is the info again. By the way, I reboot the system every time I have made Any changes to moneydance.
There was an error communicating with your financial institution. The details of this error are below.
Bank Name: USAA Custom Profile (ofx_create_new_usaa_bank_profile_custom.py)
Account: JChecking
Account Number: NUMBER IS CORRECT
A communication or parsing error occurred. This could be the result of a network problem, a proxy error, or misconfigured server.
Error Description: java.io.IOException: HTTP Error:400
java.io.IOException: HTTP Error:400
at com.moneydance.apps.md.controller.olb.ofx.OFXConnection.sendMessage(OFXConnection.java:2786)
at com.moneydance.apps.md.controller.olb.ofx.OFXConnection.sendMessage(OFXConnection.java:2563)
at com.moneydance.apps.md.controller.olb.ofx.OFXConnection.getTransactions(OFXConnection.java:972)
at com.moneydance.apps.md.view.gui.OnlineManager.downloadTransactions(OnlineManager.java:550)
at com.moneydance.apps.md.view.gui.OnlineManager.downloadTransactions(OnlineManager.java:465)
at com.moneydance.apps.md.view.gui.AccountDetailPanel.lambda$downloadTransactions$0(AccountDetailPanel.java:296)
at com.moneydance.apps.md.controller.BackgroundOpsThread.run(BackgroundOpsThread.java:136)
267 Posted by Stuart Beesley ... on 17 Mar, 2021 06:43 PM
@ik - odd.. a few questions: 1/ What version/build of MD?
2/ Do your other usaa accounts still work and download even though this one fails?
3/ Can you Help/Show Console, keep it open, download this account and send the WHOLE console. Console MUST be open when you download.
? Thx
268 Posted by ik on 17 Mar, 2021 06:48 PM
1. Ver 2021 2010
2. Flawlessly
3. That is what I sent. I did remove the account number.
269 Posted by Stuart Beesley ... on 17 Mar, 2021 06:51 PM
Hi @ik. 3. I need to see the before and after messages too.... Thx
270 Posted by dtd on 17 Mar, 2021 06:52 PM
ik - best to send an entire console via email - as there is a lot of data to redact. I've found Stuart to be trustworthy, but I wouldn't put an entire console public even with redactions as you might miss something.
that would be sbeesly at gmail.com