Table of contents
At a glance
What belongs in a Business Central validation project?
Describe the Business Central process, system version, extensions, roles, master data and interfaces. Identify functions that influence quality decisions. Assess existing evidence to define remaining tests, migration, findings and handover work. Microsoft test facilities and partner evidence can help, but their relevance depends on the actual configuration and use.
- A material flow can link multiple applications and responsible partners.
- Extensions and industry modules fall within the scope of definition.
- A sandbox or preview test requires a clear reference point to the target state.
- Ongoing updates require a competent evaluation within operations.
Monitor the movement of goods across system boundaries
For example, begin with material receipt, status determination, and subsequent use of a material. Describe which information is recorded in Business Central and which originates from another system. A status field is only an effective control when its meaning and impact have been clarified within the actual workflow.
State the product type, operating mode, client, and relevant business areas. A general assignment for "the ERP" may otherwise be too broad and incomplete. Commercial functions and GMP-related activities require justified allocation. For human medicinal product manufacturing, Annex 11 provides the system framework; other application areas should be appropriately categorized.
Standard, configuration and extensions differ
Create an inventory of the extensions used and their intended tasks. These include origin, version, responsible and known dependencies. An extension can affect a small technical section or a substantial part of the quality-relevant process. Your name alone does not describe this influence.
Let the implementation partner explain the effective configuration and relevant individual logic. The validation planning translates these details into requirements and appropriate evidence. A technically successful installation does not demonstrate that roles, status transitions, and exception handling are appropriate for the intended use. Similarly, individual component classification under GAMP is not a substitute for assessing their risks.
Who assumes which responsibility in the ERP project?
Define who establishes process rules, is responsible for technical settings, and evaluates evidence. The implementer can provide appropriate technical information and test data. However, the suitability of such data for your requirements must be clearly justified. An external CSV team requires appropriate access to current status and results.
Enter the actual point of contact and decision-makers for the responsibilities in the matrix. The distribution may vary depending on the company; however, an open question requires a clear pathway between ERP partners, CSV advisors, and your internal roles.
| Subject | Contribution of the Implementation Partner | Contribution of the operating company |
|---|---|---|
| Configuration | Explain the actual settings and dependencies | Define technical specifications and acceptance criteria. |
| Extensions | Describe version, function, and impact of changes | Assess relevance to processes and records |
| Interfaces | Mapping, error handling and technical substantiation provide | Clarify scientific significance and acceptance criteria |
| Tests | Appropriate technical documentation and environment support | Ensure intended use and results evaluation. |
| Migration | Document technical pathway and acceptance results | Data assignment, exceptions, and further usage evaluation |
| Operation | Agreed maintenance and change information provides | Define responsibility for evaluation and release approval |
Connect the test environment and actual stand
For your project, it must be established which environment and which version of the system carries the results. Microsoft allows, for Business Central online, the creation of a new Preview Sandbox as well as the upgrade of an existing Sandbox to Preview. A Sandbox copy of production may include the production's data, configuration, and customizations. Ensure that the verified version and appropriate data are maintained; production interfaces must not trigger unintended effects.
A preview environment can assist in preparing for a forthcoming update. However, its results are not automatically sufficient as validation evidence for a later production instance. Evaluate relevant differences and plan appropriate final verification activities. Early preview and subsequent usage decision serve distinct purposes.
Plan data migration and master data as separate deliverables
A technically completed import does not automatically ensure that quality-related data are correctly linked and remain usable. Therefore, identify the required data, their context, and the business rules governing transfer. This may include materials, units, status information, and relationships to other records.
Plan a reconciliation process that aligns with the significance of the data. Dataset volumes may constitute part of this, but do not address all questions regarding accuracy. Deviant or unaccepted values require a transparent and justifiable handling approach. Define clearly who is responsible for data cleansing, mapping, and decisions on exceptions. This work must not be lost during the transition between technical migration and CSV.
Sources: [1]
Planning example: A quality status is entered into the ERP system.
Suppose a laboratory process sends a quality status to an ERP interface. The project team defines the authoritative record and when a status change may affect later goods movements. Test a normal transition and exceptions such as an unmatched message or subsequent correction.
Before testing, describe how the configuration should handle each individual case. If a gap is identified, technical modifications, clearer work instructions, or alternative system boundaries may help. The actual controls provided by Business Central and its extensions will be verified at the implemented site.
Integrate the online updater rhythm into the partner contract.
Microsoft describes two main versions for Business Central online released in April and October, with minor updates issued in the remaining months. The regular update cycle for a main version spans five calendar months, followed by a one-month grace period. Afterward, any extensions that block the update can be automatically uninstalled. Microsoft states that user data is not deleted during this process; however, the affected functionality may still be unavailable. Microsoft also provides critical fixes outside the regular update schedule; these require evaluation of their impact.
Therefore, agree on responsibility for tracking release information and technical compatibility, assessing the impact on GxP processes, and promptly providing required adjustments. A potential workflow includes early compatibility testing during preview, evaluation of the final target state, and appropriate closing tests. For on-premises installations, the actual, agreed-upon update operation must be planned separately.
Define specific results upon request: evaluated affected processes, compatible extensions, appropriate test setup, reviewed findings, and a traceable usage decision. A blanket full test after each update is not required. The existing update guideline deepens ongoing maintenance.
What should be clarified regarding the proposal and handover
An appropriate task defines outcomes for process delineation, assessment of validation evidence, testing, migration, and handover. Include internal involvement and the requirements for an appropriate test environment. Explicitly state whether technical error corrections and repeat testing are included or separately planned.
Conduct a joint walkthrough of a representative process at the conclusion. Your team should be able to explain the key decisions, validation evidence, and remaining tasks. This also includes the next relevant change trigger. A complete project folder is helpful, provided its content remains actually usable by the responsible personnel.
- Define process boundaries and maintain leading records.
- Record extensions with version and responsible parties.
- Link test and target state in a traceable manner.
- Identify migration and professional alignment separately.
- Change protocol for relevant tables and fields to be defined on a risk-based basis and actually verified.
- Review authorized action statements and permitted quality-related status changes.
- Hand over responsibilities for operations and change control.
Project experience and collaboration
Scope a Business Central validation assignment
Start with a flow of goods in Business Central. Where are master data created? Which extension takes part, and which system supplies the status the process relies on? With your ERP partner, we trace the workflow and map the required evidence to it. We assess how far existing tests cover your use. A heavily customised process may first need a more detailed description of its steps and interfaces.
Frequent Questions on Business Central Validation
Is Business Central as a standard product already validated for our GMP use?
For GMP use, the specific application, configuration, extensions, and data pathways will be evaluated. Manufacturer or partner documentation may assist, provided it has been assessed for suitability for this intended use. Crucially, it must be determined whether the existing results actually meet the requirements of your established business process and what additional enhancements may still be required.
Sources: [1]
Can the ERP partner provide all validation documentation?
This depends on the agreed-upon scope and the relevant technical competence. Technical documentation and test results can provide significant support. Clarify which requirements are covered, what actual results are available, and which additional internal inspections remain pending. Internal responsibilities and the evaluation of the intended use must be explicitly defined.
Is a completed test in a preview environment sufficient?
A preview test can provide valuable insights for preparing an update. However, the alignment with the actually deployed version must be evaluated for future use. Relevant differences in version, extensions, data, and configuration must not be overlooked. Additional assessments are required based on this evaluation.
Do we need to assess all commercial processes to the same depth?
The scope is aligned with actual GxP relevance and impact on affected processes and records. An application may include functions of varying relevance. The demarcation must be justified and take into account significant shared dependencies. A one-size-fits-all treatment of all functions is therefore not an appropriate sole approach.
What information does an external CSV service provider need to provide?
Useful are process overviews, product and extension versions, existing specifications, and known data pathways. Add contact persons, test environment, planned migration, and open decisions. This enables the task to be scoped based on results. A general desire for a specific document package is often insufficient as a starting point.
What remains after implementation as an ongoing task?
The operation requires appropriate authority for changes, deviations, and maintenance of documentation. Suitable future reviews and access to required records are also part of this. Agree on these responsibilities prior to handover. The specific implementation depends on your role and the partner's contractual contributions.
Sources: [1]
Sources and review date
Primary source date: 17 October 2026. Microsoft's documentation describes technical testing options, online update operations, and their limitations. The article does not derive a general GxP suitability conclusion from this. The role matrix and interface example serve as planning aids only. Specific product functionalities and enhancements must be verified for the actual version in use. EU GMP statements relate to human medicinal products (EudraLex Volume 4).
- European Commission: EU GMP Annex 11, Computerised Systems, January 2011 revisionHuman medicinal products – GMP; in particular, §§1–4, 7, 10–13, 16–17; specific application for each section.
- ICH Q9(R1): Quality Risk Management, official text from the European CommissionRisk-driven decisions, appropriate formalities, and handling of subjectivity; own matrices are implementation proposals.
- ISPE: GAMP 5, Second Edition – Public Description of the GuidelinePublic publication description; no claimed full-text access to the paid guide.
- European Commission: EU GMP Chapter 7, Outsourced ActivitiesOutsourced GMP-related activities, suitability, responsibilities, agreements, and monitoring.
- Microsoft Learn: Testing the application overview – Business CentralTest options and limitations; Microsoft app validation is not a GxP validation.
- Microsoft Learn: Prepare for major updates with preview environmentsPreviews and sandbox environments differ from those of actually deployed target systems.
- Microsoft: Business Central online update cyclesOnline update periods and potential uninstalls of blocking extensions; treat On-Premises separately.
- European Commission: EU GMP Chapter 2, Personnel, effective from 16.02.2014Personal, role-specific training and assessment of practical effectiveness; official EudraLex entry with original chapter.
Sources checked: .
Define a relevant process jointly.
Provide a process overview together with details on extensions, interfaces, and existing evidence base. From this, it can be determined which tasks are already describable and which information should be obtained first from the operator or implementation partner.
- 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.

