Fraud Protection Status Booking Journal
Purpose of this function
The Posting journal status checks whether the journal in the SQL database has been subsequently changed.
As SQL databases can be manipulated in principle, this is a key security instrument for maintaining data integrity.
This enables auditors, owners and Hypersoft support to ensure that all bookings are available unchanged.
How it works
Each journal data record receives a hash code (checksum).
These hash codes are compared with the stored values during the status check.
Deviations indicate that data has been changed or corrupted.
The results are documented in a status file that can be made available to inspectors.
Start Status Booking Journal from the Database & Tools programme group:
| Element / Switch | Function / Description |
|---|---|
| Update | Refreshes the view. |
| overall examination |
The check for complete and unchanged data is carried out at the start of the program the last 3 months. If you want to check all existing data once, choose Overallcheck. |
| status |
|
| Display training bookings |
Scans for days on which training bookings were made and displays them:
|
Red= Modified data found. Records have been manipulated.
Black= At least one record is missing. An indefinable deletion in the booking journal has taken place.
Light green= No day-end closing, data fixed. (Refers to data converted from previous versions that did not close the day).
Green= Data is correct and fixed. This is the default, after the day's closing.
Dark red=Secured data, day-end closing not yet completed. This is the default before the day-end closing.
Pink=day completed, pre-recording active (function removed since 2016), recording open.
Grey=unsecured data, daily closing not yet done. Pre-recording mode (function removed since 2016) is active, no recording found.
Light gray=data partially saved. Pre-recording (function removed since 2016) is active.
Blue= These data are converted from older versions or via the Vectron data import. The fixing has been made.
Orange=Training bookings (press button for view).
Interpretation of results
For auditors:
No deviation → Journal is unchanged and audit-proof.
Deviations present → possible manipulation or technical errors. In this case, involve Hypersoft support.
For owners / financial managers:
Proof that the cash register data is compliant and complete.
Proof of compliance with legal obligations (GoBD, KassenSichV).
For Hypersoft support:
Helps to analyse technical problems or unusual journal entries.
Supports the preparation and monitoring of tax audits.
Best Practices
Check the status of the booking journal prior to checks and have the result ready.
In the event of anomalies, contact Hypersoft Support immediately to clarify the causes.
Carry out regular checks, even if there is no reason to do so, to ensure the integrity of the data in the long term.
Further topics:
Accounting journal, logic and filing from a fiscal point of view
Security functions in the journal
DSFinV_K Export - Instructions & file structure
Back to the overarching topic: fraud protection