Table of contents
At a glance
How do you validate Yaveon 365 for GMP use?
Validate the intended combined Business Central and Yaveon app workflow. Cover inspection plan selection, results, inspection closure, batch status, permitted postings and manufacturing instructions. Assess supplier evidence against its actual coverage, then add evidence for your configuration, process and operation. A recorded result, technical release status or signature alone does not establish that material is released for the intended use.
- Test task, batch status, manufacturing instruction, and signature requirement are distinct objects with independent statements.
- The combination of Business Central, Yaveon apps, configuration, and interfaces determines the validation scope.
- Independent target quantities and version specifications make errors at process transitions visible.
- An operational material-use decision does not replace any required batch certification by the Qualified Person.
1. Yaveon 365 and ProBatch: Maintain the actual application integration
Yaveon designates Yaveon 365 as an app family within Microsoft Dynamics 365 Business Central. It consolidates the previous solutions ProBatch and ProE-SCM. This does not imply functional equivalence between any previous ProBatch installation and the current combined solution. For validation purposes, you require the specific Business Central environment, installed apps and versions, customer-specific customizations, operating mode, and used integration interfaces.
Public support utilizes both ProBatch and Yaveon-365 pathways. Many pages do not specify an exact build number. Therefore, document which guide corresponds to your environment. Quality Assurance, as specified by the vendor, requires Lot Management; additional manufacturing, storage, and scanner functions have app-specific dependencies. An existing ERP base system does not support these supplementary functions.
This guide addresses the use of ERP systems in the manufacture of human medicinal products under EU GMP. The Commission has implemented Annex 11 in the revised version from January 2011. Whether a specific ERP function is GMP-related depends on its actual impact on product quality, patient safety, and data integrity. Requirements for food, cosmetic, medical device, and US regulations require separate evaluation.
2. Four states, four different statements
Start with the operational question: Which personnel may use which materials based on what authorization? This leads to requirements for data, decisions, and access controls. A general statement such as "batches are traceable" is insufficient to support the critical transition from testing to production or shipping.
The manufacturer provides a Compliance Kit with templates. Its specific contractual and version coverage must be aligned with the company's own process. Appropriate supplier documentation can support audits; open configurations, custom enhancements, and interfaces remain visible. Annex 11 requires a justified, risk-based demonstration of the intended use.
The following work aid prevents a green status from incorrectly confirming the wrong object. For each row, supplement the actually effective rule, decision authority, and linked evidence.
| Object | Technical status | Statement | Additional evidence |
|---|---|---|---|
| Verification scope | Inspection completed | All intended in-process values have been recorded. | Closure, evaluation, and required usage decision. |
| Batch | Configured status: RELEASED | A particular batch status is set. | Rationale, authority, and effectiveness for the specific booking pathway. |
| Manufacturing instructions | Certified | The specification is technically approved for use. | Correct version for start date, batch size, and storage location. |
| Signature requirement | A line signed | An authorized or permitted signer has acted. | Complete regulatory coverage and alignment with the correct data version. |
3. Intentional selection of test plans, data capture, and review of closure
The Yaveon support outlines a hierarchy for audit plan selection: first the business relationship, followed by the product, and then a non-restricted assignment. When multiple equally valid audit plans are available, the audit assignment is created using the plan with the highest number; in process-oriented assignment, the certified plan with its version is relevant. Review conflicting assignments against pre-defined target plans, rather than merely documenting the selected plan name.
A review request in the Released status is available for processing. "Inspection completed" indicates that the actual values have been captured. "Finished" denotes the completed closure of the review; at this point, the request is no longer editable according to the help documentation. The automation that triggers the first and last values depends on the system configuration. Therefore, it is essential to also test missing values and an unauthorized closure attempt.
During a subsequent review of the same sample, the assistance generates additional result rows in which both actual values are included in the calculation. This differs from a new sample and a new re-inspection order. Professionally define when each variant is acceptable. The technical feasibility neither justifies overwriting an undesirable result nor the ungrounded exclusion of such a result.
4. Status change and permissible use link
Yaveon documents both a usage decision derived from a completed audit task and automatic updates to the item traceability status. The automation takes into account, among other factors, the triggering event, item or quality group, previous status, and outcome. Example rules apply to attachment IN_QC and upon completion, depending on the outcome, either RELEASED or BLOCKED.
These names do not constitute an independent release justification. Your process must specify which action is permitted for each status: withdrawal, transfer, production consumption, or dispatch. Review the actual used dialogs, roles, and interfaces. An effective booking lock does not prove physical segregation in storage; for that, a suitable operating procedure is required.
Distinguish the decision to use a material from certification of a finished medicinal product batch by the Qualified Person. Annex 16 describes certification and subsequent transfer into saleable stock in the controlled release process. An ERP status cannot replace that responsibility. Identify which decision is recorded in which system.
5. Test example: 160 kg available, but only 100 kg usable
This is our proposed test, not an executed product test. The isolated test inventory contains 100 kg of an item in batch QA-A and 60 kg in batch QA-B. Both start with IN_QC. The expected result approved before the test permits shipment only with RELEASED status and through the defined QA decision path. An order requires 120 kg.
The assigned status names and rules apply solely to this example. Partial shipping is not automatically permitted and would require a separately authorized procedure. As an independent reference, batch numbers, quantities, inspection plan versions, and expected decisions are documented prior to testing. The test series does not perform actual inventory postings outside the test batch.
| Test step | Defined state | Expected behaviour | Guaranteed evidence |
|---|---|---|---|
| 1. Complete QA-A batch review. | 100 kg; Finished; within the limits; appropriate rule active. | RELEASED; 100 kg available for the intended shipment. | Original values, closure status, current status, and recorded status change. |
| 2. Fully capture QA-B batch | 60 kg; only inspection completed; closure still open. | After this, continue to count IN_QC; not as usable. | Test status and batch status, as well as actual shipping attempt in the test. |
| 3. Provide 120 kg for shipping | 160 kg total inventory, of which 100 kg is available for use. | No complete shipment: 20 kg allowed quantity is missing. | Independent quantity calculation; result in warehouse dialog and used interface. |
| 4. Complete QA-B with negative result. | Finished; outside the limits; appropriate rule active. | BLOCKED; total of 160 kg, still only 100 kg available for use. | Result reference, status change, and additional negative charge test. |
6. Verify active manufacturing instructions instead of relying on a single default identifier
A Yaveon manufacturing instruction links the bill of materials and work plan. The assistance feature includes version, start date, batch size range, and warehouse location as selection criteria. When batch size ranges overlap, ProBatch 365 selects the manufacturing instruction with the highest version number. This allows a simple change to the validity range to have an impact on orders whose article master remains unchanged.
The "Certified" status permits the use of the specification; certification may be secured by an electronic signature. Here, "Certified" refers to a software state, not a formal governmental certification. Designate test cases just prior to and at the expiry date, as well as at batch size boundaries. Subsequently, compare the actually implemented components and processes with the independent required (expected) set.
Particularly relevant is the manufacturer's note regarding default settings: the assigned bill of materials and work plan are thereby assigned to specific Business Central standard functions. However, the selection of the regulation for a production order is not solely determined by this default. Additionally, verify inheritance of status and expiration date, where such functions impact the respective process.
7. Evaluate signature rules and data requirements together
Electronic signature rules relate to actions and conditions. The available actions depend on the installed and licensed apps as specified in the help documentation. The rules define signers or groups and their associated conditions. Their mere existence is insufficient: verify activation, condition, authorization, and the actual process step triggering the signature.
Two documented individuals do not automatically imply two required signatures. The system distinguishes based on signature number: the same value allows alternative signatories; different values require multiple signatures. An effective two-person review also necessitates a defined set of authorized personnel and roles. Test both a missing second signature and an attempt by an unauthorized individual.
The manufacturer's example for production order component documentation highlights another boundary: the document data reflects the content at the time of requirement; the source document may have been modified since then. Define how a subsequent decision remains bound to the correct version. A dedicated negative test controls the source by updating it according to the requirement and verifies whether the intended decision pathway correctly handles the change. Thus, automatic invalidation of any modification is not asserted.
8. Correct scan data traceable down to article level
Quality scanning requires additional manufacturing scanning for the specified production workflows, along with warehouse scanning for incoming goods. The guidance also includes a user qualification for the actual measurement of the assigned attribute. Document these dependencies within the scope; a general scanner integration does not constitute evidence of this specific behavior.
When an inspection order is created, registered batch or serial numbers and quantities are transferred into Business Central item tracking before the goods receipt is posted. According to the supplier, later amendments or deletions in the scanner registration do not automatically update those stored data. Test the correction workflow specifically.
Compare, in a controlled test, scanner registration, item tracking, and inspection tasks before and after a quantity or batch correction. The correction instruction must specify prerequisites, authorizations, and received documentation. Unverified deletion actions in the production inventory cannot be inferred from this. The key question is whether the affected objects can subsequently be traced and reconciled to the approved target assignment.
9. Plan changes, historical records, and operation jointly
A new inspection plan version, modified status rules, or additional signature requirements can likewise impact the process, just as a software update does. Assess the implications on ongoing orders, existing results, and linked data pathways. Clearly justify which records remain valid and which targeted reviews are required. Even unchanged functions may be affected.
For historical decisions, it must be clearly established which version of the applicable specifications was in effect at the time and which relevant results were considered. Therefore, determine where the test instruction, repeat test results, status changes, signature requirements, and associated data status are retained. Possession of a current master data sheet alone does not necessarily justify a prior decision. The scope and duration of retention shall comply with applicable record types and the associated process.
In addition, consider personnel changes, disruptions, and subsequent data export. The operational qualification should demonstrate how a discontinued process is detected, assessed, and controlled upon resumption. Annex 11 addresses changes, regular evaluation, access, incidents, and archiving; therefore, no universal interval or blanket reperformance of all tests is required.
10. Preparation and Involvement in SMEs
The effort primarily depends on different testing routes, special rules, internal extensions, and data transfers. A single product group with multiple exception routes may require more clarification than many similarly processed products. Present the variants prior to test planning, including actual error and correction pathways.
QA defines evaluation, decision authorities, and professional exceptions. Production and storage provide actual work processes as well as independent target specifications. IT or the implementation partner makes available release schedules, configurations, and interfaces. The system owner integrates these informations with supplier documentation, operating procedures, and open findings. This results in a verifiable decision basis rather than a mere collection of screenshots.
- Business-Central Version, Yaveon Apps, Licenses, Extensions, and Operating Mode to be documented.
- Select representative article, inspection, batch, and manufacturing instruction variants.
- Define the allowed action and responsible decision for each status.
- Verify plan selection, closure, repeat findings, and actual booking independently.
- Signature conditions, AND/OR logic, and requirement data status traceability.
- Align scanner corrections and other interfaces up to the target object.
- Regulate historical records, access, export, and change evaluation during operations.
- Document open deviations with impact, corrective actions, and justified closure decision.
Project experience and collaboration
Compare the automated selection with the intended quality decision
With process owners and the implementation partner, we prepare several valid inspection plans or manufacturing instructions. We compare the version actually selected with your agreed rule, including boundaries and overlaps. We then trace how inspection completion and batch status affect the intended posting. Suitable partner evidence can be reused, with additional cases for your configuration and exceptions. We record which decision the software executes and which responsibility remains with your authorised staff.
Frequently asked questions about Yaveon 365
Are Yaveon 365 and ProBatch the same product?
Yaveon describes Yaveon 365 as an app family on Business Central, which bundles previous ProBatch and ProE-SCM offerings. This does not allow for the equalization of all old installations. Your project includes the actually installed apps, versions and extensions. Arrange older ProBatch guides to this inventory and clarify missing version references with the supplier.
Does an existing Business-Central validation cover the Yaveon apps?
Only to the extent that the documented coverage includes the current application environment and intended process. Review requirements, configurations, interfaces, and supporting documentation. An earlier test of a standard booking does not substitute for evidence of a subsequently introduced QA status rule. Appropriate existing evidence remains valid; a complete revalidation is not required solely due to the product name.
Has the inspection been completed and is material release therefore authorized?
No. After the Yaveon help, this test order status indicates the actual values recorded. Finished is the completed completion. The result evaluation, usage decision and batch status are to be separated from this. The decisive factor is which proven process decision allows the concrete material use. Check the actual booking path and not only the displayed order status.
Can an automated status rule replace the QA decision?
An automated rule can implement approved decision logic. Define the permitted decisions, authority and handling of exceptions, then test the outcome in an actual transaction. The status must be based on the correct information. An ERP status neither transfers process responsibility nor replaces required certification by a Qualified Person.
Why is default not enough for a production rule?
The manufacturer’s support document explicitly separates default settings from regulatory selection for manufacturing orders. Default settings incorporate specific bill of materials and work plan references for standard functions. When performing the relevant selection, additional factors such as version, start date, batch size, and warehouse location are considered. Therefore, the actually accepted order content must be verified against a previously defined expected profile.
Sources: [5]
Do two possible signers automatically mean a four-eye principle?
No. For the same signature no. Yaveon specifies alternative signatories; different numbers require multiple signatures. Additionally, roles and authorized personnel must align with the technical requirements. Test the full rule with missing signature and unauthorized individual. Having two names in a list of authorized personnel is not sufficient evidence.
What happens when the source is changed after a signature requirement has been established?
The help record reflects a snapshot of data as of the requirement date, while the source may differ at a later point in time. This does not imply a blanket automatic devaluation of the signature. Your process must define and provide evidence of which data is validated and how relevant changes are handled. A controlled comparison of the requirement state, source, and final action is an appropriate test for this purpose.
Does Business Central automatically capture any subsequent scanner corrections?
For the documented quality scanning run explicitly not: The creation of the test order writes article tracking data already before the goods are booked. Later scanner changes do not adjust them automatically. Check the appropriate correction procedure in a test environment based on all affected objects. Do not take any deletion step without controlled operational requirements.
Can a repeat inspection replace the first value?
The repeated testing of the same sample generates an additional data entry; both values are included in the result calculation. Other functions relate to new samples or new test requests. The technical validity must be defined by your procedure. An adverse result must not be eliminated solely because a subsequent measurement yields a more favorable outcome. Establish the relationship and provide a justified evaluation.
Which preparation reduces unnecessary validation effort?
Compile outstanding issues, process variations, status rules, requirements, and existing supplier documentation. Identify functional owners and provide independent target scenarios with quantities, versions, and authorized actions. This enables differentiation between genuine traceability gaps in already documented processes. Particularly complex are unresolved special cases and transitions, where responsibility between QA, IT, and operations remains unclear.
Sources and review date
Source date: 6 October 2026. The public Yaveon-365 product pages and ProBatch-/Yaveon support materials describe different applications and do not consistently reference specific builds. The versions and configurations installed by the user remain decisive. Regulatory reference: Human medicinal product GMP; other usage areas must be evaluated separately.
- Yaveon 365 – ERP for the Process Manufacturing Industry
- Yaveon 365 Quality Assurance
- ProBatch 365: Inspection Order
- ProBatch 365: Automatic Item Tracking Status Modification
- ProBatch 365: Manufacturing Specifications
- ProBatch 365: Rules for electronic signatures
- ProBatch 365: Working with the electronic signature (example)
- Yaveon 365: Inspection Orders in Production and Warehouse Processes
- European Commission: EudraLex Volume 4 – current directory
- EU GMP Annex 11: Computerised Systems, January 2011 revision
- EU GMP Chapter 4: Documentation, January 2011
- EU GMP Annex 16: Certification by a Qualified Person and Batch Release, October 2015
Sources checked: .
Ensure their Yaveon process is traceable and verifiable
Daniel Herrmann Consulting supports you in aligning technical decisions, application configurations, and existing evidence. The focus lies on the analytical methods relevant to your operation and ongoing transition points.
- 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.

