Beneficiary Contingent Split Validator
Validate caller actual primary/contingent allocation tiers independently, each 10000 bps, not adding alternatives together; no beneficiary validity, per stirpes, survivorship or estate advice.
Description
Primary and contingent beneficiary tiers are alternatives.
Primary and contingent beneficiary tiers are alternatives. Each tier should allocate its own complete 10000-basis-point share.1
The returned values include Primary split basis points total, Contingent split basis points total, Each independent tier allocates exactly all. The How section below explains the calculation, input rules and interpretation.
When to use Beneficiary Contingent Split Validator
Use Beneficiary Contingent Split Validator when you need to evaluate the supplied records under the calculation and evidence rules below. No beneficiary legal validity, per-stirpes, survivorship or estate advice is supplied.
Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
How to use Beneficiary Contingent Split Validator and understand its results
- Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
- Enter primaryBeneficiaryIds, primaryBeneficiaryBasisPoints, contingentBeneficiaryIds, contingentBeneficiaryBasisPoints using the field table and calculation rules, then run the tool.
- Read primarySplitBasisPointsTotal, contingentSplitBasisPointsTotal, eachIndependentTierAllocatesExactlyAll. 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 |
|---|---|---|---|
| primaryBeneficiaryIds | Primary beneficiary ids | list of string | Required |
| primaryBeneficiaryBasisPoints | Primary beneficiary basis points | list of number | Required |
| contingentBeneficiaryIds | Contingent beneficiary ids | list of string | Required |
| contingentBeneficiaryBasisPoints | Contingent beneficiary basis points | list of number | Required |
Enter aligned nonempty unique nonblank IDs and integer shares 0–10000 separately for each tier. Uniqueness applies within each tier; an ID may occur in both. Return totals and their joint exact-allocation flag. Incorrect totals return false rather than an input error.
primaryTotal=sum(primaryBps); contingentTotal=sum(contingentBps); valid=bothTotalsExactly10000 Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| primarySplitBasisPointsTotal | Primary split basis points total | number |
| contingentSplitBasisPointsTotal | Contingent split basis points total | number |
| eachIndependentTierAllocatesExactlyAll | Each independent tier allocates exactly all | boolean |
{
"input": {
"primaryBeneficiaryIds": [
"a",
"b"
],
"primaryBeneficiaryBasisPoints": [
6000,
4000
],
"contingentBeneficiaryIds": [
"c"
],
"contingentBeneficiaryBasisPoints": [
10000
]
},
"output": {
"primarySplitBasisPointsTotal": 10000,
"contingentSplitBasisPointsTotal": 10000,
"eachIndependentTierAllocatesExactlyAll": true
}
} Limitations and assumptions
No beneficiary legal validity, per-stirpes, survivorship or estate advice is supplied.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose 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 Insurable Interest Relationship Checker: An insurable-interest evidence map associates a relationship class with required proof. A document-presence check cannot establish the underlying legal interest. For a complementary task, use DIME Formula Need Components Calculator: DIME inventories debt, income replacement, mortgage and education separately. Mutually exclusive entries prevent double-counting the mortgage.
References
-
Beneficiary Contingent Split Validator — tool.io
Similar or alternative tools
- Insurable Interest Relationship Checker
An insurable-interest evidence map associates a relationship class with required proof. A document-presence check cannot establish the underlying legal interest.
- DIME Formula Need Components Calculator
DIME inventories debt, income replacement, mortgage and education separately. Mutually exclusive entries prevent double-counting the mortgage.