Definition · data modeling
Bitemporal data
Bitemporal data is modeling data along two independent time axes—valid time and transaction time—to capture both what was true and what was known when. For bitemporal data, the important details are the period, source evidence, reviewer, threshold, and control purpose that make the treatment auditable.
Also known as bitemporal modeling, bitemporality, bitemporal data model
Why it matters
Understanding bitemporal data matters because close, reconciliation, and audit work depend on consistent timing, source evidence, review thresholds, and ownership. A loose definition creates avoidable rework. Pluvo distinguishes when a fact became true from when it was recorded, so a later correction doesn't silently overwrite the figure a past decision relied on—you can ask what a number was under the definition you held then.
In practice
Close example
Teams use bitemporal data during close, review, or audit support when a balance or transaction needs evidence. The controller should be able to trace the number to source records, timing, reviewer, and control threshold.
Pluvo example
Pluvo distinguishes when a fact became true from when it was recorded, so a later correction doesn't silently overwrite the figure a past decision relied on—you can ask what a number was under the definition you held then.
In practice, teams should define bitemporal data with a clear source, owner, time period, and decision before they use it in reporting, planning, or operating reviews.
Understanding bitemporal data matters because close, reconciliation, and audit work depend on consistent timing, source evidence, review thresholds, and ownership. A loose definition creates avoidable rework. Pluvo distinguishes when a fact became true from when it was recorded, so a later correction doesn't silently overwrite the figure a past decision relied on—you can ask what a number was under the definition you held then.
A strong workflow for bitemporal data separates the definition from the action: first agree what the term means, then decide how it is measured, when it changes, and who is accountable for the next step.
Pluvo distinguishes when a fact became true from when it was recorded, so a later correction doesn't silently overwrite the figure a past decision relied on—you can ask what a number was under the definition you held then.
FAQ
What is the difference between valid time and transaction time?
The boundary for bitemporal data differs from related terms by scope, source data, time period, and decision use. In this glossary, it covers modeling data along two independent time axes—valid time and transaction time—to capture both what was true and what was known when, so teams should compare those boundaries before using it in reporting or planning.
Why does finance need bitemporal data?
Understanding bitemporal data matters because close, reconciliation, and audit work depend on consistent timing, source evidence, review thresholds, and ownership. A loose definition creates avoidable rework. Pluvo distinguishes when a fact became true from when it was recorded, so a later correction doesn't silently overwrite the figure a past decision relied on—you can ask what a number was under the definition you held then.