TThank you for this answer, DaveF1006. I spent most of the afternoon trying to figure out why TT was Thank Thank you, DaveF1006, for this answer. I spent much of the afternoon reading TT Community ...
See more...
TThank you for this answer, DaveF1006. I spent most of the afternoon trying to figure out why TT was Thank Thank you, DaveF1006, for this answer. I spent much of the afternoon reading TT Community posts on this issue, after I discovered that TT was calculating a penalty even though I met my total RMD. I saw that this same issue came up in the 2024 tax season, so it is distressing, as an almost-30-year-TT-user and as an Intuit shareholder, that this was not fully resolved during the off-season. That aside, I think the interview needs to ask two separate questions, rather than just one, on the page "Let's get more information" about the RMD. The interview correctly distinguishes between any RMD due before April 1 (for the unique situation of the first RMD at age 73, under current law) and then asks how much the RMD is for that specific account. The correct answer to that question, for Account A in your example is $700. TT should then ask a separate question,, "How much of the total amount of all RMDs are you allocating to this account?" The correct answer to this second question, for Account A in your example, would be $900. The text at the bottom of this page, which says "Note: Do not include the RMD for other retirement accounts you may have. RMDs should be entered separately", is confusing or misdirecting users, since in fact, you do want them to include any portion of the RMD from other accounts that they allocated to this account to satisfy the requirement to take the total RMD for the year. If TT could turn this page into two questions and clarify the language, users would not have to fill in wrong answers to questions (e.g., saying the RMD for Account A was $900, in the example, when the correct response to the question that is actually asked, is $700). Users would not have to construct a "work-around" for a bug in TT. Since you are an employee, perhaps you can forward this suggestion to the TT programmers. Until this issue is fixed, your work-around seems to me the best option.