you! PocketSense is probably not as >> robust as it could be considering that it was created for python2 and with >> community best efforts to convert it to python3 it isn

password for PocketSense, so I wasn't even thinking >>>>>>>>> about that. I should have mentioned that while writing. I expect that 3 >>

set the PocketSense scrubber to remove all MEMOs. Inspired by that, I > reviewed my past MEMOs. Most were not useful. I decided to keep a FEW > always... > > 1. F2O generates

for those who used PocketSense, but that is not necessary. If you want to generate OFX for Fidelity Investment accounts, and don't find the way to do that successfully, say so.

nicely with PocketSense. I use that for one >>>>>> mutual fund held at Vanguard. I presume it also works for stocks/ETFs held >>>>>> at Vanguard

in eg PocketSense? >>>>>> >>>>>> I have tried the following changes to the SymbolMap.csv: >>>>>> 1. Adding a 4th "

required for Pocketsense, so either a parallel install of Pythons is needed, or a "portable" version of Python 3.11 will need to be added instead - it may not worth the effort

folder of PocketSense, could be useful after you know things are working well. If for some reason, you want your own place and/or filename pattern for positions CSV file there is provision

, Cal's Pocketsense scrubber ( >>>>>>>> scrub_cL6.py >>>>>>>> ) >>>>>>>> removes BUYMF

suggest considering PocketSense for investment updates. MSN >> Money, which is used by MSMoneyQuotes, has poor support for non-US-listed >> funds, whereas PocketSense

an older pocketsense ofx file: >>>>> >>>>> >>>>> >>>>> 224381VG5 >>>>> CUSIP >>>

directly with PocketSense). In particular, I told him if closing access was security related, then they could have addressed that in other ways. My suggestions were to either implement

copy of pocketsense to copy older odx files into a backup >>>>>>>> folder, and I have had copies since 9/15. >>>>>>>> >>

file from Pocketsense now initiates an import. Thanks >>> for that. >>> It looks like you've done it again! Brilliant! >>> Can't thank you enough

successfully using Pocketsense to retrieve Fidelity data until a >>>>> few weeks ago, with my last effort today (I download weekly). I wondered >>>>

on from pocketsense (I don't have any direct connect banks >>>>>> anymore). I have two banks (PenFed and NavyFed) + Vanguard so I'm using a >>>

>> pocketsense to either download your transaction files from your bank(s), >>>>> import ofx/qfx files that you download from your bank(s) websites, or just

> recent Pocketsense import, just double-click on the combined ofx file ;) >>> >>> On Tuesday, January 6, 2026 at 12:48:20 PM UTC-6 jeff...@gmail.com >

with direct PocketSense download 2025 December. I *solicit >> others you know to currently work* (please provide the sites.dat >> descriptor entry that goes between

Vanguard that PocketSense used has been off for a while. What they have now is download via OFX. There are some flaws in that downloaded file in that stocks and ETFs are presented as mutual

WORKED. PocketSense. Thanks!!! > > > SiteName : FIDELITY > AcctType : INVSTMT > fiorg : fidelity.com > url : https://ofx.fidelity.com:443/ftgw/OFX/clients

got the pocketsense zip package from >>> https://drive.google.com/file/d/0BzRkycxr1Q1jcUszMjNjS01pbVE/view?usp=share_link&resourcekey=0-NDshuPS8nuR0j8pp2PfAtA

to invoke Pocketsense save downloaded copies of OFX files >> since 03/14/2024 and Vanguard worked with Pocketsense last worked >> 02/15/2025. Janus and Fidelity are

use the PocketSense > scripts to download quotes. Other columns no longer work, because the data > for those is downloaded rather than computed from history and price quotes

or with PocketSense is useful to me. PocketSense is useful for various credit cards, and is still working great for Fidelity-- but I recognize that direct ability is expected to be lost

never tried PocketSense or the OFX Analyzer On Sun, Sep 28, 2025 at 12:22 AM Cal Learner wrote: > If only the bottom one had the problem, I would suspect the ampersand > could be the

Thanks so much for your extra experimentation to better clarify and quantify this bug!! On Tuesday, September 23, 2025 at 10:41:26 AM UTC-4 Cal Learner

server that PocketSense accesses for your >>>>>>> Fidelity transactions and prices. >>>>>>> >>>>>>> Pocketsense

working on pocketsense. I don't have any accounts that use > DirectConnect anymore so I can't test that, but my ofx/qfx files are > imported properly from the import

have made PocketSense scrubbers, and currently have some, with Fidelity being one FI that benefits. At some point I may get inspired to add payee consolidation to the incoming processing