IT systems · Practical guide

Validating Microsoft Dynamics 365 Business Central: what to test for GxP

Which batch may be used? Who may change its data? What can still be traced after an update? For Microsoft Dynamics 365 Business Central, the answers depend on your actual processes. System owners, IT and QA can use the checks on item tracking, access, extensions and data transfers to decide which evidence is needed for their installation.

Table of contents

At a glance

How do you validate Business Central for GxP use?

Use defined requirements and tests to demonstrate that your configured Business Central system is fit for its intended GxP use. Include the version, deployment model, configuration, extensions, user permissions and interfaces. Microsoft’s documentation describes the product. Your workflow and its risks determine what additional evidence you need.

  • The relevant business process determines the validation scope.
  • Traceability, approval, and change logs serve distinct functions.
  • Partner packages and Marketplace assessments require evaluation for their intended use.
  • App versions, migration, and online updates should be considered in the planning phase.

What use of Business Central is GxP relevant?

Start with the decisions your organization makes based on business-central data. A financial journal entry and the selection of a raw material batch for production have distinct implications. Describe the data, responsible party, and consequences of incorrect processing for each process. Consider jointly used master data as well.

Annex 11 addresses computer-based systems in GMP-regulated activities. This article looks at this reference for medicinal products for human use; other GxP areas need a separate assignment. On 6 October 2026, the EU directory continued to include Annex 11 in the January 2011 revision. Part 11 is classified on the basis of relevant FDA recording requirements and actually used electronic records. A Microsoft product name does not justify this applicability.

Sources: [17] [16] [18] [19]

Define operating mode, functional scope, and system boundaries

Microsoft describes Business Central online in the Microsoft Cloud, as well as on-premises deployments. Additionally, the licensing model and the installed experience influence the feature set. The Premium experience includes, among other things, manufacturing and service management. Microsoft notes that general user support is based on the Premium experience. Therefore, any described function must be verified within the specific system.

Maintain a record of the actually deployed environment: environment, customer, application version, localization, experience, and installed apps. Include warehouse technology, identity management, and integrated systems. For a partner-hosted setup, clarify the specific architecture and operational responsibility. "In the cloud" is insufficient for this purpose.

Example of inventory review prior to test planning
InformationAssessment question
Operating model Business Central online or an actively operated on-premises installation?
Functionality Which experience, licenses, and applications support the intended workflow?
System status Which versions and configurations are in test and production?
Responsibility Who provides operational, partner, and process documentation?

Sources: [2] [1]

Verify batch release and traceability along booking records

Business Central manages article tracing through assigned article tracing codes. For continuous batch assignment, Microsoft defines "Lot Specific Tracking"; additional settings are available for warehouse activities. Expiry dates also have separate rules. Therefore, verify the configured combination and the actual booking pathway, including scanners or partner apps.

The Item Tracing page tracks booked transactions both forward and backward. Microsoft identifies a key limitation: it displays associated transactions; however, when multiple receipts are received for the same batch, additional transactions may be missing. Find Entries enhances the search by including occurrences of the batch number, including open data sets. Therefore, a single reverse tracing view should not be unverifiedly considered a complete traceability proof.

Test scenarios include goods receipt, partial consumption, transfer, dispatch, and return. Verify quantity and document references across the entire sequence. Recognize duplicate batch numbers for different articles and multiple receipts from the same supplier batch as intentionally pre-defined edge cases.

Sources: [3] [4]

Example: Raw material batch from receipt to use

Assuming a facility manages a raw material batch in Business Central and receives quality decisions from an integrated system, the requirement is: Only usable material may be selected for a defined manufacturing step. Whether the block logic arises from standard configuration, partner app, or interface remains to be determined on a project-specific basis.

Prepare comparable batches with different professional conditions. Perform the same action as intended storage or production user. Set the expected result before the test. Capture system level, user, output data, action and observed result. A different reaction is evaluated; the acceptance criterion is not made appropriate afterwards.

