Enter your idea

Fix the date coding to match the browser’s native date control, which presents dates according to the user’s locale while storing them internally in a standard format or the company's location.

The Invoice Payment and Batch Deposit ignore the organization's regional date settings when dates are entered manually. This only seems to occur in these specific windows, making the behavior inconsistent with the rest of the platform and interrupting data entry every time a payment is recorded, essentially causing havoc when regular users go to enter a date and don't check that it's correct, which makes reconciling harder, cumbersome because I have to undo what my client did.

For US organizations, typing 08/03/2026 (August 3, 2026) is rejected, while 03/08/2026 is accepted because these windows appear to be expecting DD/MM/YYYY. Or you get invalid dates because 12/17/25, there is no 17th month.

The software already knows my organization is in the US. I shouldn't have to mentally translate the date format every time I record a payment. The organization’s regional setting is probably being used to display the date after it has been accepted, but not being passed into the code that interprets what you type. A properly programmed date field would either use the browser’s native date control, which presents dates according to the user’s locale while storing them internally in a standard format, or it would feed the organization locale into the parser. HTML date controls are specifically designed to translate the user’s preferred format into a normalized internal date value