GMP Audits and Pharmacopoeias: Defending USP vs. Ph. Eur. Decisions (QA/QC)

The scene that keeps repeating (and that you can prevent)

Inspector: “Which pharmacopoeia do you follow for this test?”
QC: “We follow the Ph. Eur.”
Inspector: “And for batches destined for the US market, where do you demonstrate USP coverage?”
(Long pause. Glances exchanged. A deviation is opened.)

During audits, this is the issue I encounter most often:
companies have data, but they lack a structured evidence package that clearly links compendial requirements → methods → results → QA decisions.
Without that linkage, even a good laboratory appears “out of control.”

The obsolete (and risky) myth

“In an audit, it’s enough to say that the internal method is equivalent.”

No. In an audit, saying it is not enough.
You must prove it.

A statement without:

• a comparability protocol
• a data-backed report
• acceptance criteria
• QA approval
• change control
• assessed regulatory impact

…is perceived as a shortcut. And the inspector will treat it as such.

The 6 areas where most findings arise (FDA/EMA) on compendial divergences

1) “Missing” compendial tests

Typical case: a test required by USP is not performed because “it’s not required in the EU.”
Outcome: observation for incomplete quality control / incomplete batch release data.

Technical terms (LSI): 21 CFR Part 211, EU GMP, batch release, CoA, QP release, data review, discrepancy.

2) Uncontrolled versions/editions

This is not “just documentation”:
if you are using an outdated edition, you may be applying a standard that is no longer current.

Antidote: a compendial monitoring procedure with:

• defined frequency
• clear ownership (who assesses the impact?)
• mandatory change control when methods/specifications are affected

3) Alternative methods without a “comparability pack”

If you have chosen a single method to cover both USP and Ph. Eur., you must have:

• ICH Q2 method validation
• comparability with the compendial method (or with both, if they diverge)
• a scientific rationale (fitness for purpose, not less discriminatory)

4) “Stricter” global specifications without justification

Specifications tighter than a compendium are often acceptable, but they can lead to:

• more OOTs (out of trend)
• more OOSs (out of specification)
• more deviations and CAPAs

In an audit, you will be asked: “Why did you impose this limit on yourselves?”
You need a Justification Report (trending, process capability, stability, risk assessment).

5) Reference Standards and reference materials

If you claim alignment with USP/Ph. Eur., you must control:

• USP Reference Standards vs. EDQM CRS
• qualification of secondary standards
• management of expiry dates, certificates, and traceability

This is a classic audit topic—often underestimated.

6) Data Integrity: the risk “multiplier”

When compendial divergences exist, the following increase:

• calculations
• transcriptions
• conversions
• “interpretative” decisions

If ALCOA+ (attributable, legible, contemporaneous, original, accurate + complete, consistent, enduring, available) is not properly controlled, the divergence becomes a problem accelerator.

The “Audit Defense Table”: typical questions and inspector-proof answers

Your “Compendial Audit Pack” (what I recommend having ready)

If you had to choose only what really saves time and prevents findings, this is the minimum list:

• Compendial Applicability Matrix (CAM)
• USP vs. Ph. Eur. gap table per product (API + finished product)
• Decision log: for each divergence → choice + rationale
• Validation summary (ICH Q2) + comparability report (if single method)
• Risk assessment (ICH Q9) for omitted/rationalised tests
• Change controls demonstrating lifecycle management
• Evidence of qualified instrumentation (IQ/OQ/PQ) and system suitability
• Personnel training on compendial differences
• Controlled extracts (not “loose copies”) of relevant monographs/chapters
• Example CoAs for different markets with consistent logic

From a manufacturing perspective, the main challenge is this:
if QA does not properly “package” the Compendial Audit Pack, operations become fragile and the risk shifts to individuals (“if X is on holiday, no one knows how to answer”).

KEY POINTS TO REMEMBER

• In an audit, the question is not “did you perform many tests?”, but “did you cover the applicable requirements—and can you prove it?”
• “Alternative method” without comparability = vulnerability.
• The strongest defense is decision traceability: requirement → choice → evidence → approval.

FAQ

1) Can an inspector challenge an internal method even if it is validated?
Yes—if you cannot demonstrate its suitability against the applicable standard (comparability, specificity, sensitivity, range, robustness).

2) What makes a decision defensible when USP and Ph. Eur. diverge?
A coherent documentation package: decision log, risk assessment, validation and comparability, change control.

3) Are global specifications or market-specific specifications better to reduce findings?
It depends. What matters is that batch release demonstrates that the batch destined for a given market meets that market’s requirements.

4) What is the warning sign that a finding is coming?
When answers are verbal and no single document exists that reconstructs the decision logic.

Do you want a Compendial Audit Pack template, examples of USP/Ph. Eur. gap tables, and ready-to-use QA/QC checklists?
You’ll find the complete guide “Pharmacopoeias Compared” on guidegxp.com.