Since it happens all over Sage 100, I suspect there is a flaw in an underlying date validation routine, or a way that when a date entry is cleaned up for display, a bug at times sends the actual messed up typing as what gets saved, not the cleaned up version that is displayed.