Overview
When something changes on your dashboard — an order created, a price edited, a payment recorded — Neev writes a line into the audit log: who did it, what they did, and when. No more "who changed this rate?" guessing. The same compliance corner also builds your GST filing files — GSTR-1, GSTR-3B and the HSN summary — straight from your invoices, in the shape your filing portal expects. One place for "what happened" and "what to file."
Where to find it
The audit log is a standalone admin screen at /settings/audit. It is not one of the regular Settings tabs — it has its own route. Open it from Settings on the web; it is web-only.
Opening it needs the audit.read permission. By default the owner holds it (and so does the manager role), but most teammates do not — anyone without it lands on an "Owner-only view" message and sees no rows.
GST exports are a separate read-only surface (the gstExport queries) that pull from your finalized invoices. They live alongside your filing and integration tools, not inside the audit log itself.
Key concepts
- Audit entry — one row per change: when, the user, the action (like
orders.create), and the target (target type plus its ID). Each row keeps a before-and-after snapshot of the change. - Action — the dotted name of what happened, e.g.
orders.create,pricing.update. You filter by this exact string. - Module / target type — the area the change touched (e.g.
orders). Use it to narrow the log to one part of the business. - Keyset paging — the log loads in pages (50 at a time, up to 200), oldest-next on "Load older." It never skips or double-counts rows.
- Partitions & cold storage — older audit data is split into partitions and can be archived to cold storage so the live log stays fast. The owner can still see what's been archived.
- GSTR-1 / GSTR-3B / HSN summary — your three filing artefacts. GSTR-1 is outward supplies, GSTR-3B is the summary return, and the HSN summary rolls up by HSN code. Each comes back as a NIC-shape JSON / Excel bundle for the period you pick.
Common workflows
Open /settings/audit. Type the action in the Action box — e.g. pricing.update — or the area in the Module box — e.g. orders. The table redraws to matching rows only.
Each row shows the time (DD/MM/YYYY, 24-hour), the user, the action, and the target type + ID. That tells you exactly who touched which record and when.
The log shows the latest 50 by default. Hit Load older to pull the next page. Use Reset to clear the filters and start fresh.
Pick the artefact — GSTR-1, GSTR-3B or HSN summary — give it your GSTIN and the period start and end dates. Neev reads your finalized invoices and hands back the filing bundle to upload to the portal.
Role notes
The audit log is gated by audit.read, which by default only the owner and manager roles hold — the accountant does not. GST exports look like they're an accountant job — but by default the accountant role is not granted the GST export keys either. This is the one trap to know here.
| Role | View audit log | Run GST exports (GSTR-1/3B/HSN) | Tally export |
|---|---|---|---|
| Owner | Allowed | Allowed | Allowed |
| Accountant | Not allowed | Not allowed | Allowed |
Owner holds every non-Pack permission through the * default binding, so the owner sees the audit log and can run all three GST exports. (Pack permissions for pharma, dairy and quick-commerce only bind once that Pack is installed.)
Accountant handles money — recording payments, generating invoice PDFs, payment links, tenders — and reads financial and Tally reports. But the default binding gives the accountant only reports.tally-export, not the gst-export.gstr1 / gstr3b / hsn keys. So out of the box the accountant cannot run the GSTR/HSN exports even though the team-invite copy mentions "exports." The accountant also cannot void invoices or change pricing — those stay with the owner. To let an accountant pull GST files, the owner must grant those export permissions explicitly.
Tips & time-savers
orders.create in the Action box, or the area like inventory in the Module box, and you jump straight to the rows that matter. Pair the two to narrow a busy day to a handful of entries.The audit log and partition view stay fast even years in, because old data archives to cold storage automatically — you get history without a slow screen.
Gotchas
audit.read permission. Out of the box only the owner holds it, so if your accountant opens /settings/audit they get an "Owner-only view" and zero rows — that is not a bug. (The manager role does carry audit.read by default, so a manager can open it.) If a teammate without the permission needs a specific entry, the owner has to look it up and share it.gst-export.* permissions first.GST exports build the filing bundle for you to upload — they do not file the return for you, and there's no background job queue yet, so the file comes back right when you ask. The e-way bill is listed on marketing but has no module behind it today.