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

PURCHASING / RECEIVING CONTROL
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 exceptionFirst check: match documents as they arrive. Second check: connect a WhatsApp discrepancy report to the case, even when the documents agree.
1. The documents disagree. The discrepancy is flagged as they are matched.
PO-1042 · L1
DN-1042 · L1
INV-1042 · L1
Human review required
20 units
difference to review.
100 − 80 = 20 · invoice / documented delivery
A person checks the sources and decides the next action.
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.
What the approved purchase order requested, by line item and unit.
What the delivery evidence says arrived, including partial shipments.
What receiving confirms after shortages or damage are recorded.
What the supplier is asking to be paid for. Differences remain visible for review.
Link each order, delivery, receipt and invoice to the same case without discarding source versions.
Flag quantity or price differences, show the arithmetic and stop automatic progression when approval is missing.
Purchasing, receiving and finance decide on correction, replacement, credit or release under their own rules.
| Criterion | Recorded quantity | What the team sees |
|---|---|---|
| Purchase order | 100 units | Approved reference |
| Delivery note | 100 units | Check against physical receipt |
| Receiving | 92 accepted, 8 damaged | 8 units were not accepted |
| Supplier invoice | 100 units billed | 8 units above accepted quantity: invoice held for review |
Kaliits worked on a real Autohaus Frisch case involving Michelin: 20 items were ordered, with one damaged or missing.
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.
In the SIEMA prototype, deterministic rules make the discrepancy and invoice hold visible.
A person still decides whether to request a credit, replacement or corrected invoice. A real pilot needs your cases, acceptance criteria and approval rules.
No. A match can make a case ready for the finance review defined by your team. Payment approval remains under your controls.
A pilot should test separate receipts and open order balances rather than overwriting the first delivery.
No. It is an interactive scenario that illustrates evidence, state changes and a human decision.
We will map the evidence, people and approvals needed for a bounded pilot.