Beneficial Ownership Control Prong Checker

Audit independently established control-prong evidence separately from ownership percentages; no beneficial-owner identity inferred. Independently established columns: independent verification of significant managerial control, person identity verified, applicable rule context verified. Unknown observations and overlapping candidates retained; not automatic semantic parsing, proof of identity, fraud, authenticity, compliance or coverage.

Description

A beneficial-ownership control-prong assessment requires defined evidence of the relevant person and role.

A beneficial-ownership control-prong assessment requires defined evidence of the relevant person and role.^[1]

This checker compares annotations rather than interpreting ownership records or current rules. Use Beneficial Ownership Control Prong Checker to compare independently annotated features with the fixed rules.

When to use Beneficial Ownership Control Prong Checker

Use Beneficial Ownership Control Prong Checker to compare independently annotated features with the fixed rules. Annotate the ordered features below independently; use separate binary arrays for observed presence and whether each feature is known.

How to use Beneficial Ownership Control Prong Checker and understand its results

Annotate the ordered features below independently; use separate binary arrays for observed presence and whether each feature is known.
Enter Observed feature flags, Feature known flags using the field table and validation rules below, then run the tool.
Read Compatible Classes, Witnessed Classes, Unknown Feature Indices in the Result object; interpret the units, signs, ordering and unknown-value placeholders described below.
Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.

Input field	Meaning	Value type	Requirement
observedFeatureFlags	Observed feature flags	array of number	Required; constraints below
featureKnownFlags	Feature known flags	array of number	Required; constraints below

Enter aligned binary observed-feature and known-feature arrays in the exact column order below. The array length must match the fixed rule width. In the rule table, 1 requires presence, 0 requires absence and −1 ignores that column. A known observation contradicting a required value excludes a class; an unknown observation leaves it compatible. A witnessed class requires all nonignored columns to be known and equal to their required values. Unknown-feature indices are zero based and lists preserve rule order. The tool does not identify people, inspect documents or establish applicable beneficial-ownership coverage.

compatible = no known rule contradiction; witnessed = every nonignored rule known and matched

Use the field order, units and branch conditions described above.

Zero-based feature index	Independently annotated feature
0	independent verification of significant managerial control
1	person identity verified
2	applicable rule context verified

Fixed class	Feature 0	Feature 1	Feature 2
documented-control-prong-candidate	1	1	1

Output field	Meaning	Value type
result	Object containing the named result fields below.	object
result.compatibleClasses	Fixed-rule classes with no known contradiction; compatibility can depend on unknown features.	array of string
result.witnessedClasses	Fixed-rule classes whose nonignored requirements are all known and matched.	array of string
result.unknownFeatureIndices	Zero-based indices marked unknown, irrespective of their observed-value placeholders.	array

json

{
  "input": {
    "observedFeatureFlags": [
      1,
      1,
      1
    ],
    "featureKnownFlags": [
      1,
      1,
      1
    ]
  },
  "output": {
    "result": {
      "compatibleClasses": [
        "documented-control-prong-candidate"
      ],
      "witnessedClasses": [
        "documented-control-prong-candidate"
      ],
      "unknownFeatureIndices": []
    }
  }
}

Limitations and assumptions

This checker compares annotations rather than interpreting ownership records or current rules. Apply the exact scope and assumptions explained above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.

Alternative or Complementary methods

Use EDD Trigger Checker for a related task: Enhanced due diligence triggers depend on the institution's applicable risk policy.

Use PEP Flag Checker for a related task: PEP review depends on relevant roles and independently established evidence.

References

Beneficial Ownership Control Prong Checker — tool.io

Similar or alternative tools

EDD Trigger Checker
Enhanced due diligence triggers depend on the institution's applicable risk policy.
PEP Flag Checker
PEP review depends on relevant roles and independently established evidence.