IT systems · Practical guide

Validating Infor M3: which evidence supports subsequent partial receipts?

A batch was inspected and another quantity from production arrives later. Does the original quality decision also cover the new receipt? In Infor M3, the answer depends on the configured QMS and process. Trace the inspection request, imported results and identity of the stock before deciding which cases QA, production, warehouse staff and IT should test.

Table of contents

At a glance

How do you validate Infor M3 for GxP use?

Validate the intended process in its actual M3 version, QMS configuration and data flows. For later partial receipts, check which test requirement applies, which results carry over and which stock becomes available. Assess relevant supplier evidence, then test remaining gaps against defined outcomes, including incorrect assignment, unexpected statuses and interface failures.

  • The quality plan and testing requirements determine which results support a decision.
  • A mathematically correct total quantity does not constitute an appropriate quality assessment.
  • Late additions require a justified approach to the use of existing evidence.
  • Technical system status and legal batch certification have distinct responsibilities.

M3-Core, QMS, and additional applications specifically identify

Infor M3 is an ERP solution for manufacturing and distribution. The current product description details a tenant-agnostic cloud-based deployment. This article specifically examines the Quality Management System, or QMS. The QMS functions described herein are based on Infor documentation as of version 2026.10. This source version neither confirms the latest customer release nor verifies the configuration of your environment.

Therefore, first capture the actually deployed version, the operating mode, the involved sites, and the activated functions. A historical M3 name or a general CloudSuite license is insufficient. Allow the system owner to demonstrate the examined process for a specific order and document the corresponding active configuration.

The CloudSuite overview distinguishes core from supplementary modules, such as Graphical Lot Tracker, Factory Track, WMS, or MES. The presence of a supplementary module does not constitute evidence of its usage. Document which application reports access, which one drives quality decisions, and where downstream consumption is triggered. This results in a manageable scope rather than a blanket audit request covering all ERP functions.

Sources: [1] [2] [4]

Put the professional application before the test scope

The GMP relevance arises from the use: Does M3 affect the identity of a material, a quality decision, or a relevant manufacturing record? A commercially designated function may be involved if it controls such a process. Conversely, an unused product function does not require a pre-emptive full test. Describe the relevant workflow and its dependencies.

EU GMP Annex 11 is a key GMP guideline for computerised systems in human medicinal product manufacturing. The Commission continues to maintain the revision from January 2011. The risk-based justification of the scope of validation evidence takes into account product quality, patient safety, and data integrity. Other industries require a separate assessment; this guideline does not universally apply.

State a critical requirement, for example: A subsequently produced portion may only be used after the intended quality assessment has been performed. Specify who determines which documentation is required and what constitutes intended use. This ensures that the professional standard remains independent of the current M3 configuration settings.

Sources: [5] [6]

Understand the logic behind the inspection status determination

QMS009 outlines various rules for testing requirements and their evaluation. Among other things, different test sequences and specifications may influence automated decision-making. Individual test rules can thereby impact the assessment criteria of the quality plan. Therefore, an approved status does not automatically imply that every conceivable test has been performed and passed.

For validation, a small, deliberately divergent dataset is worthwhile: one required value is missing, another falls outside the intended range, and a third is valid. Pre-define which combination is decision-worthy. Then, compare the actual decision pathway against this predefined expectation. A screenshot of the final status alone does not explain the logic applied.

The following table is an internal reference guide. Populate your questions with your specific specifications and roles. This is not a directive to always select the most stringent available setting. What matters most is whether the selected rule accurately represents the intended quality process and whether exceptions remain clearly understandable.

Own work aid: From requirement to the decisive regulation
Area to assessPre-emptive question to be addressedTargeted comparison
Scope of testing What results are required for this decision? Scope against actually considered values
Change Can a requirement following result capture be modified? A permitted action and an attempt to make an unauthorised change
Partial receipt What documentation applies to the newly added quantity? Source of results and associated access rights
Exception Who decides on a divergent process flow? Authority, rationale and subsequent usability

Sources: [3] [6]

Later accesses with their QIPF rule to be reviewed

