Subsequent Events Type I vs II Classifier

Screen actual event timing through caller statement authorization and explicitly supplied preexisting-condition/materiality evidence, retaining adjusting/nonadjusting candidates; no discovery of underlying conditions or framework-specific final disclosure decision.

Description

Subsequent-event review distinguishes evidence of preexisting conditions from later new conditions.

Subsequent-event review distinguishes evidence of preexisting conditions from later new conditions. Timing and materiality are supplied separately.^[1]

The returned values include In subsequent event review window, Caller evidence event class, Nonadjusting disclosure candidate. The How section below explains the calculation, input rules and interpretation.

When to use Subsequent Events Type I vs II Classifier

Use Subsequent Events Type I vs II Classifier when you need to evaluate the supplied records under the calculation and evidence rules below. No underlying-condition discovery or framework-specific final adjustment/disclosure decision is supplied.

Gather the source balances and explicit accounting policy. Monetary inputs use integer minor units in one currency; for a currency with 100 minor units per major unit, 12345 represents 123.45. One basis point is 0.01 percentage points; 10000 basis points is 100%. Dates and posting signs follow the individual rules below.

How to use Subsequent Events Type I vs II Classifier and understand its results

Gather the source balances and explicit accounting policy. Monetary inputs use integer minor units in one currency; for a currency with 100 minor units per major unit, 12345 represents 123.45. One basis point is 0.01 percentage points; 10000 basis points is 100%. Dates and posting signs follow the individual rules below.
Enter reportingPeriodEndDate, eventObservedDate, financialStatementsAuthorizationDate, callerConditionExistedAtPeriodEnd, callerEventMaterial using the field table and calculation rules, then run the tool.
Read inSubsequentEventReviewWindow, callerEvidenceEventClass, nonadjustingDisclosureCandidate. 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
reportingPeriodEndDate	Reporting period end date	string	Required
eventObservedDate	Event observed date	string	Required
financialStatementsAuthorizationDate	Financial statements authorization date	string	Required
callerConditionExistedAtPeriodEnd	Caller condition existed at period end	boolean	Required
callerEventMaterial	Caller event material	boolean	Required

Enter three exact real Gregorian YYYY-MM-DD dates in 1900–2199 and condition/materiality booleans. Require authorization≥period end. Return review-window flag, outside-review-window/adjusting-candidate/nonadjusting-candidate label and nonadjusting disclosure candidate flag. An event on period end is outside this subsequent-event interval.

window=periodEnd<event≤authorization; disclosureCandidate=window and not preexisting and material

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

Output field	Meaning	Value type
inSubsequentEventReviewWindow	In subsequent event review window	boolean
callerEvidenceEventClass	Caller evidence event class	string
nonadjustingDisclosureCandidate	Nonadjusting disclosure candidate	boolean

json

{
  "input": {
    "reportingPeriodEndDate": "2025-12-31",
    "eventObservedDate": "2026-01-10",
    "financialStatementsAuthorizationDate": "2026-02-01",
    "callerConditionExistedAtPeriodEnd": true,
    "callerEventMaterial": true
  },
  "output": {
    "inSubsequentEventReviewWindow": true,
    "callerEvidenceEventClass": "adjusting-candidate",
    "nonadjustingDisclosureCandidate": false
  }
}

Limitations and assumptions

No underlying-condition discovery or framework-specific final adjustment/disclosure decision is supplied.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing fields without a declared default, 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 Revenue Cutoff Shipping Terms FOB Checker: Revenue cutoff follows an explicitly established control-transfer event. FOB wording alone cannot determine that event or satisfy all recognition criteria. For a complementary task, use Dual Dating Subsequent Event Footnote Usage Lookup: Subsequent-event treatment involves chronology, recognition and disclosure. This screen applies entered treatment labels rather than deciding their applicability.

References

Subsequent Events Type I vs II Classifier — tool.io

Similar or alternative tools

Revenue Cutoff Shipping Terms FOB Checker
Revenue cutoff follows an explicitly established control-transfer event. FOB wording alone cannot determine that event or satisfy all recognition criteria.
Dual Dating Subsequent Event Footnote Usage Lookup
Subsequent-event treatment involves chronology, recognition and disclosure. This screen applies entered treatment labels rather than deciding their applicability.