Description
Caller supplies cap, day basis and whole-unit rounding convention; no statute is selected.
A policy scenario makes eligibility bases, rates, thresholds, periods, and costs explicit. A calculated share or balance follows those assumptions. It does not select the governing policy or establish what caused an observed program outcome.
Caller supplies cap, day basis and whole-unit rounding convention; no statute is selected.
When to use this tool
Use it for statutory cap proration caller rule when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter fullCap, eligibleDays, periodDays, roundDown. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read rawCap, appliedCap. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require nonnegative fullCap, positive integer periodDays, and eligibleDays within zero and periodDays. Compute rawCap=fullCap*eligibleDays/periodDays and optionally floor it to a whole numeric unit for appliedCap.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| fullCap | Full Cap | Required. Finite number; minimum 0. |
| eligibleDays | Eligible Days | Required. Safe integer; minimum 0. |
| periodDays | Period Days | Required. Safe integer; minimum 1. |
| roundDown | Floor the raw cap to whole numeric units when true; no currency increment is inferred. | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| rawCap | Raw Cap | Required. Finite number. |
| appliedCap | Applied Cap | Required. Finite number. |
{
"input": {
"fullCap": 100,
"eligibleDays": 10,
"periodDays": 30,
"roundDown": true
},
"output": {
"rawCap": 33.333333333333336,
"appliedCap": 33
}
} Limitations and assumptions
- RoundDown floors whole units, not cents or an inferred currency increment. The caller supplies the legally applicable period, day count, and proration rule.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For statutory cap proration caller rule, check the source records and the supplied rule before comparing the result with another method. Consult the applicable authoritative rule when deciding eligibility, legal timing, fees, or obligations.
References
Similar or alternative tools
- Statutory Cap Component Inclusion
Apply supplied component-inclusion flags and a supplied cap; no statutory classification is inferred.
- Benefit Cliff Discrete Income Gap
Calculate benefit cliff discrete income gap from explicit caller-supplied inputs.