Viewing the Xero audit log
Find the record of every Xero interaction, and know what it shows and what it doesn't.
Every interaction between VanMan and Xero is recorded. To see it, go to Settings > Integrations and click View Audit Log on the Xero card.
It is a button on the Xero card, not a tab. It opens a full page headed Xero Audit Log with an API Interactions table.
What it shows
The table has columns Timestamp, Action, Status, Duration, and Xero Request ID. You can filter by Action (Token Refresh, Invoice Create, Contact Create, Health Check, Connect, Disconnect) and by Status (Success or Failure), and page through with Previous / Next.
What it does not show
Two things the audit log does not give you:
The error message. The table records that an interaction failed, but it does not display why. For the actual error text, go back to the invoice — its inline error panel is where the real message lives.
Every action type. Some sync actions are recorded but missing from the Action filter dropdown, so filtering can hide entries that exist.
In the current build, the audit log page may fail to load and show "Something went wrong." If that happens, it is a known issue, not something you have done wrong — diagnose failed sends from the invoice's own error panel instead. See troubleshooting Xero errors.
What it is good for
When it loads, the audit log answers "did that actually reach Xero?" — you can see the Connect, the invoice creates, and whether each succeeded or failed, with timestamps. For a systemic problem (nothing syncing since Tuesday), it shows you when things stopped. For a single bad invoice, the invoice's error panel is faster.
Tutorial: work out why syncing stopped
Invoices stopped reaching Xero a few days ago and you want to know when and why.
Settings > Integrations → View Audit Log on the Xero card.
If the page errors, skip to the last step — the log is not available in this build and you will diagnose from the invoices instead.
Set the Status filter to Failure. Now you are looking only at what went wrong, in time order.
Scan the timestamps for the point things changed from Success to Failure. A cluster of failures starting on one day usually means the connection lapsed then, or a Xero-side change.
Filter Action to Token Refresh. A failed refresh is the classic cause — the connection expired and could not renew itself.
The log will not spell out the error. It tells you which interactions failed and when — that is the value. For the message itself, open one of the affected invoices and read its error panel.
If it was a token or connection failure, go back to the Xero card, click Check Now, and if it is unhealthy, Disconnect and Connect to Xero again.