DateTimeCreated field in SOPOrderReturn to match Application/Database Server timezone

In 200 when a new Sales Order is created and saved, the DateTimeCreated field in SOPOrderReturn is populated and is exactly one hour behind the actual time the Sales Order was created. Having spoken to 200 Tech Support, this is because the DateTimeCreated field uses UTC rather than the same time as the database server, or the Sage Application Server...or even GMT! This causes problems if Sage Sales Order documentation (Picking Lists, Despatch Notes, Labels etc.) uses the DateTimeCreated field for processing orders on time. There is no workaround to this.