Invoice and shipment data often disagree. Quantities may differ, dates may shift, product descriptions may use different wording, or shipment records may reflect partial delivery. The dangerous response is to choose one value silently and overwrite the rest.

Preserve the original claims

The system should retain each claim separately:

  • invoice quantity and source;
  • contract quantity and source;
  • shipment quantity and source;
  • warehouse or delivery quantity and source;
  • time at which each record was produced.

A canonical case state should not erase provenance.

Classify the difference

Not every difference has the same meaning. It may be:

  • a formatting difference;
  • an expected partial shipment;
  • a timing difference;
  • an amendment not yet attached;
  • a data-entry error;
  • a potentially material inconsistency.

Create a review question

The conflict should become an explicit question such as:

The invoice shows 1,000 units while the bill of lading shows 800. Is this an authorized partial shipment, and where is the supporting amendment or delivery schedule?

Ask the right participant

The question should be routed to the party with relevant knowledge and authority, while preserving who answered and what evidence was added.

Boundary

The system may organize and explain the discrepancy, but resolution remains review-only and human-authorized. It must not approve funding, authorize payment, modify external systems through a live connector, submit a chain transaction, or execute settlement.

A trustworthy evidence workspace makes disagreement easier to inspect. It does not manufacture certainty where the records remain inconsistent.