BYTE · Security · Audit Coming soon

Audit log in BYTE: who changed what, and when

Every business asks the same question after a mistake: who changed this, and when? BYTE writes a row for each action in the organisation, and an org admin can read the history of any record, any user, or any date range.

Last updated: 17 November 2026

History, invoice 1042ActionRoleTimeCreatedAccountant09:02PostedAccountant09:14VoidedOrg admin11:40Rows in the history3Row writtenDevice recordedEach row holdsRecordInvoice 1042ModuleAccounting
Illustration of the history of one invoice: three actions in order, each with the role of the person who did it and the time. The roles and times are examples, not a screenshot.

What it covers

  • A row for each action in the organisation: the action, the person and their role, the record it touched, the time, and the module.
  • The device ID, IP address and country of the request are stored with each row.
  • The history of each record, newest first: every action taken on one invoice, bill, payslip or employee, in one list.
  • Search by record, by person, by action, or by date range, on the audit page.
  • An org admin switches the log on or off for each module, such as security, settings, accounting, POS or inventory.
  • Each row is written once, even when the write is retried.
  • Export for a chosen period as a CSV or JSON file, from a secure page that checks the admin's device and email first.
  • Only org admins read the log, because it shows what other people did.
  • Voiding an invoice or a payment writes its own row while the accounting log is on.

How it works

  1. Each action writes its row, with the person, the record, the time and the device.
  2. An org admin opens the audit page and picks a record, a person, an action or a date range.
  3. Export the rows you need as a CSV or JSON file, for the auditor or for your own files.
  4. In the audit settings, switch the log on or off for each module.

A worked example

One invoice has three entries in its history. The roles and times are examples.

TimeActionDone by
09:02CreatedAccountant
09:14PostedAccountant
11:40VoidedOrg admin

The history shows the three actions in order. Voiding the invoice writes its own row, and the original row stays as it was.

At a glance

Built means the feature is in BYTE's current build. BYTE is coming soon, so ask us for the status of anything you need.

AreaWhat BYTE doesStatus
Every actionA row per action: the person, the role, the record, the time and the moduleBuilt
Device and placeThe device ID, IP address and country are stored with each rowBuilt
Record historyOne list of every action on a record, newest firstBuilt
SearchBy record, by person, by action or by date rangeBuilt
Per moduleSwitched on or off for each module by an org adminBuilt
Written onceA retried write is recorded onceBuilt
ExportCSV or JSON from a secure pageBuilt
Who reads itOrg admins onlyBuilt

Ask us before you decide

  • Ask whose history your auditor or owner needs to see: invoices, bills, payslips or stock.
  • Ask which modules you want logged at all times.
  • Ask who in your company should read the log, and who should export it.

Questions about the audit log in BYTE

What is an audit log?

A record of every action taken in the organisation: who did it, what it touched, when, and from which device. In BYTE it is kept for each organisation, and only org admins read it.

Can I see the history of one invoice?

Yes. Search the audit page by the record, and you see every action on it, newest first.

Who can read the audit log?

Org admins only, because the log shows what other people did.

Can I switch the log off for one module?

Yes. An org admin switches the log on or off for each module, such as security, settings, accounting, POS or inventory.

Can the log be exported?

Yes. Org admins can export the rows for a chosen period as a CSV or JSON file, from a secure page that checks the admin's device and email first.

Does a voided invoice leave a trace?

Yes. Voiding an invoice or a payment writes its own row while the accounting log is on, and the original row stays as it was.

Be first to try BYTE.

Send us a short note about your business and the modules you care about. We will tell you when early access opens.

Talk to us See all of BYTE