Own test ideas; no assured standard functions
Test caseResult to be verified
Batch available for use The permitted workflow processes the correct batch and quantity.
Blocked batch The defined unauthorized activity is prevented.
Transfer interrupted Absence of status results in the agreed safe treatment.
Withdrawal of a subset The quantity and original batch reference remain traceable.

Verify authorized rights, not just role names

Access is derived from license boundaries and assigned authorizations. The Effective Permissions overview displays which rights are actually in effect and originates from which assignments. Authorization sets can also be restricted to individual customers. Therefore, actual user configurations are considered during evaluation.

Develop a role matrix for critical actions: modify expiry date, set batch status, establish approval, alter logging settings, or export data. Test authorized and unauthorized actions using appropriate test accounts. A successful test as a SUPER user does not address the authorization question for warehouse personnel. Technical interface accounts and partner access require a defined purpose and controlled management.

Sources: [5] [9]

Distinguish Change Log from professional audit trail

The Change Log records direct data modifications to selected tables and fields. It must be properly configured. Microsoft identifies interruptions during version upgrades and the possibility of cleansing entries through retention rules. Therefore, a comprehensive, gap-free history of all GxP activities cannot be inferred.

Consider instead a specific record, for example, the correction of an expiry date. What values, personnel, time, and justification are required? Where are these information elements consolidated, protected, accessed, and reviewed? Examine user-driven changes, interface integrations, and system enhancements separately. A technically present log entry does not address all relevant operational questions.

Annex 11 addresses risk-based changes and deletions relevant to GMP, including justification and regular review. For internal processes, a traceability concept based on required data, captured events, gaps, and controls is recommended. If required information is missing, a evaluated mitigation strategy must be established prior to intended use.

Sources: [6] [17]

Evaluate the approval workflow and electronic signature separately

Microsoft describes approval workflows that lock a dataset until all required approvals for processing are obtained. Termination and delegation are also envisaged. This description demonstrates a workflow but does not constitute full compliance with regulatory signature requirements.

When an electronic signature is required, assess the specific implementation including identity, signature intent, and a permanent linkage to the signed record. Part 11 addresses these aspects in dedicated provisions. For example, evaluate what occurs following an approved order in the event of a relevant change. Is the signed version unambiguously identifiable? Is a re-evaluation necessary and, if so, technically or organizationally safeguarded? Proxy scenarios also fall within this validation scope.

Sources: [7] [18]

Take on expansions and partner packages within own scope

AL-Enhancements may involve changes to tables, pages, and business logic. Business Central distinguishes between various app types, including Marketplace apps and per-tenant extensions. Capture manufacturer, app ID, version, dependencies, and affected processes. A new field in the layout has a different impact compared to modified logic in batch bookings.

Evaluate partner documentation based on the delivered solution: Which requirements and versions were reviewed? Which data and roles were utilized? What deviations remain unresolved? Microsoft's documented Marketplace assessment utilizes, for example, CRONUS demo data. Such a product evaluation does not constitute validation evidence for your specific GxP process.

A partner package may contain actionable evidence. Assign these to your requirements and supplement unproven configurations, integrations, and process scenarios. The term "extension" alone in a technical context does not constitute reliable GAMP classification. Describe the origin, degree of customization, and impact of each component prior to determining its evaluation pathway.

Sources: [8] [10] [9] [17]

Migration: More than just quantities and totals to compare

During the migration from Microsoft Business Central On-Premises to the online version, Microsoft explicitly does not specify the transfer of certain components: among these are users, permissions, most system tables, and record links. Extension data also subject to specific conditions. These limitations must be addressed in the transfer plan; a successful table run does not constitute complete transfer of all required information.

Inventory master data, batches, open activities, histories, and relationships. Define what is retained and what remains accessible in an appropriate archive or legacy environment. Compare not only quantities but also units, date interpretations, relationships, and selected process workflows. Verify re-accessibility to a historical activity.

