Timecard - Time Zone Error

Update note on this very old case as I had a customer asking about the Appointment endpoints.

Based on a separate discussion I had around the Activity endpoint, and new features in more recent editions of Acumatica.

To get full compliance here you want to be using:

• Version 25r2 or higher, and using endpoints extended off DEFAULT / 25.200.001 or later.
• The TimeEntry endpoint.
• Specify the TIMEZONE field directly.

I had separate confirmation from Acumatica, that for Acumatica time zone treatment you should:

1. If sending API values, never specify a Z value (UTC offset), always just present the time as local time (So 9 AM is 9 AM, no matter what part of the world you’re in)
2. If a Timezone field is present, set your UTC value there.
3. If having issues, try making sure your SERVER time aligns to your Work Calendar/local user.
4. Try to make sure  the same Timezone is used on all stages,so:
   1. Server is in Timezone A
   2. API User (for request submission) is in Timezone A
   3. Work Calendar for assigned resources is in Timezone A
   4. End User running payroll/coordination processes is also in Tiimezone A.

Prior to 25r2, or when using the Activity endpoint in 25r2 (or below, not tested higher) I was unable to guarantee the date selection successfully for week selection when preparing Timecards.

If you need Activity or Appointment endpoints to have Timezone, you’ll need to either customize this yourself, or get a change request in with Acumatica.

Note: Won’t affect most customers
Issues will be much more likely if you’re in Australia/New Zealand (because the UTC offset puts the workday across a date boundary if everything is confused), or if your business works 24 hours, since times closer to midnight are more likely to select the wrong day.

MYOB Only setting information:
As of time of this post, all MYOB Acumatica sites are running on Sydney time (Australian Eastern with Daylight Savings)