Sanne, in fact I don't agree, because using local time is a liability even if you use local time for everything. For example, when you want to calculate time spans, you will get up to 2 hour errors, depending if the start/end times were created during daylight-saving times or not. Also, during daylight-saving changes you can have time "going back" 1 hour, and then any audits during this hour will be out of order. In fact, during this period of time it will be impossible to even know if some audited data was created during the first 11:45:30PM or the second 11:45:30PM, for example. Also, sometimes developers test using databases on their local machines, and then they cannot use UTC to develop and test. This may also result in tests passing on local machines but not on servers. Using local time is REALLY bad, and only very small businesses that in fact have no legal requirements can afford having the approximate times that local timezones deliever.