What Is an Audit Log in ERP Systems and Why It Matters

What is an audit log? Learn which ERP events to record, how to investigate them and how to set retention under GDPR for security and compliance.

Table of Contents

An audit log is a chronological record that shows who did what, to which record, when, and with what result. In an ERP system, it helps your team connect a change to the business transaction it affected.

A warehouse count doesn’t match the stock balance. A customer questions an invoice that looks different from the version they received. Before anyone corrects the record, you need to understand what happened, not just what the screen shows now.

What an Audit Log Records and Why It Matters

An audit log is a chronological record that shows who did what, to which record, when, and with what result.

Think of a bank statement. It lists transactions and balances, but it doesn’t usually show which employee approved a correction or which terminal they used. An audit log adds that kind of accountability to system activity.

Enterprise resource planning, or ERP, is the shared system that runs sales, purchasing, stock, production, service, and finance on connected records. When someone changes a business record, an audit entry should preserve enough context for another person to review the action later.

The NIST Guide to Computer Security Log Management identifies security-relevant events such as successful and failed authentication, file access, security-policy changes, account creation or deletion, and privilege assignments. It treats log management as an organization-wide process, not an isolated application feature.

Aa employee handing a receipt to a customer, juxtaposed with a laptop displaying a digital audit log. Explaining the ERP Audit Log

What a useful entry contains

The OWASP Logging Cheat Sheet organizes investigative information around when, where, who, and what. For ERP audit logs, expect these core fields:

  • Timestamp: When the event occurred, with a clear time zone.
  • Authenticated identity: The user or service account associated with the action.
  • Initiating application or command: Where the request originated.
  • Affected record: The invoice, order, stock item, account, or setting involved.
  • Requested action: What the person or process attempted.
  • Outcome: Whether the action succeeded, failed, or was denied.

An ordinary activity history might say that an invoice was updated. A useful audit entry ties that update to an identifiable actor, a specific record, and a reviewable control event.

That distinction matters when a manager checks whether someone approved their own transaction. It also matters when an investigator needs to separate an attempted change from a completed one.

A log records evidence, not intent. An account name doesn’t automatically prove which person operated the account, especially if credentials were shared or compromised. Every entry should still help answer the essential questions: what changed, who was responsible, and when it happened.

ERP Events Every Audit Log Should Capture

ERP events to log and why

Event categoryFields to recordWhy it matters
Logins and failed authenticationUser ID, timestamp, device or address, success or failureReveals possible account misuse and repeated password guessing
Permission and role changesAdministrator, target user, old and new role, timestampHelps identify privilege creep and segregation-of-duties breaches
Invoice creation and correctionsInvoice ID, before and after values, approver, timestampSupports financial accuracy and disputed-invoice reviews
Inventory adjustmentsStock item, quantity change, warehouse, reason code, userExplains stock differences and unexplained losses
Approval decisionsApprover, decision, amount or threshold, timestampShows whether the approval chain was followed
Purchase and sales order changesRecord ID, changed fields, previous values, userLinks changes to downstream stock, cost, and billing effects
Supplier bank details and customer credit limitsRecord ID, old and new value, editor, timestampHelps detect payment fraud and unauthorized credit increases
API and integration activityService identity, endpoint, affected record, resultTracks automated changes made by external systems
Critical configuration changesSetting changed, administrator, old and new value, timestampSupports review of control settings and reporting logic
Access to sensitive personal dataRequester, purpose, record, recipient where applicableSupports GDPR accountability and data-subject inquiries

This is a starting point, not a complete logging specification. Prioritize events that affect security, data integrity, financial accuracy, and business accountability.

Authentication records show access attempts. Permission records show changes in authority. Transaction records show how people or automated processes used that authority.

Financial postings deserve particular attention. Preserve the posting reference, accounting period, actor, result, and any reversal relationship so reviewers can distinguish a correction from a deleted or overwritten history.

Capture the change, not just the latest value

For certain electronic recordkeeping systems under its jurisdiction, the U.S. Securities and Exchange Commission’s 2022 final rule specifies a complete, time-stamped audit trail covering modifications and deletions, action dates and times, actor identities, and information needed to preserve record integrity. This is a scoped regulatory requirement, not a universal ERP duty.

Its underlying properties are useful more broadly: completeness, chronology, attribution, tamper resistance, and retention. For material changes, preserve before-and-after values and the related approval context.

