Prohibited-Transaction Screen
Screen plan transactions for party-in-interest and exemption indicators.
Description
Plan-transaction review depends on parties, transaction type and exemptions.
Plan-transaction review depends on parties, transaction type and exemptions. This screen uses caller-supplied facts.1
Screen plan transactions for party-in-interest and exemption indicators.
When to use Prohibited-Transaction Screen
Use this tool to screen plan transactions for party-in-interest and exemption indicators.
Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
How to use Prohibited-Transaction Screen and understand its results
- Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
- Enter partyInInterest, coveredTransactionType, documentedExemption, transactionAmount, reviewThreshold using the field table and calculation rules, then run the tool.
- Read potentiallyProhibited, thresholdExceeded, reviewStatus. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| partyInInterest | Counterparty is a party in interest | boolean | Required |
| coveredTransactionType | Transaction type is covered | boolean | Required |
| documentedExemption | Documented exemption applies | boolean | Required |
| transactionAmount | Transaction amount | number; minimum: 0 | Required |
| reviewThreshold | Review threshold | number; minimum: 0 | Required |
Enter booleans and nonnegative amount/threshold. Investigate potential cases; otherwise party plus exemption gives review-exemption, else clear.
potential=party AND coveredType AND NOT exemption; amountGate=amount≥threshold Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| potentiallyProhibited | Potentially prohibited transaction | boolean |
| thresholdExceeded | Review threshold exceeded | boolean |
| reviewStatus | Review status | string; one of "clear", "review-exemption", "investigate" |
{
"input": {
"partyInInterest": true,
"coveredTransactionType": true,
"documentedExemption": false,
"transactionAmount": 10000,
"reviewThreshold": 5000
},
"output": {
"potentiallyProhibited": true,
"thresholdExceeded": true,
"reviewStatus": "investigate"
}
}Limitations and assumptions
The amount gate does not alter routing. No exemption validity, legal prohibition or plan compliance is decided.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Investor Threshold Screen: Apply caller-supplied investor thresholds; the caller owns jurisdiction and period rules. For a complementary task, use Contingent-Fee Screen: Screen contingent-fee facts for attest-client prohibition risk.
References
-
Prohibited-Transaction Screen — tool.io
Similar or alternative tools
- Investor Threshold Screen
Apply caller-supplied investor thresholds; the caller owns jurisdiction and period rules.
- Contingent-Fee Screen
Screen contingent-fee facts for attest-client prohibition risk.