PolicyEngine / PolicyEngine/policyengine-taxsim

ND 2025 single 951Kpsemp plus lots more

Open
#762 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
17
Forks
10
Avg merge
15h 55m
Merged PRs (30d)
1

Description

See http://taxsim.nber.org/out2psl/762

TA gives QBID, PE does not.

We have 7 variables potentially subject to QBID and we need to discuss with a knowledgable person what the appropriate treatment is. Then we need to make sure out treatment of FICA is also consistent with that. Maybe the following would make sense:

psemp,ssemp  FICA but not QBID
pbusinc,sbusinc  QBID without phaseout but not FICA
pprofinc, sprofinc  QBID with phaseout and FICA

This doesn't include a category for QBID with phaseout and no FICA. I think lawyers have argued for that treatment, but I don't thik it was accepted by the IRS or the Tax Court. We could note in the docs that pbusinc and sbusinc should be net of "reasonable salary" to the owner that would be subject to FICA. I can't really be sure about any of this.

There are also passive losses to consider. These are subject to a limitation. I am thinking that we consider all QBID type income to be active except scorps, and assume scorp income is passive. If there is a loss, FICA is not relevant, so telling users to put all passive income in the scorp slot should be a problem. We could rename it passpass.

Anyway, we should get this coordinated before we have many users!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked TAXSIM case at taxsim.nber.org/out2psl/762 and trace how the seven listed income variables are currently handled. Consult a knowledgeable tax expert on QBID, FICA, phaseouts, and passive losses; done means an agreed treatment is implemented and the relevant user-facing documentation explains the assumptions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
fintech-quant
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.