QuickBooks Online Audit Log: Find Who Changed What and When
The QuickBooks Online audit log shows who changed a transaction, when they did it, and what moved. Here is how to use it when the books look wrong.
Plenty of QuickBooks Online features demand attention every day. The audit log is not one of them. It sits quietly until a number in your books suddenly looks different, and then it becomes the most useful page you can open.
What does the audit log record?
The log keeps a running list of activity in your QuickBooks Online data. Each entry shows the user, the date and time, and a short note about what changed. Typical entries cover edited transactions, deleted transactions, and voided payments. For many changes, you can open the entry and compare the values before and after.
Where do you find the audit log?
The log is built into QuickBooks Online, so there is nothing to install or switch on. Open the gear menu and choose Audit log. You can then narrow the list by user, by date, or by the kind of event. The filters matter, because an active company can generate a lot of history in a short stretch.
How does it help when the books look wrong?
Say an invoice total no longer matches the copy you sent, or a payment seems to have vanished. Filter the log to the date range, scan for the transaction, and read the entry. You learn who made the change, when it happened, and what the figures were before. Where several people work in the same books, that turns a mystery into a short investigation. In our experience, most “who changed this” questions end right here.
Does the audit log undo anything?
No. The log is a record, not a repair tool. It will tell you that a transaction was changed or deleted, but it will not restore anything on its own. Once you know what moved, the correction is still manual work. The log saves you the hunting; the fixing stays with you.
Can you trust the user column?
Mostly, with one caveat. The column shows the sign-in that made the change, not the person behind it. If two people share one profile, the log cannot tell them apart. Where accountability matters, give each team member a separate user profile and keep the credentials private.
A habit worth building
Even when nothing is wrong, an occasional look at the log teaches you what normal activity looks like in your books. You get a feel for who signs in regularly and which transactions get touched often. That makes the odd entry stand out faster later.
The next time a figure surprises you, open the audit log before you change anything. Find the event, read the before and after values, and only then decide the correction. The history is already sitting there, waiting to be read.