-
-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Combine CG/DIV rates from AMT and Reg Tax into one set of params? #861
Comments
On Fri, 12 Aug 2016, Matt Jensen wrote:
They have been linked in the law for some years now, people might be
I can understand that. dan
|
Thanks @feenberg. This could be a solution on the webapp, but it wouldn't help users of the Tax-Calculator package. |
Now that #913 is merged, separating the rate structures applied to pass through income and other taxable income, this discussion is even more important. Now there are two opportunities for users to make mistakes:
cc @feenberg, @martinholmer, @zrisher, @GoFroggyRun, @andersonfrailey, @talumbau |
It has been almost twenty days since the last comment was added to open issue #861. Isn't it true that the potential confusion for TaxBrain users has been eliminated in TaxBrain version 0.6.7? (See the discussion of TaxBrain issue 340.) Can we close issue #861? |
@MattHJensen, Can we close issue #861? Or are there still outstanding related issues? This issue has been open since August 12. |
Sorry for not seeing the earlier comment. Happy to close this issue and doing so now. Thanks to everyone for helping to resolve it. |
Many TC and TB users have been extremely confused when they reduce the LT capital gains/dividends rates and end up losing very little revenue since almost everything is captured back by the AMT.
I wonder if we should link the AMT LT CG/DIV rates to the regular tax CG/DIV rates. Alternatively, we might want to provide some warning message if a user changes the Regular Tax CG/DIV rates but not the AMT CG/DIV rates.
There could be some other solution as well. Right now this is a major stumbling block for our users.
cc @feenberg, @Amy-Xu, @martinholmer, @GoFroggyRun
This is related to ospc-org/ospc.org#295 (comment) and potentially to #182.
The text was updated successfully, but these errors were encountered: