QuickBooks audit log tips: trace changes before you correct, with a fictional change-history illustration and the 365 Bookkeeping and BAS logo.

3 QuickBooks Audit Log Tips to Trace Changes

QUICKBOOKS AUDIT LOG TIPS · AUSTRALIA

Trace a change, compare the details and check the event source before correcting your books.

The QuickBooks audit log helps you investigate who changed a record and when. These three tips give Australian business owners a practical review sequence. First, narrow the event list. Next, compare the transaction versions. Finally, check whether an automatic process explains a system-user entry.

This guide covers QuickBooks Online, not QuickBooks Desktop. Intuit’s Australian guidance lists Simple Start, Essentials and Plus. You need an active subscription and admin access for the audit log. Also, transaction audit history requires full access rights. If a control is missing, ask your primary admin to check your access.

A change trail supports your records; it does not establish whether a change was authorised. Our ongoing bookkeeping support can help organise the underlying review process.

1. Filter the QuickBooks audit log before investigating

Start with a specific question, such as when an invoice amount changed. Otherwise, a long list of unrelated events can hide the entry you need. The log records account activity as well as financial transactions.

  1. Open Settings ⚙ → Audit log.
  2. Use the User, Date Changed and Events dropdowns to narrow the results.
  3. Locate the relevant event. The results show 150 records at a time, so review the applicable results rather than assuming the first screen contains everything.

Intuit says recorded events are available for two years. Therefore, keep your own supporting records rather than treating this screen as a permanent document archive. For example, an approval email can explain why an edit happened even when the log only records the edit itself.

Fictional example: A studio spots a changed invoice on Wednesday. The owner starts with that week’s changes and the relevant event type, then checks who made the edit. They record the invoice number and their question before asking the team.

For the wider document trail, see how one invoice moves through bookkeeping. Source: Intuit’s Australian audit-log guide.

2. Compare versions in QuickBooks audit history

Once you find the right event, examine the details before making another edit. A change to a date, amount or linked payment can have different consequences. In particular, avoid creating a second transaction simply because the current record looks unfamiliar.

  1. Where available, select View in the log’s History column. Intuit notes that this option appears only for certain transactions.
  2. Alternatively, open the transaction, choose More actions or More, then select Audit history. The control name depends on the transaction type.
  3. For a side-by-side view, choose Compare Versions from View Mode. Use Show Timeline to return to the expanded view.

The history shows who made a change, when it happened and what changed. Next, compare those details with the original document and approval. Then agree on any correction with the person responsible for the records.

Fictional example: An invoice moves from $480 to $450. The difference is $30. The owner checks the versions and finds an approved discount, so no extra invoice is needed. However, an unexplained difference stays on the query list until reviewed.

Our QuickBooks duplicate-transaction checks explain a separate prevention routine. Source: Intuit’s transaction audit-history instructions.

3. Interpret QuickBooks audit log system users

An unfamiliar user label does not always identify a new person. QuickBooks creates profiles for some automatic and support activity. Therefore, read the event and related records before drawing a conclusion.

  1. Online Banking Administration indicates an automatic change related to connected bank accounts.
  2. Support Representative identifies changes made by a QuickBooks Online support consultant.
  3. System Administration can record automatic activity, including app changes, recurring transactions or effects on related records.

For example, Intuit explains that moving a payment to a different invoice can create a system event on the original invoice. Also, data sent by a connected app can appear under System Administration. Check the surrounding activity and the relevant process owner before deciding what happened.

Fictional example: A recurring expense appears while the owner is offline. The reviewer checks the recurring setup and the event details before treating it as an unexplained manual entry. If the cause remains unclear, they pause the correction and ask for help.

A logged change is not a substitute for approval. In particular, follow separate supplier bank-detail verification checks before paying changed bank details. Source: Intuit’s explanation of audit-log user profiles.

Use this sequence within your month-end bookkeeping checklist: identify the event, compare the evidence and resolve the question before changing the record. For help maintaining a clear process, review our bookkeeping packages and pricing.

Reviewed 21 October 2026 against current Australian Intuit documentation. Examples are fictional. Procedures were checked against documentation, not tested in a customer’s QuickBooks file. General information only, not financial, taxation or legal advice.

If you need 365 Bookkeeping and BAS to assist you with bookkeeping, we’re here to help.