For an already approved testing requirement, Infor for QIPF outlines three approaches: Setting 0 utilizes existing results for subsequent access. Setting 1 requires an initial manual reclassification of the current identity. Setting 2 requires a different storage location with its own distinct identity. The subsequent consolidation depends on the appropriate status condition. For rejected testing requirements, the guidance describes dedicated workflows.

These options require a professional judgment. What conclusion does the original inspection support, and to which manufacturing process or quantity does it relate? An existing evaluation may be appropriate; however, it may not cover a subsequent activity. Document the transfer condition instead of either routinely re-evaluating every access or unconditionally accepting every result transfer.

Verify at least the selected normal pathway and a deliberately deviating initial state. Particularly informative is access following an already executed decision. Additionally, clarify whether a configuration change affects only new processes or impacts existing test requirements. This effect must not be inferred solely from the name of the setting.

Sources: [4] [6]

Identity and actual use are linked

A stock identity links in the considered M3 support inventory, article, batch, storage location, and container. This combination provides more precise traceability than a batch number alone. Prepare an overview of the involved identities and track the pathway to the intended withdrawal or onward transfer.

As a standalone audit question: Can an unclarified subset be utilized via an alternative booking pathway? Consider only the actually used pathways, such as user interface, mobile data capture, or linked production. A locally verified status change does not necessarily reflect the same impact across all integrations. Identify expected rejections, permissible interim staging, or controlled exceptions.

The technical approval of an M3 inventory must also be distinguished from a legally mandated batch certification. Annex 16 addresses, within the appropriate medicinal product scope, certification by a qualified person and the subsequent release chain. Whether the M3 maintains records or merely receives a downstream inventory must be demonstrated by the specific process.

Sources: [4] [7]

Further reading:

Example: 60 verified and 40 new units

The following example does not describe an executed M3 test. Scenario: Article P-100, Batch L-01, Order MO-01. At location A, 60 approved units are on hand. An additional 40 units will be manufactured later. There are no reservations, no rejects, and no unit reclassification. The first two table rows represent a sequence: access to B followed by evaluation. Each subsequent error case restarts with 60 units at location A and independently evaluates the later 40-unit intake.

The required action in the example states: The subsequent 40 units require a separate, documented quality decision prior to use. The first 60 units remain unaffected, provided no overarching quality finding is present. For the normal case, a dedicated Batch B area is provisionally assigned. Prior to the second decision, 100 units are available, but only 60 are suitable for the usage defined herein. Thereafter, the number may reach 100.

The matrix shows expected states, not guaranteed native blocking functions. Define prior to execution how M3 and the other process controls achieve the intended outcome. Implement controlled backtracking of case volumes, assignments, and quality data between cases. Store individual test results separately to ensure that a successful incident does not obscure the next failure case.

Example: Quantity requested – first access and evaluation, followed by independent error cases
Action or failure scenarioExpected quantity on handExpected professional judgment
Post 40 new units correctly to B A: 60; B: 40; Total: 100 B remains unused until the intended decision date is reached
The previously booked 40 units on B are to be appropriately assessed. 60 + 40 = 100 Following an appropriate decision, all 100 may be used.
Only 35 units are processed instead of 40. 60 + 35 = 95; Difference: 5 Detect the quantity discrepancy and avoid reporting successful receipt of 40
The same 40 units are processed twice. Error state: 60 + 40 + 40 = 140 Prevent or detect and investigate promptly
Existing results are accepted without review In total, the correct value can be 100. If the correct amount is present but the requirement is not met: evidence for B is missing

Sources: [6] [4]

Interfaces are followed until professional processing.

The M3 Help mentions API processes for reporting of batch releases. This does not guarantee that a customer-specific connection covers the same complete process as the user interface. Take a real message type from your integration and map its fields to the intended business objects.

Review, jointly, the article, order, batch, quantity, unit, and target reference as part of an independent test draft. A technically assumed message may still lack scientific clarification. Define the indicator by which the sender recognizes a fully processed access. In the event of an interruption, the team must establish a clear recovery procedure: is nothing scheduled, only partial processing occurred, or only the feedback was lost?

