Skip to content

Main content

Fiscal Week Closure Policy Token Tool

Compare supplied positions in the same numbered boundary week and retain the supplied ownership policy.

Loading tool…

Description

Assign a simplified fiscal-week closure label.

Date labels and intervals depend on origins, endpoint inclusion and calendar versus elapsed-time conventions. Numeric serial periods and local token formats can represent useful bookkeeping without resolving a real instant or official fiscal rule.

Assign a simplified fiscal-week closure label.

When to use this tool

Use Fiscal Week Closure Policy Token when checking a supplied date-label, duration or interval convention.

How to use the tool and how it works

  1. Enter weekEndDay, fiscalEndDay, crossingPolicy. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read crosses, owner. Inspect crosses before interpreting the associated values.

Assign a simplified fiscal-week closure label. Require weekEndDay/fiscalEndDay in [1,7] and crossingPolicy closing-year or opening-year; crosses = weekEndDay > fiscalEndDay, owner uses that policy or current-year.1

Input fieldMeaning and unitsAccepted input
weekEndDaySupplied ordinal day label; comparison with fiscalEndDay is literal, without a date/calendar lookup.Required. Safe integer; minimum 1; maximum 7.
fiscalEndDayFiscal End DayRequired. Safe integer; minimum 1; maximum 7.
crossingPolicyCrossing PolicyRequired. Text; one of "closing-year", "opening-year"; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
crossesCrossesRequired. Boolean.
ownerOwnerRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "weekEndDay": 7,
    "fiscalEndDay": 5,
    "crossingPolicy": "closing-year"
  },
  "output": {
    "crosses": true,
    "owner": "closing-year"
  }
}

Limitations and assumptions

  • These are supplied ordinal boundary coordinates, not a general calendar-week or fiscal-year calculation.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use a complete date/time implementation and the applicable calendar policy for actual scheduling and interval interpretation.

References

  1. Calculation and input contract: date/fiscal-week-closure-policy-token — tool.io

Similar or alternative tools