MS money importing stock buy as mf buy

[Gaurav Kumar]

Hi,

I am not sure if this has been asked before and answered.

I am downloading transactions from Vanguard using their download center, and earlier using the pocketsense.

It seems that items which have been marked as <BUYSTOCK> is being treated as <BUYMF>.

This would not have been an issue for me, except that some of these have been imported as STOCKS already for a different account.

Also, when I am selling these "stocks identified as mf", it is again creating problem, because it is taking these as "<SELLSTOCK>".

I have manually fixed on my investments today, by deleting and adding them again. It was no fun.

Is there anyway to fix these?

I would appreciate an help or pointer to this.

Thank you.

Regards,

Gaurav

[Cal Learner]

While I do import OFX from Vanguard with PocketSense, I only have mutual funds there.

When you look at the Details for that stock in Money, does it say Investment type: Stock>

[Cal Learner]

Correction: I used to download from Vanguard via PocketSense. My last transaction shown in Money was last year, so I did a QFX download just now. No surprises, but no help for you.

Still, it would be good to know  does Details for your stock say Investment type: Stock?

[Gaurav Kumar]

Hi Cal,

Thank you for your prompt response.

The script VUG (ETF) is showing as "Shares".

But when I am adding using OFX, the tag is showing as "<BUYSTOCK>". But MS Money is not able to tag it as shares, and is looking at a list of investments all marked as "Unit Trust".

Regards,
Gaurav

--
You received this message because you are subscribed to the Google Groups "Microsoft Money" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microsoft-mon...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/6086b151-6156-4596-b09a-1f4668c5de83n%40googlegroups.com.

[Cal Learner]

I don't understand " script VUG (ETF) ".

I understand Microsoft Money largely, but am not sure of the terminology for the UK version.

In the Details for the Investment in Money, does it say the Investment type is Stock, Mutual Fund, CD, Bond, Cash Unit Trust, Index, Managed Fund, Other, Gilt, or what?

To get to the Details of an investment, right-click a reference in a register. to that security, select go to investment, select "Details" in the left column. Alternatively, right-click the investment in the Portfolio, and choose the one that involves Details.

[J Hoban]

Cal read " script VUG (ETF) ". as " symbol VUG (ETF) ".

I also have issues with importing Vanguard qfx files having EFT, the file is inconsistent in their handling of ETF.  Transactions are tagged with  BUYSTOCK, SELLSTOCK.  But in later sections, <SECLISTMSGSRSV1><SECLIST>, the EFT is identified as a MF, not STOCK.  Reading the file into MsMoney, the new EFT is created with the investment type "Mutual Fund".  The file I am working with has other unrelated issues... I really need cut the file down to a small example to experiment.  

 Example from the downloaded .qfx file (Note: the units, price, and totals are made up.) 

              <BUYSTOCK>
                  <INVBUY>
                     <INVTRAN>
                        <FITID>767545624
                        <DTTRADE>20250923160000.000[-5:EST]
                        <DTSETTLE>20250924160000.000[-5:EST]
                        <MEMO>BUY
                     </INVTRAN>
                     <SECID>
                        <UNIQUEID>92203J407
                        <UNIQUEIDTYPE>CUSIP
                     </SECID>
                     <UNITS>10
                     <UNITPRICE>50
                     <TOTAL>-500
                     <SUBACCTSEC>CASH
                     <SUBACCTFUND>CASH
                  </INVBUY>
                  <BUYTYPE>BUY
               </BUYSTOCK>

               <POSMF>
                  <INVPOS>
                     <SECID>
                        <UNIQUEID>92203J407
                        <UNIQUEIDTYPE>CUSIP
                     </SECID>
                     <HELDINACCT>CASH
                     <POSTYPE>LONG
                     <UNITS>10
                     <UNITPRICE>50
                     <MKTVAL>500
                     <DTPRICEASOF>20250925160000.000[-5:EST]
                     <MEMO>Price as of date based on closing price
                  </INVPOS>
                  <REINVDIV>N
                  <REINVCG>N
               </POSMF>

        <MFINFO>
            <SECINFO>
               <SECID>
                  <UNIQUEID>92203J407
                  <UNIQUEIDTYPE>CUSIP
               </SECID>
               <SECNAME>VANGUARD TOTAL INTL BOND INDEX ETF
               <TICKER>BNDX
               <UNITPRICE>50.00
               <DTASOF>2026000000[-5:EST]
               <MEMO>Price as of date based on closing price
            </SECINFO>
            <MFTYPE>OPENEND
            <YIELD>0.0
         </MFINFO>

