Resources · 82

Reliable reports: time zones, cutoffs and late events

Avoid shifted reporting days, duplicate counts and inconsistent comparisons between exports and dashboards.

· 9 min

Unstaffed satellite communications station at dusk AI-generated editorial illustration

What this guide helps achieve

  • Describe instants and business days
  • Define period boundaries
  • Handle late arrivals
  • Reconcile equivalent scopes
  • Test reconstruction

Quick check

  • Is converting everything to UTC enough?
  • Why does a total change after export?
  • Is a late event a duplicate?

Step-by-step method

  1. 01

    Describe instants and business days

    Separate event, ingestion and modification timestamps from business dates. A UTC instant alone does not define a store’s trading day. Retain a named business time zone when needed. PostgreSQL converts timestamps with time zone to UTC without retaining the original zone; store that zone separately if required.

    Deliverable: date and time-zone dictionary.

  2. 02

    Define period boundaries

    Use an inclusive start and exclusive end. Calculate boundaries in the business time zone before conversion. Test daylight-saving changes, month ends and dates without times. A local day does not always have the same duration; do not assume every day lasts twenty-four hours.

    Deliverable: period-assignment examples.

  3. 03

    Handle late arrivals

    Decide which report may change, for how long and with what label. Retain ingestion time and identifiers to distinguish delay from duplication. Do not silently overwrite a distributed report: provide a dated snapshot, revision or correction suited to its use.

    Deliverable: revision policy and discrepancy log.

  4. 04

    Reconcile equivalent scopes

    Compare sources using identical periods, business states and cutoffs. Separate created, paid, cancelled and refunded orders. Examine individual records near day boundaries before concluding that collection lost data.

    Deliverable: record-level discrepancy reconciliation.

  5. 05

    Test reconstruction

    Replay an interval containing a clock change and late events. A reconstruction at the same cutoff should explain any differences. Display time zone, freshness and provisional or closed status beside results.

    Deliverable: reconstruction test and report legend.

Define a period and retain the cutoff

Instants, business-day assignment and the published report state answer three different questions.

  1. Bound the day

    Write both boundaries with their time zone and specify inclusive start, exclusive end.

  2. Identify known events

    Keep activity time, receipt time and stable identifier separately.

  3. Date the report state

    Publish the cutoff and compare revisions with unchanged scope and rules.

In the fictional data, A and B belong to January 12; C belongs to January 13. B is unknown to the pipeline at 09:00 and explains the revision from 40 to 100 at 11:00.

Three events, one business day and two report states

Fictional data; amounts use one common unit. The January 12, 2026 business day in Europe/Paris starts inclusively at 2026-01-12T00:00:00+01:00 and ends exclusively at 2026-01-13T00:00:00+01:00. In UTC: January 11 at 23:00 through January 12 at 23:00. Receipt times below carry the +01:00 offset.

EventEvent instant in UTCPipeline receiptAssignment and effect
A · amount 402026-01-11T23:30:00Z2026-01-12T00:32:00+01:00It is January 12 at 00:30 in Paris. A belongs to January 12 and is known at both cutoffs.
B · amount 602026-01-12T22:59:00Z2026-01-13T10:00:00+01:00It is January 12 at 23:59 in Paris. B belongs to January 12 but arrives after the January 13, 09:00 cutoff.
C · amount 1002026-01-12T23:00:00Z2026-01-13T00:01:00+01:00It is January 13 at 00:00 in Paris. C is exactly at the exclusive end: it belongs to the next day.
Two comparable statesSame business day and assignment ruleCutoffs: January 13 at 09:00 and 11:00 (+01:00)First total: 40, containing A. Revised total: 100, containing A + B. The difference of 60 is a late arrival; C stays excluded from both states.

Acceptance case to reproduce

Fictional example: these inputs describe no customer or observed result.

View case inputs
{
    "event_time": "2026-10-08T23:30:00Z",
    "report_zone": "UTC+02:00",
    "local_time": "2026-10-09T01:30:00+02:00"
}

Expected decision

The event belongs to October 9 in the specified zone. Also retain its UTC instant.

Verification procedure

  1. Fix report time zone and reference instant.
  2. Replay an event near midnight.
  3. Keep UTC, local date and cutoff rule. Include an ambiguous local time during a clock change; retain offset and zone rather than inferring an instant.

PostgreSQL — Date/time types

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
CalendarNamed zone, week start and period boundaries
TimestampsEvent, ingestion and modification times; precision and origin
CutoffSnapshot time, revision window and late-arrival handling
ReconciliationIncluded states, identifiers and explained differences

