A supplier file can contain a certificate that was current when it was uploaded but expires before the work begins. Staff may notice the document is present without noticing the date mismatch. An automated renewal queue can make that mismatch visible, as long as it does not turn document extraction into a legal or technical eligibility decision.
The proposed workflow below identifies the supplier document, extracts its stated validity period and compares it with the approved project window. It prepares a reviewable follow-up item. The procurement owner remains responsible for the applicable requirements, authenticity checks and decision to use the supplier.
Identify the document before extracting its dates
Match the certificate to a verified supplier reference and document category. A company display name alone can be ambiguous, and a file called latest certificate may be an older copy. Record the source file, version and extraction status rather than relying on the filename.
Distinguish issue date, valid-from date, expiry date and other dates in the document. A stamp date or payment date is not automatically the end of validity. Preserve the exact wording and page or section reference for each candidate. If the document describes a condition rather than a fixed expiry, record that condition for review instead of manufacturing a date.
Google's Document AI overview describes OCR, text and layout extraction, classification and structured field extraction. Those capabilities can support the preparation stage, but do not verify a certificate's authenticity or establish that it satisfies a procurement requirement. Source: Google Document AI overview
Confirm the project window and comparison rule
Use the approved project record for the start and, where relevant, end date. Do not compare against an unconfirmed date mentioned in an email. Record the project version because a delayed start can change the timing result, while an earlier start can remove the time available for renewal.
Have the procurement owner define whether the relevant document must cover the start, a particular activity or the whole project window. This is a requirement decision outside the model. A certificate that reaches the start but expires during the work may need a different flag from one that expires beforehand.
Also decide how exact date boundaries are interpreted. The workflow should not guess whether a stated expiry includes the whole date or which timezone applies to a timestamp. Preserve uncertain wording and ask the responsible reviewer. Do not present a proposed internal comparison convention as a legal interpretation of validity.
Supplier-document renewal queue
Use this complete hypothetical queue and processing contract. All supplier references and dates are fictitious; the comparison rules require owner approval before live use.
Project: TEST-PROJECT-A, approved start 2 November 2026 and planned end 20 November 2026. Proposed queue rule: distinguish expiry before start, expiry within the window, adequate recorded coverage for the chosen window and unresolved evidence. None of these labels establishes eligibility.
| Supplier and source | Extracted evidence | Timing flag | Reviewable next step |
|---|---|---|---|
| TEST-SUPPLIER-A, file CERT-A page 1 | Stated expiry 30 October 2026; supplier reference matches | Recorded expiry precedes approved start | Procurement owner verifies the document and drafts a renewal request |
| TEST-SUPPLIER-B, file CERT-B page 2 | Stated expiry 10 November 2026 | Starts covered under the proposed comparison, but expiry falls within project window | Owner checks required coverage and plans appropriate follow-up |
| TEST-SUPPLIER-C, file CERT-C page 1 | Stated expiry 30 November 2026 | Recorded date extends beyond planned end | Keep source and review status; do not label legally eligible |
| TEST-SUPPLIER-D, file CERT-D | Issue date visible; expiry section unreadable | Validity unresolved | Request a readable approved source through the procurement process |
| TEST-SUPPLIER-E, CERT-E1 and CERT-E2 | Two copies state different expiry dates | Conflicting document evidence | Hold timing conclusion until the owner identifies the authoritative version |
Each queue item stores supplier reference, project reference and version, document category, source reference, extracted validity wording, interpreted date with review status, comparison rule version, timing flag, follow-up owner and proposal status. A follow-up task remains a draft until the configured review and task-creation rules are met.
Change handling: recompute affected items when the approved project window or authoritative certificate changes. Retain the earlier result's reference and mark it superseded rather than silently overwriting the reason for the original follow-up. If a renewal task already exists, update or link it under the owner's rule instead of creating another copy.
Acceptance cases: a clear expiry before start; expiry inside the project window; expiry after the end; missing validity; conflicting copies; and a changed project start. Verify the extracted source wording, deterministic comparison, queue disposition and absence of unintended external messages. The owner decides which items require action and what evidence is needed to close them.
The queue is complete when every supplied certificate has a traceable disposition and unresolved cases have owners. A row labelled recorded coverage adequate only answers the selected date-comparison question, not the broader supplier-approval question.
Validate extracted fields without inventing missing values
OpenAI's Structured Outputs guide documents schema-constrained responses and refusals. A schema can require separate fields for issue date, validity date, source and uncertainty. It does not guarantee that the model selected the correct date or read a poor scan accurately. Source: OpenAI structured outputs
Compare the extracted wording with the actual page for affected items. Use an explicit missing or unreadable status instead of a plausible replacement date. If extraction fails, keep the original source unchanged and route the issue to the designated procurement owner.
Document category also needs checking. An insurance schedule, training certificate and supplier declaration may contain different date purposes and requirements. The workflow can classify candidates, but the owner must confirm the category before applying its approved comparison rule.
Work through normal, missing and duplicate evidence
In a hypothetical normal case, TEST-SUPPLIER-A's readable document clearly states an expiry of 30 October. The approved project begins on 2 November. The queue flags that recorded expiry precedes the start, cites the page and prepares a renewal follow-up for review. It does not assert that the supplier may or may not perform the work.
In a missing-date case, the scan shows only an issue date. The assistant records validity unresolved and identifies the unreadable section. It does not add a common-looking annual expiry or infer validity from the document's age. The owner obtains the necessary evidence through the approved route.
In a duplicate case, two files have the same certificate number but different validity text. Filename recency is insufficient to choose the authoritative record. Preserve both references and hold the timing conclusion until the owner resolves the difference. One unresolved supplier item can refer to both copies without creating duplicate renewal tasks.
Keep renewal proposals separate from execution
OpenAI's function-calling guide distinguishes a model request from application execution and returned output. Apply that distinction to task creation and supplier contact: a proposed follow-up is not a sent renewal request or completed task. Source: OpenAI function calling
The application should check the approved supplier target, recipient, project and existing task before executing an authorised follow-up. If the operation's outcome is uncertain, reconcile it rather than sending the same request again. Completion should mean the verified action occurred, while renewed-document review remains a separate stage.
FAQ about certificate-expiry automation
Can the queue declare a supplier eligible for the project?
No. This design flags recorded document timing against an owner-approved rule. Authenticity, applicability and legal or technical requirements need the responsible procurement and qualified review processes.
What if a certificate expires during the project rather than before it?
Show that separate timing condition and ask the owner which coverage requirement applies. Do not assume that coverage at the start is sufficient for the whole activity.
How should a new certificate close an existing renewal item?
Match the verified supplier and document category, review the new evidence and recompute the approved comparison. Record which item it supersedes and the owner's closure decision. Upload presence alone is not acceptance.
If your business needs help defining this process, explore Document processing, the wider AI automation services, and our custom-agent workflow guide. The agents and automation comparison and custom AI agent glossary explain the terms. To discuss your records and approval rules, get in touch.