[Cal Learner]

Ah.... I understand. I had not run across the use of the word "script" in that use.  As you know, an ETF should be represented as a stock (shares) in Money. The OFX/QFX should be using <POSSTOCK> and <STOCKINFO> rather than the MF versions.

1. I wonder if other Vanguard ETFs held at Vanguard, such as VOO, VTIP, VOOG, etc  have that same OFX/QFX bug, or is it unique to VUG?

2. I wonder if Vanguard support would like to be aware of this and possibly cause a fix?

3. I wonder if Quicken deals with that (although Quicken might be moving away from QFX)?

If it is systemic and Vanguard is not going to fix it, a scrubber in Python could be made. 

[Gaurav Kumar]

Thank you Cal and J.

I had the same issue with VTI. I realized that when I recently sold VTI and moved the money to VUG.

VTI units were added as Mutual Funds, but at the time of sell, it tagged it as Shares.

Thanks and Regards,
Gaurav.

To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/3b336d5a-8dd0-427a-9aed-da32bdd86116n%40googlegroups.com.

[Cal Learner]

Gaurav, are you a UK user?

I am thinking maybe I will buy a bit of VOO to test that.

I don't write scrubbers quickly, but one day I can be inspired and work on it. That day might be a long time coming. If somebody else is inspired, I do publish some Fidelity scrubbers that are complex but demonstrate some techniques I have found useful.  I also have some much simpler ones.

Thinking about how to implement it might be to require a list of symbols to work on... Or look for any symbol that does not have the format (LLLLX if L stands for any letter and X means X) or (regex "^\w\w\w\wX$") that is treated as a mutual fund in the problem places, and convert those. But that might mess up cases where there are funds/unit trusts in places that don't follow the US symbol convention -- five letters ending in X.

It would be much better if Vanguard was made aware of this, and worked on fixing it. 

[Gaurav Kumar]

My MS money is the UK version.

Other than that, nothing to do with UK.

I was looking for options to shift to US version, but didn't find any simple process.

All my investment accounts are US based.

Thanks and Regards,
Gaurav.

To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/97943137-6658-45eb-af7b-ace6c681cfebn%40googlegroups.com.

[Cal Learner]

Oops... I had gotten muddled, and what I had really been wondering is about our other contributor. I now realize that contributor is probably using a US-based account. I had been wondering if different things were being served to different places. 

I presume your OFX/QFX lists the CUSIP as   <UNIQUEID>922908736 for VUG.

[Gaurav Kumar]

Hi Cal,

If you send me your email ID, I will send the downloaded OFX file to you for analysis..

Below is what I see with the CUSIP.

VTI was sold, VUG was bought. Both are ETFs.

            <STOCKINFO>
                <SECINFO>
                    <SECID>
                        <UNIQUEID>922908769
                        <UNIQUEIDTYPE>CUSIP
                    </SECID>
                    <SECNAME>VANGUARD TOTAL STOCK MARKET ETF
                    <TICKER>VTI
                    <DTASOF>99991231160000.000[-5:EST]
                    <MEMO>SELL
                </SECINFO>
            </STOCKINFO>
            <MFINFO>
                <SECINFO>
                    <SECID>
                        <UNIQUEID>922908736
                        <UNIQUEIDTYPE>CUSIP
                    </SECID>
                    <SECNAME>VANGUARD GROWTH ETF
                    <TICKER>VUG
                    <UNITPRICE>484.08
                    <DTASOF>20250923160000.000[-5:EST]

                    <MEMO>Price as of date based on closing price
                </SECINFO>
                <MFTYPE>OPENEND
                <YIELD>0.0
            </MFINFO>

