What an AI audit trail should record
The record to expect, and how to test it.
The short answer
Enough to rebuild any action from the record alone.
Why is ERP audit not enough?
ERP audit records what changed and who changed it. An AI audit trail must also record why: the request in the person’s words, each step taken and what it returned.
When does the difference show?
When something goes wrong. “The work order has the wrong site” is answerable from ERP audit. “Why did it choose that site?” is answerable only if the steps and their results were kept.
What happens when the reason is not recorded?
Without the steps and their results, a correct looking record in IBM Maximo, IFS or SAP has no explanation behind it, and a wrong one has no trail back to the request that caused it.
What do audit trails often leave out?
Three items a full record of each turn must hold.
Step inputs
A step’s name alone tells you a create was tried, not what it was about to write.
Failed attempts
A permission refusal is evidence the control worked. It belongs in the record.
The model
When behaviour changes between two dates, the first question is whether the model did.
Does the ERP record it too?
It should. Called as the person who asked, the ERP records the change against that person. With a shared integration account, every AI change carries one anonymous name.
What does that look like later?
A compliance question arrives about a batch of adjustments, and every one is attributed to SVC_AI_INTEGRATION. The conversation log may explain it, but your ERP audit no longer stands on its own.
How does NgageChat handle it?
NgageChat runs every request under the signed-in person’s own ERP permissions, never a shared service account, so the ERP’s own history names the person. The record it keeps for each turn is set out in the guide to AI that acts.
What should you test first?
Rebuild one write from the audit data alone.
-
Write by asking
Create and update a record.
-
Query the store
Pull that conversation from the store.
-
Check every step
Every step, not just the reply.
-
Check the ERP side
The ERP names who asked.
More questions from ERP teams
How long is the audit data kept?
That is a deployment decision. If you run NgageChat in your own cloud, retention is yours to set under your own policy.
Can we export it to our SIEM or archive?
Yes. The records sit in a queryable store, so they can be exported or streamed. Bring your retention and tooling needs to the design conversation.
Are failed attempts logged too?
Yes, and they are often the more useful half, including permission refusals, which show the security model working.
Does this apply to IBM Maximo and SAP too?
Yes. Every request NgageChat runs, in IBM Maximo, IFS or SAP, is written to the same audit trail: who asked, what was planned, what ran and what came back.
See NgageChat answer a question from your ERP
Send us a task you have not prepared for. We run it with you, live, on a test system.