When a document is generated in Wello solution — whether it is a service report, an invoice, a sales order, or any other document — every date and time shown on that report needs to make sense to the person reading it. Because businesses often operate across different regions, the same moment in time can appear as a completely different hour depending on where the reader is located. A service visit that happened at 2:00 PM in New York would show as 8:00 PM in Paris if the time is not properly adjusted.

To solve this, the Wello solution includes a Report Timezone feature. This feature ensures that all dates and times displayed on generated reports are automatically converted to the local time of the relevant location, account, or organization — so every report reader sees times that are accurate and meaningful to them, without needing to do any manual conversion.

The system maintains a comprehensive, pre-configured list of all recognized time zones worldwide. This list is centrally managed and cannot be modified by individual users, which ensures consistency and accuracy across all domains.

Each time zone entry in this list includes the full name of the time zone (for example, "Eastern Standard Time"), its abbreviation (such as "EST"), the offset from universal coordinated time (the global time reference), and — where applicable — all the details needed to handle seasonal clock changes, commonly known as daylight saving time.

This means the system knows exactly when clocks move forward or backward in regions that observe those changes, and it adjusts report times accordingly.

Every organization, account, and location in the system is linked to a specific time zone. This is how the system knows which local time to use when generating reports.

During the initial setup of a domain, the organization is required to have a time zone assigned. This can happen in one of two ways: if the mapping feature is enabled, the system can automatically determine the correct time zone based on the organization's address using a geocoding service. Alternatively, the time zone can be selected manually in the address field from a dropdown list during setup.

Since reports typically reflect work that was performed at a specific location, the time zone of that location is especially important. Each location in the system has an address, and the time zone is determined based on that address.

When the mapping feature is available, the system automatically identifies the correct time zone through a geocoding process — essentially looking up the geographical coordinates of the address and matching them to the appropriate time zone. If the mapping feature is not included in the current plan, the system will prompt for a manual time zone selection when creating a new location.

By default, the organization's time zone is pre-filled, so in many cases no extra action is needed.

For locations created through the Import module, an API, or a plugin, the system attempts to determine the time zone automatically in the background. If that is not possible, the organization's time zone is used as a fallback.

It is always possible to manually change the time zone assigned to a location at any point, giving full flexibility when automatic detection does not match the desired setting.

The screenshot below shows an example of how the time zone appears when editing or creating a location address. In this case, the system has detected "Europe/Berlin (UTC+01:00)" for an address in Belgium, and a confirmation that geocoding was successfully completed is displayed.

Not every document uses the same time zone. The system determines which time zone to apply based on the type of document being generated and the entity most relevant to that document. Below is how each document type is handled:

In each case, all dates and times that were originally stored in universal coordinated time are automatically converted to the appropriate local time before the report is generated. This means the person reviewing the document sees dates and times that correspond to the real-world clock at the relevant location — no manual adjustments are needed.

Regions around the world handle seasonal time changes differently. Some regions observe daylight saving time (where clocks are moved forward by an hour during warmer months), while others do not change their clocks at all.

The system accounts for this automatically. For any time zone that observes daylight saving, the system checks whether the specific date being shown on the report falls within the daylight saving period. If it does, an additional offset is applied so that the displayed time accurately reflects the local clock at that moment — whether it was standard time or daylight saving time.

This means reports generated for a location in New York, for example, will correctly show Eastern Standard Time during winter months and Eastern Daylight Time during summer months, without any manual intervention.

A dedicated field is available under the location information section of reports to indicate which time zone was used for the dates and times shown. This field can be optionally added to the report layout, providing full transparency to the reader about which local time reference was applied. This is particularly useful for businesses operating across multiple regions, as it removes any ambiguity about the times displayed on the document.