Model Wash Sale of Schwab Mutual Fund

BSabolik
BSabolik Quicken Windows Subscription Member ✭✭
edited September 13 in Investing (Windows)

I've know this has been asked and answered but I don't believe any of the solutions are correct! I recently sold my second partial batch of USATX mutual funds with Schwab. Both sales incurred small disallowed losses due to reinvestment of dividends that USATX paid before and after the sale within the 30 day before and after period.

Schwab uses FIFO for lot handling and average cost accounting for mutual funds. Ideally we want to lower the cost of those first shares of the sale and raise the cost of the reinvested dividend shares but we also want those dividend shares to go out first on the next sale.

I understand how to do everything but controlling the allocation of shares on the next sale. Setting Quicken to average cost grays out the window allowing you to pick which shares each sale uses. Unchecking the average cost is in direct contrast to Schwab's accounting method but allows selection of lots for sales. Changing the dates ruins the past net worth calculations as well as just seems like a horrible idea.

I've used Quicken all my life (many years) they should be able to handle this with a check box and a few additional fields to allow the correct way to process disallowed loss wash sales. I'll come up with a less than optimal way to handle this but I hate that people think that because it is answered on this forum that Quicken doesn't need to work on this!

Tagged:

Comments

  • BSabolik
    BSabolik Quicken Windows Subscription Member ✭✭

    Here's my procedure to at least be able to balance to historical statements…

    Procedure to Handle Disallowed Loss of USTAX Sales on Quicken

    • Usually caused by reinvested dividends 30 days before a sale and 30 days after.
    • Schwab uses FIFO for lot handling and average cost accounting.
    • Quicken cannot fully support these transactions.
      • Cannot handle lowering the costs of the first out shares to zero the loss up to total shares reinvested
      • Cannot handle raising the costs of the dividends causing the wash sale while keeping balances of available to past statements.
      • Cannot handle pushing those lots to the top of the queue so they are sold next.
      • Goal: To balance cost basis with Schwab’s statements. There is no way to keep the lots in-sync! This means we cannot modify the dividends in the past month that contributed to the disallowed loss nor can we change dates of dividends!
    • Therefore, we need to:
      • Change only the ReinvDiv’s from the current statement period to just Div’s.
      • Create a Buy for the # of shares from the “changed” ReinvDiv’s.
        • Set the total cost initially to the cost of the ReinvDiv’s.
        • Compare Quicken’s Cost Basis to the Schwab’s statement
        • The difference should be the disallowed loss.
        • Add this difference back into the total cost of the ReinvDiv’s
        • Double check that the Cost Basis is now in balance.
      • Fund the Buy with the amount equal to the Disallowed Loss and offset the entry to the category, “Disallowed Loss”. Set Payee to IRS indicate in memo it was from the wash sale due to the dividends and their dates.
      • Indicate on all related transactions that a disallowed loss is involved.
  • q_lurker
    q_lurker Quicken Windows Subscription SuperUser ✭✭✭✭✭

    I don’t recall anyone before asking about a wash sale combined with use of average cost. You are further complicating the question by wanting to specify lots. I would not put this in the asked-and-answered category. Your case, while not necessarily unique, does strike me as uncommon.

    A few perhaps disjointed comments:

    I have never liked or trusted Quicken’s average cost implementation. Part of that is not having used it. Some of it is knowing the IRS used to allow two average cost methods and Quicken only had one implemented. Some of it was knowing data would get out of sync (inconsistent) if the user did a MF conversion, Stock acquisition, or Shares Transferred action( and perhaps others). I also never understood how Quicken maintained average cost when both buys and sells were taking place

    As I do understand it, the average cost in Quicken is a very internal calculation. When you sell shares the program still treats that as a FIFO sale. Thus, problems develop with those transaction actions I listed above.

    I also view wash sale rules as screwy on their own making it difficult to determine when and how they apply. And, as I understand it, the IRS has changed some of those rules recently.

    So how might something play out in you situation? Suppose one had 1000 shares at an avg cost of $11/share (11,000 total cost). Investor sells 1 share at $9 for a $2 loss. Now has 999 shares with $10,989 basis. Buys 1 share for $10 raising the total basis to 10,999. The wash sale rules say the immediate capital loss is not allowed, such that the $2 gets added on to the ongoing basis.

    In all likelihood, I would edit that sale to sell at $11 (no immediate cap loss) and edit the buy to be at $12 raising the total basis to the $11,001 where it should be.

    I would not ask Quicken programmers to figure out an algorithm to cover all possible pertubations of these cases.

  • BSabolik
    BSabolik Quicken Windows Subscription Member ✭✭

    With good financial software, a user should be able to mirror the security lots of their brokerage firm at any point in time and still generate a valid Net Worth statement for any point in time. In this case, it means adding fields, (possibly a child row) to the transaction (lot) such as DisallowedDate, DisallowedLoss and DisallowedLossTransferred which would affect the cost basis while maintaining the original data.

    The DisallowedLoss field would be used to lower the cost basis of the lot sold and the DisallowedLossTransferred field would be used to raise the cost of the offending Buy or ReinvDiv transactions. The outgoing sales queue would still be FIFO but with the sort Key prepended with a character that would force all lots with an amount in DisallowedLossTransferred to the top.

    The queue and costing methods are separate and should not be thought as one excluding the other.

    Quicken is coasting on years of development… a few enhancements like this should be expected.

This discussion has been closed.