# AI Agent Action Audit Log Worksheet for ERP Changes > Source: https://netray.co/tools/agent-action-audit-log-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Record agent actions, the tool called, the ERP record affected and the approver, with a computed latency and exception count. ## Category compliance-legal ## Audience - Internal auditor - ERP administrator - IT security ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Date **Key:** date **Type:** date #### Requesting user **Key:** user **Type:** text #### Tool called **Key:** tool **Type:** text #### ERP record **Key:** record **Type:** text #### Action **Key:** action **Type:** select **Options:** - Read - Draft create - Update - Rejected - Error #### Approver **Key:** approver **Type:** text #### Minutes to approve **Key:** asked **Type:** number #### Outcome **Key:** outcome **Type:** select **Options:** - Applied - Declined - No change - Failed #### Note **Key:** note **Type:** text **Rows:** **Date:** 2026-10-14 **User:** m.chen **Tool:** get_open_purchase_orders **Record:** Vendor 1042 **Action:** Read **Approver:** n/a **Asked:** 0 **Outcome:** No change **Note:** Late order query **Date:** 2026-10-14 **User:** m.chen **Tool:** update_promise_date **Record:** PO 100482 line 3 **Action:** Update **Approver:** s.okafor **Asked:** 12 **Outcome:** Applied **Note:** Vendor confirmed new date **Date:** 2026-10-15 **User:** p.nair **Tool:** update_promise_date **Record:** PO 100611 line 1 **Action:** Update **Approver:** s.okafor **Asked:** 45 **Outcome:** Declined **Note:** Date conflicts with production plan **Date:** 2026-10-16 **User:** p.nair **Tool:** create_draft_requisition **Record:** REQ draft **Action:** Error **Approver:** n/a **Asked:** 0 **Outcome:** Failed **Note:** Item not found **Totals:** #### Total approval minutes **Key:** asked **Agg:** sum **Format:** minutes #### Longest approval wait **Key:** asked **Agg:** max **Format:** minutes #### Entries **Key:** tool **Agg:** count **Format:** integer **Summary:** #### Average minutes per entry **Key:** avg_wait **Expr:** sum_asked / count **Format:** decimal **Notes:** Your real audit trail should be written automatically by the MCP server or gateway. Use this sheet to define the fields, run a pilot by hand, or reconcile exceptions during review. ## Content **Intro:** If an AI agent can change ERP data, someone will eventually ask who asked for it, what ran and who said yes. This worksheet defines the audit fields and lets you keep a manual log during a pilot or review. **Sections:** #### How to use the log **Body:** Add one row per tool call that matters: every write, every rejected request and every error, plus reads that touched sensitive data. Record the requesting user, the tool and the ERP record. For writes that need human approval, capture the approver and the minutes until they decided. The outcome column separates applied changes from declined and failed ones. Export to Excel for audit evidence and review the exceptions weekly during the first months of a pilot. #### Fields every agent audit trail needs **Body:** Beyond what this sheet shows, a production log should hold a unique request ID, the model and prompt version, the exact tool arguments, the generated query and the ERP response status. Store the identity of the person behind the request, not just the service account, otherwise you cannot answer who asked. Keep the log append-only and out of the agent's own write reach. **Bullets:** - Request ID that ties prompt, tool call and ERP transaction together - Requesting user and approver identities - Tool arguments before and after validation - Model and prompt version - Before and after values for every update #### Reading the example **Body:** The sample shows one approved date change after twelve minutes, one declined after forty-five and one failed requisition. The declined entry is the valuable one: it shows the approval step caught a conflict with the production plan. Average approval time also tells you whether the human gate is workable or becoming a bottleneck that users will route around. #### Common mistakes **Body:** Logging only successful actions hides the failures auditors care about. Logging only the service account hides the user. Letting the agent itself write its own audit entries is weak because a faulty agent can also write a faulty log. Check retention against your regulatory needs and keep personal data in the log to the minimum. **Cta:** Netray's ERP agents log the question, the generated query and approvals so changes are traceable. If you are designing the audit trail for your own build, we can review the fields. **Faq:** #### Which agent actions must be logged? **Answer:** At minimum every write, every refusal, every error and every read of sensitive data. Many teams log all tool calls because storage is cheap and the log is the only way to reconstruct what happened. #### Should the log be inside the ERP? **Answer:** Use the ERP's own audit where available, but also keep an independent log at the MCP server or gateway. It captures the prompt and tool arguments, which the ERP does not see. #### How long should we retain agent logs? **Answer:** Follow your records retention policy and any regulation that applies to the underlying transactions. Financial changes often need years, while debug detail can be kept shorter. #### Does this sheet replace automatic logging? **Answer:** No. It defines the fields and supports pilots and reviews. Production logging should be automatic and tamper resistant. ## Search terms ai agent audit log template, agent activity log excel, ai change log erp, llm tool call log spreadsheet, ai audit trail template, agent action register, human in the loop approval log --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json