An application programming interface, or API, lets systems exchange requests automatically. An integration can change inventory or financial records without a person opening an ERP screen, so service identities need traceability too.

The guide to ERP system data provides useful context for understanding how shared business records connect. Those relationships help determine which changes deserve an audit entry and which identifiers investigators will need.

Logging every click creates noise without necessarily improving control. The practical test is more demanding: can an investigator establish who changed a supplier’s bank account, when, from which device, and under whose authority?

How Audit Records Reconstruct an Incident

A single log entry shows an event. An ERP audit trail connects the evidence needed to explain a business outcome.

The NIST audit log glossary distinguishes logs from the wider trail investigators assemble across records. In practice, useful reconstruction depends on related transaction identifiers, consistent timestamps, and identifiable users or processes.

Hypothetical example of an unauthorized inventory adjustment

A warehouse supervisor finds fewer units on a shelf than the ERP balance shows. While reviewing the item’s history, the supervisor discovers an earlier adjustment that increased the recorded quantity.

The investigator asks: Was this an approved count correction, a mistake, or an unauthorized entry? The audit record identifies the account that posted it, the warehouse, the timestamp, and the quantity change. The reviewer then checks the reason code, count sheet, and approval.

The account identifier establishes where to investigate, not whom to blame. A shared warehouse login or an automated import may require additional evidence before the team can attribute responsibility to a person.

Hypothetical example of an unexpected invoice modification

A customer disputes an invoice total after receiving the document. The current record alone can’t explain why the customer’s copy differs.

The investigator compares the original and corrected values, the editor, and the change time. They then check whether the correction followed a price approval, a return, or a delivery discrepancy.

The business sequence may begin with a sales order, continue through a warehouse stock movement, and end with a finance posting. A change that appears in finance may therefore originate in an earlier operational decision.

Hypothetical example of a suspicious login

An account signs in from an unfamiliar device outside its usual working pattern. Soon afterward, someone changes its permissions.

The reviewer connects the authentication event to the role change and checks the administrator account that granted access. An unusual device or time is a reason to investigate, not proof of compromise. Approved travel, support work, or a scheduled integration may explain it.

A chart showing how audit records help reconstruct incidents through three stages: event, audit record, and investigation.

Event → Audit Record → Investigation → Corrective Action

Follow the business transaction beyond the screen where someone noticed the problem.

At SIX, we investigate ERP issues by examining the wider business process around the issue, not only the screen where it appeared. That means checking related operational and financial records before concluding that the visible change caused the problem.

The corrective action should match the evidence. A team might reverse an incorrect adjustment, revoke compromised access, retrain a user, or document a legitimate correction. Where financial records must remain intact, use an authorized reversal or correcting transaction rather than erasing the original entry.

Record the conclusion and its supporting evidence. An unresolved gap should remain visible in the case record instead of becoming an unsupported assumption.

How to Filter and Investigate Audit Records

Start by preserving the relevant evidence before anyone edits the affected business record. Use a controlled export or protected case record, retain its context, and note who collected it.

Computer monitor showing an audit log dashboard with user activity data in a modern office workspace.

Narrow the search without losing context

  1. Set the date range. Begin around the suspected event, allowing for shift changes, time zones, and delayed synchronization. Check whether the displayed time describes the action itself or when a collector received it.

  2. Filter by user or service identity. Review the activity associated with the account, including automated processes. Don’t assume a service account identifies the person who initiated the wider workflow.

  3. Select the activity type. Narrow the search to stock adjustments, invoice changes, authentication, or permission updates. Keep failed and denied actions available because they may explain what preceded a successful change.

  4. Find the affected record. Search using the invoice number, order reference, stock item, or other stable identifier. Names and descriptions are less reliable because users may edit them.

  5. Open the transaction history. Read the sequence and inspect available before-and-after values. Distinguish a saved change from a rejected request, canceled operation, or later reversal.

  6. Compare related evidence. Check approvals, assigned permissions, and linked records across departments. Combining business records with security logs can show whether a new-device login preceded a financial change.

  7. Classify the finding and document the response. Decide whether the evidence supports a legitimate action, an operational mistake, unauthorized activity, or an unresolved case. Assign an owner to each corrective action and preserve the reasoning.

A search result isn’t automatically a complete incident timeline. Missing events may reflect a filter, an integration boundary, a collection failure, or an action that wasn’t covered by the logging scope.

