Platform
Who changed what and when: traceable in the tenant.
Relevant events are logged: creating, changing, sending, and locking documents, user actions, and configuration changes. The log is tenant-wide and supports internal audit, without a separate audit tool.
These are the points this feature covers day to day.
The workflow in Jupiter ERP, on this page.
Background, typical workflows, and concrete panel capabilities, more detail than the summary above.
The activity log records who changed, sent, or locked documents, master data, or settings and when. It is part of the platform and included in every plan.
Who may view the log is controlled by permissions. It does not replace GoBD archiving, but it makes team actions internally auditable.
The log answers who created, changed, sent, or locked a record, and when. It lives in the system area and is included in every plan.
For review inside the team, the question is often which person sent the document. That is what the log is for.
Immutability of the accounting documents themselves is controlled by period locking, not by the log alone.
The main building blocks at a glance, complemented by the longer description above.
Filter the log in the system area: who changed or sent which record and when.
Sends, status changes, and period locks appear in the log, alongside the document history.
The activity log is part of the platform and included in every plan, independent of booked modules.
Start for free: write invoices on the Free plan. Choose plan, term, and add-ons in the app afterwards. Custom adaptations or API integration? Get in touch.
