Regulations and compliance · Practical guide

Annex 16 and batch release: what must the IT system show?

Several systems may contribute to batch release under Annex 16. The laboratory confirms results, the Qualified Person certifies the batch and the warehouse receives an available stock status. Distinguish these decisions and verify that they relate to the right batch in the human medicines GMP process.

Table of contents

At a glance

Does an ERP status of “released” mean that a batch has been certified under Annex 16?

No. Identify the decision represented by the ERP status and verify that the Qualified Person certified that specific batch where required. Annex 16 distinguishes review of manufacture and control, certification by the QP and transfer to saleable stock. The system should support these links, authorities and notifications. A similarly named status in a laboratory or warehouse does not replace certification.

  • Labor assessment, QP certification, and inventory availability have different meanings.
  • The correct batch and the decisive decision must remain linked.
  • Early release must be prevented during allowed movements under quarantine.

1. Clarify the scope of application and the release criterion

Sources checked on 7 October 2026. This article uses Annex 16 as revised on 12 October 2015, effective from 15 April 2016, for authorised human medicines and medicinal products manufactured for export. Investigational medicinal products are subject to additional specific provisions. Annex 16 does not replace official batch release.

The fundamental principles distinguish the evaluation of manufacturing and control, the certification of the finished product batch by a Qualified Person (QP), and the subsequent transfer to sellable inventory or export. This describes functional responsibility, not a mandatory model involving three software interfaces.

Therefore, for each internally used term such as "Release", "Approved", or "Free", define clearly what it signifies. A laboratory status may indicate the completion of result evaluation. It must not be interpreted solely by its name as evidence of QP certification.

Sources: [1] [2]

2. Assign decisions instead of mere status names

Capture where a decision is made, who is authorized to make it, and how it is subsequently used downstream. Multiple decisions may be represented within a system. What is critical is their clear meaning and reliable assignment.

The following matrix provides a practical translation of the technical differences. It does not claim to represent a universal sequence of all laboratory, storage, and manufacturing activities.

Assistance: Which decision is supported by which IT justification?
DecisionPossible system justificationDoes not mean
Labor results evaluated Test instruction with evaluated results and authorized approval QP certification of the finished product batch
QP Certification takes place Certificate of authentication uniquely attributable to the batch Automatic eligibility of each logistical booking
Transfer to saleable inventory Controlled status change with significant certification basis Substitute for missing certification or certification of another batch
Movement under quarantine Permitted transportation and storage process with maintained safeguards Release for sale or market supply
Delayed lockout decision Traceable restriction on further handling Retrospective overwriting of the original decision without apparent history

Sources: [1] [3]

3. Authorities and electronic recordkeeping control

The certification itself remains the responsibility of the Quality Personnel (QP). Annex 16 allows for the involvement of appropriately trained individuals or third parties for specific preparatory tasks, without deriving a general delegation of the certification responsibility.

When a computerised system records certification and batch release, Annex 11 Section 15 explicitly limits certification to QPs who perform unique identification and documentation of the individual responsible, along with an electronic signature. This specific requirement must be distinguished from a general signature obligation applicable to any arbitrary quality personnel.

Do not verify only the role designation. What matters is whether the designated individual is authorized to perform the relevant process and whether their action remains linked to the correct batch and the appropriate decision content. A general administrator account is not equivalent to a personal authentication.

Sources: [1] [3]

4. Test the handover with an incorrect batch assignment

In the following example, two batches, A and B, each consisting of 100 packages are present. Certificate of Quality (QP) certification is documented for batch A; it is not yet documented for batch B. The warehouse may transfer batch A to available for sale inventory according to the established procedure. Batch B shall remain safeguarded until a suitable decision is made.

The table specifically evaluates the relationship between decision-making and batch. It does not specify packaging quantity or software functionality. For a permissible quarantine transfer, the actual site- and procedure-specific conditions apply; mere rebooking does not constitute batch release.