For a repeat occurrence, the quantity chain must remain clear and traceable. Do not assume automatic duplicate prevention until the specific pathway has been validated. Compare incoming data, processing, inventory changes, and quality assignment. Chapter 4 of the GMP Guideline supports the assignment of relevant activities to their corresponding records; the proposed message matrix represents a practical implementation thereof.

Sources: [4] [6] [8]

Further reading:

Review the roles and changes to the decision

Distinguish between result capture, requirement change, inventory reclassification, and professional approval. A common role name provides little insight into actual authorities. Test an authorized process and the same action performed by a user without the appropriate responsibilities. Also consider technical accounts when they have access to decision-critical data.

For a controlled correction, original condition, occasion and resulting decision should remain understandable. This is a test target; this article does not claim a complete native M3 history for all objects. Request version-adapting documents and examine the actual available records. A pure end state list does not answer the question about the change process.

Evaluate electronic signatures based on their specific intended use. EU GMP Annex 11 distinguishes between general signatures and the specific case of computerized batch certification. For FDA documentation, the applicability of Part 11 must first be determined. A user login or a button for approval does not imply a universal requirement for electronic signatures nor does it guarantee their complete compliance.

Sources: [6] [8] [9]

Evaluate existing evidence and changes purposefully

Assign a supplier or partner certificate to the corresponding internal requirement. Do the versions match? Is the quality management system (QMS) active? Is the configuration consistent? Is the initial state and test result documented? What deviations are present in the certificate? Document the rationale for its transferability and identify any remaining open questions. A suitable external test does not need to be fully replicated solely because of its authorship.

When performing an update, the impact on your analytical method validation is particularly relevant. A change to result transfer, interface, or status logic may require a different scope of validation compared to a simple display modification. Select regression testing based on the affected requirements and available documentation. This does not imply automatic full revalidation nor a general waiver of independent verification.

Plan also a data loss or recovery case. It is not enough that the inventory is visible again if its quality receipts are missing. A separate restoration comparison should take into account related processes, decisions and relevant history. Responsibility, storage purpose and available restart procedures therefore belong to the operational transfer.

Sources: [6] [8]

Start with a specific preparation checklist

Name a qualified quality and production expert, the system owner, and point of contact for warehousing and integrations. The M3 partner shall describe the configuration and product boundaries. Responsibility for the own technical specifications remains with the company. These roles may overlap within a small team; however, their responsibilities must remain clearly identifiable.

The effort depends particularly on variations in the quality plan, locations, data pathways, legacy systems, and the availability of appropriate test conditions. Prior to scheduling, agree on who will define decision rules, provide test data, and evaluate open deviations. A brief joint walkthrough with an actual process object provides greater clarity than a general functionality list.

  • Record usage, product status, QMS activation, and affected locations.
  • Selected QIPF rules and subject-matter transfer conditions are documented.
  • Provide requirements with predefined target and responsible decision-maker.
  • Prepare appropriate partial accesses, countermeasures, and controlled resets.
  • Assign manufacturer records, interface specifications, and open validation questions.
  • Plan control rights, corrections, restoration, and operational handover.

Sources: [6]

Project experience and collaboration

Check subsequent production quantities together with their assessment

Production, warehouse staff and Quality select a batch with several partial quantities reported against one manufacturing order. We agree which inspection applies to a subsequent receipt and which stock may then be used. We compare those expectations with the configured M3 rule and the data passed between steps. A known configuration change may need only focused additional testing. Different receipt types or unclear carry-forward rules first require agreement on scope. We establish the expected effect on quantity and status before testing.

Frequent Questions about Infor M3 and Partial Accesses

Do we need to retest every subsequent subset in the laboratory?

The scope of your existing testing coverage determines the validity of the results, not the product name. Justify how the findings are transferable to specific manufacturing processes, volumes, and conditions. The M3 configuration must reflect this decision. This article's example deliberately requires an independent assessment of the second subset; it does not establish a general requirement for repeated laboratory testing.

Sources: [4] [6]

Is QIPF 0 inherently unacceptable in GMP use?

