Whitepaper · November 2026

Late arriving data needs more than one clock

Your July report said Antwerp. A row that arrived late says Ghent. Both are right. Learn how to land late data in the past without erasing what your platform already said.

Get the whitepaper in your inbox

A look inside

13 pages. Worked examples with real rows, three figures, ten questions to put to any platform and a glossary.

Whitepaper cover
CoverLate arriving data needs more than one clock
Whitepaper page on why one clock is not enough
Why one clock is not enoughBusiness date, transaction date, load date and when each version was known
Whitepaper page with the problems a history table has to solve
What a history table has to solveEleven problems and what the engine guarantees for each
Whitepaper page with ten questions about late data
Ten questions about late dataEach one with an answer you can check