A test using only A might not detect the critical error. The countercase B demonstrates whether an existing certification could be inadvertently applied to a different batch.

Example: Certification must pertain to the correct batch.
ActivityPrerequisiteExpected decision
A: Record 100 packages as for sale Certificate A and other specified conditions are in place Within the scope of a controlled process, acceptable
B: 100 packages to be booked as for sale Only Certification A available Do not permit release on the basis of another batch’s certification.
B: 30 packages internally reallocated Permitted procedure under maintained quarantine protection No automatic classification as marketable
B after relocation 30 packages at destination, 70 at origin site A total of 100; required safeguards remain in place for both quantities
Notice for A to reprocess Decision has already been correctly implemented No unintended additional modification of other batches

Sources: [1] [3]

5. Clearly notify the certification at the next location

When certification and transfer take place in salesable holdings at different locations, Annex 16 requires a regulated agreement. Section 4.3 mentions a formal and unambiguous notification of QP certification, referring to Chapter 4.

For an electronic data path, content, identity, recipient and processing of the message should be comprehensible. A technical confirmation of receipt does not only prove that the correct batch status was created in the target. Also check missing, duplicated or misallocated messages based on your actual process.

Not every data pathway operates asynchronously, and not every organization requires the same technical solution. Describe the real transition. When manual transfer of critical data is involved, appropriate additional accuracy controls must be considered.

Sources: [1] [3] [4]

6. Maintain traceability of changes and subsequent limitations

A status may change for various reasons. It should be distinguished between a technical correction, a new business decision, and a restriction on further handling. The previous decision status must not become unclear as a result.

Annex 11 addresses relevant changes, access controls, and the evaluation of incidents. Derive the required evidence for your release process from this. A general recording of any technical event is not equivalent to a substantiated, professional incident history.

When a interface or role rule is modified, assess its impact on existing batches and future decisions. The appropriate scope may also include unchanged functions that are dependent on the change.

Sources: [3] [4]

7. Checklist for the electronic release process

The checklist helps QP, quality assurance, warehouse and IT to record the same meaning of the status used. It complements the business requirements of certification and does not replace their complete evaluation.

  • Product and activity scope, as well as specific release requirements, have been clarified.
  • Laboratory evaluation, certification and storage status differed.
  • Authorization for certification and personal electronic logging verified.
  • Batch, product, and required decision scope clearly assigned.
  • Communication between involved sites and systems is defined.
  • Uncertified batches protected against premature transfer to saleable inventory.
  • Authorized quarantine movements with retained safeguards described.
  • Errors related to incorrect identity, failure to notify, and repeated processing have been reviewed.
  • Relevant subsequent changes and decisions kept comprehensible.

Sources: [1] [3]

8. Prior to any modification of the ERP, define the business rules.

A SME should first walk through a concrete example from laboratory test result to warehouse release decision jointly. Where is the certification located? What evidence does the warehouse receive? Who decides in the case of a discrepancy? These questions cannot be reliably answered by selecting a standard status.

The IT translates the defined rules into authorizations, data relationships, and controls. Suppliers can provide existing functionalities and evidence accordingly. Whether they cover the intended process must be verified based on the actual configuration.

A clear assignment simultaneously reduces unnecessary duplicate work: not every location needs to independently redevelop the same decision. However, it must be able to reliably identify which valid decision applies to the relevant batch.

Sources: [1] [3]

Project experience and collaboration

Link IT status to the batch release decision

We trace a batch through laboratory assessment, certification, stock status and any later block. Which system entry records each decision? Defining a status more precisely may resolve ambiguity. If different systems are involved, we also test handovers and authorised roles. Decisions remain with the designated people. We help link evidence and technical controls so a logistics posting cannot obscure a missing release.

Frequently asked questions about Batch release and IT

Is "released" in the LIMS equivalent to the QP certification?

Not automatically. A LIMS status can describe the laboratory assessment. The key aspect is documented meaning in the process. Certification of the finished product batch by the Quality Personnel (QP) must be clearly identifiable and properly assigned to the correct batch.

