Timezone handling for QUOTIM and fallback timestamp fields in EMA API (OMM protocol)

Nickolus_Snan

We're consuming FX rates via the LSEG EMA API using the OMM protocol and processing quote timestamps from multiple rate sources (Refinitiv, FENICS, etc.).

We're observing that timestamps appear to be sent in mixed timezones across different RICs:

• Some RICs: QUOTIM interprets as UTC (ie. BBD= has a QUOTIM raw value of 17:48:03 which reflects the same timestamp as our downstream application)
• Other RICs: QUOTIM appears to be in EDT/local time (ie. AED3Y= has a QUOTIM raw value of 15:59:04 but our downstream application reflects 19:59:04, which would seem to indicate the QUOTIM is reflecting an EDT timestamp and not UTC)

Questions:

1. Per LSEG/Refinitiv documentation, should QUOTIM always be UTC, or is per-RIC timezone handling expected?
2. When QUOTIM is unavailable, should we use VALUE_TS1 (time) combined with VALUE_DT1 (date)? Is this the intended fallback, and what timezone do these fields use?
3. Is there a metadata field (RIC config, snapshot field, or data dictionary entry) that indicates the timezone for a given RIC or rate source?
4. For multi-source feeds, do different sources have different timezone conventions?

Any guidance on proper timestamp and timezone handling would help us normalize across all rate sources.

Jirapongse

@Nickolus_Snan

Thank you for reaching out to us.

This forum is dedicated to software developers using LSEG APIs. The moderators here do not have in-depth expertise in all content available through LSEG products, which is required to answer content-related questions such as this one.

I found that you have already submitted a service request to the Content Support team regarding these questions. The team is currently investigating your request and will provide a response as soon as possible. In the meantime, please follow up directly with the Content Support team for further updates.