Definitions
In plain terms
A trade may have happened before a bar closed but arrive after the first bar result was emitted. The pipeline needs a declared correction policy.
Technical
Lateness is measured against a named event-time field, arrival boundary, watermark or deadline, and tolerance; handling may append, revise, quarantine, or reject.
Scope
Late does not mean false, and the acceptable delay is system-specific.
Examples
- A governed dataset records late-arriving data explicitly instead of inferring it from an ambiguous field.
Common misconceptions
- Late-Arriving Data does not have one universal meaning without its stated market, source, and time context.
Concept relationships
Prerequisites
Related
Where this concept is used
- ImportantTime BarsD01-F01-A01
- ImportantTick BarsD01-F01-A02
- ImportantTick-Imbalance BarsD01-F01-A05
- ImportantDuplicate-Trade ResolverD01-F02-A05
- ImportantRefresh-Time SamplingD01-F03-A03
- ImportantAsynchronous Return AlignmentD01-F03-A05
- ImportantMissing-Bar Gap ClassifierD01-F04-A01
- ImportantFeed-Latency MonitorD01-F04-A02
- ImportantPoint-in-Time Availability GuardD01-F04-A05
- ImportantSurvivorship-Bias Guard: Keep Historical Failures in the TestD02-F04-A02
- ImportantIntraday Index-Level CalculationD03-F01-A05
Evidence and governance
- Fintech Builder Glossary Definition Contract The Fintech Builder · internal governed contract
Supports: preferred label, short definition, technical definition
Limits: Defines governed platform behavior rather than claiming these policies are universally prescribed by external McClellan methodology.
- Reviewed by
- fintech-builder-owner-approved
- Last reviewed
- 2026-07-26
- Next review
- 2027-07-26
- Record status
- published