Sources: [1]

Does Annex 16 require three separate IT systems?

No. The technical decisions may be documented in one or more systems. Clear accountability, appropriate authorizations, and reliable linkages are essential. The description of the release process does not imply a specific software architecture.

Sources: [1] [3]

Can certification be delegated to a general QA role?

The certification is the responsibility of the Quality Personnel (QP). Certain preparatory tasks may be carried out by trained individuals or third parties as specified in Annex 16. This does not confer general authority to any QA role, including the responsibility to perform QP certification.

Sources: [1]

When does Annex 11 explicitly refer to an electronic signature?

Section 15 addresses the use of a computerized system for recording certification and batch release. It specifically addresses personal identification, restriction of certification to QPs, and electronic signatures. This is not a general statement applicable to every quality workflow.

Sources: [3]

May a batch be moved before it has been certified?

Annex 16 provides for dispatch under quarantine to an approved location under certain conditions. Protection against premature release must be maintained. Internal authorized movements must be distinguished from transfers to saleable stock.

Sources: [1]

Does an email containing the word "approved" suffice?

The notification must be formal, unambiguous, and properly linked to the relevant certification and batch. Whether a specific communication pathway is appropriate depends on its content and the controlled processes involved. A standalone term lacking identity and decision rationale is insufficient.

Sources: [1] [4]

What are we testing at the interface to the warehouse?

Verify the correct batch identity, significance, and processing of the decision, as well as appropriate failure scenarios. This may include missing, duplicate, or incorrectly assigned notifications. A technical receipt alone does not substantiate the correct professional target status.

Sources: [3] [1]

Are all batches of a batch automatically marketable upon partial reallocation?

No. Quantity and location are distinct from the relevant quality decision. In this example, the 30 packs moved and the 70 packs remaining belong to the same uncertified batch and stay under the appropriate controls. Movement does not replace certification.

Sources: [1]

Does this process apply unchanged to investigational medicinal products?

No. Annex 16 applies its principles to investigational medicinal products subject to different legislation and more specific Commission guidance. Consider the requirements for clinical trials separately. The release process for an authorised commercial batch cannot simply be applied to an investigational medicinal product.

Sources: [1]

What foundation supports a project prior to ERP configuration?

Create a clear mapping of decision, authorized role, required basis, and subsequent permitted action. Include a flawed batch reference as a review case. This will clearly demonstrate which standard functions are applicable and which supporting evidence is still missing.

Sources: [1] [3]

Sources and review date

Sources checked on 7 October 2026. This article covers human medicines within Annex 16. Investigational medicinal products and official batch release are subject to additional specific provisions. The examples support discussion and do not replace a full QP assessment or represent executed product tests.

  1. EU-GMP Annex 16: QP Certification and Batch ReleaseRevision dated 12 October 2015, applicable from 15 April 2016. Scope, general principles i–iii, sections 1.1, 1.6–1.7 and 4.1–4.3, and the glossary address certification, responsibility, quarantine and notification.
  2. European Commission: EudraLex Volume 4Current Directory, retrieved 07.10.2026; Human medicines: Annex 16, effective 15 April 2016
  3. European Commission: EU GMP Annex 11, Computerised SystemsJanuary 2011 revision, applicable from 30 June 2011. Sections 4.7, 5–6, 9–10 and 12–15 cover data flows, failure cases, changes, authorisations and electronic batch release.
  4. European Commission: EU GMP Chapter 4, DocumentationJanuary 2011, in force from 30 June 2011. The principle and sections 4.1–4.3 and 4.8–4.10 cover clear documentation, recording and traceability.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Make the batch decision unambiguous in the system

We assist you in aligning professional release criteria, authorizations, and interfaces, and deriving appropriate validation evidence from them. The responsibility and decision-making authority of the Quality Authority (QP) remains clearly embedded within the intended 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.

Send a project enquiry Customer testimonials →