Repository navigation
Conversation
long_term_capital_loss_carryover bundled a person's own carryover (Schedule D line 14) with a terminating estate or trust's unused loss passed through on the final Schedule K-1 (Form 1041), box 11, code D, which 26 U.S.C. 642(h)(1) and Reg. 1.642(h)-1(a) allow to the beneficiary. It now adds two leaf inputs: own_long_term_capital_loss_carryover and estate_or_trust_long_term_capital_loss_carryover. The K-1 has a short-term counterpart (box 11, code C, Schedule D line 5), so short_term_capital_loss_carryover adds the matching short-term leaves. An amount entered as the sum is still used for that year, and the microdata uprating overrides keep a dataset column holding either sum on the series its leaves follow. Arizona's property tax credit adds the short-term memo back on line D, as ITR 12-1 item (7) requires and as it already does for the long-term one; d1107 keeps estate or trust losses in that addback. Fixes #10021 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review round 1 on #10211: - A sum entered for a simulation now becomes the person's own carryover when a Simulation or Microsimulation is built, as employment_income becomes employment_income_before_lsr. Core does not uprate a variable that adds others, so a 2024 sum read for 2026 (in a situation, or a dataset loaded by Core's variable-centric loader) would otherwise have dropped to zero. A sum entered for one person also zeroed every other person's leaves in that simulation; it no longer does. - The sums cite 26 U.S.C. 642(h)(1) for the estate or trust part. Their references now follow the repo's page rules and cite the Schedule K-1 (Form 1041) instructions. - short_term_capital_gains and long_term_capital_gains now say they are Schedule D lines 7 and 15, net of the carryover the memo records. - Arizona's code C add-back is marked as pending Max's confirmation (d1512); d1107 ruled on code D. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WIP: validation still running; the full description follows.
Splits
long_term_capital_loss_carryoverinto the person's own carryover and the carryover from a terminated estate or trust (Schedule K-1 (Form 1041), box 11, code D). Adds the short-term counterpart (box 11, code C) the same way. Follow-up to #9762 per d1107. Fixes #10021.🤖 Generated with Claude Code