Overview and GoB Logbook
annual overview
In the year overview, you can view all months of a selected year from the cash book. The view can also be grouped by input/output, VAT rate, both or none of these. The posting total shows how many postings the total is based on.
- By clicking on an entry the affected month is displayed, here the weeks are listed.
- By clicking on an entry the affected week is displayed, here the days are listed.
- By clicking on an entry, the affected day is displayed and the bookings are listed here.
The GoB Log is a logbook which can be kept in accordance with the principles of proper accounting (GoB). The cash book is protected from a cash deficit during processing, which prevents the cash balance from falling below 0 to be GoB compliant. In order to be able to track all changes in the cash book, each change is therefore recorded.
The GoB Log contains the exact booking date, booking text, payment type, amount and the sales tax from the cash book. All other field changes are not recorded in the logbook. The logbook also contains the following fields for historical display:
- Log date: The exact time when the entry was made.
- LogID: ID that is unique for each posting, from create to edit to delete.
- Type: The type of change that created the entry (create/edit/delete).
- User: The user who triggered the entry.
With the GoB Log every relevant change in the cash book can be traced back to the cash book. Since the data is safely stored on a server, it cannot be changed without being recorded in the GoB Log.
All data from the import is saved together with the executing user. Even if data are excluded from the import, they are first entered in the GoB Log and then deleted again.
Another help is a filter for highlighting entries where the affected day and the day of the change are far apart. (Late entry after X days).
Numbering Hedges
The document number can be freely assigned by the user. It can be assigned more than once, since a document can also contain several tax rates (such as 19% and 7%). These postings are split for the cash journal, but are on a document/invoice. Internally, the system automatically assigns a unique ID, which makes an entry in the cash book unique. This ID is not visible on the surface and cannot be changed by the user.
Furthermore there is the so-called 'LogID' which marks the booking / the cash book entry in the logbook according to GoB. In the logbook it can be checked whether GoB relevant changes to the entries have been made by the user. The same LogID means that it is the same record that was changed. Even if the document number should be the same, the LogID is different and identifies the record.
Screenshot from the logbook...
Here you can see two bookings. It is also possible to read in the logbook whether entries have been changed, which did not happen in the case of the two entries.
Back to the parent page: cash book