Snowball vs Avalanche Payoff Compare Tool
Compare full explicit debt ledgers under smallest remaining balance versus highestAPR extra allocation after rounded interest/minimums, stable original-index ties and same budget. Caller independently verifies edition, jurisdiction, applicability and one currency; screening does not establish legal compliance, coverage or bank approval.
Description
Debt snowball and avalanche strategies prioritize extra payments by different rules.
Debt snowball and avalanche strategies prioritize extra payments by different rules.1
Comparing the same explicit ledger and budget separates those rules from assumptions about borrower behavior. Use Snowball vs Avalanche Payoff Compare Tool to evaluate the supplied inputs under the model explained below.
When to use Snowball vs Avalanche Payoff Compare Tool
Use Snowball vs Avalanche Payoff Compare Tool to evaluate the supplied inputs under the model explained below. Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
How to use Snowball vs Avalanche Payoff Compare Tool and understand its results
- Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
- Enter Debt ids, Opening debt minor, Caller annual apr bps, Caller monthly minimum minor, Caller monthly budget minor, Caller maximum months using the field table and validation rules below, then run the tool.
- Read Snowball remaining minor, Avalanche remaining minor, Snowball interest minor, Avalanche interest minor; 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 |
|---|---|---|---|
| debtIds | Debt ids | array of string | Required; constraints below |
| openingDebtMinor | Opening debt minor | array of number | Required; constraints below |
| callerAnnualAprBps | Caller annual apr bps | array of number | Required; constraints below |
| callerMonthlyMinimumMinor | Caller monthly minimum minor | array of number | Required; constraints below |
| callerMonthlyBudgetMinor | Caller monthly budget minor | number | Required; constraints below |
| callerMaximumMonths | Caller maximum months | number | Required; constraints below |
Enter at most 128 unique nonblank debt IDs with aligned opening balances, annual APRs and monthly minimums. Balances, minimums and budget are nonnegative integer minor units at most 1000000000000; APRs are integers from 0 to 100000 basis points and horizon is 1 to 600 months. Each month add interest rounded half away from zero using balance×APR/120000, then pay min(balance,callerMinimum). Budget must cover all those minimums or execution fails. Allocate leftover by increasing remaining balance for snowball or decreasing APR for avalanche, with original-index ties. Repeat until each strategy pays off or reaches the horizon. Return remaining balances in original order and accumulated interest; the tool does not claim payoff at the horizon or include fees, changing rates or new debt.
monthlyInterestMinor=roundHalfAway(balanceMinor×annualAprBps/120000); minimums first, then priority-ordered extra payments Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| snowballRemainingMinor | Snowball remaining minor | array of number |
| avalancheRemainingMinor | Avalanche remaining minor | array of number |
| snowballInterestMinor | Snowball interest minor | number |
| avalancheInterestMinor | Avalanche interest minor | number |
{
"input": {
"debtIds": [
"small",
"large"
],
"openingDebtMinor": [
100,
200
],
"callerAnnualAprBps": [
0,
12000
],
"callerMonthlyMinimumMinor": [
10,
10
],
"callerMonthlyBudgetMinor": 150,
"callerMaximumMonths": 1
},
"output": {
"snowballRemainingMinor": [
0,
170
],
"avalancheRemainingMinor": [
90,
80
],
"snowballInterestMinor": 20,
"avalancheInterestMinor": 20
}
}Limitations and assumptions
Comparing the same explicit ledger and budget separates those rules from assumptions about borrower behavior. 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 Savings Bucket Sub Account Goals Behavioral Design Lookup for a related task: Savings buckets can partition a displayed balance or goal within an account.
Use ROA Return On Assets Bank Calculator for a related task: Bank return on assets relates signed net income to an adopted average asset measure.
References
Similar or alternative tools
- Savings Bucket Sub Account Goals Behavioral Design Lookup
Savings buckets can partition a displayed balance or goal within an account.
- ROA Return On Assets Bank Calculator
Bank return on assets relates signed net income to an adopted average asset measure.