To handle certificates of conformance automatically, read each certificate as it arrives, tie it to the supplier, purchase order and lot, and check it against the goods receipt in the ERP. Only then is it attached to the receipt or the lot. A certificate that does not match stops with a reason before the material is released.
On the shop floor it looks like this. The delivery arrives, and the certificate is in a plastic sleeve on the carton. Someone from quality has to scan it, find the order line and the lot, and link them. With dozens of deliveries a week, that is a full job.
The certificate usually travels with the paperwork the warehouse already handles. Teams that check supplier delivery notes against the purchase order have most of the pieces in place.
What a certificate of conformance contains
Supplier and order
Who made or supplied the goods, for whom, and against which purchase order. Without the order number it is hard to know which receipt the certificate belongs to.
Part and lot
Part number, description, quantity, and the lot or serial number. The lot is the field that matters. Without it the certificate cannot be tied to the right material.
Standard or specification
Which standard the part meets, sometimes with test results or a reference to a separate lab report.
Signature and date
Who approved it on the supplier side and when. This is what an auditor asks to see.
Why certificates pile up
One certificate per lot
A single delivery can come with several certificates, one for each lot. All of them must be kept and found again years later.
The link is made by hand
Someone finds the order line, the goods receipt and the lot in the ERP and attaches the file. It is the same kind of work as receiving against packing lists, with more fields and less time.
They arrive scanned in batches
The warehouse scans a day of certificates into one PDF. Before anything can be linked, someone has to split the file and work out which page belongs to which supplier.
The gap shows up in the audit
When an auditor asks for the certificate of one lot, the search through folders and mailboxes begins. If it is not found, that is a finding, not just an inconvenience.
What the automation has to do
Read certificates in any layout
Every supplier has their own form. A new supplier should work from the first certificate, with no template. That is the general problem of unstructured documents in manufacturing supply chains.
Find the receipt and the lot
By supplier, order number, part and lot. The record already exists in the ERP. The certificate has to find it.
Check before attaching
Part, quantity and lot on the certificate against the goods receipt. A certificate for a lot that was never received should not be filed as if it were fine.
Stop what does not match
With a short reason, so quality knows whether to call the supplier or the warehouse.
How it works with DOConvert
DOConvert is the AI layer for the ERP. It reads the certificate, finds the matching record, checks it, and only then attaches it. Here is one delivery.
The certificate arrives
By email from the supplier or as a scan from the warehouse, alone or together with the delivery note and the invoice.
DOConvert identifies the supplier and the part
From the sender, the part number and the order number. When several pages come in one file, they are read into the right records, using document merging and validation.
The goods receipt is read from the ERP
With its order line, quantity and lot. For Priority users this runs through the DOConvert Priority connector, which is bi-directional. On Oracle Fusion Cloud ERP and Infor M3 the connection is direct too, with no middleware.
The certificate is checked
Lot, quantity and order line against the receipt. A certificate with no matching lot, or a quantity that does not fit, stops with a short reason.
The certificate is attached
Stored and linked to the goods receipt and the lot. In an audit it is one click away. The wider picture for Priority users is in the Priority ERP document automation guide.
DOConvert is listed on the Priority Market, where the connection and the supported document types are described.
Who it fits
- Manufacturers in regulated industries, medical, aerospace, defense and food, that need a certificate for every lot
- Quality managers who receive dozens of certificates a week and link them by hand
- Purchasing and warehouse managers who want the certificate tied to the receipt on the day of delivery
- IT and IS managers who want a direct connection to the ERP, with no custom development
Questions and answers
What is the difference between a COC and a COA?
A certificate of conformance states that the goods meet a specification or standard. A certificate of analysis lists actual test results. Both are read and linked the same way.
What if the certificate arrives before the goods?
It is kept and waits for the goods receipt. When the receipt is created in the ERP, the link is made.
Do suppliers need to send certificates in a set format?
No. They keep sending what they send today. There is no template per supplier.
How long does it take to start?
A typical DOConvert implementation takes about 10 business days, in the cloud or on your own servers.
Want to see it on your own documents? Book a Demo or Get Started