TL;DR
We show procurement, QA, and QC teams how to use a steroid API COA as a batch-review tool. A passing COA supports review, but we also reconcile shipment identity, interpret assay and impurity data, assess water and solvent results, request missing evidence, and complete incoming verification through an approved quality system.
A Certificate of Analysis (COA) is one of the first documents a buyer should review when an API shipment arrives. It provides batch-specific analytical evidence from the supplier, but it does not replace supplier qualification, incoming testing, or the buyer's own quality procedures. Before accepting a steroid API shipment, procurement and quality teams should confirm that the document, analytical results, approved specification, and physical shipment all agree.
A steroid API COA should identify the exact material, batch, specification, test methods, acceptance limits, and actual results. Depending on the molecule, the review may include identity, assay, related substances, residual solvents, water content, and other molecule-specific tests. The document should also contain appropriate release authorization and information that allows the batch to be traced back to the supplied material.
This guide provides a practical sequence for reviewing an API certificate before batch acceptance. It also explains what to check when results are unclear, close to specification limits, or inconsistent with the shipment.
What Should You Check First on a COA?
Review the document in a consistent order rather than jumping directly to the assay result. Start with the material and batch identity, then confirm the applicable specification and methods before interpreting the analytical results. Finally, reconcile the document with the shipment and verify that the release information is complete.
A practical review sequence is:
-
API name and chemical form
-
Batch or lot number
-
Manufacturer and manufacturing site
-
Manufacturing date and retest or expiry information, where applicable
-
Specification and specification revision
-
Analytical methods
-
Identity
-
Assay and calculation basis
-
Related substances
-
Residual solvents
-
Water content
-
Other molecule-specific tests
-
Authorized release or signature
-
Shipment and packaging details
The sequence matters because an excellent analytical result is not useful if it belongs to the wrong batch or was compared with an outdated specification.
What Does a COA Actually Prove?
A COA provides the supplier's batch-specific analytical evidence against an established specification. It can show what was tested, which method was used, what acceptance criteria applied, and what result was obtained for that particular batch. Under ICH Q7, API certificates include information such as the API name, batch number, release date, tests performed, acceptance criteria, results, and authorized approval.
A COA should therefore be treated as one part of the batch-release documentation package. It does not independently establish that the supplier is qualified, that the manufacturing site remains acceptable, or that the buyer's incoming-testing requirements have been satisfied. Those decisions require additional quality and supplier controls.
It helps to separate three activities:
Activity | What It Means |
COA review | Review the supplier's batch-specific analytical evidence |
Incoming testing | Verify the material through the buyer's own approved testing process |
Supplier qualification | Assess the supplier, manufacturing site, quality system, and broader supply capability |
This distinction is particularly important for regulated manufacturing. A passing certificate can support batch review, but it should not be treated as a substitute for the buyer's established quality system.
Check Identity and Chemical Form
Identity should be reviewed before interpreting assay or purity results. The test should provide sufficient confidence that the material is the intended API and, where necessary, distinguish it from closely related compounds. FDA Q6A notes that identity procedures should have appropriate specificity, so a single chromatographic retention time may not always be sufficient on its own.
The chemical form on the document should also match the purchase order, approved specification, and material requirement. This matters where steroid APIs are available as different salts, esters, stereochemical forms, or other related forms. A COA can therefore look complete while still describing a material that does not match the buyer's approved requirement.
Understand Assay and Its Calculation Basis
Assay indicates the amount of API measured using a defined analytical procedure and calculation basis. Before comparing the number with the specification, check the method, acceptance range, units, and whether the result is reported on an as-is, dried, or anhydrous basis. This is particularly relevant when the API will be used as a Pharma API in regulated manufacturing.
For example, suppose one batch reports 98.8% assay on an as-is basis while another reports 99.4% on an anhydrous basis. The two numbers cannot automatically be compared because the second calculation excludes the effect of water. The water result and stated calculation basis must be understood before using either number for manufacturing calculations or supplier comparison.
This is why a high assay value should never be reviewed in isolation. Confirm what the number represents before deciding whether the batch meets the approved requirement.
Do Not Treat 99% Purity as 99% Assay
Purity and assay can describe different analytical measurements. A chromatographic purity result may describe the proportion of detected components attributed to the API under a defined calculation, while assay measures API content using its specified analytical procedure. A statement such as “99% purity” therefore does not automatically mean that the API has a 99% assay.
For example, a material could show 99.2% chromatographic purity while its assay is 98.7%, depending on the methods and calculation basis. Water, residual solvents, analytical methodology, and the components included in each calculation can all affect how the results are interpreted. Buyers should therefore review purity, assay, water, residual solvents, and related substances together.
Review Related Substances and Impurity Results
Related substances provide information about the impurity profile of a batch. The review should consider specified impurities, unspecified impurities, total impurities, and unexpected or unidentified peaks where applicable. The important question is whether the reported profile meets the approved, molecule-specific specification and whether anything unusual requires investigation.
ICH Q3A provides reporting thresholds for new drug substances, including a 0.05% reporting threshold under specified conditions for substances with a maximum daily dose of 2 g or less. This threshold provides regulatory context, but it should not automatically be treated as the purchasing limit for every steroid API. The applicable specification, molecule-specific assessment, intended use, and market requirements remain the basis for acceptance.
If an impurity, assay result, or another critical attribute is unusually close to its acceptance limit, do not assume that the batch should automatically be rejected or accepted. Depending on the situation, the buyer may need chromatograms, additional analytical data, historical batch information, method details, or clarification from the supplier. The purpose is to understand whether the result is normal process variation or something that requires further investigation.
Confirm the Specification Before Reviewing Results
The specification should be identified before the analytical results are assessed. Check the specification name, revision or version, acceptance criteria, and applicable pharmacopoeial or in-house reference. USP, BP, Ph. Eur., and JP references may be relevant depending on the API and market, but simply naming a pharmacopoeia does not establish that every applicable requirement has been met.
An in-house specification is not automatically a concern. However, the buyer should understand what it covers, which methods support it, what the acceptance limits are, and whether the specification is the currently approved version. Comparing a current COA with an outdated specification can lead to an incorrect batch-release decision.
The same issue applies when a COA simply states “complies.” For critical attributes, actual numerical results are generally more useful because they allow the buyer to identify trends, assess proximity to limits, and investigate unusual results.
Check Residual Solvents, Water, and Other Tests
Residual solvents should be reviewed against the applicable specification and analytical method. The result should identify the relevant solvent or reporting approach rather than leaving the buyer to infer what was tested. Water content should also be considered alongside the assay calculation basis and any applicable storage or stability requirements.
Other tests depend on the specific API. These may include elemental impurities, physical characteristics, particle-size information, microbiological attributes, or other molecule-specific requirements where applicable. Buyers should therefore avoid using a generic checklist as a substitute for the approved product specification.
Check COA Authenticity and Release Information
A technically complete COA should also be internally consistent. Check the API name, batch number, manufacturer identity, manufacturing site, release date, issue date, and authorized approval or signature. Where applicable, also check the document format or revision to ensure the certificate is the current version used by the supplier.
The release information should connect the analytical results to an authorized quality decision. If the manufacturer, site, batch number, or release information is unclear, the buyer should resolve the discrepancy before proceeding. Document authenticity is not merely an administrative issue because incorrect batch documentation can undermine traceability.
Reconcile the COA With the Actual Shipment
The certificate should match the material that physically arrived. Compare the API name, chemical form or grade, batch number, quantity, container labels, relevant dates, and packaging information against the purchase order and packing or shipping documents.
Manufacturing and retest dates should also be reviewed where applicable. Some APIs may use a retest date rather than an expiry date, depending on the product and established stability programme. The terminology and applicable period should therefore be checked against the supplier's approved documentation rather than assuming that every API follows the same date system.
Any mismatch should be investigated before the material is accepted into the manufacturing workflow.
What Does a Practical COA Review Look Like?
Consider a hypothetical batch with the following results:
Test | Specification | Reported Result | Review |
Identity | Conforms | Conforms | Confirm method and chemical form |
Assay | 98.0–101.0% | 99.1% | Within limit; confirm calculation basis |
Related substance A | NMT 0.20% | 0.18% | Within limit but relatively close |
Total impurities | NMT 1.0% | 0.42% | Within limit |
Water | NMT 1.0% | 0.7% | Review with assay basis |
Residual solvent | NMT applicable limit | Pass | Confirm method and individual results where required |
The 99.1% assay does not need to be interpreted without context. The reviewer should first confirm whether it is reported as-is, dried, or on another basis, then assess the water result and applicable method. The 0.18% impurity is within the stated limit, but because it is relatively close to the 0.20% specification, the reviewer may choose to examine the chromatogram, historical trend, or supplier clarification depending on the buyer's quality procedure.
The example illustrates why a COA should be reviewed as a complete document rather than as a list of pass/fail numbers.
COA Red Flags to Watch For
Some discrepancies deserve immediate clarification before batch disposition. Common red flags include:
-
Missing or inconsistent batch number
-
API name or chemical form that does not match the purchase requirement
-
Generic or incomplete specification
-
Outdated specification or unclear revision
-
“Complies” without useful analytical results
-
Missing analytical method information
-
Unexpected impurity peaks or incomplete impurity reporting
-
Results unusually close to acceptance limits
-
Missing manufacturer or manufacturing-site information
-
Unclear release authorization
-
COA dates that conflict with shipment documents
-
Container labels that do not match the certificate
-
Quantity or grade mismatch between documents
-
Unclear retest or expiry information where applicable
A red flag does not automatically mean that the material fails specification. It means that the available evidence is incomplete, inconsistent, or unusual enough to require review before acceptance.
How Aarise Pharma Supports API Documentation Review
For companies sourcing APIs, Aarise Pharma can support discussions around product requirements, batch documentation, analytical information, manufacturing-source details, and supply requirements. The exact documentation available will depend on the API, source, specification, and intended application.
Buyers should continue to apply their own supplier qualification, sampling, identity testing, incoming-testing, and market-specific requirements. A supplier's documentation should support that review rather than replace the buyer's quality system. For API sourcing or documentation questions, contact our team with the specific product and requirement.
Frequently Asked Questions
What Should I Check First on a Steroid API COA?
Start with the API name, chemical form, batch number, manufacturer, site, dates, specification, and specification revision. Then review the analytical methods and results for identity, assay, impurities, residual solvents, water, and other applicable tests. Finish by checking authorization and reconciling the certificate with the shipment documents.
What Are the Most Common COA Discrepancies?
Common issues include incorrect batch numbers, mismatched API forms, outdated specifications, missing methods, incomplete results, unclear release authorization, and differences between the certificate and container labels. Date or quantity discrepancies can also create traceability problems. Any inconsistency should be investigated before the batch is accepted.
What Should I Do if a Result Is Close to the Specification Limit?
A result close to the limit should be reviewed in context rather than automatically accepted or rejected. Depending on the quality procedure, the buyer may request chromatograms, additional analytical information, historical trends, method details, or supplier clarification. The decision should follow the approved specification and quality system.
Can I Accept an API Based Only on the Supplier's COA?
Not necessarily. The COA provides batch-specific evidence from the supplier, while the buyer may have separate supplier qualification, sampling, identity-testing, and incoming-testing requirements. The batch should be accepted according to the buyer's approved quality procedures.
How Do I Verify That the COA Matches the Actual Shipment?
Compare the API name, chemical form or grade, batch number, quantity, container labels, manufacturer, relevant dates, and packaging information. These details should agree across the COA, purchase order, packing or shipping documents, and physical shipment. Any mismatch should be resolved before disposition.
Why Is the Assay Basis Important?
Assay values reported on different bases may not be directly comparable. An as-is result can include the effect of water or other measured components, while a dried or anhydrous basis adjusts the calculation differently. Always confirm the stated basis before comparing results or calculating manufacturing quantities.
Can a COA Replace Supplier Qualification?
No. A certificate describes the analytical results of a particular batch, while supplier qualification assesses the broader manufacturing, quality, regulatory, and supply capabilities of the source. Both are important parts of a controlled API procurement programme.
Final Takeaway
A COA is an important part of API batch review, but it is not the entire release decision. The practical approach is to verify the material and batch first, identify the correct specification and revision, understand the analytical methods and calculation basis, review critical results, and investigate anything unusual or inconsistent.
The final check should connect the certificate to the physical shipment and the buyer's own quality system. When the COA, specification, shipment documentation, and incoming-testing requirements all align, the buyer has a much stronger basis for making a controlled batch-release decision.
