Dealing with errors parsing OFX data generated by banks & brokers is an unfortunate fact of life.  It's impossible to test all cases in advance; I just have to deal with them as they come up.

If you find a bug, please submit an issue with the usual info - your OS, Python version, ofxtools version, and the error traceback (scrubbed of any personal information like $username, account numbers, etc.).

I definitely want to follow up on it, but people here are probably far less interested in the details.

2

(10 replies, posted in Institution Comments)

Ah, looks like Vanguard's parsing requirements are actually this:

If you send OFXv1 with SGML-style unclosed elements, then you need newlines.  If you use closing tags, then you can either insert newlines or not; either will work.

They need newlines for OFXv2.

Strange.

3

(10 replies, posted in Institution Comments)

I was able to connect to Vanguard using the details from the OFX Home listing.

It looks like they will accept any version of OFXv1/v2, but they need newline characters to be inserted between tags.  I had no issue with cookies.

4

(6 replies, posted in Institution Comments)

I just set this up for USAA bank.

For OFXv1, USAA is only accepting versions 1.0.2 and 1.5.1; the elements can't have closing tags (i.e. XML-style <TAG>text</TAG> won't parse for OFXv1).  They're also accepting OFXv2.0 and 2.0.2, which is a better choice.

ORG="USAA", FID="24591" for the bank.

Username is USAA left zero-padded to 9 digits (not 10; that doesn't work).
Password is 4-digit PIN, as used on the website and phone service.

BANKID="314074269" (their ABA routing #).

This works currently.

I don't have investment accounts with them to check.

5

(30 replies, posted in Institution Comments)

OK I just set this up.

First: log into the website, and in your account profile under "Security" or "AccountSafe (sm)" select "desktop apps".  Click to enable Quicken.

Then make an OFX connection.  It looks like they're not supporting OFXv1 anymore, but will take any version of OFXv2.  I used ORG="B1" (Jamie Dimon doesn't forget his roots) and FID="10898", which worked.

The website tells you that they only support the current version of Quicken and the previous one (a little kickback from INTU I suppose), so you'll need to set APPID/APPVER accordingly... QWIN 2700 worked for me.  You need to set CLIENTUID, as noted in the profile (and previous comments upthread).

Upon first connection, the SONRS STATUS tells you need to verify your identity within 7 days.  To do this, log back into Chase website and choose "Secure Messages" (currently located under that mobile-friendly hamburger), where something about "Activate Quicken" will be waiting.  Click the link; they'll want you to type in a security code they send to text/email as a 2nd auth factor.  The process notified me of some sort of "Prefilled identification code", which I didn't use for anything... it didn't to billed in as an AUTHTOKEN, for instance.

After that you should be good to go.  I was able to download both bank and credit card data (using the ABA routing number for BANKID, per usual).

This is for personal accounts.  For business accounts, they want $9.95/mo to authorize the service instead of clicking "download transactions".

Hey guys,

I've written a tool that might help you if you're struggling to set up OFX connections.

ofxget --scan

You can read about it here :

https://ofxtools.readthedocs.io/en/late … igurations

You can also use it to discover authentication requirements like CLIENTUID and "Change PIN on first login", by using

ofxget --profile

.

Thanks to Jesse for his work in keeping this database alive.

<?xml version="1.0" encoding="utf-8"?>
<institution id="475">
<name>BB&amp;T</name>
<fid>BB&T</fid>
<org>BB&amp;T</org>
<url>https://eftx.bbt.com/eftxweb/access.ofx</url>
<ofxfail>0</ofxfail>
<sslfail>0</sslfail>
<lastofxvalidation>2019-04-20 23:16:51</lastofxvalidation>
<lastsslvalidation>2019-04-20 23:16:50</lastsslvalidation>
</institution>

8

(1 replies, posted in Resources)

there's some information available about Quicken's implementation of OFX.
in particular, there is this:
http://fi.intuit.com/ofximplementation/ … gGuide.pdf

they also have this, although i haven't tried it:
http://fi.intuit.com/ofximplementation/ … ertool.zip

9

(0 replies, posted in Bugs/Troubleshooting)

is it just me, or is your OFX server validation rather severe?

i was trying to add this entry:

'fiorg': 'CompassBank',
'fid': '2201',
'url': 'https://www2.compassweb.com/ofxsecurity … server.dll'

and your app told me that it was getting back properly-formatted OFX responses, but it wasn't quite willing to go out on a limb and commit to the proposition that this was a working OFX server it could enter into the database.

meanwhile, i am able to use this information to download OFX files just fine.