Worked example

Illustrative situation

Compare two dated states of the same fictional report: 40 at the 09:00 cutoff, then 100 at 11:00. The business-day orders have not been redefined; the pipeline received B between those cutoffs.

Decision and expected evidence

Display business period, time zone, assignment rule and cutoff together. Explain whether late arrivals trigger a revision or an exclusion under the report contract. Arrival after a cutoff is not a new sale occurring at its receipt time.

Distinguish the mechanisms

MechanismPurposeCheck or limitation
Business dateAssign activity to a calendarIs not an instant without a convention
Event timeMeasure when activity occurredCan arrive late or use an inaccurate clock
Ingestion timeMonitor pipeline freshnessIs not necessarily the activity date

Management indicators

IndicatorWhat it measuresFirst action
Ingestion delayTime between activity and pipeline availabilityDefine an appropriate provisional window
Period revisionsChanges between comparable dated snapshotsSeparate delays from corrections
Boundary discrepanciesRecords assigned to different daysCorrect the time convention

Common pitfalls

  • Is not an instant without a convention
  • Can arrive late or use an inaccurate clock
  • Is not necessarily the activity date

Frequently asked questions

Is converting everything to UTC enough?

No. UTC helps compare instants; days, weeks and cutoffs still require a business time zone and calendar.

Why does a total change after export?

New events, corrections or business-state changes may be included. Check cutoff and revision policy before comparing.

Is a late event a duplicate?

No. Check its identifier and content; ingestion delay does not establish repetition.

Timelines: UTC and time zones

Reliable timelines separate wall time, instants and receipt

In cyber logs, OSINT collection or dashboards, two lines displaying 02:30 can represent different instants. Receipt order can also differ from event order. Preserving both axes avoids inventing a causal sequence from a simple string sort.

Fictional offline exercise for Europe/Paris, using IANA 2026e rules supplied by tzdata 2026.5. March and October 2026 clock changes are acceptance cases. The times and six deliveries describe no real incident. A correct conversion establishes neither source-clock accuracy nor log authenticity.

Four pieces of information that do not replace each other

Four pieces of information that do not replace each other
InformationWhat it providesWhat it does not establish
Original textReceived representation, precision and any supplied offset.Clock accuracy or event identity.
UTC instantA comparable position on the time axis.The business calendar or original zone.
Named zone and versionCivil-time rules applied to a local time.Device synchronization.
Observation timeWhen the collector saw the line according to its own clock.When the event actually occurred.
The same 02:30, two instants 60 minutes apart
The same 02:30, two instants 60 minutes apart On 25 October 2026 in Europe/Paris, 02:30 with +02:00 corresponds to 00:30 UTC and fold 0; 02:30 with +01:00 corresponds to 01:30 UTC and fold 1. The instants are 60 minutes apart. Europe/Paris · 2026-10-25 · 02:30:00 First occurrence · fold 0 02:30:00 +02:00 00:30:00 UTC 2026-10-25 Second occurrence · fold 1 02:30:00 +01:00 01:30:00 UTC 2026-10-25 60 min Compare UTC instants, beyond displayed wall times.

An ambiguous local time remains undecidable without more information. The profile expects an explicit fold choice or an offset consistent with the claimed zone. The diagram shows two instants, not a duplicate to delete. Computation uses UTC for elapsed durations and comparisons across the fold.

12 inputs and their normalization decisions

Two contracts are tested: local time plus a named zone, or an offset timestamp plus the zone it claims to represent. The teaching profile requires YYYY-MM-DDTHH:MM:SS, with Z or ±HH:MM in the second contract. Fractions, leap seconds, lowercase variants and -00:00 are outside this profile; that does not declare them all invalid under RFC 3339.

T01 · Repeated time without a choice
Received text
2026-10-25T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

  • 2026-10-25T00:30:00Z · 2026-10-25T02:30:00+02:00 · fold 0
  • 2026-10-25T01:30:00Z · 2026-10-25T02:30:00+01:00 · fold 1

Selected instant : No instant selected

Clarify: two possible instants

Two UTC candidates exist. Neither is selected by default: the record needs clarification rather than an invented instant.

T02 · First occurrence selected
Received text
2026-10-25T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
0

Valid UTC candidates

  • 2026-10-25T00:30:00Z · 2026-10-25T02:30:00+02:00 · fold 0
  • 2026-10-25T01:30:00Z · 2026-10-25T02:30:00+01:00 · fold 1

Selected instant : 2026-10-25T00:30:00Z

Temporal interpretation resolved

