A plate can arrive with a clean certificate, test values comfortably inside spec, and a heat number that belongs to a different melt. Receiving inspectors see it often enough that the order of checks matters: establish identity and traceability first, then read the reported values. Run it the other way and the passing numbers quietly vouch for the wrong steel.
Material certification is documented proof that a raw material meets specified chemical and mechanical requirements along with the requirements of the order. For metals, that proof is commonly a mill test report (MTR), certified material test report (CMTR), or mill certificate. It connects the delivered plate, pipe, fastener, or fabricated component to its heat or lot and records what a receiving inspector needs to verify it against the purchase order (PO) and the project specification.
A certificate may carry actual chemistry and mechanical test values, or it may only declare conformity. Quality engineers and receiving inspectors need to know which type the order called for and what a valid MTR should contain before releasing material, which is where material test report validation starts.
What a Mill Test Report Contains
The MTR determines whether delivered metallic material is the grade, size, heat, and condition the project team ordered. Mill layouts vary, but the standard fields do not:
Mill identity: Producing mill, facility, certificate number, and issue date.
Order reference: Purchaser, PO, contract, or material submittal reference.
Product description: Form and dimensions, such as plate thickness or pipe diameter and schedule.
Specification: Material grade, governing specification, and specification revision, expressed against the project specifications the order was written from.
Traceability identifier: Heat number, melt number, or lot number.
Chemistry: Chemical composition, including applicable alloying elements.
Mechanical results: Yield strength, tensile strength, elongation, hardness, or impact results as required.
Processing: Manufacturing route, heat treatment condition, and supplementary tests where applicable.
Certification mark: Authorized signature, inspection stamp, or other certification mark.
The values must be actual results when the governing specification requires heat-specific testing. A generic specification sheet showing typical properties is not a substitute for an MTR tied to the delivered material.
MTR vs. Certificate of Conformance
When the PO says "material certificate," confirm what the requirement actually means. An MTR provides test evidence for identified material. A certificate of conformity, also called a certificate of conformance or CoC, is the manufacturer's or supplier's declaration that the supplied product meets stated requirements.
Project file | What it asserts | Actual test data | Typical traceability |
|---|---|---|---|
MTR or CMTR | Identified material meets the stated specification | Yes | Heat or lot number |
CoC | Supplied product conforms to the order or named requirements | Not necessarily | PO, part, shipment, or lot reference |
A CoC may be appropriate for a fabricated component, coating, fastener, or general product when the contract only requires a declaration. It should not replace an MTR when the project specification requires actual chemistry, mechanical properties, or heat-specific evidence.
EN 10204 Certificate Types 2.1, 2.2, 3.1, and 3.2
European and international project requirements reference EN 10204 by type, so verify the exact type on the PO before manufacturing the material. The EN 10204 types differ mainly in whether test results are specific to the delivered material and who validates them.
Type | Evidence provided | Batch-specific | Validation |
|---|---|---|---|
2.1 | Declaration of compliance; no test data | No | Manufacturer |
2.2 | Declaration plus non-specific test results | No | Manufacturer |
3.1 | Results from the actual product supplied | Yes | Manufacturer's authorized inspection representative, independent of production |
3.2 | Specific results with additional verification | Yes | Manufacturer's independent representative plus purchaser or designated third-party inspector |
Only Types 3.1 and 3.2 establish that the reported test results came from the delivered heat. Identify a Type 3.2 requirement during procurement, because the required independent inspection has to happen while the material is being made. A 3.2 requirement raised after production usually cannot be satisfied.
How Heat and Lot Numbers Preserve Traceability
Verify that the heat or lot number on the certificate matches the physical marking and the PO line before continuing the certificate review. The heat number links metal produced from one melt to the chemistry and test results recorded for that melt. Lot numbers perform a similar role for fasteners, consumables, and other grouped products.
Traceability breaks more often after receipt than at receipt. Plates get split, pipes get cut, bundles get separated, and fabricated parts lose the original mill marking. Before cutting or subdividing material, transfer the identification to both the usable piece and the remainder under the project's approved procedure. The receiving report, MTR, material tag, cut list, and fabrication record must all retain the same identifier, which is a document-control problem as much as a shop-floor one.
Receiving Inspection Checks Before Material Release
Receiving inspection compares the documents against the delivered material. Run the sequence below before accepting incoming steel, pipe, plate, fasteners, or fabricated components. Identity comes before results, and disposition comes before release.
Match the Delivery to the PO
Start by confirming that the shipment, physical markings, and certificate describe the same ordered material.
Confirm what was ordered: Check the PO line, project specification, approved material submittal, grade, dimensions, required certificate type, and supplementary testing requirements.
Identify the delivery: Record the supplier, packing slip, quantity, product form, dimensions, and visible condition. Separate mixed heats or lots instead of recording a bundle as one batch.
Match physical markings: Compare the stamped, painted, tagged, or attached heat or lot number against the MTR or CoC. Hold material with missing, illegible, or conflicting markings.
Review certificate identity: Confirm the mill, certificate number, date, purchaser, PO reference, grade, specification revision, and product description. A supplier-specific layout is acceptable if it includes the required information and is coherent.
Validate Test Results and Certification
Once identity and traceability match, compare the reported values and the certification against the governing requirements.
Compare reported results: Check chemistry, tensile and yield strength, elongation, hardness, impact testing, heat treatment, and other ordered values against the governing limits. Do not treat a pass statement as numerical evidence when actual results are required.
Validate certification: Confirm the required signature or stamp and the correct EN 10204 type where applicable. Escalate altered-looking PDFs, inconsistent typefaces, missing pages, or unexplained corrections.
Disposition Certificate Exceptions
Do not correct a mismatch by assumption. Route the exception to the staff authorized to decide the material's status.
Disposition exceptions: Quality engineers or authorized receiving staff decide whether to release, quarantine, reject, or request corrected project files. Preserve that decision alongside the certificate-to-material traceability record.
Physical verification remains essential. Positive material identification (PMI), retesting, or third-party inspection may still be required by the specification or the risk level, and certificate review does not replace any of them.
Common Material-Certificate Failure Points
Seven failure modes account for most held material. Each one is caught at a different point in the sequence above, and each has a different disposition.
Unreadable scan: Caught at certificate identity review. A scan too poor to confirm the heat number cannot be dispositioned at all, so request a legible copy rather than accepting the values and moving on.
One certificate covering several unidentified heats: Caught when the delivery is identified. Bundles arrive as one line, and the certificate lists three melts. Separate the material by heat before recording receipt, or the traceability record is wrong from the first entry.
CoC supplied where a 3.1 was ordered: Caught at certification validation. This is a procurement failure surfacing at receiving, and it usually cannot be corrected after production, so escalate to the buyer rather than the mill.
Missing signature or stamp: Caught at certification validation. The mill can normally reissue it, which makes this the cheapest exception on the list to clear if raised the same day.
Outdated specification revision: Caught when the certificate is compared to the PO. A certificate against a superseded revision may still conform, but the engineer of record decides that, not receiving.
Split material without transferred markings: Caught downstream, in the shop, after the certificate has already been accepted. The remainder piece has no identity and no path back to one.
PO description that does not match the certificate: Caught when the delivery is matched to the PO. Before rejecting anything, confirm whether the mill shipped the wrong product or the PO was written against the wrong line.
Supplier layouts and terminology vary widely, which is the practical ceiling on automating this review. Extraction can read a certificate number as a heat number, or a specification limit as an actual result. Review rules need tuning against the mills a site actually buys from, and staff must review false-positive flags before anyone treats the output as a decision.
An AI Agent Workflow for Incoming Material Certificates
Built world project teams and fabricators define the receiving checklist and the release authority first, then configure Datagrid's AI agents to review incoming material certificates against it. The agents collect MTRs, POs, submittals, and receiving reports from IMAP email, SharePoint, Procore, Autodesk Construction Cloud, or other supported sources. This workflow is narrower than quality control data analysis, which covers inspection records and audit preparation rather than incoming documents.
Interpret Incoming Project Files
Certificates and related project files become structured fields that can be compared consistently. Datagrid's Audit Agent interprets incoming MTRs, CMTRs, mill certificates, and CoCs (including scanned PDFs) and extracts the mill, PO, grade, specification revision, dimensions, heat or lot number, test values, and signature status. The cross-check compares those extracted fields against the PO, submittal, and project specification.
When we set this up, we start with the two or three mills a site buys most from and get extraction right on their layouts before adding the long tail, because a rule set tuned on one mill's template will misread the next one.
Cross-Check Order Requirements
Cross-checks run after extraction, comparing certificate details against the specific PO line, the submittal, and the project specification. The agent detects missing certificates, mismatched heat numbers, absent signatures, incorrect certificate types, and values outside configured limits, and staff reviews each flagged exception before material release.
For example, the agent pairs an MTR from IMAP email with its PO line in Acumatica and the physical marking in the receiving report. It extracts the heat number and the actual tensile value, then compares both against the order requirements. If the certificate and the marking do not match, the agent flags the mismatch for staff review, because passing test values do not override a certificate-to-marking mismatch.
Route Exceptions and Preserve Traceability
When a comparison produces an exception, it routes to the responsible reviewer along with the evidence behind the disposition. The workflow assembles a structured traceability record linking the source certificate, PO line, material identifier, and review status.
Receiving teams can then monitor certificates matched to PO lines, unresolved heat-number mismatches, missing signatures, exception age, and material held pending corrected files. Those measures describe workflow health. They do not imply that every flag is a defect or that automated review guarantees conformity.
The boundaries matter here. Unreadable scans and mixed heats still require staff review, as do tables that place specification limits beside actual values. Configured rules must be updated whenever PO requirements or specification revisions change. An AI agent can compare a physical identifier only when receiving staff have captured it in a material tag, receiving report, or other connected file, and it cannot inspect the material or perform PMI. Quality engineers and receiving inspectors retain authority over physical verification, PMI requirements, material release and rejection, and exception disposition.
Simplify Material Certification Tasks with Datagrid's Agentic AI
Receiving inspection is a document-comparison job that scales badly with delivery volume. Datagrid's AI agents take the comparison and hand the inspector the exceptions:
Certificate backlog triage: Rank held and unreviewed certificates by the material's place in the fabrication schedule, so the plate that ships Monday gets looked at before the fasteners in the yard.
Missing-certificate detection: Identify PO lines that received material with no certificate on file at all, which a certificate-by-certificate review structurally cannot find.
Heat-number and entity matching: Compare the certificate, the physical marking recorded at receipt, and the PO line as a three-way match, not a pair.
Specification-revision drift: Flag certificates issued against a superseded revision of the governing specification, and route them to the engineer of record instead of receiving.
Downstream traceability gaps: Surface material that was cut or subdivided without a transferred identifier, before the remainder reaches a fabrication record with no heat behind it.
Physical verification, PMI, and every release or rejection decision stay with the quality engineer.
Create a free Datagrid account and point it at one PO with a long delivery history to see which lines received material against a certificate nobody reconciled.
Frequently Asked Questions About Material Certification
Most questions here reduce to two: which certificate does the order actually require, and what happens when the paperwork and the material disagree.
What is material certification?
Documented proof that a delivered raw material meets the chemistry, mechanical properties and order requirements it was bought against. For metals, that proof normally arrives as a mill test report tied to a heat number, or as a certificate of conformance that declares compliance without reporting measured values.
How do you obtain a material certificate?
State the required certificate and type on the PO, then request the certificate tied to the delivered heat or lot. Requirements added after production may not be available, particularly where independent witnessing was required.
What is the difference between an MTR and a certificate of conformance?
An MTR reports actual test values for identified material and ties them to a heat or lot number. A certificate of conformance declares that the product meets stated requirements and may include no test data. Specify an MTR wherever the spec calls for measured values tied to the delivered heat.
Which EN 10204 certificate type should a project specify?
Specify Type 3.1 when the reported results must come from the delivered product and be validated by an inspection representative independent of production. Specify Type 3.2 when the purchaser or a third-party inspector must also verify those results, and raise that requirement during procurement rather than after manufacture.
What should happen if the heat number does not match?
Hold the material and follow the receiving disposition workflow. Quality engineers or authorized receiving staff decide whether to quarantine, reject, or request corrected files, and passing test values do not override the mismatch.
