Table of contents
At a glance
How do you validate KUMAVISION medtec365?
Identify the intended medical device process, Business Central foundation and KUMAVISION modules in use. Test how approved master data and component batches flow into orders and consumption. Use relevant supplier evidence and add cases for open requirements. The regulatory scope, risks, configuration and data transfers determine the evidence needed. A sector label or a module named “Compliance” does not replace this assessment.
- Business Central, KUMAVISION base and medtec add-ons serve distinct functions.
- The release of a document amendment must be distinguished from its use in a task assignment.
- FEFO selection, batch purity, and quality decision address various questions.
- Medical devices QMS and human medicinal product GMP require separate validity assessment.
Capture Business Central and industry-specific modules together
KUMAVISION medtec365 is a sector-specific solution for medical technology built on Microsoft Dynamics 365 Business Central. The product description alone does not provide sufficient assurance regarding system boundaries. To establish a reliable system boundary, it is necessary to capture platform status, KUMAVISION base, medtec enhancements, additional apps, and the actual implemented integrations. A version list should clearly indicate which combinations have been evaluated and are subsequently deployed.
The support function describes compliance and batch-specific production as additional, license- and activation-required modules. Therefore, the presence of a function name in a presentation does not confirm the availability of the control in your environment. Please have the specific activation, setup, and responsible role demonstrated. Additionally, an additional approval workflow has its own prerequisites.
The article is based on the manufacturer support document available as of 6 October 2026. It does not include a current medtec build. The cancellation support document details the retirement of a cancellation function in BC 2024 Wave 2. For implementation, you will require your partner to provide the appropriate version and compatibility confirmation.
Explicitly state the medical device scope
Start with the product and its intended operational purpose: Which data control manufacturing, testing, labeling, or quality release decisions? What records are required for these functions? Identify the relevant markets and have QA or Regulatory Affairs assign applicable regulatory requirements. The mere use of a medical device ERP system does not fully define this scope.
Within the applicable FDA Medical Device Scope, the Quality Management System Regulation (QMSR) shall apply starting 2 February 2026. It incorporates ISO 13485:2016 by reference. The FDA-CSA Guidance dated 3 February 2026 outlines a risk-based approach for production and QMS software. The FDA also details the integration of the standard therein. For project-specific normative requirements, the relevant normative text must be consulted.
The Guidance does not address software functions of a medical device itself. Similarly, medtec365 is not solely subject to Human Medicinal Product GMP requirements due to its industry. An additional actual medicinal product process requires a separate compliance assessment. The following work aids focus on the ERP in a medical device company and do not constitute a universal Annex 11 compliance checklist.
Align validation evidence to decisions.
A viable requirement defines the technical outcome. "Compliance module activated" refers to a configuration. "An unauthorized change must not yet impact the intended new production order" can be specifically evaluated. Supplement by specifying which data version shall apply and how ongoing orders are to be managed.
Assign a responsible party and existing evidence to each requirement. Microsoft documentation explains the platform; KUMAVISION documentation explains the industry-specific functions. The partner can provide evidence for specific configurations and enhancements. Your organization determines the intended process. This structure aims to make existing evidence usable and to keep outstanding questions visible.
The table serves as an internal reference tool, not a prescribed document format. A shared overview is sufficient, provided the relationships are clearly understood. Avoid rephrasing the same general requirement multiple times. A clear mapping is more effective—specifying which function supports which step and identifying where a faulty transition can be detected.
| Transition | Expected result for this example | Existing and supplementary evidence |
|---|---|---|
| Change to an item | Only the intended approved version will be effective | Module description, established rule, separate change scenario |
| Order creation | The order uses the instruction assigned to it | Order data against released reference status |
| Batch selection | The selected assignment meets the process specification. | Manufacturer process and independent quantity and identity verification |
| Consumption | Recorded components match the specified design. | Commissioning, actual consumption and corrections |
| Change to the system | Open implications will be decided prior to use. | Change description, compatibility assessment, and targeted residual testing |
Copy, approval, and efficacy differ
With version control in place, medtec365 defines a specific workflow: the item remains usable during the change. A copy is updated; release of the associated compliance certificate transfers the data to the original item. This represents a key functional boundary. However, this does not establish how each existing order or individual extension responds to the change.
Select a truly process-relevant field for the own test that supports the version in use. Prepare a request prior to the change and a request following approval. Explicitly define the intended reference. Additionally, assess the actions taken if the change is rejected and whether an unauthorized role could circumvent the intended pathway.
Avoid a general statement such as "all orders will be automatically updated." Depending on technical specifications, such an update may be undesirable. Document the criteria used to evaluate open orders and identify who authorizes adjustments. Changes to bill of materials or work instructions must be assessed using a version-controlled mechanism; a copy of the item record does not serve as valid evidence for all master data objects.
Review the release protocol and substantive history together
The KUMAVISION-base assistance separates the approval workflow from content changes. A change protocol must be established for the display of such modifications. Therefore, a completed compliance record alone does not prove that all required field updates have been documented. Rules, involved tables, and relevant fields must be included in the review.
A validated article with a controlled change may serve as a test case. Compare the initial value, new value, responsible person, and approval reference at the point in the process where such information is required. Subsequently, allow a reader without change responsibility to trace the process. The reader should be able to identify which version corresponds to the considered batch. A general log export does not need to automatically address this question.
Second-person checks and multi-stage approvals are configurable functions. Assess the purpose of each signature even when the workflow is configured correctly. Evaluate Part 11 where the applicable FDA recordkeeping requirements bring the electronic record within scope. A signature field alone cannot establish compliance or demonstrate that every internal workflow step requires an electronic signature.
FEFO, sufficient quantity and separate handling of consumption
The support for batch-wise production distinguishes between searching for the first expiring stocks and a quantity-based search. The latter may select a sufficiently large batch, even if a smaller batch expires earlier. In the absence of total inventory, order splitting or order reduction is envisaged. Which approach is technically appropriate must be determined by your production procedure.
Before testing, describe whether an order may utilize multiple component batches, whether it should be split, and what additional prerequisites apply. An expiry date is only one factor in this decision. Locking, reservations, units, spare materials, and actually available quantities may introduce further evaluation points. This document does not assume the existence of a universal native control.
The documented transition to fixed component batch assignment requires a pre-established and unaltered commissioning record. Therefore, evaluate a manually modified proposal, if your facility permits such action. Compare actual consumption against the intended reference. A correct selection prior to execution is insufficient if a different batch is subsequently incorporated.
Example: 100 units from two available batches
This example is calculated independently. It is not a completed medtec365 test. An order requires the production of 100 units, each requiring exactly one piece of component C-01. Batch A contains 60 pieces and expires on 31 January 2027. Batch B contains 120 pieces and expires on 31 March 2027. On the assumed test date of 6 October 2026, both batches are deemed usable according to their respective quality assessment.
Additional reservations, shortages, unit conversions, and other limiting components are excluded. The internal specification permits exactly one component batch per production order. Consequently, a single order can therefore be fully supplied by batch B. Alternatively, prior to execution, a split into 60 and 40 units is decided. Both approaches consume 100 units; their order- and batch-related allocations differ.
Each table row restarts with A = 60 and B = 120, totaling 180 units. Assignments, quantities, and approval statuses are systematically reset between cases. The matrix defines the intended operational states. How these states are achieved, prevented, or detected upon deviation is part of the actual configuration validation.
| Variant or failure scenario | Independent quantity calculation | Decision and test basis |
|---|---|---|
| An order for 100 units of B | A: 60; B: 120 − 100 = 20; Rest: 80 | Batch B; selection, commissioning, and consumption are consistent |
| Two assignments: 60 from A, 40 from B | A: 0; B: 80; Rest: 80 | Separate orders with an unambiguous component batch for each |
| 60 units from A and 40 units from B in a single order | Usage: 100; Residual: 80 | Quantities match, but the specified single-batch rule is still violated |
| Only 95 units from batch B were consumed, but 100 units were reported back. | A: 60, B: 25, remaining: 85, difference: 5 | Identify and resolve discrepancies; do not confirm as appropriate consumption |
| 100er consumption from B processed twice | Calculated requirement: 200; B has only 120 | Retesting shall not be considered a second authorized consumption; verify error pathway |
Evidence from the actual configuration is measured.
The product page lists validation packages as support. Verify their actual content: which version, modules, settings, and requirements were reviewed? Which source data, results, and deviations are documented? For each accepted validation evidence, justify why it aligns with your intended use. A package may include appropriate standard or customer-specific documentation; its scope cannot be inferred from the name alone.
Add the missing interconnections, for example scanners, labeling, third-party manufacturing, or a leading document management system, if these actually form part of the process. The available sources do not support arbitrary integrations. A dedicated test should verify the professional identity of the order, component, and result across the interface and intentionally expose any errors.
The FDA-CSA Guidance considers appropriate existing activities and supplier information when selecting additional validation evidence. It is not a blanket waiver of testing. For your team, a concise list of remaining questions is helpful: Which assertion is already substantiated, under what conditions does it hold, and what specific uncertainty remains? From this, targeted supplements can be developed instead of an ungrounded full revalidation.
Trace changes through field references to affected records
The decommissioning assistance highlights a typical dependency: a departmental function can be replaced by a Microsoft standard function. It also points to decommissioned table fields that may involve adjustments, reports, or configurations. Therefore, after a relevant change to the system, verify the referenced fields in use; an unchanged screen appearance does not constitute sufficient evidence.
Arrange release notes to your requirements. If a change affects the approval path, consider an open and a completed process. If the batch assignment is affected, use a suitable target case with defined baselines. The scope depends on the effect and existing evidence, not only on the number of new functions.
Additionally, specify how required records shall remain available following restoration or system change. A separate restoration scenario may enable a comparative review of inventory status, approval reference, and associated order. Review the responsibilities defined in the operating contract. The term "cloud" does not imply specific storage or verified restoration of the complete process.
Define tasks and effort requirements prior to project initiation
For a viable launch, you need representatives from QA/QM, Production, Storage, and IT, along with the responsible KUMAVISION partner. Regulatory Affairs should be included for regulatory compliance issues. Management does not need to justify field filters, but decisions, availability of technical personnel, and a clearly defined scope of responsibilities must be ensured.
The effort drivers are concrete: variants of master data sharing, additional modules, interfaces, open old assignments and missing test data. In addition, there is the availability of appropriate supplier receipts and the effort for a controlled reset. Determine these points at a representative process before granting a duration. A general number for all medtec365 projects would not be loadable.
- Document the medical device process, markets, and applicable regulatory areas.
- Document the BC-, base-, medtec- and App versions together with licenses.
- Provide approval rules, field mappings, and intended change tracking.
- Prepare article, order, and component references with independent target values.
- Define normal condition, exception, repetition, and controlled reset.
- Evaluate the manufacturer package, assign residual testing tasks, and hand over operations.
Project experience and collaboration
Trace the approved data version through to component consumption
With process owners, Quality and the implementation partner, we follow one medical device order through the configured medtec365 and Business Central functions. We connect approved master data, component batch and recorded consumption. Suitable partner records may cover standard functions. Configuration differences and data handovers need additional evidence. We help define the scope and independent expected results. The evidence relates to your installed configuration and the regulatory framework that applies to it.
Frequently asked questions about KUMAVISION medtec365
Has medtec365 been validated for our medical device process?
The industry solution and supplier documentation provided can serve as important evidence. Whether these documents are relevant to your specific application depends on the process, version, configuration, and actual data pathways. Take appropriate documentation with justified rationale and address any outstanding requirements. A marketing claim regarding validation does not constitute a complete evaluation of your specific manufacturing process or quality management system.
Does Annex 11 apply automatically to medtec365 in the medical devices sector?
No, a general industry designation does not justify a human medicinal product GMP application. First, determine the actual medical device process and its applicable regulatory scope. If the same environment is additionally used for a GMP-relevant medicinal product activity, that area must be separately evaluated. A general medicinal product inspection checklist would not serve as an appropriate basis for all medtec365 functionalities without such proper classification.
Which FDA-CSA version applies to the described framework currently?
The guideline takes into account the final Guidance issued on 3 February 2026 for production and QMS software within the medical device scope. It supersedes the September 2025 version. The QMSR is effective from 2 February 2026. Assess its applicability to your organization; the Guidance is not a general software requirement applicable to all industries.
Do we still need to perform a complete validation of Business Central?
The validation approach is based on the specific combination of systems used and their intended purpose. Separate existing platform documentation, industry-specific functionalities, and custom configurations. A comprehensive, one-size-fits-all platform testing is therefore not sufficient. Similarly, evaluating only the add-on component is inadequate if its performance depends on core functionalities or data transfers. Document the scope of coverage and targeted enhancements.
Can production continue during an article change?
The documented article versioning provides that the previous article remains usable during the change to a copy. The effectiveness of the new data follows the release. Check whether this function is set up in your system and which orders should use which stand. The description is not a flat-rate release, to run any change process parallel without further decision.
Sources: [2]
Does an approved compliance record indicate a complete history?
Not automatically. The core function differentiates the approval record from the separately required change log. Select the tables and fields relevant to your process and verify their actual traceability. Evaluation of retention, readable assignment, and access rights is also required. The function name alone does not guarantee completeness nor specific regulatory suitability.
Should we always use FEFO instead of quantity-based search?
Select your justified production rule. FEFO may necessitate splitting when a smaller, earlier-expiring batch is involved. A sufficiently large subsequent batch can enable a continuous order. Evaluate the decision together with all relevant conditions and actual consumption. Neither the earliest expiry date nor sufficient quantity alone addresses all quality concerns.
Sources: [4]
Is batch-pure production always required?
This example is provided solely as a recommended option. Its necessity for your process must be justified on a technical and regulatory basis. The add-on module offers a technical solution. Additionally, assess how exceptions, manual changes, and traceability are handled. The availability of a specific function does not imply a universal obligation to use it.
What do we need as a small manufacturer before commencement?
A clear, well-defined process, a known version and module inventory, and accessible decision-makers from Quality and Manufacturing are beneficial. Provide representative articles, orders, batches, and existing supplier documentation. The partner supplements technical equipment and system boundaries. Missing elements are planned as specific tasks; a large project organization is not automatically required.
What determines the duration of a medtec365 validation?
The scope primarily depends on the modules used, different release rules, interfaces, customizations, and available personnel. Test data, reset effort, and the involvement of your subject matter experts also influence the process. Start with a joint evaluation of a representative process. A fixed timeframe or a price derived solely from the product name would obscure these differences.
Sources and review date
As of October 6, 2026. The public medtec365 support contains no current build number. BC 2024 Wave 2 is referenced exclusively as a documented functional boundary. FDA Reference: QMSR and CSA Guidance February 2026, where applicable. Manufacturer descriptions do not substitute for evaluation of the specific module and configuration combination.
- ERP Software for Medical Devices — KUMAVISION medtec365
- Compliance — KUMAVISION medtec365
- Compliance — KUMAVISION base
- Batch Production — KUMAVISION medtec365
- Retired Functions — KUMAVISION medtec365
- FDA: Quality Management System Regulation (QMSR)
- FDA: Computer Software Assurance for Production and Quality Management System Software, 03.02.2026
- FDA: Part 11 — Scope and Application
- European Commission: EudraLex Volume 4, Human Medicinal Products - GMP
Sources checked: .
Compile your medtec365 documentation evidence appropriately
We support you in defining system boundaries, release handovers, and specific test cases for your intended medical device process.
- 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.