fold 0 selects the first 02:30 occurrence: +02:00 and 00:30 UTC. This choice must come from producer information, beyond a collector’s hidden preference.

T03 · Second occurrence selected
Received text
2026-10-25T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
1

Valid UTC candidates

  • 2026-10-25T00:30:00Z · 2026-10-25T02:30:00+02:00 · fold 0
  • 2026-10-25T01:30:00Z · 2026-10-25T02:30:00+01:00 · fold 1

Selected instant : 2026-10-25T01:30:00Z

Temporal interpretation resolved

fold 1 selects the second occurrence: +01:00 and 01:30 UTC. Its wall display matches T02, but the instant is one hour later.

T04 · Missing spring local time
Received text
2026-03-29T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

No valid local candidate

Selected instant : No instant selected

Reject: missing local time

On 29 March 2026, 02:30 does not exist in this zone. A round trip through UTC returns no candidate to that local time. Merely attaching tzinfo does not validate it.

T05 · Unambiguous local time
Received text
2026-10-22T10:00:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

  • 2026-10-22T08:00:00Z · 2026-10-22T10:00:00+02:00 · fold 0

Selected instant : 2026-10-22T08:00:00Z

Temporal interpretation resolved

These rules yield one UTC position. Acceptance covers temporal interpretation. Device-clock accuracy remains unverified.

T06 · Unknown zone
Received text
2026-10-25T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Pariss
Fold choice
Not supplied

Valid UTC candidates

Check not performed

Selected instant : No instant selected

Reject: unknown zone

Europe/Pariss is unavailable in the supplied rules. The profile rejects it instead of silently substituting the server zone.

T07 · Fold value outside the contract
Received text
2026-10-25T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
2

Valid UTC candidates

Check not performed

Selected instant : No instant selected

Reject: invalid fold choice

The profile accepts only 0, 1 or no fold choice. It rejects 2 before selection.

T08 · Impossible calendar date
Received text
2026-02-30T10:00:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

Check not performed

Selected instant : No instant selected

Reject: impossible date or time

30 February 2026 is not a calendar date. A correctly shaped string is insufficient to produce an instant.

T09 · Consistent +02:00 offset
Received text
2026-10-25T02:30:00+02:00
Contract
Offset timestamp + claimed zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

  • 2026-10-25T00:30:00Z · 2026-10-25T02:30:00+02:00 · fold 0
  • 2026-10-25T01:30:00Z · 2026-10-25T02:30:00+01:00 · fold 1

Instant carried by the offset : 2026-10-25T00:30:00Z

Conversion back to the claimed zone : 2026-10-25T02:30:00+02:00

Selected instant : 2026-10-25T00:30:00Z

Temporal interpretation resolved

+02:00 matches the first occurrence of this Paris wall time. It yields the same instant as T02.

T10 · Consistent +01:00 offset
Received text
2026-10-25T02:30:00+01:00
Contract
Offset timestamp + claimed zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

  • 2026-10-25T00:30:00Z · 2026-10-25T02:30:00+02:00 · fold 0
  • 2026-10-25T01:30:00Z · 2026-10-25T02:30:00+01:00 · fold 1

Instant carried by the offset : 2026-10-25T01:30:00Z

Conversion back to the claimed zone : 2026-10-25T02:30:00+01:00

Selected instant : 2026-10-25T01:30:00Z

Temporal interpretation resolved

+01:00 matches the second occurrence. It yields T03’s instant, which differs from T09.

T11 · Offset inconsistent with the zone
Received text
2026-03-29T02:30:00+01:00
Contract
Offset timestamp + claimed zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

No valid local candidate

Instant carried by the offset : 2026-03-29T01:30:00Z

Conversion back to the claimed zone : 2026-03-29T03:30:00+02:00

Selected instant : No instant selected

Reject: time and zone disagree

The +01:00 string denotes a calculable instant, but conversion to Europe/Paris displays 03:30 with +02:00. It contradicts a claim of Paris local time 02:30. Rejection applies to this zone claim; the timestamp can still have meaning in another context.

T12 · Missing offset in the second contract
Received text
2026-10-25T02:30:00
Contract
Offset timestamp + claimed zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

Check not performed

Selected instant : No instant selected

Reject under the format contract

Offset mode requires an explicit offset. The same text can belong to T01’s local contract, but switching contracts must be explicit.

Three civil days, three UTC durations

Three civil days, three UTC durations
Europe/Paris dateInclusive UTC startExclusive UTC endElapsed duration
2026-03-292026-03-28T23:00:00Z2026-03-29T22:00:00Z23 h
2026-10-222026-10-21T22:00:00Z2026-10-22T22:00:00Z24 h
2026-10-252026-10-24T22:00:00Z2026-10-25T23:00:00Z25 h

