Material certificates and serial traceability at goods receipt

Topics: oil and gas material traceability; material certificate tracking; lot and serial identity; certificate coverage.

A delivery arrives with a certificate PDF attached to the purchase order. The receiving screen shows “documents present”. During review, the team finds that the certificate identifies one delivered lot but says nothing about the second.

Material certificate traceability requires a relationship between the purchase requirement, received identity, supporting document and reviewer decision. A file attached somewhere in the transaction is not enough to establish that relationship.

Define the requirement at order stage

The purchase order should identify the applicable specification and document requirements, including the required revision or approval basis where relevant. The supplier response and accepted deviations should remain linked. Otherwise receiving is asked to decide what documentation was intended after the goods have arrived.

JIP33 separates technical, information and quality requirements within its procurement framework. Where adopted, that structure can help organise the order's requirements. It does not establish acceptance of an individual certificate or delivered item. IOGP JIP33 FAQ

The qualified quality or materials owner defines which identity checks and document reviews apply. Requirements differ by item and transaction. A receiving application should not demand a heat number for every spare or assume a generic certificate is appropriate for every order.

Keep the requirement's version separate from the submitted document's revision. “Specification revision B required by PO-118” and “certificate C-91 revision 2 received” answer different questions. The record should show which requirement the reviewer assessed the certificate against, including an accepted deviation where one exists.

Trace two lots through one delivery

Illustrative example. Order PO-118 requests 12 units with specified certificate requirements. Eight units arrive under lot L-41 and four under lot L-42. The delivery includes certificate C-91 revision 1, which identifies L-41 only.

The receiver records all 12 units as physically arrived, with their actual identities. The eight units do not become accepted merely because the lot number matches; the qualified reviewer still evaluates the required evidence. The four units should not inherit C-91's coverage because they travelled on the same vehicle.

After review, the authorised owner accepts L-41 and leaves L-42 on hold. The resulting record is 12 received, eight accepted and four held under the illustrative process. Commercial invoice handling should receive the relevant disposition, as discussed in three-way matching for spares.

A revised certificate needs a visible relationship

Suppose the supplier later sends C-91 revision 2, now listing both lots. Retain revision 1 and record the new submission. The reviewer checks the revision's relevance and authenticity through the approved process, including any changed content affecting the earlier lot.

The system should not replace the old attachment and automatically release L-42. Nor should it assume the previously accepted L-41 is unaffected if the new document changes information relevant to that decision. The qualified owner determines the impact and records the disposition.

For partial deliveries, the same certificate may legitimately relate to several receipt lines. Model that many-to-many relationship with the covered identities and quantities. A blanket link from the certificate to the PO header can conceal gaps in later receipts.

The reverse relationship matters as well: one received group may require several kinds of evidence. If the order calls for both a material certificate and a separate inspection record, receiving the first document should complete only that requirement. Show the outstanding requirement against the same lot, with its reviewer, rather than collapsing all documents into one “certificate received” checkbox.

Keep identity, document presence and acceptance distinct

A receiving clerk can record labels, serials, lots and delivered quantities. A document-control role can check that the required files were supplied and can be opened. The designated technical or quality reviewer decides acceptance within their authority. Finance and AP use the resulting approved evidence for their own process.

Missing identity, unreadable certificate, wrong revision, mismatched lot, incomplete coverage and disputed authenticity need different exception reasons. Each should show the affected receipt, owner and required next action. “Certificate issue” is too vague to manage a queue.

Avoid creating replacement identities merely to match paperwork. If the physical label and supplied document disagree, preserve both observations and refer the case. The system's purpose is to expose the discrepancy, not make it disappear.

Design the record so an auditor can follow it

A useful relationship record contains the PO line, required document type and revision basis, receipt line, item, lot or serial where required, document identifier and revision, reviewer, disposition, date and exception reference. Keep the original file in the controlled repository with appropriate access.

General provenance concepts help distinguish the source document, review activity and responsible person. W3C PROV provides that broader data-lineage vocabulary; the acceptance rules remain those of the approved procurement and quality process. W3C PROV overview

A stable document link should open the exact version used for the decision. A separate current-version link can help day-to-day work. If a repository migration changes URLs, preserve the document identity so historical receipt records remain traceable.

Carry the relationship through later stock movements. If L-41 is split between two stores, both records should lead back to the accepted receipt and certificate version. A returned unit should retain that history while receiving its own return and disposition record. Moving stock or changing a bin should not create a new, unsupported claim of document coverage.

Automate the comparisons that are actually deterministic

Rules can compare recorded identifiers, detect missing documents and prevent an unsupported default status. Integration can carry approved dispositions to the ERP and document references to the EAM. Show failed synchronisation explicitly so a hold is not lost between systems.

For scanned certificates, show the extracted lot or certificate number beside its source location. A reviewer can then check a confused letter or a row taken from the wrong table. If the identifier remains unreadable, leave it unresolved and request clarification. A correctly transcribed number still says nothing by itself about authenticity or material conformity.

Measure accepted receipt lines with complete required evidence, held quantities by reason and age, and revised documents awaiting impact review. Sample accepted lines as well as the hold queue. A short queue could reflect good submissions or premature releases; only the evidence trail distinguishes them.

Use the ERP’s existing receipt and attachment controls when they can represent each required document, covered identity and reviewer disposition. Add a linked coverage register when certificates span several receipts or one lot needs several document types. The choice should be tested with the split-delivery example: an authorised reviewer must be able to reconstruct exactly which evidence supports each accepted quantity.

Summary and next actions

Traceability is a chain from the order's requirement to the received identity, document version and authorised decision. Keeping each link explicit lets the team accept supported receipts and investigate gaps without losing the history.

1. Select one split receipt and map certificate coverage at lot or serial level.
2. Separate arrival, document completeness and qualified acceptance in the workflow.
3. Test a mismatched identity, missing coverage and a revised certificate.
4. Confirm that holds and later decisions reach invoice matching and asset records correctly.

A receipt-traceability assessment can use one split delivery and a revised certificate to test the current records. The review should identify where lot coverage, document versions or acceptance status are lost between receiving, the repository and AP.