<!-- https://learnsql.cpetoday.com/functions/m/datetimezone-utcnow -->
# DateTimeZone.UtcNow

Language: Power Query M
Category: Date and time
Syntax: DateTimeZone.UtcNow() as datetimezone
Summary: Returns the current date and time in UTC, the universal reference time, with a zone offset of zero.
Returns: The current UTC time as a datetime with a time zone value.
Level: Advanced
Related: DateTimeZone.SwitchZone, DateTime.LocalNow, DateTime.From, DateTime.Date, DateTime.FixedLocalNow

## What it does
DateTimeZone.UtcNow gives the current time in UTC. UTC is the reference that most systems use when they store a timestamp, whatever the local time. A bank, a payment processor or a cloud accounting API often records times in UTC. Knowing that a timestamp is UTC is what allows it to be converted to the local time of the business.
## Syntax and arguments
- The function takes no arguments. Empty parentheses are required.
## Example
A team loads transactions from a system that stores every timestamp in UTC. The report run time is shown in UTC so the team knows which data cut it reflects.

```powerquery
let
    RunUtc = DateTimeZone.UtcNow(),
    RunLabel = DateTime.ToText(DateTime.From(RunUtc), "yyyy-MM-dd HH:mm", "en-US") & " UTC"
in
    RunLabel
```

The label shows the current UTC date and time, for example "2026-10-29 14:30 UTC". Because it is calculated at refresh time, it changes each time the report is refreshed.
## Example: a second, different use
Compare two timestamps from different systems by converting both to UTC before the comparison, so a time zone difference does not look like a late posting.
## Things to watch
- A datetime without a time zone is not UTC, even if it looks like it. Check where the data came from.
- A UTC value is correct for storage and comparison, but a report should show local time to the reader.
- Converting to local time needs a zone offset, and a fixed offset does not change with daylight saving. See DateTimeZone.SwitchZone.
- The function returns a time zone value, not a plain datetime.
## In business terms
Cross border payments, global systems and cloud feeds all record time in UTC. Keeping the reference clear is how a team avoids a cut-off error where a payment appears to be on the wrong side of midnight.
