A date may indicate the order, delivery or update of the document. If its meaning is unclear, programs can compare different events as if they were equivalent. Time also requires consistent reference when work involves locations or systems with different settings.
I propose to name the fields according to the event and to verify the format used. Data processing must be monitored during imports and connections. A date displayed correctly can still have been interpreted with a different order between day and month.
In a hypothetical example, one report uses the date of entry while another uses the date of sale. Daily results can diverge without operations missing. The difference emerges by clarifying the event to which each measure relates.
Verification includes cases close to the change of day and ambiguous formats. Technical choices must be agreed with those who manage the tools. An understandable time reference allows you to compare data and reconstruct work sequences without attributing to an interpretation problem the meaning of a missing event.