Boundaries are consecutive local midnights converted separately to UTC. A civil day and a duration of 24 hours serve different needs. This table changes no organizational cutoff rule.

Six fictional deliveries, four event identifiers

Studied window: 25 October 2026, from 00:00 UTC inclusive to 02:00 UTC exclusive. Clocks are assumed accurate only for the exercise. Each snapshot uses deliveries observed strictly before its cutoff. Receipt does not change an event’s time-window assignment.

Six fictional deliveries, four event identifiers
Delivery / eventEvent instant UTCObservation UTCRole in the exercise
R01 / E012026-10-25T00:50:00Z2026-10-25T00:51:00ZInitial observation · 2026-10-25T02:50:00+02:00
R02 / E022026-10-25T01:10:00Z2026-10-25T01:11:00ZInitial observation · 2026-10-25T02:10:00+01:00
R03 / E032026-10-25T01:30:00Z2026-10-25T02:20:00ZLate arrival · 2026-10-25T02:30:00+01:00
R04 / E042026-10-25T02:00:00Z2026-10-25T02:01:00ZExclusive end boundary · 2026-10-25T03:00:00+01:00
R05 / E022026-10-25T01:10:00Z2026-10-25T02:10:00ZIdentical E02 redelivery · 2026-10-25T02:10:00+01:00
R06 / E012026-10-25T00:55:00Z2026-10-25T02:30:00ZConflicting E01 version · 2026-10-25T02:55:00+02:00

R01 displays 02:50 with +02:00 and R02 displays 02:10 with +01:00. String sorting puts R02 before R01; instant sorting puts E01 at 00:50 UTC before E02 at 01:10 UTC. Computed chronological order still establishes no causal relationship.

Three dated states: explain 2 → 3 → 2

Three dated states: explain 2 → 3 → 2
State / UTC cutoffIncluded eventsCountExplanation
S1 · 2026-10-25T02:00:00ZE01, E022S1: E01 and E02 are known and inside the window. E03 has not yet been observed.
S2 · 2026-10-25T02:25:00ZE01, E02, E033S2: E03 explains the increase from 2 to 3. R05 identically redelivers E02, counted once; E04 remains at the exclusive end.
S3 · 2026-10-25T02:40:00ZE02, E032S3: R06 reveals two different temporal contents for E01. The local policy sends both versions to review and removes E01 from the included count, now 2. This quarantine policy belongs to the exercise; other workflows may choose differently.

An event identifier deduplicates here only when UTC instant and kind match. The same identifier with changed content triggers review. The exercise preserves the conflict instead of overwriting a version or deleting it without a trace. Earlier snapshots retain their dates. These are fictional exercise counts, with no measurement of real activity.

Six records to reconstruct the timeline

  • Original text and received precision, retained with a protected source reference.
  • Normalized instant, claimed zone, rule version and ambiguous/missing-time decision.
  • Observation time and the component whose clock produced it, separately from event time.
  • Stable identifiers and the rule separating identical redelivery from conflicting versions.
  • Inclusive/exclusive boundaries, cutoff and included records for every published snapshot.
  • Unverified clock limits: synchronization, drift, precision or causal order.

Conversions use the Europe/Paris file bundled with tzdata 2026.5, IANA 2026e. Clarification, format and quarantine decisions are a local editorial method. OpenTelemetry distinguishes source and observation time; this page claims neither a conforming OTLP record nor verification of real clocks.

Python 3.12.14 · tzdata 2026.5 · IANA 2026e

Primary sources and rule version

  • IETF · RFC 3339 · Standards Track · July 2002
    §4.2 Numeric offsets · §5.1 Ordering · §5.6 Internet timestamp format
  • Python · PEP 495 · Final · Python 3.6+ · checked 2026-10-22
    Fold and gap · constructors do not validate missing times · temporal arithmetic
  • Python 3.12 · zoneinfo · Python 3.12 documentation · checked 2026-10-22
    fold · data sources · ZoneInfo.from_file
  • IANA · Time Zone Database 2026e · Release 2026e · 2026-09-29
    Versioned time-zone database · scope of the exercise
  • IANA · 2026e Europe rules · tzdb 2026e · source file
    Rule EU: March/October last Sunday at 01:00 UTC · Zone Europe/Paris
  • OpenTelemetry · Logs Data Model · Stable model · living documentation · checked 2026-10-22
    Timestamp: source clock · ObservedTimestamp: collection-system clock

Sources reviewed on

Official references

References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.