What is the purpose of audit trails in ERP systems, and how should they be implemented?

• A. To track changes for accountability and compliance; immutable logs with timestamps, user identifiers, and change details.
• B. To store user credentials in plaintext for fast login.
• C. To summarize financial performance quarterly.
• D. To speed up reporting by caching data.

Answer: (A)

Audit trails in ERP systems are about recording who changed what, when, and why, providing a traceable record for accountability and regulatory compliance. The best approach uses immutable logs that capture precise details for each modification: a timestamp, the user or system identity, the affected data, and the before-and-after values or a clear change description. This tamper-evident, centralized log enables auditors to verify activities, investigate issues, and demonstrate governance over critical data across modules. Implementing this involves writing logs in a secure, append-only or tamper-resistant store, protecting access with strong controls, and retaining records for an appropriate period. It also means integrating logging into data-modification workflows and offering ready-to-use audit reporting and search capabilities, so the information is actionable and auditable. Storing plaintext credentials, summarizing financials, or caching data for speed are unrelated to auditability and focus on security, reporting scope, or performance rather than traceability.