Audit log
Every important action in your account is recorded with the user, date, and detail of the change - to settle disputes, demonstrate compliance, and reconstruct the history of any document.
Mosce ERP keeps a complete, tamper-proof record of all important actions performed in your account. This guide explains what the log contains, who can view it, and how to use it.
Reading time: ~5 min
What is the audit log?
The audit log is a chronological record of every significant action executed in your account: who did what, on which record, when, and with what result. Each entry includes:
- User - name and email of the person responsible.
- Date and time - exact timestamp in the tenant's time zone.
- Resource - the type of data affected (invoice, product, customer, etc.).
- Identifier - the internal code or number of the specific record.
- Action - create, modify, delete, export, send, or the corresponding event type.
- Change detail - the previous and new values where applicable.
The log serves three main purposes:
- Settle internal disputes - know exactly what changed, who changed it, and when.
- Demonstrate compliance - present evidence of activity to the DGII or other agencies.
- Reconstruct history - understand how a document reached its current state.
Collection always active
Mosce ERP captures every important action on all plans, without exception. There is no switch to pause or disable it. Traceability is a platform guarantee, not an optional feature.
Who can view the log depends on the plan and the user's permissions - that's explained in the next section. But capture always happens, even on the free plan.
Who can view the log
Access to the audit log viewer has two independent requirements that must both be met:
| Condition | Requirement |
|---|---|
| Plan | Starter or higher (STARTER, PROFESSIONAL, or ENTERPRISE) |
| Permission | audit:read assigned to the user by the account administrator |
Free plan: the log is still captured normally, but the viewer is not available. If you try to access it, Mosce ERP shows you an invitation to upgrade your plan. To access the viewer, upgrade to the Starter plan or higher in Settings › Billing and subscription.
Starter plan or higher: the Audit log option appears in the sidebar only when your plan enables it and you have the audit:read permission. If you are the account Owner you have full access by design; if you are an Administrator, the permission comes included in your role by default.
Related permissions
| Permission | What it allows |
|---|---|
audit:read | View the account's audit log and filter it by user, date, resource, or action. |
audit:export | Download the filtered log in CSV format. Not pre-assigned to any role - the account administrator must grant it explicitly to the role that needs it (typically an external accountant or auditor). |
To create a custom role with these permissions, go to Settings › Roles and enable the corresponding permissions. See Users, roles, and permissions for the step by step.
What is recorded
The log covers all operational and configuration areas of the account:
Business operations
- Customers and suppliers (creation, removal, data edits).
- Products, variants, and inventory adjustments.
- Quotations, sales orders, and purchase orders.
- Invoices, credit notes, and payments.
- Expenses and expense vouchers.
Electronic fiscal vouchers
- Creation and submission of e-CFs to the DGII.
- Cancellations and replacements.
- Recorded contingency events.
Account configuration
- Users: invitations, activations, role changes.
- Custom roles and permissions.
- Catalogs: tax rates, credit conditions, margins.
- Fiscal sequences and electronic signature certificate.
- Integrations (email and storage).
When support enters your company
There is one situation worth explaining plainly, because it affects what you will read in your own log.
When you report a problem that cannot be reproduced any other way, the support team can act as your user for a limited time, to see exactly what you see. While that happens, everything that occurs is recorded under your user's name, because that is what genuinely happened to your data: if a client was created, that client exists and that session created it.
What does not appear in your log is which support engineer was behind it. That part is kept separately, in the platform's internal record, together with the reason the team noted when opening the session.
Why it works this way
The alternative would be to show the support engineer in your log "for transparency". The opposite was chosen deliberately: your log has to read as the story of your operation, without outside names mixed in among your team's. Tracing who came in from outside is the platform's responsibility, not noise for you.
Put briefly: you see what was done; the platform also sees who was behind it.
The limits of that session
- It lasts 30 minutes at most and ends on its own.
- It cannot do everything. Reserved operations, such as changing your plan, are refused even while the session is live.
- If it ends while somebody has a screen open, the application says so, and that screen can no longer save anything.
Retention
How long Mosce ERP keeps the history varies by plan:
| Plan | Retention |
|---|---|
| Free | 30 days |
| Starter (STARTER) | 7 days |
| Professional (PROFESSIONAL) | 30 days |
| Enterprise (ENTERPRISE) | 90 days |
Entries related to electronic fiscal vouchers are not deleted automatically, regardless of the plan, due to regulatory requirements.
If you need a longer history, upgrade your plan. Accumulated history is not lost when you change plan - only the retention window for new entries is adjusted.
Available filters
From the Audit log viewer you can narrow the search with:
- Date range - from / to.
- User - by name or email address.
- Resource - data type (invoice, quotation, product, customer, etc.).
- Action - create, modify, delete, export, send.
The table shows each entry with its resource identifier. You can copy that identifier to open the affected record directly or to include it in a report.
Limitations
- The audit log is immutable - individual entries cannot be edited or deleted. This is part of the log's integrity guarantee.
- Entries are purged automatically when they reach the plan's retention limit.
- There is no view that consolidates the history of multiple tenants on a single screen (each account has its own log).
Related
- Users, roles, and permissions - how to create custom roles and assign
audit:read/audit:export. - Billing and subscription - how to upgrade to the Starter plan or higher to access the viewer.
- e-CF documents - electronic fiscal vouchers whose traceability is kept permanently.
Deleting a branch
What Mosce ERP checks before letting you delete a branch, what can be blocking it and how to fix each case, and what happens to its warehouses, its registers, and its assigned people once the delete goes through.
Billing and subscription
How to view your plan, change it, handle the trial period, update the payment method, and download your Mosce ERP subscription invoices.