For initial setups, configuration packages are also under consideration. Microsoft restricts RapidStart configuration packages to this setup and does not recommend importing them into production tenants that are already in active use. The selected tool and its approved usage are therefore part of the planning.

Sources: [11] [12]

Interfaces are followed until professional processing.

Business Central provides REST APIs for integration with other applications; these APIs are enabled by default in online environments. However, the availability of these APIs does not imply that each required integration has been implemented or technically validated. For each connection, describe data objects, direction, identities, mapping, and error handling procedures.

In a laboratory integration scenario, a result status could influence material usage. Review the assignment of items and batch within the example scenario, including unknown identifiers, duplicate messages, and subsequent status corrections. Document the source record, transfer reference, and result in the target system. A successful HTTP call alone is insufficient for this comparison.

Additionally, agree on who is responsible for detecting failed transfers and making decisions. Repeat occurrences must be technically understood. Therefore, changes to the laboratory, middleware, or a partner app must be evaluated in the same context as changes in Business Central.

Sources: [13]

Online updates are supported with a reusable audit trail.

Microsoft defines two major update cycles annually, along with smaller updates. Administrators schedule maintenance within approved timeframes. During major version updates, Marketplace apps are updated; required app updates may also occur during smaller environment updates. Per-tenant extensions are planned separately in coordination with the responsible developer. Therefore, a once-reviewed app list does not remain automatically unchanged.

Align the announced changes with your critical processes. Prepare an appropriate test environment with a representative configuration. Reusable tests should, for example, cover batch processing, permissions, approvals, and key interfaces. Add targeted tests for specifically affected functions. Document findings, responsible parties, and the decision prior to the production release.

This guide provides the Business Central audit trails. A general procedure for cloud releases should be addressed in a complementary deep dive; it neither replaces the specific Microsoft Calendar nor the coordination with your app providers.

Sources: [14] [15] [10]

Checklist for the Start of Business Central Validation

This planning aid consolidates the previously described evaluation criteria for an initial meeting.

  • Operating mode, version, customer, experience, and installed apps are recorded.
  • Intended use and requirements for the relevant business processes are described.
  • Critical failure modes, acceptance criteria, and appropriate test data have been defined.
  • Roles, change logs, and required authorizations can be verified within the test system.
  • Partner certifications, interfaces, and the scope of a migration are assigned.
  • Action plan and responsible parties for open findings are aligned.

Project experience and collaboration

Trace a transaction across Business Central extensions

With the process owners, IT and, where relevant, the extension partner, we follow a real type of transaction in Business Central. For example, we trace a batch through postings, permissions and connected applications and map existing evidence. A limited configuration may need targeted additions. For numerous extensions or a migration, we first agree system boundaries and responsibilities. We derive tests around actual material and data use and define a workable process for later changes.

Frequent Questions on Business Central Validation

Can Microsoft Dynamics 365 Business Central be used in a GxP environment?

A consideration for implementation arises when your specific environment provides the necessary controls and validation evidence for the intended GxP process. Describe the relevant workflows and compare your requirements against standard functions, configurations, and available enhancements. A product name or partner offering alone is insufficient as proof. Open gaps require a formally evaluated decision prior to using the solution for the intended purpose.

Do we need Business Central Premium for validation?

Validation itself is not a premium feature. The required business processes determine the functionality and licensing scope. Microsoft assigns manufacturing and service management to the premium experience. Work with your partner to identify which standard features and apps are used in your workflow. Selecting an experience does not replace appropriate user licenses or testing of the implemented solution.

Does Microsoft, in Business Central online, assume our validation?

Microsoft operates and maintains the online service. Your organization still requires a clear evaluation of the specific regulated use case. This includes internal requirements, roles, configuration, and integrations. Agree with Microsoft or the contractor and the implementation partner on which evidence is available. Subsequently, define the additional internal assessments and decisions that will be required.

Does the Change Log serve as a GxP Audit Trail?

