Audit ERP Function Calling Idempotency Checklist

Role: Senior Financial Systems Automation Specialist in public accounting and audit advisory.

Context

• Audit Practice: {{audit_firm}}
• Financial ERP System: {{target_erp_system}}
• Authorized Write Operations: {{write_permission_scope}}
• API Rate Limit: {{rate_limit_threshold}}
• Idempotency Key Standard: {{idempotency_key_format}}
• Support Escalation Route: {{human_escalation_channel}}

Task

Develop an audit-grade function calling verification checklist to validate that ledger mutation tools, journal entry lookups, and account reconciliation calls executed by an autonomous audit agent are deterministic, perfectly idempotent, and strictly compliant with accounting controls.

Method

1. Map out all function schemas in {{write_permission_scope}} against {{target_erp_system}} transaction validation rules.
2. Confirm that every mutation function call requires a deterministic UUID formatted according to {{idempotency_key_format}}.
3. Validate that client-side function retry logic respects {{rate_limit_threshold}} using exponential backoff with jitter.
4. Verify that double-entry balance constraints (Debits = Credits) are verified locally before sending tool arguments to the API.
5. Audit system logging to verify full traceability: prompt hash, tool name, parsed arguments, API response code, and execution time.
6. Test boundary failure behavior to confirm immediate notification to {{human_escalation_channel}} upon encountering unmapped accounts.
7. Check authorization tokens to ensure read/write separation complies with {{audit_firm}} segregation of duties policies.

Constraints

• MUST require explicit validation of {{idempotency_key_format}} on 100% of state-changing tool calls.
• MUST NOT allow any function invocation that lacks a reversible transaction log or audit trail.
• All checklist items MUST specify the testing technique (Unit Test, Integration Test, Security Review).
• Language must strictly adhere to professional accounting audit standards.

Output format

Structure the response in three clear parts:

1. Audit Control Context (brief 2-3 sentence overview covering {{target_erp_system}} integration boundaries).
2. Tool Execution Safety Checklist (12-16 item checklist with columns/tags for Phase, Check Item, and Verification Method).
3. Risk & Escalation Matrix (table with Trigger Event, Automatic Action, Escalation Target).

Self-review

• Ensure {{idempotency_key_format}} and {{rate_limit_threshold}} have dedicated checks.
• Verify no write actions can exceed {{write_permission_scope}}.
• Confirm formatting uses strict markdown checklist syntax.