Definition · temporal data
Transaction time
Transaction time is the time dimension recording when a fact was stored in the database, forming the immutable system-of-record history. For transaction time, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
Also known as system time, record time, ingestion time
Why it matters
Understanding transaction time matters because close, reconciliation, and audit work depend on consistent timing, source evidence, review thresholds, and ownership. A loose definition creates avoidable rework. Transaction time records when each fact was stored, which is what lets an answer be reconstructed as it would have computed on a prior date. Pluvo rebuilds every answer's path through trace IDs, anchored in this as-recorded history.
In practice
Close example
Teams use transaction time 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
Transaction time records when each fact was stored, which is what lets an answer be reconstructed as it would have computed on a prior date. Pluvo rebuilds every answer's path through trace IDs, anchored in this as-recorded history.
In practice, teams should define transaction time with a clear source, owner, time period, and decision before they use it in reporting, planning, or operating reviews.
Understanding transaction time matters because close, reconciliation, and audit work depend on consistent timing, source evidence, review thresholds, and ownership. A loose definition creates avoidable rework. Transaction time records when each fact was stored, which is what lets an answer be reconstructed as it would have computed on a prior date. Pluvo rebuilds every answer's path through trace IDs, anchored in this as-recorded history.
A strong workflow for transaction time 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.
Transaction time records when each fact was stored, which is what lets an answer be reconstructed as it would have computed on a prior date. Pluvo rebuilds every answer's path through trace IDs, anchored in this as-recorded history.
FAQ
What is transaction time in a bitemporal database?
Transaction time is the time dimension recording when a fact was stored in the database, forming the immutable system-of-record history. For transaction time, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
Why is transaction-time history immutable?
Understanding transaction time matters because close, reconciliation, and audit work depend on consistent timing, source evidence, review thresholds, and ownership. A loose definition creates avoidable rework. Transaction time records when each fact was stored, which is what lets an answer be reconstructed as it would have computed on a prior date. Pluvo rebuilds every answer's path through trace IDs, anchored in this as-recorded history.