Describe the relationship graph
Write down which records should connect: purchase order to invoice, invoice line to order line, and shipment to receiving event. Real workflows may contain split shipments and multiple invoices for one order. A one-document-to-one-document assumption can quietly remove the cases your model needs to learn.
Retain meaningful mismatch cases
A useful evaluation includes missing references, partial quantities, changed prices, duplicated submissions, and unresolved links. Define whether each mismatch is observable from the supplied documents. Do not label a transaction incorrect solely because an omitted internal approval system contains information unavailable to the model.
Keep evidence and outcomes distinct
Separate document text from a reviewer’s matching decision. Record which fields supported a link, whether a person adjudicated it, and whether the outcome remains uncertain. Preserve revisions and cancellation status so an old purchase order does not become an apparent contradiction in the current record.
Scope the sourcing request
Provide representative document bundles and the expected output graph before requesting volume. Ask for counts of complete bundles and incomplete cases independently. Fiund can discuss source-specific access, permitted uses, and privacy review; those details need confirmation for the particular project rather than inference from a file sample. A useful pilot bundle might include one order fulfilled in two shipments and billed through two invoices. Ask a reviewer to trace the quantities through all artifacts. If the link cannot be supported from delivered references, label it unresolved instead of treating an internal business assumption as ground truth for reconciliation.
Review checklist
- Draw allowed one-to-many relationships
- Define match and mismatch evidence
- Count complete document bundles
- Document revision and cancellation rules