TIME
Returns a time of day built from hour, minute and second numbers.
TIME(<hour>, <minute>, <second>)Returns: A time value (a datetime fraction of a day, with no calendar date).
What it does
TIME builds a time of day from hours, minutes and seconds. Most finance reports only need a date, so TIME is less common than DATE. It is useful when a system timestamps transactions and the team needs to test them against a cut-off, such as the 2:00 PM wire deadline of a bank. TIME can also be added to a date to make a full timestamp.
Syntax and arguments
- hour: the hour from 0 to 23. Required.
- minute: the minute from 0 to 59. Required.
- second: the second from 0 to 59. Required.
Example
A treasury team wants to flag wire requests that were submitted after the 2:00 PM cut-off. The wire log stores a full timestamp. A calculated column strips the date part and compares the time part with the cut-off.
Cut-off Status =
IF(
'Wire_Log'[SubmittedAt] - INT('Wire_Log'[SubmittedAt]) > TIME(14, 0, 0),
"After cut-off",
"On time"
)
INT removes the date part of the timestamp, which leaves the time as a fraction of a day. TIME(14, 0, 0) is the same kind of fraction for 2:00 PM, so the two can be compared directly. The timestamp must be in the time zone of the cut-off, or the flag will be wrong.
Example: a second, different use
TIME can add a fixed posting time to a date, such as when a batch always posts at 6:00 AM.
Batch Posted At = DATE(2026, 10, 29) + TIME(6, 0, 0)
Things to watch
- Compare times only with time values. A full timestamp and a time of day must be lined up the same way, or the comparison gives odd results.
- Time zones matter. A timestamp stored in UTC is not the same as a local cut-off.
- Most finance models should keep dates and times in separate columns. Keep the time part only when a control needs it.
- TIME returns a fraction of a day, so the result looks like a small decimal number if it is shown without a time format.
In business terms
TIME appears in treasury and payments work: cut-off checks for wires and ACH files, batch posting times, and audit trails that show when a transaction was entered. It is rarely needed for month-end totals.