Closing Operations

Working with a computer system used to involve repeating "batch" closing runs. On the one hand, they were essential, since there was only a limited storage capacity and since it was possible and necessary to delete transactional data after so-called daily-, monthly-  or annual closings.

IT closings were also necessary for non-dialog-oriented applications, which used to start the actual data processing as a "batch job" after complete data collection (daily closing, account closing etc.). After a certain "operating" time (according to computer performance), the user used to receive the result in terms of an expression.

These regular "closings" are technically no longer required. Today, storage and speed are usually sufficient to process data immediately and to keep it longterm on the computer. 

As for reporting however, these "closings" still need to be done: for this, it requires to collect periods of abgegrenzte figures. It should technically be enough to just start the according database requests or evaluations and to present the result as the "closing" to the management. Unfortunately data quality is often not good enough to just pass such figures without double-checking.

The following will describe, which steps are essential to obtain secure evaluation data. This includes mainly checks.