Regards,
Gaurav

To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/72c3300f-eb0a-45a7-83f6-ed304db5d4a9n%40googlegroups.com.

[J Hoban]

This is messy...  

On Gaurav's sell Vanguard tagged VTI info as STOCKINF.  In my file, when reporting the position it is tagged as MFINFO.  That is a bit weird. 

         <MFINFO>

            <SECINFO>
               <SECID>
                  <UNIQUEID>922908769
                  <UNIQUEIDTYPE>CUSIP
               </SECID>
               <SECNAME>VANGUARD TOTAL STOCK MARKET ETF
               <TICKER>VTI

               <UNITPRICE>327.18
               <DTASOF>20250927160000.000[-5:EST]

               <MEMO>Price as of date based on closing price
            </SECINFO>
            <MFTYPE>OPENEND
            <YIELD>0.0
         </MFINFO>

There are no buys or sells in the file I am looking at,  for the most part it is only reporting positions, in it all ETFs are tagged as MFINFO.  I am wondering if Gaurav's example only happens on sells, or when the whole position is sold out.  

Recently I was helping someone move from paper record keeping to electronic using Money.  Everything went smoothly until I downloaded a Vanguard ofx.  Like Gaurav, I spent a bit of time cleaning up after the import, it likely would have been quicker to have done everything by hand.  That file has Stock, Bond, Mutual Fund, and ETF transactions.  When I have the time I'll pick apart that file and report on the issues I find.  

[Cal Learner]

Progress. 

Already changing <MFINFO> descriptors to <STOCKINFO> with the appropriate adjustments. My identification key is that a real mutual fund or MMF will have a symbol that is 4 capital letters followed by an X.  If there are exceptions to that, let us know.

Next will work on changing appropriate <POSMF> to <POSSTOCK> for CUSIPS identified in round 1.

[Gaurav Kumar]

Hi Cal,

This sounds like a good plan. 5 upper case alphabets ending with X to identify MF.

Regards,
Gaurav

To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/dabd551c-891d-480d-b3a0-2084149c01e0n%40googlegroups.com.

[J Hoban]

Cal, 

I would not have thought to look for a pattern in the <TICKER>, your rule, ccccX, likely applies to other fund families.  

[Cal Learner]

Alert:  WAIT Found a bug or two... there will be an update. Feel free to play, but know that there are already some known bugs in the production of the ModOut.ofx file, which is intended to be the repaired file.

On Monday, September 29, 2025 at 1:57:10 PM UTC-5 Cal Learner wrote:

I wrote code to address the problem discussed on this page.

Seems to be working, but you decide. It is often better to make a copy of your *.mny file, and open the copy to test.  Don't forget to switch back to your main *.mny after testing.

The reason for the odd naming is that I modified my PocketSense scrubber, and expect to later release an update. The included files in scrub_cl6_vanguard.zip:

•  scrub_cl6_vanguard.py #the Python file... not pretty, but questions on this thread are encourage.
•  vangofx.bat  #Use this; modify to match your situation. Finds latest Vanguard qfx in the normal downloads folder, and passes that to the Python program
•  vang.txt #a file with a few notes
•  vang_test_file.qfx #test file I used in working on scrub_cl6_vanguard.py -- ignore normally.

 
https://drive.google.com/file/d/1-eWz6Bxy512CsHg2Xsjbi5Cvd08GSMu_/view?usp=sharing link should give you public access to copy scrub_cl6_vanguard.zip.
 
 Lightly tested. Mistakes are more than possible. Identify what works or not. I am not planning to make this fancy.
 
 Cal Learner.
 
 SHA1                                              Size  Name
---------------------------------------- -------------  ------------
e6b5e6b365c6001a66bb3950c8fc6c0463d16a15         10589  scrub_cl6_vanguard.zip

[Cal Learner]

REVISED:  I wrote code to address the problem discussed on this page.

Seems to be working, but you decide. It is often better to make a copy of your *.mny file, and open the copy to test. I am keeping a copy in scrub_cl6_vanguard.py scrub_cl6_vanguard.py.bk4 so that if you refer to line numbers, I can reference that.

The reason for the odd naming is that I modified my PocketSense scrubber, and expect to later release an update.  Try this one.

Included files in scrub_cl6_vanguard.zip

•  scrub_cl6_vanguard.py #the Python file... not pretty, but questions on this thread are encourage.

•  vangofx.bat  #modify to match your situation. Finds latest Vanguard in the normal downloads folder, and uses that to pass to python.

•  vang.txt #a file with a few notes
•  vang_test_file.qfx #test file I used in working on scrub_cl6_vanguard.py -- ignore normally.

 
https://drive.google.com/file/d/1Tmbzzo86Tjxic2e2qB4-U3FoU3gNHAfQ/view?usp=sharing revised link should give you public access to copy scrub_cl6_vanguard.zip.
 
 Lightly tested. Mistakes are more than possible, although there are fewer than when I first uploaded. Identify what works or not. I am not planning to make this fancy -- going for functional.

 
 Cal Learner.
 
SHA1                                              Size  Name
---------------------------------------- -------------  ------------

ad1469f34a2c0b139241e85a7fa1610da88fdc59         10630  scrub_cl6_vanguard.zip

[Cal Learner]

More Vanguard QFX/OFX thoughts:

1. I suspect that quotes may be marked with the wrong date for mutual funds, and maybe others. A mutual fund's latest closing was Sep 26 as of now, while the market is still open.  

https://finance.yahoo.com/quote/VUG/history/ is a good way to get history (for VUG in my example), although I see that they list a close for Sep 30 even though the market is still open.  It could be interesting to check your Money History that is coming in when you get the Vanguard QFX.

2. When I was testing Vanguard qfx without being scrubbed, I found that it might cause you to define an ETF as a MF. You might check that.

3. With my Fidelity scrubber, I am able to get the closing prices to come in with the right date. I may try to do the same with Vanguard.

[Cal Learner]

Another HOLD: I found another flaw. As written, scrub_cl6_vanguard.py expects to have some code from PocketSense in the same folder. 

I will address this, but if you tried and got an error from an import line, sorry.  I don't think that dependency needs to exist. I will post again with revised code which can truly stand alone.

Also, this has only been tested using Python 2.7.x where x is over 10. I may get it working either with Python 2.7 and with 3.x. PocketSense needs 2.7. The intention is to get this scrubber to either work stand alone, for at least Vanguard, but also be used as a PocketSense scrubber.

[J Hoban]

I have an OFX file downloaded from Vanguard that has a little of everything: stocks, bonds, mutual funds, and EFTs.  The EFTs have the issue documented in this thread.  The OFXAnalyzer gave these issues:

• ·      WARNING: Transaction skipped <BUYSTOCK> and <SELLSTOCK>: INFO security type does not match transaction
• ·       WARNING: Duplicate SECNAME in <DEBTINFO>: NOTE: Money security names need to be unique within the first 70 chars <SECNAME>GOVT NATL MTG ASSN II POOL #00
• ·       ERROR in <SELLDEBT>:<ACCRDINT> should be greater than or equal to zero
• ·       ERROR: TOTAL calculation incorrect for <SELLDEBT>  (also for all transactions) .

Attached is a zip file documenting the issues, has an example problem file, and contains a set of python 3.11 files that scrub the problem file. 

Caution: Not PocketSense, narrowly tested and run only by me.  Use at your own risk.