Investigators should inspect only the personal data needed for the case. Purpose-limited access keeps a payment investigation from turning into an unnecessary review of unrelated employee or customer information.

Questions to answer before closing the case

  • Authority: Was the account permitted to perform the action at that time?
  • Approval: Did the required person approve the actual change?
  • Timing: Does the timestamp align with a known business event?
  • Impact: Which transactions, balances, documents, or people were affected?
  • Communication: Who needs the finding, and who owns the follow-up?

Close the case when the evidence supports the conclusion and the required actions have owners. If attribution remains uncertain, state that limitation plainly.

How Long to Keep Audit Records Under GDPR

An invoice dispute surfaces eighteen months after the sale. Whether you can answer it depends less on how much you logged than on whether each category in the chain, the order, the stock movement, the payment record, was kept long enough to reconstruct together.

There is no universal audit log retention period. Retention works like an archive room: every shelf gets a label saying what belongs there and when it goes, so the room stays usable instead of filling with unmarked boxes. Set retention by purpose, risk, and the obligations that apply to each category.

For payment-card systems in scope, the PCI DSS logging requirements summary describes the PCI DSS 4.0 industry standard’s minimum of 12 months, with the most recent three months immediately available for analysis. That figure is the floor for one category. The table below shows where each other category takes its schedule.

Audit log retention drivers by category

Log categoryRetention driverWho sets the period
Authentication and security eventsIncident investigation and risk assessmentThe customer’s documented risk review
Financial and invoice audit recordsAccounting and tax recordkeeping rules in the relevant countryNational accounting and tax law
Personal-data access recordsGDPR storage limitation and accountabilityThe documented processing purpose
Permission and configuration changesControl evidence and segregation-of-duties reviewsInternal control policy
API and integration recordsReconciliation of transactions across systemsIntegration agreements and audit requirements
Payment-card in-scope systemsPCI DSS logging requirementsPCI DSS (12-month minimum, three months immediately available)

Keep useful evidence without collecting everything

GDPR pushes against the instinct to keep everything forever. Data minimization means limiting personal data to what the purpose needs. Storage limitation means keeping identifiable personal data no longer than necessary for that purpose, subject to applicable lawful requirements.

More logging is not automatically safer. A category kept longer than its purpose allows creates exposure without adding accountability, and a table full of records nobody can justify is harder to defend than a smaller set with clear reasons.

Accountability requires a defensible explanation of those decisions. The EU legal discussion of personal-data consultation records highlights the importance of recording the operation’s justification, timing, and relevant identities so access can be reviewed. The retention period itself belongs in that explanation.

Avoid copying entire customer profiles, payroll fields, or document contents into an audit entry when an identifier and a protected reference will do. Restrict access to sensitive before-and-after values to the investigators who need them.

The NIST log-management lifecycle guide treats disposal as one stage alongside generation, transmission, storage, and analysis. Deletion belongs in audit log management from the start, scheduled like every other stage.

Retention rule: Keep what you can justify, protect what you keep, and document when it should be removed.

Three situations commonly reshape the schedule. Financial evidence may need to satisfy national accounting and tax rules. A food producer may also need operational evidence for traceability, with obligations set by country and product. An active investigation or dispute can require a legal hold that suspends scheduled deletion for relevant evidence; document the hold’s scope, approval, and release conditions so it stops at the records it covers.

The company determines and meets its legal duties. Software executes them: configurable retention, such as the retention settings in SIX ERP, applies the decisions, and the periods themselves come from legal and tax advisers for each jurisdiction, including rules for access, export, holds, and verified disposal.

Keeping Audit Logs Complete and Tamper Resistant

A log is only as reliable as the path between the original event and the evidence an investigator reads. Collection, forwarding, parsing, transformation, storage, and administrator activity can each introduce gaps or changes.

The CISA logging reference architecture emphasizes preserving provenance and integrity across that path. Provenance means being able to establish where a record originated and how it reached its current form.

Protect the collection path

  • Centralize protected evidence. Send security- and control-relevant events to a separately protected repository so investigators can correlate activity across systems.
  • Authenticate and encrypt transport. Protect event transmission against unauthorized reading and forged submissions.
  • Separate administrative duties. Restrict modification and deletion rights so application administration doesn’t automatically provide unchecked control over its evidence.
  • Synchronize clocks. Align servers, modules, and mobile devices so reviewers can interpret event order, while preserving relevant time-zone information.
  • Maintain append-only or immutable copies. Protect historical evidence against rewriting, with controls appropriate to the threat and system architecture.

