Yes, this is a security bug. Depending on the closing date entered, the date might advance to the 12th month, or might retreat all the way back to January of a given year, allowing wanton edits in the file during periods that are supposed to be closed.
It's actually amazing how lame this is, because dates in QuickBooks are usually stored internally as numbers, something like 44871 for today, but seems like the date here is stored as text and then - sometimes - adjusted if the resulting date is invalid.
For example, if you set the closing date to August 1 while the computer date format is DD/MM/YYYY, set it so to "01/08/2022", save it, and try to record a new transactions in July 2022, you'll get a message saying that the transaction date is before the closing date. So far, so good.
But then if you change the system date format to MM/DD/YYYY, reversing the month/day order, then even while QuickBooks is still running and the transaction form is still open (or restart QuickBooks. It doesn't matter), then you can record the transaction in July without getting any messaging!
This is because after making the system date format change, and then you open preferences and review the closing date, QuickBooks still displays "01/08/2022" as the date, only now it thinks that means January 8, not August 1!
And so, now the user can add/edit/delete transactions all the way back to January 8.
Seems slightly wrong.
