Skip to content
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

Should CG income be included in the base for calculating ETI substitution effect? #36

Open
MattHJensen opened this issue Jan 12, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@MattHJensen
Copy link
Contributor

MattHJensen commented Jan 12, 2019

Currently the substitution effect is calculated using taxable income (c04800) as the base. See https://github.com/PSLmodels/Behavioral-Responses/blob/master/behresp/behavior.py#L199.

If one were to apply both a non-zero substitution elasticity and a non-zero long-term capital gains elasticity, does it mean that we are double counting some behavior?

And if so, would a reasonable solution be to remove LTCG from the substitution effect by subtracting it from c04800 prior to the calculation of the substitution effect?

If one were to model short-term capital gains separately, would STCG also need to be subtracted from c04800 prior to the calculation of the substitution effect?

--

This is related to PSLmodels/Tax-Calculator#2189, so cc @andersonfrailey @codykallen @MaxGhenis.

This is related to PSLmodels/Tax-Calculator#2180, so cc @evtedeschi3 @martinholmer.

Given Dan's familiarity with the ETI literature, cc @feenberg.

@MattHJensen MattHJensen added the question Further information is requested label Jan 12, 2019
@MattHJensen MattHJensen changed the title Should CG income be included in the base for calculating substitution effect? Should CG income be included in the base for calculating ETI substitution effect? Jan 14, 2019
@martinholmer martinholmer reopened this Feb 22, 2019
@martinholmer
Copy link
Collaborator

The resolution of issue #36 will be handled after version 0.6.0 is released.

@martinholmer
Copy link
Collaborator

@MattHJensen, Can you repeat here the reason you mentioned in our conversation about why removing long-term capital gains from the taxable income base used to compute the substitution effect is desirable.

@martinholmer martinholmer added enhancement New feature or request and removed question Further information is requested labels Feb 22, 2019
@martinholmer
Copy link
Collaborator

@MattHJensen, after our recent phone conversation, I reread issue #36. Your original comment in that issue says nothing about what I understood you to say on the phone. My understanding of the motivation is that somebody specified a reform that change the top bracket rate only for regular income, but not for long-term capital gains or for qualified dividends. And then that person was surprised to see a behavioral response (using the response function) for filing units that had only long-term capital gain or qualified dividend income. If you view that as a problem that needs to be fixed, then (to me) it suggests a couple of important things about your approach:

  1. Both long-term capital gains and qualified dividends need to be netted out of taxable income.

  2. Doing the netting out should be an option (not hardwired into the response function's logic) because many reforms change the rates on both kinds of incomes.

  3. The implications for the income effect also need to be considered.

An alternative way to handle this might be to hardwire the response function to compute the substitution effect as the sum of two terms: a response on regular taxable income (using the MTR on labor income as now) and a response (using MTRs on dividend income) on long-term capital gain plus qualified dividend income. If you could make that approach work, you could hardwire the logic and obviate a need for a confusing option. The income effect could be computed as the sum of two terms computed using the change in taxable income caused by labor-income tax effects and capital-income tax effects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants