nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

malfunction of "mutual fund conversion" entry

Howard1

Hello,

Please see the attached files. The graphic is a capture of our entry of data for a "mutual fund conversion". The pdf is the resulting security report. For some reason, the investment amount for all of the converted purchases is the same number. The result is a total transaction value of $510.534.27 for a transaction of $3,582.07. Apparently, the processing of the input for mutual fund conversions has been miscoded.

Quicken Windows Classic Premier version R55.15 build 27.1.55.15

Can this be repaired?

Thank you.

mutual fund conversion report.pdf

mutual fund conversion entry window.jpg

Find more posts tagged with

Comments

Jim_Harman

I suspect that the old fund is set to "Use average cost." A bug in the Mutual Fund Conversion multiples your cost basis by the number of lots you hold if this option is selected.

If possible, revert to a backup from just before the conversion and go to Tools > Security list. Find the old security and click on the name to open the Security Detail view. Click on Edit Details and if the Use average cost box is checked, un check it.

If you don't have a recent backup, you will have to delete the Removed transaction for the old fund and all the Added transactions for the new fund that were generated by the conversion.

Please let us know if this resolves your issue.

Howard1

Thank you for your suggestion, Mr. Harman. We caught this three weeks after the entry, so using the backup from that time would have required re-entry of all transactions since then. Instead, we used the "Edit Multiple Transactions" function in the investment registry to easily remove the previous conversion. After unchecking "Use Average Cost" in the security details view, the subsequent Mutual Fund Conversion was executed properly.

We never knew about this bug.