Relationship Bonus Tracker

Compare caller-supplied expected and observed records for relationship bonus tracker.

Description

Relationship bonuses commonly depend on several separately defined account conditions.

Relationship bonuses commonly depend on several separately defined account conditions. A completed-label checklist helps track the supplied terms.^[1]

Compare caller-supplied expected and observed records for relationship bonus tracker.

When to use Relationship Bonus Tracker

Use this tool to compare caller-supplied expected and observed records for relationship bonus tracker.

Prepare the supplied account terms, common-currency amounts or recorded indicators requested. Determine applicable thresholds separately.

How to use Relationship Bonus Tracker and understand its results

Prepare the supplied account terms, common-currency amounts or recorded indicators requested. Determine applicable thresholds separately.
Enter bonusRequirements, completedRequirements using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. 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
bonusRequirements	Bonus requirements	list of string	Required
completedRequirements	Completed requirements	list of string	Required

Enter bonusRequirements as the nonempty expected list and completedRequirements as observations, which may be empty. Trim entries, compare case-insensitively using en-US lowercase and collapse duplicates. Return matched/missing expected labels and unexpected observed labels. Output follows first occurrence order with the last duplicate’s trimmed spelling.

coverage%=100matchedUnique/expectedUnique

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "bonusRequirements": [
      "direct deposit",
      "minimum balance",
      "new money"
    ],
    "completedRequirements": [
      "direct deposit",
      "new money"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "direct deposit",
      "new money"
    ],
    "missing": [
      "minimum balance"
    ],
    "unexpected": []
  }
}

Limitations and assumptions

No bank terms, balances, qualifying deposits or bonus payment are verified. Blank entries are errors; requirements are entirely caller-supplied and items have equal weight.

Numeric inputs, where present, 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.

Alternative or Complementary methods

Use Deposit Account Comparison: Compare two deposit accounts from balances, disclosed APYs, and annual fees. For a complementary task, use Escrow Cushion Check: Compare a projected escrow cushion with a caller-supplied month limit.

References

Relationship Bonus Tracker — tool.io

Similar or alternative tools

Deposit Account Comparison
Compare two deposit accounts from balances, disclosed APYs, and annual fees.
Escrow Cushion Check
Compare a projected escrow cushion with a caller-supplied month limit.