From the documented function, a blanket prohibition does not follow. What is decisive is whether result transfer aligns with your justified process. Assess the prerequisites and implications for the newly added inventory. If your requirement entails an additional decision, the configuration must not circumvent this unnoticed. A preferred setting cannot be considered valid without a specific usage context.

Sources: [4] [6]

Why is a batch status alone insufficient as test evidence?

The status shows a condition. It alone does not explain the access involved or the decisive results. Link it to the identity of the stock, quality requirement and booking process. Especially in the case of combined quantities, a correct total number can cover an unexplained origin or lack of quality evaluation. A targeted counter-event makes this limit visible.

Sources: [3] [8]

Which M3 version does the guideline address?

The described QMS functions are based on the public information documentation as of version 2026.10. This represents a documented source base, not a statement regarding the latest release or tenant configuration. For implementation, compare the installed version, activated features, and specific settings against the corresponding vendor documentation. Older M3 installations will not be unverifiedly equated.

Sources: [4] [1]

Do Graphical Lot Tracker and MES automatically fall within the scope?

Only to the extent that they are actually used within the intended process. The CloudSuite overview presents additional applications separately from the core system. Capture license, data source, handover, and operational responsibility. A separately illustrated traceability feature is not automatically equivalent to the primary quality decision; its specific purpose determines the additional supporting evidence.

Sources: [2]

Is M3 approval already the legal batch certification?

No. A technical M3 authorization does not replace certification of a medicinal product batch by a qualified person. Clarify whether the M3 process itself records such a decision or merely reflects a subsequent material status. For the electronic recording of certification and batch release, Annex 11, Section 15, specifies particular requirements regarding authorization, unambiguous personnel assignment, and electronic signature. Technical status, professional judgment, and the associated evidence must be distinctly separable.

Sources: [6]

Can we test the interface with the same data as the surface?

This can provide a meaningful comparison when the initial state and technical actions align. However, supplement your own error types within the handover process: missing assignment, partial processing, duplication, or lost response. The key factor is the technical outcome with supporting evidence, not merely a successful technical confirmation. The specific interface remains a separate subject for review.

Sources: [4] [6]

What must our team prepare prior to project start?

Useful elements include a defined process, product, and configuration status, designated point of contact, and representative test orders. Additionally, existing evidence, selected decision rules, and access to an appropriate test environment are essential. If any documentation is missing, document the open question and its impact. A complete collection of all ERP documents should not serve as a one-size-fits-all starting criterion.

Sources: [6]

What factors determine effort and duration?

Above all, differing quality rules, multiple booking pathways, customer-specific customizations, and unclear legacy assignments impact the scope. The availability of QA, production, and partners also plays a role. Plan based on key requirements and open evidence. A fixed duration derived solely from company size, user count, or M3 licenses would not constitute a reliable assessment.

Sources: [6] [2]

Must the entire process be revalidated after each update?

First, assess the actual change and its impact on the functions in use. Appropriate supplier documentation and existing tests assist in identifying open risks. Repeat or supplement the necessary evaluations as required. Assigning a new version number alone does not justify a complete restart nor the unaltered adoption of all prior decisions.

Sources: [6]

Sources and review date

As of October 6, 2026. QMS functions: Infor document branch 2026.10. Product and suite overviews are undated. Customer release, QMS activation and additional applications have to be synchronized separately. The tables contain own work aids; no product test has been performed. Complementary targeted source comparison on October 18, 2026: Annex 11 No. 15 for separation of technical status and electronically recorded batch certification.

  1. Infor M3 | Cloud ERP for Global Manufacturers & Distributors
  2. Overview — CloudSuite Manufacturing
  3. Quality Approval Rules and Process
  4. Quality Management System (QMS) and Its Impact on Manufacturing Order Processing
  5. European Commission: EudraLex Volume 4
  6. EU GMP Annex 11: Computerised Systems
  7. EU GMP Annex 16: Certification by a Qualified Person and Batch Release
  8. EU GMP Chapter 4: Documentation
  9. FDA: Part 11 — Scope and Application

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Define their M3 traceability pathway specifically

We support you in distinguishing partial accesses, quality decisions, and inventory movements and in evaluating the existing evidence.

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