{
 "slug": "qp-certification-receipt",
 "topic_id": "TOPIC-122",
 "cluster": "Pharma, Biotech & Clinical Trial GxP Identity",
 "tier": "Tier B",
 "title": "The QP certification nobody can verify: batch release across the EU supply chain",
 "summary": "A Qualified Person accepts personal legal liability for certifying each batch for EU release. The artefact carrying that certification is a PDF or a register entry inside the marketing authorisation holder's own system.",
 "lede": "There is a person, named in a marketing authorisation, who is personally liable under EU law for each batch released to the European market. Their certification is the last gate before a medicine reaches a patient. It travels as an attachment.",
 "date": "2024-07-21",
 "category": "Compliance",
 "author_id": "elias-vanterpool-osei",
 "tags": [
  "Qualified Person",
  "batch certification",
  "Annex 16",
  "EU GMP",
  "falsified medicines",
  "supply chain"
 ],
 "image": "https://cdn.twc.sh/images/igcache/QP%20Certification%20Receipt/1200_630/blog.jpg",
 "schema": "Article",
 "key_takeaways": [
  "QP certification is a personal legal act recorded in a corporate system. Downstream parties inherit it without any means of independent verification.",
  "Annex 16 permits reliance on assessments performed by others. A portable receipt must represent that reliance chain rather than obscure it.",
  "Offline verification against a published key removes the need for a distributor or authority to contact the marketing authorisation holder."
 ],
 "body": [
  {
   "type": "h2",
   "text": "The person, and what they carry"
  },
  {
   "type": "diagram",
   "kind": "chain",
   "alt": "Personal liability, institutional record",
   "caption": "The liability is on an individual. The evidence is a row in a company's system.",
   "nodes": [
    {
     "label": "QP reviews the batch",
     "sub": "personal responsibility",
     "note": "legal"
    },
    {
     "label": "Certification recorded",
     "sub": "register entry or PDF",
     "note": "internal",
     "bad": true
    },
    {
     "label": "Product moves through the chain",
     "sub": "multiple parties",
     "note": "unverifiable",
     "bad": true
    },
    {
     "label": "Question arises years later",
     "sub": "who certified?",
     "note": "",
     "bad": true
    }
   ]
  },
  {
   "type": "p",
   "html": "Meet the role rather than the regulation. A Qualified Person is a named individual, with defined qualifications, whose signature certifies that a batch has been manufactured and checked in accordance with the marketing authorisation and GMP. Under Directive 2001/83/EC they carry that responsibility personally. Not the company. The person."
  },
  {
   "type": "p",
   "html": "In a modern supply chain that person may be in Dublin, certifying a batch manufactured in Hyderabad, tested in a contract laboratory in Milan, imported through a site in Amsterdam, and distributed through wholesalers in six countries. Each of those parties relies on the certification. None of them can check it."
  },
  {
   "type": "h2",
   "text": "What reliance looks like today"
  },
  {
   "type": "p",
   "html": "A wholesaler receiving product relies on documentation supplied by the seller. The documentation includes a certificate referencing the QP's certification. Verification, in practice, means recognising the letterhead and the relationship."
  },
  {
   "type": "p",
   "html": "Where document signing is used, it usually verifies an organisational certificate — that the file came from a company — rather than the QP's personal act. That is a meaningful difference. The regulation places liability on an individual; the artefact attests to a corporation."
  },
  {
   "type": "callout",
   "title": "Why this matters more since the Falsified Medicines Directive.",
   "html": "The FMD built serialisation infrastructure to verify that a pack is what it claims to be. It did not build anything to verify that the release decision behind that pack was made by the person who claims to have made it. The two problems are adjacent and only one has been solved."
  },
  {
   "type": "h2",
   "text": "The QP Certification Receipt"
  },
  {
   "type": "p",
   "html": "The design goal is a certification that travels with the product and verifies anywhere, decades later, without contacting anyone."
  },
  {
   "type": "table",
   "head": [
    "Field",
    "Content"
   ],
   "rows": [
    [
     "<code>batch</code>",
     "Product, strength, batch number, manufacturing site"
    ],
    [
     "<code>ma_reference</code>",
     "Marketing authorisation number and member state"
    ],
    [
     "<code>certification_basis</code>",
     "Which elements the QP assessed personally and which were relied upon"
    ],
    [
     "<code>reliance_chain</code>",
     "References to the underlying confirmations relied on under Annex 16"
    ],
    [
     "<code>qp</code>",
     "The QP's personal credential assertion, with their registration reference"
    ],
    [
     "<code>issued_at</code>",
     "Timestamp, RFC 3339"
    ]
   ]
  },
  {
   "type": "p",
   "html": "The third and fourth fields are the interesting ones and they are what makes this an Annex 16 design rather than a naive one."
  },
  {
   "type": "h2",
   "text": "Representing reliance honestly"
  },
  {
   "type": "p",
   "html": "Annex 16 explicitly contemplates that a QP may rely on assessments performed by others — on-site quality personnel, other QPs in the chain, contract laboratories — provided the reliance is documented and the QP retains ultimate responsibility."
  },
  {
   "type": "p",
   "html": "A receipt that omitted this would misrepresent the act. A QP does not personally re-test every result; they certify on the basis of a documented chain. So the receipt carries the chain: each confirmation it relies on is itself a signed statement, referenced by hash. Verification then answers a richer question than the paper does today — not merely <em>did the QP certify</em>, but <em>on what documented basis</em>."
  },
  {
   "type": "p",
   "html": "This is a case where making the artefact verifiable also makes it more honest, which is usually the sign that the design is right."
  },
  {
   "type": "h2",
   "text": "Who gains, in order"
  },
  {
   "type": "ol",
   "items": [
    "<strong style=\"font-weight:600\">The QP.</strong> Personal liability without personally verifiable evidence is an uncomfortable position. A signed receipt is the QP's own record, not their employer's.",
    "<strong style=\"font-weight:600\">Wholesalers and importers.</strong> Verification stops being a relationship question.",
    "<strong style=\"font-weight:600\">Competent authorities.</strong> Inspection and market surveillance gain an artefact that can be checked without a request to the MAH.",
    "<strong style=\"font-weight:600\">The MAH.</strong> Fewer documentation disputes, faster release of held consignments."
   ]
  },
  {
   "type": "h2",
   "text": "The honest constraints"
  },
  {
   "type": "p",
   "html": "Two, stated plainly. First, a receipt is not a legal instrument recognised by any authority; certification remains governed by Annex 16 and national implementation, and this sits alongside rather than inside that framework. Second, adoption has a network property: a receipt only helps a downstream party who knows to check it, so early value comes from bilateral arrangements rather than from ecosystem effects."
  },
  {
   "type": "p",
   "html": "Neither constraint prevents a single MAH from starting with one product family and one distribution channel, which is how every verifiable-document scheme that eventually worked actually began."
  },
  {
   "type": "h2",
   "text": "Why the QP is an unusual case"
  },
  {
   "type": "table",
   "caption": "What makes this different from ordinary approval",
   "head": [
    "Property",
    "Consequence"
   ],
   "rows": [
    [
     "Personal legal liability",
     "The individual, not only the company, is answerable"
    ],
    [
     "Named on a manufacturing authorisation",
     "Their identity is a regulated fact"
    ],
    [
     "Decision is per batch",
     "High volume, individually consequential"
    ],
    [
     "<strong style=\"font-weight:600\">Evidence held internally</strong>",
     "<strong style=\"font-weight:600\">Nobody downstream can test it</strong>"
    ]
   ]
  },
  {
   "type": "p",
   "html": "The mismatch between personal liability and institutional evidence is the whole argument. A QP carrying personal responsibility should have an artefact they can produce independently of their employer's systems, including after they leave."
  },
  {
   "type": "h2",
   "text": "Objections and honest limits"
  },
  {
   "type": "p",
   "html": "<strong style=\"font-weight:600\">“The register is the legal record.”</strong> It is, and it sits in a system the QP does not control and may lose access to. Their liability does not end with their employment."
  },
  {
   "type": "p",
   "html": "<strong style=\"font-weight:600\">“Downstream parties rely on the authorisation, not the batch.”</strong> For routine purposes, yes. When a batch is questioned, the specific certification becomes the artefact, and at that point its testability matters."
  }
 ],
 "faq": [
  {
   "q": "Does this change the QP's legal responsibility?",
   "a": "No. Responsibility is set by Directive 2001/83/EC and national implementation. The receipt changes only what can be demonstrated about the certification afterwards."
  },
  {
   "q": "How does it handle reliance under Annex 16?",
   "a": "By representing it explicitly: the receipt references the signed confirmations relied upon rather than implying the QP assessed everything personally."
  },
  {
   "q": "Will it still verify in fifteen years?",
   "a": "That is a design requirement, not an afterthought. Issuer keys are published with validity periods and retained historically, so a receipt verifies against the key that was valid at issuance."
  },
  {
   "q": "Is this an alternative to serialisation?",
   "a": "No. Serialisation verifies the pack; this verifies the release decision. They address different questions and are complementary."
  },
  {
   "q": "Why should a QP hold their own copy?",
   "a": "Because the liability is personal and outlives their employment, while the record sits in an employer's system they may lose access to."
  },
  {
   "q": "Can downstream parties verify a certification today?",
   "a": "No. It is an internal register entry or PDF, testable only by asking the manufacturer."
  },
  {
   "q": "What should the signature bind?",
   "a": "The batch record digest, so the certification demonstrably covers what the QP reviewed."
  }
 ],
 "sources": [
  {
   "t": "EudraLex Volume 4 — EU GMP guidelines",
   "u": "https://health.ec.europa.eu/medicinal-products/eudralex/eudralex-volume-4_en"
  },
  {
   "t": "Directive 2011/62/EU — Falsified Medicines Directive."
  },
  {
   "t": "21 CFR Part 11 — electronic records and signatures",
   "u": "https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11"
  }
 ],
 "related": [
  {
   "slug": "part-11-signature-evidentiary-ladder",
   "title": "A username and a password: what a GxP signature proves",
   "category": "AEO"
  },
  {
   "slug": "cross-boundary-oversight-chain",
   "title": "Sponsor oversight across the CRO and CDMO boundary",
   "category": "Compliance"
  },
  {
   "slug": "exception-disposition-receipt",
   "title": "Signing the deviation, not the dashboard",
   "category": "Compliance"
  }
 ],
 "wordcount": 991,
 "url": "/blog/qp-certification-receipt.html",
 "reading_time": "4 min read",
 "image_title": "QP Certification Receipt",
 "seo_title": "QP batch release across the EU supply chain",
 "meta_description": "A Qualified Person accepts personal legal liability for certifying each batch. The artefact carrying it is a PDF or a register entry.",
 "hub": {
  "slug": "topics/gxp-identity",
  "title": "Pharma and GxP identity"
 },
 "answer": "Not by anyone downstream. A Qualified Person accepts personal legal liability for certifying each batch for EU release, and the artefact carrying that certification is a PDF or a register entry inside one company's system. A party receiving the product cannot test it.",
 "answer_q": "Can a QP certification be verified across a supply chain?",
 "glossary": [
  {
   "term": "Qualified Person",
   "def": "The individual who certifies batches for release in the EU, carrying personal legal responsibility."
  },
  {
   "term": "Batch certification",
   "def": "The act permitting a batch to be placed on the market, performed per batch."
  },
  {
   "term": "Manufacturing authorisation",
   "def": "The site licence naming the QPs, which makes their identity a regulated fact."
  }
 ],
 "checklist": {
  "title": "Making a certification portable",
  "id": "qp",
  "desc": "Four steps.",
  "steps": [
   {
    "name": "Sign as the QP, not as an account.",
    "text": "Personal credential, personal liability."
   },
   {
    "name": "Bind the batch record digest.",
    "text": "So the certification covers what was reviewed."
   },
   {
    "name": "Give the QP a copy.",
    "text": "Their liability outlives their employment."
   },
   {
    "name": "Publish the site key.",
    "text": "So a downstream party can verify without contacting you."
   }
  ]
 },
 "cta": {
  "title": "Where this fits in Manav",
  "html": "Manav binds the signer to the exact record being certified, on a credential under their sole control, and produces a receipt an inspector can verify years later without access to the manufacturing system.",
  "href": "../docs.html",
  "label": "See signature binding"
 }
}