FTB-C000068 / Data quality concept

Late-Arriving Data

Late-arriving data is a record that reaches a processing boundary after the expected time for its event, partition, or decision window.

Also known asdelayed datalate record

Intermediate 11 linked topicsPublished

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

Tutorials planned

These catalogued topics use this concept, but their complete build has not shipped yet.

  • D01-F01-A01 Important
  • D01-F01-A02 Important
  • D01-F01-A05 Important
  • D01-F02-A05 Important
  • D01-F03-A03 Important
  • D01-F03-A05 Important
  • D01-F04-A01 Important
  • D01-F04-A02 Important
  • D01-F04-A05 Important
  • D02-F04-A02 Important
  • D03-F01-A05 Important

Evidence and governance

  1. 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
Last reviewed
2026-07-26
Next review
2027-07-26
Record status
published
Written by

Fintech engineer building market-data and financial systems, and the author of every article, glossary record, and reference implementation on The Fintech Builder.