Look up your OFX settings

Look up the OFX settings for your financial institution(s)…

[ALSO]  If you are able to download OFX data from your financial institution’s website, use the Save option rather than Open, and you should be able to find all of your your settings (except url) in that file.  This is particularly useful when you aren’t having luck with the other sources.   As an example, many banks use the routing number as the the bankid, but for National City bank, I had no luck until I opened up the website induced OFX file in Notepad and used that bankid data instead.  Too bad they were bought out by the less progressive PNC Bank – I’ll have to downgrade from Direct Connect OFX to website QIF downloads 😦 next month.


If Microsoft Money is still Online, you also have the final option (courtesy of Glyn SImpson) of activating a registry key to enable logging for your online banking communications within Microsoft Money.   This can be achieved by using the ‘provlogs.reg’ registry file found in the MNYCORES\PSS folder and again, will allow you to find all of your your settings (except url) in the log file(s).

To enable the logging, you simply need to double click the file (see below to obtain it), and allow the changes to be made to your registry when prompted.

If you enable the logging, then you will find that two files are created within the same directory that your Money file is in (or sometimes the Microsoft Money installation directory), containing logging information about the online banking call. These files will have names RQ.txt and RS.txt

To turn off the logging, there is a similar file ‘nologs.reg’ which needs to be applied. It is advisable, for security as well as performance reasons, to turn the logging off when you are not using it. To use this file, double click it in the same way as you do with the provlogs file, and when the warning is displayed to insert the information in the registry, click the button to allow it.

‘Provlogs’ is used for Microsoft Money 2003 and later versions. The files to enable the registry changes, are downloadable through the patches page.

Note that in Microsoft Money 2006 and later, it is necessary to reapply the registry file each time when starting Money, or when opening a new file, as these versions removes the logging when you exit the program. You don’t need to use the ‘nologs’ registry file for these versions.

-ameridan

Advertisements

107 Comments »

  1. ameridan said

    I really think the problem lies with the fact that the one clientUID that is generated in the sites.dat file works fine as long as you only have one account user for each financial institution. So, whichever Chase account that is processed first in the scripts gets in with that clientUID, but the next one(s) are rejected. If you have a spouse and they too have an account or there is a joint and a personal account (and perhaps a business account), that single clientUID isn’t going to work for all of the accounts. This issue is brought up in recent comments on Pocketsense’s blog. Robert is considering generating the clientUID differently, so pipe in with a any ideas on his blog.

    For now, Robert offers this idea to get the multiple accounts working:

    The easy fix for having unique ClientUID values for each person would be to install separate copies of the scripts in their own directories (his and hers, as an example). That would keep things separate (and simple). Just copy everything to another folder, and edit the sites.dat and delete the ClientUID line (if it exists). Run setup for each, to configure which accounts to update from that copy (probably just deleting all but hers in the second copy). The ClientUID value is created on first run for a new install, but only if it isn’t found in sites.dat.

    • Ken H said

      Very interesting observation. I thought I could fix the problem by creating a 2nd site entry in sites.dat and call it Chase Business. Unfortunately, that doesn’t work. The Client UID isn’t associated with a particular site; it appears as a standalone line at the bottom of sites.dat. I even tried moving the Client UID line up within the sites.dat entry for Chase; thinking it would then only be associated with that entry. That didn’t work, either.

      This leads to the question: what happens if other banks decide to implement ClientUID? Will we need separate directories for each?

      BTW, this explains why I can only get Chase personal account info and HumblePie can only get business. It’s whichever you request first that generates the ClientUID entry.

    • Ken H said

      Been meaning to post that I did create a second folder with all the Python scripts copied into it. Then deleted all but the Chase Business entry in site.dat. I’m now able to run the two separate Money updates and get correct data for both personal and business accounts. Once the problem was understood, the solution (workaround) was very easy.

      On a completely different topic, is anyone getting downloads for Citi checking or savings accounts? I’ve tried all the different entries in the various listings of OFX settings to no avail. If someone has entries they know work, could you post them? Thanks!

      Happy New Year to all. Let’s hope Quicken is still with us throughout the new year so that all the servers don’t get axed 🙂

  2. ameridan said

    Other institutions can use the same clientUID, but again only for one account. I hope Schwab doesn’t go this route as I have several accounts there.

  3. ameridan said

    A Pocketsense user named John has come with the changes needed in the Python scripts to assign unique clientUIDs for those having multiple accounts at banks requiring ofx version 103. I’m thinking Robert might incorporate these changes into a future release, but for those who can’t wait, see the suggested changes at http://pastebin.com/9UJ333RZ and go to https://www.uuidgenerator.net/ to generate the extra additional version 4 clientUID numbers.

  4. Cindy said

    @Ken H,

    I was able to get Citibank checking to work. Here is what you need for the setup:

    SiteName : CitiBank ACCT
    AcctType : BASTMT #bank statement
    fiorg : CITIBANK
    fid : 2102
    url : https://www.oasis.cfree.com/fip/genesis/prod/02101.ofx
    bankid : #use routing number on your checkbook or savings acct
    brokerid :
    appid :
    appver :
    mininterval:
    timeOffset :

  5. Ken H said

    Thanks for clearing that up. I tried posting my OFX file here. Couldn’t see how you’d been able to get transactions to download.

    • Cindy said

      I’m sorry Ken. My post was a mistake. The settings work to connect but it doesn’t work to download. Still investigating. I’ll reply if I figure it out.

  6. Cindy said

    Sorry, I replied too soon. The settings I found seem to be some kind of test settings that allow you to connect but doesn’t work to download financial data. I’m still searching to get the right settings.

  7. Cindy said

    Ken H or Ameridian,

    I may have found why Citibank is no longer downloading, but I’m hoping someone with more technical understanding may be able to find a workaround. Here’s some info:

    According to this Quicken announcement (http://www.quicken.com/support/citibank-discontinuing-direct-connect-service-quicken), Citibank discontinued direct connect services on October 2, 2015. However, Quicken software still allows Express Web Connect to download without manually logging into the website. This implies that there were changes to the servers. So, I’m assuming this means there is some way to still use pocketsense to download into Money, but I haven’t yet found the settings online.

    Does anyone have ideas how to get this?

  8. Cindy said

    (Cont’d)

    I also found this announcement confirming Citibank’s discontinuation of Direct Connect. https://www.iggsoftware.com/support/articles/ibank-5/citibank-discontinuing-direct-connect-service/

    Igg Software is also able to offer automatic downloads too, so I’m hopeful we can find the settings to update pocketsense.

  9. Ken H said

    Great job finding those posts. But, I think, the second one says it all: “Accounts enabled for OFX services at Citibank prior to 10/2/15 may still work for an unknown amount of time. As far as we know, Citibank will not enable any new accounts after 10/2/15.” I don’t think there’s much chance of success if downloads have to be enabled on the Citi side. I’ve seen that requirement with other banks and until they do their thing, no amount of effort will allow it to work for us.

RSS feed for comments on this post

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: