Security functions in the journal
Purpose of this page
The Hypersoft journal is the central record of all bookings.
Hypersoft has special security mechanisms in place to prevent manipulation or ambiguity.
These mechanisms guarantee the complete, unadulterated and traceable storage of all processes.
Bookings in the Hypersoft system are traceable from origin to completion.
With Hypersoft Trace, processes can be tracked in detail.
Even complex processes (e.g. payments, transfers, credit notes) remain fully documented.
Further topics:
Fraud Protection with Hypersoft Trace
Trace in the master transaction overview
Transfer report after multiple transfers
2. Reopen cancellation monitoring
Hypersoft safety fuse
A reopen cancellation occurs when a process that has already been completed is subsequently reopened and changed.
Hypersoft explicitly identifies such cases so that they can be clearly distinguished from normal cancellations.
This ensures that:
-
Owners can understand when employees make unusual changes.
-
The auditor must have proof that all changes have been documented and taken into account for tax purposes even after completion.
-
Tax evasion or internal fraud cannot be concealed - even if it is not intentional.
Practical example
A guest pays an invoice in cash and later requests a split or change.
The system reopens the transaction and generates an offsetting entry (with a negative sign).
The transaction is rebooked with a positive number.
The journal therefore contains three entries: original, offsetting entry, new entry.
The reopen cancellation is clearly marked.
Benefits for owners and inspectors
Owners can prove to auditors that all transaction changes are fully visible.
Auditors can see that Hypersoft does not conceal any manipulations, but on the contrary transparently reports suspicious changes.
This creates legal certainty and trust - for both sides.
Further topics: Monitor reversal after completion
SQL databases can theoretically be changed at a later date.
The status booking journal is a checking mechanism that addresses this risk:
Hash code check: Each booking receives checksums that are compared during export or checks.
Presentation of results:
"No deviation" → Journal is unchanged and tamper-free.
"Deviations" → possible data manipulation or technical errors.
Verification function: For auditors, this is direct proof that the journal has not been subsequently changed.
Further topics: Fraud Protection Status Booking Journal
Best Practices
Always point out these safety functions to the inspector.
If you have questions about unusual bookings, provide trace reports or the booking journal status.
Owners should regularly check the reports on reopen cancellations.
In the event of anomalies, consult with employees immediately.
Actively show auditors: "Even changes after completion are recognisable and traceable with us."
This turns the message around:
Not "Watch out, something could go wrong here", but "Hypersoft protects you by also documenting subsequent changes and making them transparent for auditors".
Back to the overarching topic: Security & data integrity