IT systems · Practical guide

Can the Business Central change log serve as a GxP audit trail?

A Business Central change log can exist without capturing a particular quality-relevant change. Identify the data and write paths your configuration records, then verify that a reviewer can reconstruct the context later.

Table of contents

At a glance

Does the Business Central change log meet GxP requirements?

Enabling the Business Central change log alone is insufficient. It can support an audit trail where relevant tables and fields, write paths, user attribution, retention and review are configured and demonstrated. Test gaps, administrative changes and behaviour during upgrades. Availability of a product feature does not establish that the configured system meets your GxP needs.

Define the question within the business process

This article examines Dynamics 365 Business Central with a quality-related application. It does not refer to verification of all financial transaction changes. Start with records whose modification could impact product quality, traceability, or a business decision—such as a quality parameter, a batch reference, or a release status in an extension.

Record the edition, version, online or on-premises operation, extensions, and organisation. An extension may include its own tables or formatting rules. Therefore, a protocol record for a standard table does not automatically demonstrate coverage of the customer-specific quality process.

Annex 11 addresses risk-based audit trails and their understandable review. The appropriate implementation arises from actual application. The following matrix serves as an independent work aid. It does not constitute general certification of Business Central.

Sources: [1] [2]

What functions are provided by the standard feature and where you should look for more detailed information

Microsoft provides a change protocol for selected tables, fields, and types of changes. The configuration is therefore part of the validation evidence. A globally enabled switch does not confirm that the relevant quality attribute is included. The manufacturer's documentation also specifies limitations, for example, fields with an auto-increment property.

Change logs, field monitoring, and activity logs are not the same. An import error in the activity log addresses a different question than the history of a critical master data modification. Assign a specific evidence source to each required statement. Avoid the generic term "audit trail" when multiple functions with distinct boundaries are involved.

Microsoft notes the session-dependent nature of the display and the possibility of deactivation during a version upgrade. This information is relevant to test design. A blank protocol screen does not necessarily prove missing data capture; conversely, a documented upgrade window should not obscure potential unexplained changes to critical data.

Sources: [2]

Build a coverage matrix instead of a functionality list

First, create a list of critical business events. Describe each event in the language of the respective department and complete the table, field, and actually used write path. API calls or imports may also be relevant. Whether the required entry is generated is verified within the specific system and cannot be inferred from a surface-level test.

Capture dataset, user, or technical identity, timestamp, and both old and new values. For modifications or deletions of GMP-related data, Annex 11 Section 9 further requires documented justification. Verify that your application or process captures this justification and unambiguously links it to the change. A free-text entry in a separate email is insufficient without this linkage.

Consider also deletion, reinstallation, and modifications to the protocol configuration. The question in each case is: Can an authorized reviewer determine what technically occurred? A technical data set number lacking a retained business context may be insufficient for this purpose.

Own coverage matrix for a quality process
EventTo be reviewed coverageExpected relationship
Change limit value Concrete table and field; Surface and import Before/after, Identity, Time point, Reason, Item reference
Change batch status Standard or extension; all used routes Batch and relevant status sequence
Delete critical data set Incident and retained context Affected records remain identifiable
Change the logging configuration Activation and configuration changes Authority and legitimate justification
Retrieve history Role, Filter, Company, and Storage Complete relevant view for the review

Sources: [1] [2]

Test example: a limit value is set more strictly

Article A-17 has a release-relevant limit of 10.0 mg. A duly authorized master data responsible party changes it to 9.5 mg. A second role is permitted to read this value but not to modify it. A technical interface may update the same table within the agreed process.

First, verify the authorized change through the user interface. Following the session transition as specified in the documentation, search the audit trail entry. Expected elements include the correct document, old and new values, associated identity, and timestamp. Then, confirm that the professionally justified reason for the change is reliably linked. If the reason is missing, identify the gap and evaluate a suitable remedial action.

Repeat the relevant case regarding the actually used interface pathway. The required evidence is not "any entry exists," but rather the same technical and professional context linking the technical identity and the triggering event. Subsequently follows a rejected attempt to modify the read-only role. The absence of an unauthorized change and a documented authorized intervention are distinct audit assertions.

Own test procedure with positive and negative cases
CaseActionAcceptance criterion
Permitted change 10.0 mg to 9.5 mg via named role Dataset and relevant changes traceable
Interface modification Identical field modification across agreed import Traceable authoring pathway and identity
Unauthorised change A read-only role attempts a change Change according to authorization concept prevents
Correction 9.5 mg reduced to 10.0 mg Both events remain distinguishable
Review Reviewer is looking for A-17 through time range filter Relevant events legible and traceable

Sources: [2] [1]

Upgrade and administrative rights as separate validation topics

