The problem you just gave yourself is that NOW you have to remember if you already did something,... e.g. your "arrears" situation.
Your comments about accounts in arrears that trigger a specific type of update means that if you open the DB twice on the same day, you have to remember that you did something the first time that you don't want done again. I.e. double-charge of arrears. This makes it more complex.
If you have a power outage on the 25th of the month, you have to remember on every 25th of a month that you DID generate your output so that on the day of the power recovery after the DB was down on the 25th, you can remember that you didn't yet create your desired outputs. If it happens that you do some processing of updates during this output generation, you would again run in a double-processing case.
How many people can open this DB with the right to run that required output? If the answer is "more than one person" then you also have to allow for possible simultaneous actions that would trigger double-reports or double-arrears. This sounds like a situation that INVITES destructive interference in everyday operation.
Then there is the question of a database proposed to enjoy 24/7 activity, which I will CATEGORICALLY tell you is not going to happen. Every so often, because of memory leaks that clog up Windows scratchpad memory in something called Non-Paged Pool and, to a lesser extent, in Paged Pool, Windows MUST be rebooted. More directly, whether you like it or not, Windows WILL reboot - and not give you a choice - AND it will be the ugly type of reboot derived from a Blue Screen of Death. Having an Access app open during one of these forced reboots is the proverbial hole so big you could drive a Mack truck through it. This is one of the circumstance that KILLS databases - because if there is a pending update in this DB at the time that Windows takes the big dirt nap, you can corrupt your DB irretrievably. OK, admittedly Microsoft has improved the stability of Windows - but it still isn't perfect.
This concept - a 24/7 database - is fraught with peril.
