My college's class scheduling website also had hours of operation. One of the rumors was that it would stop students from drunkenly dropping all of their classes, but the real truth was that it was based on an old system that needed to process things overnight and they couldn't get funding to modernize it. This was UMD -- it was notorious when I was there for being annoying but still cracks me up.

Thanks! I'm glad you like it. I do think it could have some cool dynamics but that is what I'm testing right now.

I know a bank in Sweden that does _not_ do this and apparently runs various batch jobs at something like 1-3 am. So, one night I made a transaction to it and it looked just fine in the app, then it was mysteriously gone in the morning! On the receiving side; my cash had still been withdrawn! I called the support and we eventually realized that no, you shouldn't do transfers at 2 am on a Saturday because it's likely to fail and then we have to wait for the weekend to be over for them to reappear. I was like... "Alright, thanks. But maybe you should close your app these hours..."

The software engineer within me shudders at the thought of running batch jobs in production while there are ongoing transactions, and where conflicts can and are fully expected to happen.

Which bank was it?

The US social security administration site did (and still might) do this as well.

Likely to enable batch processing in the evening without dealing with sync issues

Wouldn't surprise me at all.

One day we'll have the manpower and brains to figure out how to just have out of hour entries added to the next day's batch.

Federal EIN registration site does this as well