Plan for a version upgrade and ensure critical data is controlled during the transition. This includes a documented as-is state, evaluated migration or enhancement steps, and a technical reconciliation post-upgrade. The resumption of standard logging following the interruption does not prove which changes occurred during the downtime.

Prior to the upgrade, define the additional evidence required. This may include object-level reconciliations, controlled upgrade protocols, or targeted function tests. The scope shall be determined by the nature of the change. A mere user interface update and a data transformation involving new status rules require distinct evaluation approaches.

Assess who can configure logging, delete entries, or modify retention policies. An administrator may require extensive authorizations. In such cases, controlled distribution, justified usage, and appropriate independent monitoring should be considered. Professional oversight should not solely depend on the same individual whose actions are being evaluated.

Sources: [2] [1]

Storage and review operationally anchored

Determine retention from the records involved and the requirements that apply. A system default does not establish the appropriate period. Check the active policy, its filters and access to older data. The required context must remain understandable after archiving.

The review requires a specific question: Which changes impact a decision, which deviations need clarification, and who is responsible for addressing them? A monthly archived master file without review or validation does not answer these questions. The timing and depth of the review are determined by the process and risk assessment; a universal frequency is not justified in this context.

Document representative evidence of how a reviewer identifies and evaluates relevant changes. This includes effective filters, correct selection of the organisation, and access to the source record. For example, a reviewer must be able to determine whether a limit was changed before or after the considered quality decision.

Sources: [1] [3] [2]

So the suitability decision is understandable.

The outcome may take three forms: the existing configuration meets the requirements to a specified extent; it requires targeted enhancements; or for certain processes, a different technical or procedural solution is necessary. Justify this decision on an event-by-event basis. A general statement such as "standard setup is sufficient" or "ERP cannot handle this" is equally unhelpful.

Summarize open gaps, their impacts, and corrective actions. If a relevant change is not traceable, also assess its implications for already generated records. A future configuration correction does not replace this retrospective review. For unacceptable risks, the use must be restricted or suspended accordingly.

Provide the approved configuration, test cases, review rules, and responsibilities to operations. Add triggers for re-evaluation: expansions, new fields, additional organizations, new interfaces, or changes to storage conditions. This ensures the statement remains verifiable beyond the implementation project.

Sources: [1] [3]

Project experience and collaboration

Find the audit trail for a relevant change

Your process owners choose a known change, such as a revised limit. We look for its traces in the configured Business Central environment. Which field was written, through which route, and what can a reviewer still read? A few missing fields may need a targeted addition and test. Inadequate logging and operating rules may require a wider control plan. We explicitly assign responsibility for administrator access, retention and subsequent review.

Frequent Questions about the Business Central Change Log

Is field monitoring the same as the change log?

No. Microsoft describes separate functions with individual configurations. Field monitoring, for example, can provide alerts for monitored fields. Check which function is actually used in the specific process and which history is retained in practice. The presence of multiple enabled functions does not automatically result in complete GxP coverage.

Sources: [2]

Why might a change take time to appear in the log?

Microsoft indicates that a required restart of the user session is necessary for changes to be displayed. Consider this during test execution. Afterward, verify the correct company, the configured table, the field, and the filters. If the entry remains absent, document the finding and assess the actual coverage.

Sources: [2]

Are API changes automatically adequately documented?

Automated logging has not been generally validated for the required GxP traceability evidence. Verify the configured table and the field corresponding to the actual write path used, for example API, import, or extension; a successful surface test alone is insufficient. The technical identity must be linked to a controlled procedure. Additional evidence may be required for the technical trigger and reason for change.

Sources: [1]

What happens to the change log during an upgrade?

The manufacturer's documentation describes a deactivation during a version upgrade, followed by reactivation. Therefore, evaluate interventions performed during the upgrade window separately and plan appropriate reconciliations. Automatic log restarts do not retrospectively confirm the significance of all data modifications made.

Sources: [2]

Must every table be fully documented?

Determine the scope of critical records and business events. Untargeted full logging can make the review more difficult and have technical implications. However, leaving out relevant fields is also not reasonable. Keep selection and limits in a cover matrix.

Sources: [2] [1]

Can old protocols be deleted for storage space relief?

Only after a justified retention decision and a controlled procedure. Consider the associated records, ongoing investigations, and the requirement for traceability. Test guidelines and authorizations such that relevant history is not inadvertently lost or overwritten.

Sources: [1] [2]

Sources and review date

As of October 14, 2026. Regulatory classification and manufacturer responsibilities are separately documented. Examples, test matrices, and templates are standalone reference tools; they are customized for actual usage purposes.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. Microsoft: Review changes in Business CentralField/table selection, session management, upgrade procedures, and retention policies; reviewed on 14.10.2026.
  3. PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →