Beat Holdings Conflict
Find securities holdings that overlap organizations on a reporting beat.
Description
A beat-holdings conflict screen identifies overlapping issuer labels between reporting coverage and supplied holdings.
A beat-holdings conflict screen identifies overlapping issuer labels between reporting coverage and supplied holdings. Matching is purely textual.1
Find securities holdings that overlap organizations on a reporting beat.
When to use Beat Holdings Conflict
Use this tool to find securities holdings that overlap organizations on a reporting beat.
Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
How to use Beat Holdings Conflict and understand its results
- Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
- Enter coveredOrganizations, heldSecurities using the field table and calculation rules, then run the tool.
- Read conflictingHoldings, conflictCount, conflictFound. 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 |
|---|---|---|---|
| coveredOrganizations | Organizations on the beat | list of string | Required |
| heldSecurities | Organizations represented in holdings | list of string | Required |
Trim/lowercase both lists and discard blanks. Compare covered labels as a set, deduplicate matched holdings in first-seen order and return normalized overlaps, count and boolean. Empty lists are allowed.
conflict=unique overlapping holdings count>0 Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| conflictingHoldings | Holdings overlapping the beat | list of string |
| conflictCount | Conflict count | integer; minimum: 0 |
| conflictFound | Conflict found | boolean |
{
"input": {
"coveredOrganizations": [
"Acme",
"Beta"
],
"heldSecurities": [
"Gamma",
"ACME"
]
},
"output": {
"conflictingHoldings": [
"acme"
],
"conflictCount": 1,
"conflictFound": true
}
}Limitations and assumptions
No holdings are fetched and no issuer identity, subsidiary relationship, materiality or policy exception is resolved.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. 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 Protest Support Conflict: Screen protest-support facts for assignment conflict. For a complementary task, use Procurement Donor Overlap: Compare caller-supplied requirements and observations for procurement donor overlap.
References
-
Beat Holdings Conflict — tool.io
Similar or alternative tools
- Protest Support Conflict
Screen protest-support facts for assignment conflict.
- Procurement Donor Overlap
Compare caller-supplied requirements and observations for procurement donor overlap.