Time zones

Time zones: so that the same time remains the same everywhere

• As soon as teams, locations or systems work across time zones, a local time is no longer sufficient. A correctly maintained time zone prevents misunderstandings regarding appointments, protocols and time-controlled processes.
• The time zones can be assigned to calendars so that the times are displayed correctly when an invitation from a calendar event is sent. (see Administration > Calendar initialization > Calendar names)
• You can find the overview in Administration > Master data initialization > Time zones.

Fields explained

• Name: Understandable name for the selection, for example “Berlin / Central European Time”.
• IANA: Standardized technical time zone identifier, for example “Europe/Berlin”. The spelling and slash must be exactly correct.
• Active: Determines whether the time zone is offered for new selections.
• Sorting order: Determines the position in lists.

Invest safely

1. Check whether the required IANA time zone already exists.
2. Get the identifier from a reliable time zone source.
3. Give it a name that your users will immediately understand.
4. Activate, sort and save the entry.
5. Check the selection in a time-related test case - even in summer and winter time.

Deactivate instead of deleting

If a time zone is no longer needed for new data, deactivating it is usually safer than deleting it. This means that existing assignments remain traceable.

Related topics

1. For key users – understand and prepare processes › Basic settings › Company › Company locations
2. For key users – understand and prepare processes › Basic settings › Company › Countries
3. For beginners – basics for daily work › Calendar

Frequently asked questions