Names on a report have different roles
Record both roles clearly so the register preserves who supplied the material and who actually reported the result.
Our public material-register example shows a synthetic report beside downloadable output. Use it to inspect how values and source references travel together. The self-service ParseMill trial is for invoice PDFs; supplier test reports and engineering review need a separate fit discussion.
Keep source wording and normalized organization names separate. A trading name, abbreviation or logo may need clarification before it can be matched to an organization record. The register should not invent legal or commercial relationships from visual proximity.
Use a document-context identity sheet
| Role | Synthetic source text | Evidence location | Relationship status |
|---|---|---|---|
| Supplier | North Quay Materials | Delivery cover, P1 | Sender of supplied packet |
| Report issuer | Harbor Test Laboratory | Report header, P2 | Issuer explicitly named |
| Manufacturer | Not stated | No applicable label found | Unknown |
| Customer named on report | Example Fabrication | Client field, P2 | Named client; not assumed supplier |
The organizations are invented. The fixture deliberately leaves manufacturer unknown and keeps the named client separate from the supplier. A single company can hold several roles, but each assignment should have supporting evidence rather than being copied automatically from one confirmed role.
W3C: Provenance model primer distinguishes agents and their involvement in activities. That supports recording the role a party actually played instead of treating every name as interchangeable metadata.
Capture roles with evidence
- Inspect the report header, signature block, client fields and delivery context. Record exact names, role labels and source locations.
- Separate source-reported roles from internal contact or procurement information. Label any relationship established outside the report with its own evidence.
- Normalize names only under a reviewed mapping, retaining original strings. Keep ambiguous abbreviations and unstated roles in an exception list.
- Verify that role assignments apply to the correct report segment when several reports share one PDF. Check every new issuer header and cover.
NIST: Metrological traceability explains that laboratory accreditation does not itself qualify a laboratory to approve a particular product. Do not turn an issuer identity or laboratory reference into an unsupported manufacturer or approval claim.
Handle logos and conflicting labels
A logo may identify a brand, parent organization or document template owner. Use explicit labels and authoritative context where available, and mark uncertain roles rather than guessing. If the delivery cover and report body name different issuers, preserve the conflict for clarification.
Do not merge organization records solely because their names look similar. A mistaken identity match can attach results to the wrong supplier and contaminate later comparisons. Keep the original name and source reference available for review.
Verify the identity handoff
For the fixture, North Quay remains supplier, Harbor remains issuer, Example Fabrication remains named client and manufacturer remains unknown. The recipient can see exactly which roles the source supports and which relationships are still unconfirmed.
Bring a report naming several parties to a supplier-register fit discussion. Define the roles and evidence your receiving process needs before agreeing a pilot. General issuer, manufacturer and laboratory-role extraction is outside the invoice trial’s promise.
Put it to work with ParseMill
Check the example against the work you need done
Compare the synthetic report, extracted rows and source references. For your own supplier reports, discuss the document type and review requirements before agreeing to a pilot.
Also working with supplier invoices? Try the invoice-to-Excel workspace. Any wider document pilot needs an agreed scope and fee.
Invoice processing: $49 USD/month · 500 PDF pages · one user. Buy only after you have checked the fit on your own invoices.
Sources and editorial notes
- W3C: Provenance model primerChecked 2026-10-25
- NIST: Metrological traceabilityChecked 2026-10-25
Written by ParseMill. Worked examples are illustrative process examples, not customer results. Software availability can vary by subscription and region; check the linked documentation for your account. Review decisions and approvals remain with your team.