Proof Of Loss Deadline Days Lookup

Audit actual caller independently established proof-of-loss trigger against verified filing class calendar-day window; no denial/notice trigger substitution, business-day inference or legal deadline certification.

Description

Proof-of-loss timing begins at an independently established trigger.

Proof-of-loss timing begins at an independently established trigger. A class-specific calendar-day window gives a deadline and signed time remaining.^[1]

The returned values include Caller proof of loss deadline civil date, Signed days until caller deadline, Caller deadline already passed. The How section below explains the calculation, input rules and interpretation.

When to use Proof Of Loss Deadline Days Lookup

Use Proof Of Loss Deadline Days Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. No business-day adjustment, alternate trigger selection or legal deadline certification is supplied.

Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.

How to use Proof Of Loss Deadline Days Lookup and understand its results

Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
Enter observedProofOfLossTriggerCivilDate, callerProofOfLossClassIds, callerVerifiedProofOfLossCalendarDays, queryProofOfLossClassId, observedAsOfCivilDate using the field table and calculation rules, then run the tool.
Read callerProofOfLossDeadlineCivilDate, signedDaysUntilCallerDeadline, callerDeadlineAlreadyPassed. 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
observedProofOfLossTriggerCivilDate	Observed proof of loss trigger civil date	string	Required
callerProofOfLossClassIds	Caller proof of loss class ids	list of string	Required
callerVerifiedProofOfLossCalendarDays	Caller verified proof of loss calendar days	list of number	Required
queryProofOfLossClassId	Query proof of loss class id	string	Required
observedAsOfCivilDate	Observed as of civil date	string	Required

Enter exact real Gregorian YYYY-MM-DD dates in 1900–2199 for trigger and as-of, aligned nonempty unique nonblank class IDs and integer windows 0–3660, plus an exact query ID. Return the generated deadline, signed days remaining and a strictly passed flag; the deadline date itself is not passed. Generated dates must remain in the supported years.

deadline=triggerDate+catalogDays; remaining=deadline−asOf; passed=asOf>deadline

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
callerProofOfLossDeadlineCivilDate	Caller proof of loss deadline civil date	string
signedDaysUntilCallerDeadline	Signed days until caller deadline	number
callerDeadlineAlreadyPassed	Caller deadline already passed	boolean

json

{
  "input": {
    "observedProofOfLossTriggerCivilDate": "2026-01-01",
    "callerProofOfLossClassIds": [
      "standard",
      "expedited"
    ],
    "callerVerifiedProofOfLossCalendarDays": [
      30,
      5
    ],
    "queryProofOfLossClassId": "standard",
    "observedAsOfCivilDate": "2026-01-20"
  },
  "output": {
    "callerProofOfLossDeadlineCivilDate": "2026-01-31",
    "signedDaysUntilCallerDeadline": 11,
    "callerDeadlineAlreadyPassed": false
  }
}

Limitations and assumptions

No business-day adjustment, alternate trigger selection or legal deadline certification 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 Appeal Deadline Days From Denial Lookup: An appeal filing window starts from the independently established appealable denial date. It differs from a response deadline. For a complementary task, use Prior Auth Turnaround Window Lookup: Prior-authorization turnaround depends on the complete-request trigger and verified request class. Calendar days differ from business days.

References

Proof Of Loss Deadline Days Lookup — tool.io

Similar or alternative tools

Appeal Deadline Days From Denial Lookup
An appeal filing window starts from the independently established appealable denial date. It differs from a response deadline.
Prior Auth Turnaround Window Lookup
Prior-authorization turnaround depends on the complete-request trigger and verified request class. Calendar days differ from business days.