Insurable Interest Relationship Checker
Audit actual relationship-class evidence against caller independently verified required proof map; no relationship implies legal insurable interest automatically and no eligibility/legal verdict.
Description
An insurable-interest evidence map associates a relationship class with required proof.
An insurable-interest evidence map associates a relationship class with required proof. A document-presence check cannot establish the underlying legal interest.1
The returned values include Caller required interest evidence id, Caller required interest evidence present. The How section below explains the calculation, input rules and interpretation.
When to use Insurable Interest Relationship Checker
Use Insurable Interest Relationship Checker when you need to evaluate the supplied records under the calculation and evidence rules below. No relationship automatically proves insurable interest; no legal eligibility verdict 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 Insurable Interest Relationship Checker 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 callerRelationshipClassIds, callerVerifiedInterestEvidenceRequiredIds, queryRelationshipClassId, observedInterestEvidenceIds using the field table and calculation rules, then run the tool.
- Read callerRequiredInterestEvidenceId, callerRequiredInterestEvidencePresent. 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 |
|---|---|---|---|
| callerRelationshipClassIds | Caller relationship class ids | list of string | Required |
| callerVerifiedInterestEvidenceRequiredIds | Caller verified interest evidence required ids | list of string | Required |
| queryRelationshipClassId | Query relationship class id | string | Required |
| observedInterestEvidenceIds | Observed interest evidence ids | list of string | Required |
Enter aligned nonempty unique nonblank class IDs and required evidence strings, an exact class query and unique nonblank observed evidence IDs. Required evidence strings are nonblank and at most 128 characters; matching is exact without normalization. Return required ID and its presence flag.
requiredEvidence=catalog[exactRelationship]; present=observedEvidence.includes(requiredEvidence) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| callerRequiredInterestEvidenceId | Caller required interest evidence id | string |
| callerRequiredInterestEvidencePresent | Caller required interest evidence present | boolean |
{
"input": {
"callerRelationshipClassIds": [
"family",
"business"
],
"callerVerifiedInterestEvidenceRequiredIds": [
"family-proof",
"financial-interest"
],
"queryRelationshipClassId": "business",
"observedInterestEvidenceIds": [
"family-proof"
]
},
"output": {
"callerRequiredInterestEvidenceId": "financial-interest",
"callerRequiredInterestEvidencePresent": false
}
}Limitations and assumptions
No relationship automatically proves insurable interest; no legal eligibility verdict 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. Extremely large text inputs are rejected. 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 Beneficiary Contingent Split Validator: Primary and contingent beneficiary tiers are alternatives. Each tier should allocate its own complete 10000-basis-point share. For a complementary task, use FNOL First Notice Required Fields Lookup: First-notice completeness distinguishes field presence from verified content. Having every required field does not establish its truth.
References
-
Insurable Interest Relationship Checker — tool.io
Similar or alternative tools
- Beneficiary Contingent Split Validator
Primary and contingent beneficiary tiers are alternatives. Each tier should allocate its own complete 10000-basis-point share.
- FNOL First Notice Required Fields Lookup
First-notice completeness distinguishes field presence from verified content. Having every required field does not establish its truth.