These are recommended design practices, not claims about a particular deployment. Their effectiveness depends on configuration, access control, and ongoing verification.

Consider a hypothetical sequence: an administrator changes permissions in an HR-related workflow, someone later edits supplier bank details in finance, and a mobile user approves a payment-related action. Central correlation helps the reviewer determine whether these events belong to one authorized process or require separate investigation.

Ready to Improve your Business with SIX ERP

Test evidence collection as a business control

Generate known events deliberately in a controlled environment. Confirm that expected fields arrive intact, timestamps remain interpretable, and related identifiers survive forwarding and parsing.

Test alerts and search functions as well as storage. A record that exists but can’t be found by invoice reference or service identity may be of little use during an incident.

Assign named owners for collection failures, access reviews, and control testing. During each scheduled review period, reconcile selected high-value transactions against their audit evidence and investigate missing or inconsistent records.

For a broader explanation of how individual records form reviewable evidence, the Doczen guide to audit trails is a useful companion. The practical distinction is between storing events and maintaining an evidence chain someone can examine.

Organizations assessing wider cybersecurity governance can also consult our guide to NIS2 and how ERP supports preparation. Treat logging as part of controlled operations, with documented responsibilities and reviews, rather than a feature enabled once and forgotten.

Review Your Audit Log Scope Before Go-Live

Settle these decisions before users depend on the system:

  • Material events: Identify the actions that need accountable records.
  • Personal data: Decide which fields need to appear in logs.
  • Access and export: Name who may investigate, administer, and share evidence.
  • Retention: Approve category-specific rules with jurisdiction-specific legal and tax advice.
  • Testing: Define how the team will prove that required events are recorded.

SIX ERP includes role-based permissions, controlled access, audit trails, secure document handling, and configurable retention. These functions support records management and GDPR principles, but they don’t guarantee legal compliance.

Its connected business records let teams follow transactions across FinanceFlow for financial processes, StockFlow for warehouse activity, PurchaseFlow for procurement, and ManufacturingFlow for production. The investigation scope should reflect the Flows and workflows the company uses, not an assumed standard setup.

Give business users ownership

Assign a business owner who understands both the transaction and its approval rules. Our guide to the power user role explains a useful point of coordination between operational teams and technical support.

When reporting an issue to SIX, include what you were trying to do, what happened, which users or processes are affected, and the steps that reliably reproduce the problem. Include relevant record identifiers and timing without sending unnecessary personal data or credentials.

Reference documents for your control review

The linked documents throughout this article provide the supporting reading:

  • NIST: Special Publication 800-92, Guide to Computer Security Log Management.
  • SEC: Final rule on electronic recordkeeping systems.
  • CISA: Logging reference architecture.
  • EU privacy framework: GDPR storage limitation and accountability principles, alongside the linked discussion of access records.
  • Payment-card security: PCI DSS logging requirements summary.

A useful go-live review ends with agreed scope, accountable owners, and test evidence. It shouldn’t end with an unchecked assumption that every important action is already covered.


SIX ERP connects operational and financial records with audit trails and configurable retention to support accountable business processes. Visit SIX ERP to review your event list with a SIX expert and map your audit requirements to the transactions, approvals, and handoffs your team needs to trace.

Frequently Asked Questions

