Does A Certificate of Analysis Expire? Gaps In The File

Last month a buyer in Hyderabad sent us a question that looked simple and was not. The certificate of analysis in his file was fourteen months old, the drums were still sealed, and his auditor wanted to know whether the document still counted. Could he release against it, or did he need new paper?

The question deserves a direct answer, but the document he was worried about is the wrong one.

A certificate of analysis never expires the way a perishable good does. No validity field is printed on the document, and no marking on it loses force after twelve months. What decides whether the paper still counts sits elsewhere: three dates, none of which is the issue date.

The short answer first. A certificate of analysis is bound to one identified batch, and it goes stale in three ways — the drums in front of you are not the batch it describes, the retest period on that batch has closed without a retest, or the specification it reports against has since been revised. Note what that list does not contain: no date printed on the certificate. All three checks take under five minutes at a desk, and two need nothing more than the receiving file.

The Three Dates People Keep Mixing Up

Certificate headers carry a cluster of dates: production, issue, sometimes a review date. Buyers pick the most visible one and start counting months. That is almost always the issue date, sitting next to the signature block, and it is almost always the wrong one.

Date on the fileWhat it controlsWhat it does not do
Production dateAnchors the batch. When the manufacturer assigns a retest period, the clock starts from this day — not from shipping, invoicing, or order confirmation.Says nothing about document validity. A certificate issued two days after production and one issued ten months later can both be perfectly valid.
Issue dateWhen this document was generated and signed. Useful for confirming that the specification version quoted was current at issuance.Does not expire the certificate. An old issue date is a prompt to ask questions, not a verdict.
Retest / expiry dateThe only date with real teeth. Once it passes, the material needs retesting before use, and the original certificate is no longer sufficient on its own.Not always present. If the field is blank, the question moves to the specification sheet or the quality agreement, and the supplier should state where it is defined.

The issue date comes up constantly in buyer questions. It is visible and looks authoritative, and counting from it feels like diligence. But the question that counting answers — “is this document old?” — is not the question that matters. How the retest period is actually set is a question about the material and the data underneath it; whether the certificate counts is a question about the paper and the batch it names. Ask them of the wrong document and the answers will be reassuring and irrelevant at the same time.

The First Way A Certificate Goes Stale: Wrong Batch

This is by far the most common cause, and it has nothing to do with time.

A certificate of analysis reports results for one identified batch. Not a product, not a grade — one batch, one string of characters. The moment the drums in front of you carry a different string, the certificate is not “old”. It is describing a different material, and it could have been issued that same morning and still carry no evidentiary value for your lot.

The mismatch arises in two places, neither of them unusual. Sales desks reuse a presentable PDF across enquiries without verifying that the batch on the paper matches the batch on the offer. Receiving clerks file three documents from one envelope without noticing that the certificate says 24K-0332 while the drum sticker says 24K-0382. Neither case involves bad faith, and both leave a file that an auditor can pull apart with a single question.

January and February are our peak months for seeing this. Year-end shipments accumulate, the clerk doing the filing is not the person who negotiated the order, and one of our own despatch files once carried a certificate under the wrong drum number for weeks before anyone noticed. The document was fine. The folder was wrong. That is the level this check operates at: physical, routine, a copy-and-compare exercise.

So check the batch string first — it is the same reason the identifier that ties the paper to the drum matters more than any date printed on the certificate. If the strings do not match, the age question is irrelevant. You need the right certificate, not an older one.

The Second Way: The Retest Window Closes

This is where the document and the material finally meet.

When an intermediate is produced, the manufacturer assigns it an expiry date or a retest period, and that assignment rests on data — the ICH quality guideline family lays out the regulatory logic across Q7 and the stability-adjacent texts. Once the period lapses, the material must be retested before use. For the buyer holding the certificate, the consequence is specific: after the retest date, the original certificate stops being sufficient evidence on its own.

The results on it were true of the material as it was — not as it is now, on paper, even if the powder itself has not changed.

This is not a claim that anything degraded. Plenty of intermediates retest well within limits years past the window. The claim concerns evidence: a moment has passed, and the only way to extend the record is a new result — a retest by the supplier, with a fresh certificate referencing the same batch and the new date.

The practical response is narrow. Do not debate whether the material has degraded; request a retest certificate. A supplier who provides one within a week is demonstrating a functioning quality system. A supplier who argues the point instead is also communicating something.

The Third Way: The Specification Moved

The least visible of the three, and the one that catches experienced buyers precisely because nothing looks wrong.

