Sourcing Negotiations Closing Earlier Than Configured Time Based on Time Zone

We observed a scenario in Oracle Fusion Cloud Sourcing where a negotiation configured to close at a specific local time was considered already closed by the system, preventing suppliers from submitting additional responses, even though from the user’s perspective the configured closing time had not yet been reached.

This behavior suggests that the negotiation closing time may be evaluated using a different time zone than the one expected by users.

Could you please clarify:

• Which time zone is used as the source of truth to determine the effective negotiation closing time in Sourcing
• How application, server, or Legal Entity time zone settings impact the negotiation close time