This is a follow-up to this discussion -
I've managed to get the vanguard 403b accounts up to date in quicken and into a state where new transactions are recorded correctly using web connect (.qfx files).
It looks the precipitating event for this mess was a change to the .qfx files that vanguard generates. Prior to to 09/2024, each fund was uniquely identified in the file by the CUSIP ID – the same identifier was used for the both individual transactions and holdings information.
Starting last September it appears that the transactions are identified by the CUSIP ID but the holdings by a version of the vanguard fund number. As an example, VSIIX (https://investor.vanguard.com/investment-products/mutual-funds/profile/vsiix#overview) has CUSIP ID = 922908785 and associated security name ‘Vanguard Small-Cap Value Index Fund Institutional Shares’, but an alternate ID = ‘VGI000865’ and associated security name ‘Small-Cap Value Idx Inst’. I’m assuming this change in how a given fund is represented in the .qfx file is what broke the import process.
To get things working again I did the following – as always back up everything and your mileage may vary…
- Delete ‘Unknown Security’ from the quicken security list.
- For all funds in the affected accounts, uncheck ‘Matched with online security’ in the Edit Details dialog.
- Generate vanguard .qfx files – one for each account, and only for the time period not already covered by the entries in quicken for a given account. I don’t know how important this is in the long run, but this way I didn’t have to work through multiple accounts in a given .qfx file, and didn’t have to rely on quicken to accurately match existing transactions.
- Back up quicken file – seriously, do it.
- Pick one of the .qfx files and import the contents into quicken. This time the security matching appears to work – ended up with entries covering the specified time period with the expected ticker and name (associated with the CUSIP) – and most importantly no ‘unknown security’ entries.
- Review everything carefully before accepting. In my case I had number of ‘Near Match’ entries that were new transactions, not matches.
- Rinse, repeat for any other accounts.
- I had to do some cleanup for the transactions that correspond to vanguard fee entries – they came in as miscellaneous transactions that were not actually affecting the share balance.
As a result of this process, the Quicken security list now has both the CUSIP related info and the alternate ID related info for the same fund (ticker symbol) as two separate entries. Also, with the holdings in the .qfx file being specified with the alternate ID, the security comparison is out of sync – for each fund there is a paired set of entries where the ‘Shares Reported’ are listed under the short security name associated with the alternate ID, and the 'Shares in Quicken' under the long security name associated with the CUSIP ID.
Thanks for the replies and comments on the original thread – pieced together this resolution from those and other community threads.
-Frank
[Edit - Fixed Link]
