I know this is an old topic, but I believe I have found where the timezone on the servers does have an impact. We have business transactions that occur in Central time. However, because they are later in the evening (24/7 Production operation), they end up having a transaction date of the next day. All users and legal entities are set to Central time.
I did find this article which was related to AX 2012, but I'm expecting the same functionality:
Some fields in Dynamics AX contain information about dates, some fields contain information about time, and some fields contain information about both. The fields that contain both use UTC. UTC supports multiple time zone capabilities running server-based code. The fields that only contain date information or only contain time information do not have time zone capabilities. An example of a field that does not have time zone capabilities is the Invoice Date. Invoice Date extends a date type, carries no time information, is not based on UTC, and has no time zone capabilities. If you are using a field that does not have time zone capabilities and you need it to work across multiple time zones and you require transaction-level posting with the local date and time, then you must set up an AOS in each time zone. If you do not setup a separate AOS for each time zone, then the posting date will be reflected by the time zone which the AOS is associated not the local time zone. For example, if your AOS is based in Greenwich Mean Time (London) and a subsidiary of your company is based in the Central Time Zone (Chicago), the time difference is usually 6 hours behind. Any transaction that is posted after 6:00 PM in Chicago will be recorded as a transactional date for the following day, thus you will have an incorrect posting date based on local time zone.
We're working on testing this in a Tier 1 environment to confirm.
