Understanding RFX Timezone Conversion

  • Updated

This article explains how the system handles timezone conversion for dates and times listed on a Request for a request (RFX), such as the close date, and when this conversion happens.

Key Ideas

RFX dates and times, such as the RFX close date, are saved within the system using Co-ordinated Universal Time (UTC).

  • When a Buyer sets a date and time (e.g., 4:30 PM in Victoria), the system converts this time to UTC and saves it.

  • When a Supplier views the RFX, the date and time (in UTC) is converted to the local timezone selected in their profile before being displayed.

  • Conversion Example: If a Buyer in Victoria sets a close time of 4:30 PM (converted to UTC), and a Supplier in Western Australia views the RFX, the system converts the saved UTC time into the Western Australia timezone and displays it to the Supplier.

  • The only time all parties (Buyer and Supplier) will see the exact same date and time is if they have the same timezone setting in their respective profiles.

Limits & Notes

  • Documentation Times: Any supplementary documentation you provide/attach to an RFX that includes a time should stipulate the timezone.

  • The software will not convert dates/times within documentation to the user's local timezone. This is to avoid misunderstanding or conversion errors.

What's Next / Related

  • Link to an adjacent task like "Update your Supplier Profile Settings" (to change timezone).