A receiving clerk reports a physical discrepancy to the operations team

PURCHASING / RECEIVING CONTROL

See the mismatch before an invoice moves forward.

Match the documents as they arrive. When reality at the bay differs, link the report to the case and prepare the WMS or ERP update for review.

Describe a purchasing exception

Documents first. Then reality at the bay.

First check: match documents as they arrive. Second check: connect a WhatsApp discrepancy report to the case, even when the documents agree.

Two layers of control

1. The documents disagree. The discrepancy is flagged as they are matched.

SOURCE DOCUMENTSILLUSTRATIVE DATA

Purchase order

PO-1042 · L1

100units

Delivery note

DN-1042 · L1

80units

Invoice

INV-1042 · L1

100units

Human review required

20 units
difference to review.

100 − 80 = 20 · invoice / documented delivery

A person checks the sources and decides the next action.

Inspect sources and rules

Matching preserves the purchase order, delivery note and invoice values. A count or receiving exception is a separate source. A report from the floor prepares an update; it does not change the WMS or ERP on its own. Thresholds and approvals follow your scenario.

Demonstration of two operational situations. Illustrative quantities. No data sent and no system changed.

Keep four quantities separate

Ordered

What the approved purchase order requested, by line item and unit.

Delivered

What the delivery evidence says arrived, including partial shipments.

Accepted

What receiving confirms after shortages or damage are recorded.

Invoiced

What the supplier is asking to be paid for. Differences remain visible for review.

A controlled exception flow

  1. Capture the evidence

    Link each order, delivery, receipt and invoice to the same case without discarding source versions.

  2. Compare and hold

    Flag quantity or price differences, show the arithmetic and stop automatic progression when approval is missing.

  3. Record a decision

    Purchasing, receiving and finance decide on correction, replacement, credit or release under their own rules.

Illustrative case: eight units need review

CriterionRecorded quantityWhat the team sees
Purchase order100 unitsApproved reference
Delivery note100 unitsCheck against physical receipt
Receiving92 accepted, 8 damaged8 units were not accepted
Supplier invoice100 units billed8 units above accepted quantity: invoice held for review

Autohaus Frisch / Michelin: a real case, 20 ordered and one exception

Kaliits worked on a real Autohaus Frisch case involving Michelin: 20 items were ordered, with one damaged or missing.

Scope and details

This is a real case background, confirmed by Mehdi Kourchal on 4 October 2026, rather than an invented purchasing scenario. This case concerns a receiving exception. No price, measured processing time or financial resolution is added to the account.

A prototype scenario, not a customer result

In the SIEMA prototype, deterministic rules make the discrepancy and invoice hold visible.

Scope and details

A person still decides whether to request a credit, replacement or corrected invoice. A real pilot needs your cases, acceptance criteria and approval rules.

What the pilot does and does not do

Does a match automatically approve payment?

No. A match can make a case ready for the finance review defined by your team. Payment approval remains under your controls.

Can it handle partial delivery?

A pilot should test separate receipts and open order balances rather than overwriting the first delivery.

Is the SIEMA demo a production system?

No. It is an interactive scenario that illustrates evidence, state changes and a human decision.

Bring one recurring purchasing exception

We will map the evidence, people and approvals needed for a bounded pilot.

Request a workflow diagnostic