The unit and reference are part of the meaning
A distributor may buy by case, receive by pallet and sell by each. Supplier item numbers can coexist with internal stock codes and customer-specific aliases. A document that looks complete can still point to the wrong item or imply the wrong quantity when these relationships are flattened.
An invoice-to-draft task should use approved unit conversions and supplier-item mappings. It should compare the invoice against the relevant purchase-order lines and receipts, allowing the organization’s stated policy to determine how split shipments, partial receipts and backorders are handled. Unrecognized aliases belong in an exception queue.
Choose one operational handoff
Start with an observable handoff: a draft exists, a change set is ready for review, or a checked export has been produced. Each has a clear receiving team and a defined evidence requirement. Keep purchasing decisions and inventory adjustments in their own workflows, with the permissions and controls those effects require.
| Workflow to evaluate | Key evidence | Boundary |
|---|---|---|
| Supplier invoice draft | Supplier match, receipt references, checked quantities | No payment or posting implied |
| Catalog change preparation | Source attributes, unit mapping, product identity | No automatic channel publication |
| Export normalization | Source keys, row counts, rejected conversions | No inventory adjustment implied |
Keep discrepancies attached to the work
Freight charges, substitutions and returns should retain their business context. A quantity difference may be expected for a partial shipment, while a unit mismatch may invalidate an otherwise matching total. The task needs the relevant source references and policy, not just a threshold applied to the grand total.
Reconcile against current destination state before a write. A receipt can be corrected while an invoice task is running, and another operator may create the draft first. Version checks and duplicate handling should protect those concurrent actions without obscuring the reason for a hold.
For a pilot, select one company, supplier cohort and document family. Include cases across purchasing units and receiving patterns, then review exceptions with the team that resolves them today. Bring your destination system and data requirements into the discussion so the adapter scope and acceptance criteria reflect the way your operation works.
Missing a detail or found a problem?
Send a documentation question →