Reg CC Funds Availability Schedule Calculator
Route caller verified RegCC tranche amounts/lags through explicit holiday/weekend calendar excluding deposit day, distinct from ACH cutoff/settlement schedule; no standard threshold or exemption invented. Caller independently verifies edition, jurisdiction, applicability and one currency; screening does not establish legal compliance, coverage or bank approval.
Description
Funds availability assigns different deposit amounts to different release dates.
Funds availability assigns different deposit amounts to different release dates.1
Business-day counting requires the institution's applicable weekend and holiday calendar as well as verified tranche rules. Use Reg CC Funds Availability Schedule Calculator to evaluate the supplied inputs under the model explained below.
When to use Reg CC Funds Availability Schedule Calculator
Use Reg CC Funds Availability Schedule Calculator 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 Reg CC Funds Availability Schedule Calculator and understand its results
- Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
- Enter Deposit date, Deposit minor, Caller tranche minor, Caller tranche business day lags, Caller weekend weekdays, Caller holiday dates using the field table and validation rules below, then run the tool.
- Read Caller tranche availability dates, Caller cumulative available 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 |
|---|---|---|---|
| depositDate | Deposit date | string | Required; constraints below |
| depositMinor | Deposit minor | number | Required; constraints below |
| callerTrancheMinor | Caller tranche minor | array of number | Required; constraints below |
| callerTrancheBusinessDayLags | Caller tranche business day lags | array of number | Required; constraints below |
| callerWeekendWeekdays | Caller weekend weekdays | array of number | Required; constraints below |
| callerHolidayDates | Caller holiday dates | array of string | Required; constraints below |
Enter a real Gregorian deposit date in 1900–2199, deposit and aligned nonempty tranche amounts as nonnegative integer minor units up to 1000000000000, and nonnegative nondecreasing integer business-day lags from 0 to 1000. Tranche amounts must sum exactly to the deposit. Supply weekend weekdays 0=Sunday through 6=Saturday, leaving at least one working weekday, and distinct real holiday dates; empty calendars are allowed. Lag 0 returns the deposit date even on a nonworking day; positive lags count working days strictly after it. Return tranche dates and cumulative amounts in supplied order. Calendar walking is bounded and resulting dates must remain supported. No Reg CC schedule, deposit cutoff or exception is installed.
releaseDate[i]=callerBusinessDaysAfter(depositDate,lag[i]); cumulativeMinor[i]=ΣtranchesThroughI Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| callerTrancheAvailabilityDates | Caller tranche availability dates | array of string |
| callerCumulativeAvailableMinor | Caller cumulative available minor | array of number |
{
"input": {
"depositDate": "2026-01-02",
"depositMinor": 1000,
"callerTrancheMinor": [
200,
800
],
"callerTrancheBusinessDayLags": [
1,
2
],
"callerWeekendWeekdays": [
0,
6
],
"callerHolidayDates": [
"2026-01-05"
]
},
"output": {
"callerTrancheAvailabilityDates": [
"2026-01-06",
"2026-01-07"
],
"callerCumulativeAvailableMinor": [
200,
1000
]
}
}Limitations and assumptions
Business-day counting requires the institution's applicable weekend and holiday calendar as well as verified tranche rules. 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 Mobile Check Deposit Fraud Hold Extension Regcc Interplay Lookup for a related task: Mobile deposit availability and exception holds depend on product terms and applicable rules.
Use Hold Extension Exception Lookup for a related task: Deposit hold exceptions depend on observed facts and applicable policy.
References
Similar or alternative tools
- Mobile Check Deposit Fraud Hold Extension Regcc Interplay Lookup
Mobile deposit availability and exception holds depend on product terms and applicable rules.
- Hold Extension Exception Lookup
Deposit hold exceptions depend on observed facts and applicable policy.