The Change Log is not a general substitute for all audit trail requirements. It records direct modifications to specific tables and fields and is disabled during version upgrades and can be pruned in accordance with retention rules. Capture the relevant technical information and compare it with the established Change Log and other supporting evidence. Also consider changes introduced by applications or interfaces. Separate specifications are required for retention, protection, and retrievability. Missing protocol information cannot be retrospectively supplemented by simply enabling the Change Log.

Sources: [6]

Is a Business Central approval automatically considered an electronic signature under Part 11?

No. The workflow function alone does not establish compliance with the applicable signature requirements. First, verify whether such a signature is required for the process. Then, assess the complete implementation, including personnel assignment, significance, and linkage to the relevant record. Additionally, the handling of subsequent changes and proxy signing must be clearly defined for the process.

Can we take over our partner's validation package?

Use appropriate validation evidence after evaluating its coverage. Key elements include verified versions, configurations, requirements, roles, and test data. Establish a mapping to your own requirements. Uncovered interfaces, customer-specific workflows, and relevant deviations remain visible. A comprehensive package may be helpful; however, its scope alone does not indicate suitability for your installation.

Is every Business Central Extension automatically GAMP Category 5?

No. Distinguish between widely used product functions, configuration, and custom-developed logic, and assess their impact on the intended process. The technical term "extension" does not determine GAMP classification. Document the justified evaluation of the components within your established approach.

Do we need to revalidate everything after every online update?

Plan a documented impact assessment and the derived testing activities. A unchanged process may require different evidence compared to a modified app with new booking logic. Maintain an appropriate stock of repeatable critical process validations. Include the affected change cases and resolve open findings prior to the production update. The specific dates must fall within the available update window.

Is the complete history retained during a NAV or on-premises migration?

You must not assume this generically. The path of migration, the source version, enhancements, and data volume determine whether adoption is justified. Microsoft explicitly identifies exceptions in the Business Central cloud migration, for example regarding users and permissions. For prior NAV environments, the appropriate upgrade path must additionally be clarified. Define required historical information individually and assess its future readability and traceability.

What documents do we need before testing begins?

Prepare a system overview, intended use, specific requirements, and an assessment of critical failure scenarios. Supplement with a list of application and interface components, roles, appropriate test data, and available partner evidence. Agree on acceptance criteria and responsible parties for test results. This forms a robust workload definition. A fixed duration can only be meaningfully planned once these details and the availability of stakeholders are established.

Sources and review date

The basis for the review includes Microsoft Learn, the EU-GMP Directory, Annex 11, and the specified US sources. Documentation outlines functions and limitations; internal test examples are recommendations. Specifics regarding versioning, licensing, and partner requirements must be verified at the individual system level.

  1. Microsoft Learn: Enable premium features
  2. Microsoft Learn: Deployment of Dynamics 365 Business Central
  3. Microsoft Learn: Set up item tracking with serial, lot, and package numbers
  4. Microsoft Learn: Trace item-tracked items
  5. Microsoft Learn: Assign permissions to users and groups
  6. Microsoft Learn: Audit changes
  7. Microsoft Learn: How to use approval workflows
  8. Microsoft Learn: Extensibility overview
  9. Microsoft Learn: Testing your extension
  10. Microsoft Learn: Managing Apps
  11. Microsoft Learn: Business Central on-premises to online migration: End-to-end overview
  12. Microsoft Learn: Apply Company Configuration Packages
  13. Microsoft Learn: API v2.0 for Business Central
  14. Microsoft Learn: Managing updates in the Business Central admin center
  15. Microsoft Learn: Update cycles
  16. European Commission: EudraLex Volume 4
  17. European Commission: EU GMP Annex 11, January 2011 revision
  18. eCFR: 21 CFR Part 11, Electronic Records; Electronic Signatures
  19. FDA: Part 11, Electronic Records; Electronic Signatures — Scope and Application

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Clarify the specific scope of validation

Bring together system status, app list, and the affected business processes. From this, open evidence and the next action items can be derived.

  • 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 →