Every mutation, logged through the canonical module | HelloBooks POS Bill creates, edits, voids, returns, refunds, overrides, settings changes — all flow through the same audit trail you use for back-office bookkeeping. SAP / Xero-grade, never POS-grade.
Every mutation, logged through the canonical module
Bill creates, edits, voids, returns, refunds, overrides, settings changes — all flow through the same audit trail you use for back-office bookkeeping. SAP / Xero-grade, never POS-grade.
Part of HelloBooks POS · Architecture / safety
The audit trail is what separates a real accounting POS from a “till that emails reports”. HelloBooks runs every mutation through the canonical audit module — append-only, signed, queryable — so SAP-grade compliance is the default, not an upgrade.
Every detail, dialled in
Built for the till, validated against the canonical accounting engine — so every POS sale closes the books cleanly.
Append-only by design
No row is ever updated in place; every change writes a new audit record with the prior value, the new value, the actor, the action, and the timestamp. The audit log is the source of truth for state changes.
- Append-only writes
- Prior + new value captured
- Actor + action + timestamp
- Cryptographically tamper-evident
Queryable by anyone with access
Filter by entity, by user, by outlet, by action type, by bill, by date range. Export for audit. The CFO, the auditor, the franchisor all read from the same authoritative log.
- Multi-axis filter
- Per-bill drill-down
- Per-user activity
- Export for audit
Permissioned read
Audit data is sensitive — write access is engine-only; read access is permissioned by role. Cashiers cannot read audit; managers can read their outlet; auditors can read everything.
- Engine-only write
- Role-based read
- Per-outlet scoping
- Auditor SSO supported
Why teams move off legacy tills
- Audit log shallow or absent
- Updates in place lose history
- Read access ungated
- Auditor needs Excel exports
- Append-only canonical module
- Full state-change history
- Permissioned by role
- Auditor reads natively
Questions, answered
How long is audit data retained?
Indefinitely by default. Per-entity retention policies can be configured; the engine enforces them.
Can the audit log be edited?
No — append-only. Even support engineers cannot edit prior records; corrections are new records with explicit reversal semantics.
Does this comply with regulator expectations?
Yes for the jurisdictions we support (India GSTN, AU, UK HMRC). For US SOX-style controls the read-permissions and append-only properties meet the bar.
Can I integrate with my SIEM?
Yes — audit events stream out via webhook to your SIEM of choice. Real-time visibility for security teams.
Related POS features
Ready to automate your books?
Join 2,000+ businesses saving 20+ hours per month. Get started free — no credit card required.