SAR Filing Window Days Lookup
Route caller independently established SAR trigger/window/extension to inclusive civil deadline, separate unavailable filing evidence; no default legal clock or actual reporting advice. Caller independently verifies edition, jurisdiction, applicability and one currency; screening does not establish legal compliance, coverage or bank approval.
Description
A SAR deadline model needs an independently established trigger, window and extension.
A SAR deadline model needs an independently established trigger, window and extension.1
Date arithmetic does not select the governing filing rule or certify that filing occurred. Use SAR Filing Window Days Lookup to evaluate the supplied inputs under the model explained below.
When to use SAR Filing Window Days Lookup
Use SAR Filing Window Days Lookup 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 SAR Filing Window Days Lookup and understand its results
- Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
- Enter Caller sar trigger date, Caller verified calendar day window, Caller independent extension days, As of date, Filing evidence known, Filing observed using the field table and validation rules below, then run the tool.
- Read Caller modeled sar deadline, Days until caller deadline, As of after caller deadline, Known filed, Filing evidence unknown; 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 |
|---|---|---|---|
| callerSarTriggerDate | Caller sar trigger date | string | Required; constraints below |
| callerVerifiedCalendarDayWindow | Caller verified calendar day window | number | Required; constraints below |
| callerIndependentExtensionDays | Caller independent extension days | number | Required; constraints below |
| asOfDate | As of date | string | Required; constraints below |
| filingEvidenceKnown | Filing evidence known | boolean | Required; constraints below |
| filingObserved | Filing observed | boolean | Required; constraints below |
Enter exact real Gregorian YYYY-MM-DD trigger and as-of dates in 1900–2199, integer caller calendar-day window and extension from 0 to 3660 each, and boolean filing-known and filing-observed values. Add window and extension to the trigger, rejecting a resulting deadline outside the supported date range. Return deadline, signed days until it, strict as-of-after status, knownFiled as known and observed, and unknown status as not known. Equality is not after deadline. No governing filing rule, business-day calendar, trigger determination or filing verification is supplied.
deadline=trigger+window+extension; daysUntil=deadline−asOf; after=asOf>deadline; knownFiled=known and observed Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| callerModeledSarDeadline | Caller modeled sar deadline | string |
| daysUntilCallerDeadline | Days until caller deadline | number |
| asOfAfterCallerDeadline | As of after caller deadline | boolean |
| knownFiled | Known filed | boolean |
| filingEvidenceUnknown | Filing evidence unknown | boolean |
{
"input": {
"callerSarTriggerDate": "2026-01-01",
"callerVerifiedCalendarDayWindow": 30,
"callerIndependentExtensionDays": 0,
"asOfDate": "2026-01-31",
"filingEvidenceKnown": false,
"filingObserved": false
},
"output": {
"callerModeledSarDeadline": "2026-01-31",
"daysUntilCallerDeadline": 0,
"asOfAfterCallerDeadline": false,
"knownFiled": false,
"filingEvidenceUnknown": true
}
}Limitations and assumptions
Date arithmetic does not select the governing filing rule or certify that filing occurred. 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 Stablecoin Reserve Attestation Monthly Report Reading Guide for a related task: A reserve report has a defined entity, date, assurance scope and liability basis.
Use Structuring Pattern Flag Checker for a related task: A transaction-pattern screen depends on verified grouping and explicit review thresholds.
References
-
SAR Filing Window Days Lookup — tool.io
Similar or alternative tools
- Stablecoin Reserve Attestation Monthly Report Reading Guide
A reserve report has a defined entity, date, assurance scope and liability basis.
- Structuring Pattern Flag Checker
A transaction-pattern screen depends on verified grouping and explicit review thresholds.