Description
Compare explicit submission/receipt clocks after supplied common-reference offsets.
A regulatory record check applies a supplied rule to labels, dates, identifiers, or amounts. Exact matches and clock boundaries matter, but a consistent record does not itself establish legal compliance. The governing jurisdiction, rule version, and authoritative evidence must be selected separately.
Compare explicit submission/receipt clocks after supplied common-reference offsets.
When to use this tool
Use it for authority receipt submission time offset when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter submitted, receiptTimestamp, sourceOffset, receiptOffset. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read rawLag, referenceLag. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Return rawLag=receiptTimestamp-submitted and referenceLag=(receiptTimestamp-receiptOffset)-(submitted-sourceOffset).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| submitted | Submitted | Required. Finite number. |
| receiptTimestamp | Receipt Timestamp | Required. Finite number. |
| sourceOffset | Source Offset | Required. Finite number. |
| receiptOffset | Receipt Offset | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| rawLag | Raw Lag | Required. Finite number. |
| referenceLag | Reference Lag | Required. Finite number. |
{
"input": {
"submitted": 100,
"receiptTimestamp": 110,
"sourceOffset": 2,
"receiptOffset": -1
},
"output": {
"rawLag": 10,
"referenceLag": 13
}
}Limitations and assumptions
- Offsets must use the same unit and sign convention for a common reference. No submission, receipt, source authenticity, or authority deadline is independently verified.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For authority receipt submission time offset, check the source records and the supplied rule before comparing the result with another method. Consult the applicable authoritative rule when deciding eligibility, legal timing, fees, or obligations.
References
Similar or alternative tools
- Authority Clock Stop Day Basis
Apply already resolved calendar/business clock-stop counts without interpreting agency timelines.
- Authority Question Response Deadline Gap
Calculate authority question response deadline gap from explicit caller-supplied inputs.