Is there a way to prevent creating AR receipts with that far out of a future date?
Summary:
When a user manually creates an AR receipt, there is currently no validation to prevent entering a receipt date that is significantly in the future.
In this case, the intended receipt date was 8/26/2025, but the user inadvertently entered 8/25/2026—almost a year later. The error was not noticed until around August 20, 2026.
By the time the discrepancy was identified, the user was unable to reverse the receipt because the Reverse option was grayed out.
Client Question / Requirement
Is there a way to introduce a validation or restriction that prevents users from creating AR receipts with dates significantly in the future? For example, could the system restrict the receipt date to the current date or within a defined future-date tolerance?
Tagged:
0