A certificate is only as current as the specification it reports against. And specifications are revised: a limit is tightened, a method is updated to a newer edition, or a parameter is added that was not previously tested. When that happens, an older certificate can be internally consistent, freshly signed, batch-matched — and still describe the material against a standard you no longer accept.

Catching this takes one comparison. The certificate quotes a specification version or revision date; the specification sheet in your file quotes one too. Placed side by side, that is the whole test. How acceptance criteria get set and revised is worth understanding for exactly this moment: if your file holds version 3 of the specification and the certificate quotes version 2, there is a gap between what was measured and what you need measured. Sometimes the gap is cosmetic. Sometimes the parameters your release decision depends on were never tested at all.

We encountered this on our own side once. A buyer’s auditor flagged that our certificates quoted a water-content method edition that had been superseded two years earlier. The results were fine; the method reference was stale. A week and a template update fixed it, but the auditor’s point stood: a certificate quoting a superseded method edition is a document from an older quality system, whatever its issue date says.

What An Auditor Reads First

Now consider the same file from the auditor’s side. A receiving file for an imported intermediate holds the certificate, the packing list, the invoice, and whatever else the supplier enclosed. The certificate is the first page they touch, and they read it in a strict order.

Batch, first. The string on the certificate against the string on the drum, the packing list, the invoice — character for character, not the age of the paper. The geography paper in the same envelope is pulled into the same cross-check, because a consignee or origin mismatch raises exactly the questions auditors like least.

Specification, second: the current version, method editions still in force, revision dates that reconcile.

Dates, last. Production date anchoring the batch. Retest or expiry date against today. Issue date as a sanity check, nothing more. An auditor who finds a fourteen-month-old certificate with a matching batch, a current specification and an open window will pass the file without a second look; a two-month-old certificate for the wrong batch stops the same file.

Age is the third question. Most buying desks treat it as the first. Correcting that inversion is the single most useful change a receiving desk can make.

Five Checks At The Desk, Five Minutes Total

None of this requires a laboratory or a procedure rewrite. It requires a habit: the same five checks, in the same order, every time a document envelope lands on the desk.

Batch string: certificate against drum sticker against packing list. Three sources, one string of characters, and any mismatch halts acceptance. This is also the check that catches reused PDFs, and how a faked certificate gives itself away usually starts in the same place — forgery and staleness fail at the same checkpoint.

Retest or expiry date against today. If the window has closed, the conversation with the supplier changes shape: accept-or-reject becomes retest-or-return.

Specification version against the sheet in your file. Same version, same method editions, or a written explanation of the difference — in writing, before the goods ship, not after.

Signature and issuer. A certificate signed by the supplier’s own quality unit is normal and acceptable for intermediates; a missing signature block, or a generic mailbox as the contact, is not. The line-by-line way to read a certificate covers the remaining header fields in detail.

Internal consistency. Results sitting exactly on every limit — which almost never happens with real data. Units that do not match the method. A purity figure with no reference point. Stale documents and fabricated ones share a symptom: they stop making internal sense.

Five minutes in total; run in order, they answer the fourteen-months question every time.

A note on who runs them. On most receiving desks the envelope lands with the warehouse clerk — the busiest person in the building and the least equipped to judge a specification revision. So the checks have to be crude enough to survive that: copy-paste the batch strings, no eyeballing; write today’s date on the folder next to the retest date in highlighter; send the specification-version question to the supplier’s contact before the container arrives. The buyers who get this right are not the ones with the most sophisticated QC. They are the ones who designed the clerk’s task so it cannot be done wrong.

When The Paper Really Has Gone Stale

If the checks fail — the window has closed or the specification has moved, and the drums are already in your warehouse — the sequence is straightforward.

Order a retest. A clean result repairs the file: new certificate, same batch, new retest period, with both documents kept in the receiving record. If the supplier cannot or will not retest, or the retest raises questions of its own, that is where a third-party result settles it — one certificate you commissioned, against a method both sides agreed in advance.

Then write the rule down before the next order. One line in the quality agreement or the receiving procedure: which dates are checked, against what, and who signs off. The clause that makes document freshness contractual costs one email to add and one signature to activate.

The buyer from Hyderabad? His certificate was batch-matched, current against the specification, and four months inside an open retest window. It counted. He had been counting from the issue date — the one date on the page that decides nothing.

In one sentence: the age of a certificate of analysis is a question, never the answer. The batch, the retest window, and the specification are the answer. Check them in that order.

Scroll to Top

Contact us to Get the Best Product Solution