SEPA Cutoff Deadline Lookup
Resolve caller SEPA bank local cutoff and weekend/explicit-holiday processing calendar with supplied business-day lag; exact cutoff is included, time zone/DST already caller resolved, not a network guarantee or universal SEPA deadline.
Description
A local bank cutoff and processing calendar jointly determine the modeled Single Euro Payments Area (SEPA) processing and settlement dates.
A local bank cutoff and processing calendar jointly determine the modeled Single Euro Payments Area (SEPA) processing and settlement dates. Time zone and daylight-saving conversion must already be resolved.1
The returned values include Effective processing civil date, Caller modeled settlement civil date, Missed caller same day cutoff. The How section below explains the calculation, input rules and interpretation.
When to use SEPA Cutoff Deadline Lookup
Use SEPA Cutoff Deadline Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. No universal SEPA deadline, time-zone inference or network settlement guarantee is supplied.
Prepare observed financial records and verified caller terms. Use one currency for integer minor-unit money and preserve leading zeros in identifier text. One basis point is 0.01 percentage points. Resolve dates, local clocks, counting rules and evidence flags as specified.
How to use SEPA Cutoff Deadline Lookup and understand its results
- Prepare observed financial records and verified caller terms. Use one currency for integer minor-unit money and preserve leading zeros in identifier text. One basis point is 0.01 percentage points. Resolve dates, local clocks, counting rules and evidence flags as specified.
- Enter submissionLocalDate, submissionLocalClock, callerLocalCutoffClock, callerBusinessDaySettlementLag, callerHolidayDates using the field table and calculation rules, then run the tool.
- Read effectiveProcessingCivilDate, callerModeledSettlementCivilDate, missedCallerSameDayCutoff. 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 |
|---|---|---|---|
| submissionLocalDate | Submission local date | string | Required |
| submissionLocalClock | Submission local clock | string | Required |
| callerLocalCutoffClock | Caller local cutoff clock | string | Required |
| callerBusinessDaySettlementLag | Caller business day settlement lag | number | Required |
| callerHolidayDates | Caller holiday dates | list of string | Required |
Enter exact real Gregorian YYYY-MM-DD dates in 1900–2199, exact HH:mm local clocks, integer lag 0–30 and explicit holiday dates. Weekends and supplied holidays are closed. On an open date only, submission strictly after cutoff sets the missed flag; equality qualifies. Advance to an open date and count later business days for settlement. Return processing date, settlement date and missed-open-day-cutoff flag. Calendar searches are bounded to 3660 iterations and generated dates must stay supported.
processing=nextBusinessDay(open and submission>cutoff?date+1:date); settlement=processing+businessDayLag Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| effectiveProcessingCivilDate | Effective processing civil date | string |
| callerModeledSettlementCivilDate | Caller modeled settlement civil date | string |
| missedCallerSameDayCutoff | Missed caller same day cutoff | boolean |
{
"input": {
"submissionLocalDate": "2025-01-03",
"submissionLocalClock": "17:00",
"callerLocalCutoffClock": "16:00",
"callerBusinessDaySettlementLag": 1,
"callerHolidayDates": [
"2025-01-06"
]
},
"output": {
"effectiveProcessingCivilDate": "2025-01-07",
"callerModeledSettlementCivilDate": "2025-01-08",
"missedCallerSameDayCutoff": true
}
}Limitations and assumptions
No universal SEPA deadline, time-zone inference or network settlement guarantee 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 ACH Settlement Window Same Day Lookup: Same-day ACH window selection compares a local submission clock with verified cutoff/settlement pairs. A missed final window must remain explicit. For a complementary task, use Open Banking Consent Expiry Days Lookup: An open-banking consent window includes grant date and excludes expiry. Revocation evidence separately suppresses the timing outcome.
References
-
SEPA Cutoff Deadline Lookup — tool.io
Similar or alternative tools
- ACH Settlement Window Same Day Lookup
Same-day ACH window selection compares a local submission clock with verified cutoff/settlement pairs. A missed final window must remain explicit.
- Open Banking Consent Expiry Days Lookup
An open-banking consent window includes grant date and excludes expiry. Revocation evidence separately suppresses the timing outcome.