Skip to main content

Audit Log

The Audit Log shows who changed what across your books, and what happened to every email you sent. Use it to answer questions after the fact: who edited an amount, when a setting changed, or whether a client received their invoice.

Learn about the Audit Log · 1:47

Read the transcript
Okay, today we're going to cover the Audit Log. So the Audit Log lives in the bottom left menu with your avatar and Audit Log has its own screen. This page shows you all of the transactions that have been changed in your accounting transactions or your company settings. There's also payments and payment gateways and payment instructions that are audited. So here you can see if we have a look at a single transaction, this transaction was changed. If we open it up, we can see that there were five changes to this transaction and each one will display exactly what was changed. You can also expand it further to see all the fields of that transaction. So we don't only record the accounting transactions, we also have email delivery audits. So this is very useful for investigating why an email hasn't reached its recipient or why you're not receiving emails. But if you expand the bounces, it will tell you exactly why. So this address doesn't exist and it will not be retried. Some bounces are permanently quarantined and if the issue has been resolved, you'll need to reach out to support and we can request the quarantine to be lifted. So then the Audit Log, you can also see on the accounting transactions. So this is an audit of what happened to that exact transaction. So if we go to the same transaction that we looked at earlier in the Audit Log, at this time we will see it on the accounting transaction screen. So we can see when it was created, who edited it and what was changed on this transaction right within the transaction. So very useful. So that covers the Audit Log.

Before You Begin​

You need the audit.read permission to open the Audit Log. Owners and Admins have it, as do the Accountant, Bookkeeper, and Read-only roles.

The Audit Log is deliberately readable by read-only roles. An accountant reviewing your books can check history without being able to change anything.

Opening the Audit Log​

  1. Select your avatar in the bottom-left corner
  2. Select Audit Log

The screen opens on the Changes tab. A second tab, Email delivery, covers outgoing email.

What Fiskl Records​

Change tracking captures edits to the records that affect your accounts and your money:

  • Transactions — accounting transactions and journal entries, including the references that tie them to source documents
  • Clients and Vendors
  • Company settings — including the locked period, base currency, fiscal year end, and tax defaults
  • Payment instructions — the bank details shown to clients on invoices
  • Payments — amounts, dates, and status recorded against invoices
  • Documents and folders — uploads, renames, moves, deletions, and the malware scan result for each file

Every entry records who made the change and when. It also records whether a person made the change, or an automated process such as a bank feed, a payment provider, or a scheduled journal.

info

Change tracking captures edits from the moment it went live. Records last saved before then have no history — this is stated on screen rather than shown as "never edited", which would be misleading.

Reviewing Changes​

The Changes tab lists changes newest first. Each entry shows the person or process responsible, the record affected, and what happened — Created, Edited, or Deleted.

Select any row to expand its full history in place. The history shows each change to that record over time. Expand a single change to see the fields that changed, with their before and after values.

A change shows the fields a person would recognise. Derived and internal values are counted rather than listed, shown as N further fields hidden. Select Show all fields to see every value recorded at that point, including the raw detail supplied by a bank feed or payment provider. Nothing is dropped silently.

Changes saved together are grouped, labelled Grouped because they were saved together. This grouping is based on records sharing a save timestamp, so it reflects one save rather than a formally recorded batch.

info

Ledger account and tax names shown in history are their current names. Amounts, dates, and text are exactly as recorded at the time. Renaming a ledger account changes how older history reads.

Filtering Changes​

Four filters narrow the list:

  • Date changed — the period you want to review
  • Record type — transactions, clients, vendors, company settings, payment instructions, payments, documents, or folders
  • What happened — created, edited, or deleted
  • Changed by — a specific teammate, or System for automated changes

Each filter shows how many changes match. If your filters return nothing, Fiskl states how many changes exist in total, so an over-narrow filter is never mistaken for an empty log.

Restoring a Deleted Document​

Deleting a document in Documents archives it rather than destroying it. Its entry in the Audit Log carries a Restore button, which brings the file back to your library.

Restore is available while the document is still archived, which is 90 days from the deletion. After that Fiskl deletes the file permanently and the button disappears, though the record of the deletion remains.

Two limits apply. You need the document.delete permission, on the principle that whoever can remove a file can bring it back. And restore covers documents only — a deleted folder cannot be restored, so recreate it and move the restored files into it.

A quarantined document is recorded as a system action, not as a change by the person who uploaded it. The entry names the threat that was found. See Document Security and Scanning.

Checking Email Delivery​

The Email delivery tab shows every email Fiskl sent on your behalf, including invoices and quotes.

Each row shows when it was sent, the type of email, the recipients, and the outcome. Statuses include Delivered, Sent, Queued, Bounced, Marked as spam, Rejected, and Error.

When an email bounces or is marked as spam, Fiskl explains the reason in plain language rather than showing the raw provider response. This tells you whether the address is wrong, the mailbox is full, or the recipient's mail server refused the message.

tip

If a client says they never received an invoice, check this tab before resending. A Bounced status usually means the email address needs correcting on the client record.

Reviewing a Single Record​

You do not need the Audit Log to check one transaction. Open the transaction and select View history in the dialog to see its full change history in place.

The Audit Log is the better route for reviewing activity across your whole account. It also holds the history of records that have since been deleted.

Common Issues​

I cannot see the Audit Log in my menu

The Audit Log requires the audit.read permission. Owners, Admins, Accountants, Bookkeepers, and Read-only roles have it by default. If your role should include it, ask an Owner or Admin to check your permissions. See Permissions Reference.

A record shows no history

Change tracking captures edits from the point it went live. A record last saved before then has nothing recorded, which Fiskl states directly rather than claiming the record was never edited. Any change from now on appears in the log.

A change is listed as made by "System"

Not every change comes from a person. Bank feeds, payment providers, scheduled journals, receipt scanning, and automated categorisation all write to your books. These are recorded as System changes, and the log names the process responsible where it can.

A transaction was deleted and I need to know where it came from

Deleting a transaction removes it and its source details from your books, but not from the audit log. The last recorded state before the deletion is kept, including the references that identify where the transaction originated. That covers the payment or invoice reference, and the raw detail supplied by the bank feed or payment provider. Open the deleted record's history from the Audit Log and select Show all fields.

I deleted a document by mistake

Open the Audit Log, filter Record type to documents, and find the deletion. Select Restore on that entry to return the file to your library. This works for 90 days after the deletion, and needs the document.delete permission.

If the folder the document was in has also been deleted, the file returns to the top level of your library.

The history shows a ledger account name I no longer use

Names shown in history are resolved when you view the page, so they reflect current names. Amounts, dates, and text are stored exactly as recorded at the time. If a ledger account has been renamed, older history shows the new name.