To keep your firm functional and punctual, MerusCase keeps track of just about every activity with an exact timestamp. You can see exactly when messages were sent and received, when activities were created, when events are scheduled, and when billable time was recorded. 

Accurate timestamps are essential for everyday tasks. If, for example, your system clock is an hour behind and you have a depo scheduled in the MerusCase calendar for 10:30, you might miss it when your event reminder pops up an hour late. Clocks that are off by many hours or even days can cause trouble when making invoices and ledger items, where wrong invoice dates and billing periods could cost the firm hundreds or even thousands of dollars if rejected for inaccuracy. 

MerusCase's servers update their time automatically from dedicated time servers linked to atomic clocks and GPS satellites. Modern operating systems (Windows, Mac OSX, most distributions of Linux) periodically update their clocks from the same servers, so it's pretty rare for our users to see this error message. 

Some computers, however, may have time syncing turned off, or have an internet connectivity problem which prevents the computer from reaching these time servers. Computers have their own internal clocks, but when Daylight Savings Time rolls around, these instantly become an hour early or an hour late.

We had a user email in who was seeing this message over and over, even after going to their system clock and updating the time. Their message came in a short time after Daylight Savings, so we guessed that the time change meant their workstation wasn't auto-updating the time.  

They'd taken the time to update the clock themselves and were still being presented with the error, so we knew there was still an incorrect time somewhere. After they closed and re-opened their browser to clear temporary files (including stored time settings), they were still seeing the warning message.

Some computers in office environments pull their settings from a centralized server in the office. This is a domain setup, and the settings managed by the domain controller include user profiles, permissions, and time settings. They checked their domain controller, and sure enough, time syncing was turned off there: it was applying the wrong time to every computer in the domain.

Setting the auto-updating clock on the server soon fixed all of the client computers in the office. They thanked us for getting an answer, and promised to have strong words with their office's IT for leaving automatic time updates off!