Originally Posted by RogerD408

Just a guess, but it sounds like a simple math error to me. Cancellation Date = Reservation Date -1 gives you the wrong date (let's not even get into time of day). And since they have to take into account the property's timezone, they've got to be doing more math as the likelihood of the web server actually being in the same time zone is probably rare.

Yes, it's frustrating when the system doesn't work right. Yes, it should be fixed. Will we see it anytime soon? Probably not. So in the meantime it's up to us to keep track and hope the backend works and a charge is not processed.