This is almost certainly a result of your timezone.
When a Date Only picker returns a value, it returns a DateTime, where the time component is midnight for the local timezone - e.g. 2012-01-04 00:00:00.
When this value is converted to UTC time, it can become a value for the previous day. For email, if the local time zone for the above datetime is +2, then UTC time would be 2012-01-03 22:00:00.
Naturally, if you simply look at the date part of the date time, this now appears to be an entire day before. I would suggest you start by looking at the date component of the Expiry date - is that offset by your timezone setting?
SharePoint does store all datetimes in UTC time, so it will convert that local datetime to UTC. I'm not sure, off the top of my head, what timezone the datetimes in the AfterProperties are in.
Cause
The problem I'm updating a list with a date field (just the date) using the Client object model but when the date is inserted is one day off from the introduced date
After searching for a long time, it turns out that the “problem” was how SharePoint stores dates. Indeed SharePoint converts dates to UTC … that’s why my comparison was not good!
So when you want to work in code behind with dates, do not forget to convert to UTC!
For this, two methods:
SPTimeZone.UTCToLocalTime et SPTimeZone.LocalTimeToUTC
Solution
Another option would be to retrieve the time zone of SharePoint and explicitly convert now in local time by using the .NET Framework when you save the item list as shown below.
//1.Retrieve SharePoint TimeZone
- var spTimeZone = context.Web.RegionalSettings.TimeZone;
- context.Load (spTimeZone);
- context.ExecuteQuery ();
- var fixedTimeZoneName = spTimeZone.Description.Replace("and", "&");
- var timeZoneInfo = TimeZoneInfo.GetSystemTimeZones().FirstOrDefault(tz => tz.DisplayName == fixedTimeZoneName);
- listItem ["DateTime"] = TimeZoneInfo.ConvertTimeFromUtc (dt, TimeZoneInfo);

Mick levesquePosted Aug 5, 2021, 11:47 PM
That will not work if your language is something else than english on your user o365 settings.
Razim KhanPosted Aug 3, 2017, 2:31 AM
System.TimeZoneInfo' is a 'type' but is used like a 'variable' the following error display
Rajkiran SwainPosted May 27, 2015, 9:24 AM
nice
Sibeesh VenuPosted May 27, 2015, 5:59 AM
Good one.
Santhakumar MunuswamyPosted May 26, 2015, 3:48 PM
Nice