**Source URL:** https://quality.veevavault.help/en/lr/20489/

# Time Zones in Vault

Vault stores time data in Coordinated Universal Time (UTC). When a user views time information (DateTime fields), Vault displays the information in their user profile _Timezone_ and in the format of their _Locale_.

When a domain user is first created, their _Timezone_ and _Locale_ are defaulted to the _Vault Time Zone_ and _Base Locale_ configured in **Admin > Settings >** **Language & Region Settings**, but Admins can select a different _Timezone_ and _Locale_ for the user during creation, and users can update their own _Timezone_ and _Locale_ in their user profile.

There are some exceptions where Vault displays DateTime information to the user in UTC, such as in signature pages.

## Document and Object Fields

Vault displays document and object DateTime fields in the user's time zone.

## eSignatures

When Vault captures an eSignature, an entry action sets the _Approved Date_ (DateTime) and saves it in the _Vault Time Zone_. The eSignature timestamp is stored in UTC.

When a user views eSignature information in the Vault UI, such as when viewing an object record that has an eSignature, Vault displays the signature time in the signing user's time zone.

However, Vault displays the eSignature time on signature pages and overlay pages in UTC, because signature pages and overlay pages are not dynamically updated depending on which user is viewing the document.

## Entry Actions

For entry actions, Vault saves DateTimes using the _Vault Time Zone_ and stores the values in UTC.

## Workflow Task Due Dates

Vault displays workflow task due dates in the viewing user's time zone. The task's status (such as whether the task is overdue) is determined based on the assigned user's time zone.

In Training and Study Training, it is possible for a _Training Assignment_ record's _Due Date_ to be different from the workflow task's due date. This is because Vault's training automation logic sets this value on the assignment, separate from the related workflow task that can include specific due date configuration.

## Reports

Vault displays DateTimes in reports in the viewing user's time zone.

## Formatted Outputs

Vault displays DateTimes in formatted outputs in the time zone of the user generating the output.

## Audit Trails and Audit Logs

When viewing audit trails and audit logs, Vault displays DateTimes in the _Timestamp_ column in the viewing user's time zone. For dates displayed in the _Event Description_ column, Vault evaluates the dates in the context of the _Vault Time Zone_. For example, when the _Effective Date_ is set using `today()` via an entry action (a server process), Vault uses the _Vault Time Zone_ to determine the value of `today()` at the time the server process ran.

For example, in a Vault with the _Vault Time Zone_ set to Eastern Standard Time (EST)_,_ a document's _Effective Date_ is set using `today()` via an entry action at 5:15 PM EST on March 25, 2026\. When a user with a user profile _Timezone_ of New Zealand Daylight Time (NZDT) views the _Document Audit History_ for the document, the _Event Description_ displays _Effective Date set to "3/25/25"_, while the _Timestamp_ of the event displays _26 Mar 2026 11:15 AM NZDT_. This is because `today()` used the _Vault Time Zone_ (EST) to set the _Effective Date_, while the _Timestamp_ for the event uses the viewing user's time zone (NZDT).

## Jobs and Daylight Saving Time

When scheduling a daily job, Vault uses the _Vault Time Zone_. If the _Vault Time Zone_ observes Daylight Saving Time (DST), the job scheduler adjusts scheduled daily jobs by one hour to account for the difference.

For example, a daily job normally scheduled at 8:00 AM Pacific Standard Time (UTC-8) will be rescheduled to 9:00 AM Pacific Daylight Time (UTC-7) once DST begins, and rescheduled back to 8:00 AM Pacific Standard Time (UTC-8) once DST ends. In relation to UTC, the job remains scheduled at 15:00 UTC, because UTC does not observe DST.

## Data Calculation

When calculating dates and times using Vault formulas, the calculation may or may not perform time conversions depending on whether the formula includes multiple Date fields only, multiple DateTime fields only, or a mix of both.

For calculations involving multiple Date fields (and no DateTime fields), Vault does not perform a time zone conversion during calculation, because Date fields are not associated with a time or time zone.

For calculations involving multiple DateTime fields (and no Date fields), Vault does not perform a time zone calculation. Because the DateTIme fields are stored in UTC, the function is not affected by time zone. Vault performs a date-to-date calculation and round values to the nearest integer. For reports referencing these fields, values can include decimal places when defined to accurately reflect date differences.

For calculations involving both Date and DateTime fields, Vault converts the DateTime value from UTC to the _Vault Time Zone_ and truncates the time portion of the value. Vault then performs the date-to-date calculation. It does not account for Daylight Saving Time (DST).

**Note**: Some functions accept a `timezone` or `user` parameter, which can impact whether Vault performs a time zone conversion during calculation. See documentation for individual Date and DateTime functions in the Vault Formula Reference Guide.