Frequently Asked Questions about ERP Audit Logs, Security, and Compliance

  • An ERP audit log is a chronological record of activities performed within business software. It records who performed an action, what information was affected, when the event occurred, and whether it succeeded. Audit logs help businesses investigate changes to financial transactions, inventory, purchasing, customer records, and user permissions.

  • An audit log records individual system events, while an audit trail connects related records to reconstruct the history of a business transaction. For example, an audit log may show an invoice modification, while an audit trail helps explain how the related sales order, delivery, approval, and financial posting contributed to that change. In practice, the terms are often used interchangeably.

  • Yes, provided the ERP has appropriate audit logging enabled. It can record the user associated with an invoice modification, the time of the change, and the affected information. More detailed systems may also preserve previous values, new values, and approval references. These records help finance teams investigate invoice disputes, unauthorized adjustments, and accounting discrepancies.

  • ERP audit logs should prioritize activities affecting security, financial accuracy, and business operations. Important examples include login attempts, permission changes, invoice modifications, inventory adjustments, purchase order approvals, supplier bank account changes, and critical system configuration updates. Automated transactions performed through APIs or integrations should also be traceable.

  • ERP audit logs help detect and investigate suspicious activities by recording changes to sensitive information and financial transactions. For example, a change to supplier bank details or an unusual credit-limit increase can be reviewed against the responsible account and approval history. Audit logs do not prevent fraud by themselves, but they support monitoring, accountability, and internal controls.

  • GDPR does not impose one universal audit-logging requirement for every ERP transaction. However, organizations must implement appropriate security measures and demonstrate accountability for personal data processing. Audit logs can help document access to sensitive information, investigate security incidents, and review user activity. Logging must also respect GDPR principles, including data minimization, purpose limitation, and storage limitation.

  • The ability to modify audit records depends on the system’s security architecture and access permissions. Reliable audit logging should protect historical entries against unauthorized modification or deletion. Recommended controls include restricted administrative access, separately protected log storage, and tamper-resistant records. These safeguards help preserve evidence during investigations.

  • ERP audit logs support financial audits by documenting changes to invoices, approvals, accounting entries, and other important transactions. Auditors can use these records to examine whether business procedures and access controls were followed. Audit logs also help organizations investigate discrepancies and demonstrate the operation of internal controls. Their presence alone does not guarantee regulatory compliance.

  • Audit logging creates historical records that can be reviewed after an event. Activity monitoring analyzes current or recently collected events to identify unusual behavior, operational problems, or security risks. Both are useful: monitoring can alert administrators to suspicious activity, while audit logs provide the evidence needed to investigate what happened.

  • ERP audit logs can help warehouse managers identify when stock quantities were changed, which account performed the adjustment, and which inventory records were affected. Investigators can compare those changes with stock counts, warehouse movements, purchase receipts, and approvals. This helps determine whether a discrepancy resulted from an operational mistake, an authorized correction, or potentially unauthorized activity.

  • There is no single retention period that applies to every ERP audit log. Retention depends on the information recorded, the purpose of logging, applicable accounting and tax requirements, and security risks. Financial audit records may require different retention periods from authentication logs or personal-data access records. Organizations should establish documented retention policies and review them regularly.

  • SIX ERP connects operational and financial information across modules such as FinanceFlow, StockFlow, PurchaseFlow, and ManufacturingFlow. Its audit trails and access controls support accountability for business transactions and system activity. By linking relevant records across departments, companies can investigate changes in the context of the wider business process rather than examining individual transactions in isolation.

Read the SIX Business Brief

See how connected ERP workflows improve manufacturing, field service and sales, with measurable results from everyday operations.

Tags

Turn new ideas into better business flows

Every business works differently. Talk with a SIX expert about your goals, processes, and where connected workflows could make a difference. Together, we’ll explore a practical next step for your company.

Learn more about the SIX Business Management solutions

SIX brings every part of your business into one connected environment. Explore our solutions for customer management, sales, service, manufacturing, inventory, purchasing, people, finance, and intelligent automation. Start with the processes you need today and add new capabilities as your business grows, without creating disconnected systems or duplicate data.

AIFlow Logo
Optimize your business with automated AI Flows
Field Service Management Flows end-to-end
Manufacturing Processes
Production from order to ex-factory
Offer to Invoice and Fulfillment
Modern Customer and Lead Management
Warehouse and Inventory Management
Compliant Human Resource Management
Financial Management and Reporting
Purchasing, Procurement and Supplier Management
Professional Procurement from PO to PR

Explore related content

ERP Adoption in Bulgaria.

ERP in Bulgaria 2027: The Digital Divide Is Becoming a Business Risk

Bulgaria’s ERP adoption reached just 26.6% in 2025, far below the EU average. Discover why this digital gap matters and how connected business processes, automation, and SIX ERP can help companies become more competitive in 2027.

Read More >
B2B ERP for SMEs

B2B ERP: Connecting Sales, Stock, Purchasing and Finance

A practical guide to B2B ERP for Bulgarian SMEs, manufacturers and service firms: what it covers, how to choose it, and how to implement it in phases.

Read More >

HR Software for Manufacturing Companies: A 2026 Guide

Discover why HR software for manufacturing companies must go beyond employee records and attendance. Learn how SIX PeopleFlow connects workforce availability, skills, certifications, shift scheduling, and production planning to prevent delays, improve labor efficiency, and ensure the right qualified people are available for every job.

Read More >