Ordered
What the approved purchase order requested, by line item and unit.
PURCHASING / RECEIVING CONTROL
See the mismatch before an invoice moves forward.
Compare purchase orders, delivery evidence, accepted quantities and invoices in one review flow. Available for controlled pilot implementation.
Keep four quantities separate
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.
THE PROCESS AT A GLANCE
Follow the quantities that matter.
A recorded delivery is not always the accepted quantity. The reviewer sees the difference before release.
- 01Read the order and delivery
- 02Compare accepted and billed
- 03Hold for a named decision
A controlled exception flow
- 01
Capture the evidence
Link each order, delivery, receipt and invoice to the same case without discarding source versions.
- 02
Compare and hold
Flag quantity or price differences, show the arithmetic and stop automatic progression when approval is missing.
- 03
Record a decision
Purchasing, receiving and finance decide on correction, replacement, credit or release under their own rules.
Illustrative case: eight units need review
| 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 |
A prototype scenario, not a customer result
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.
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.
Related reading
Explore Blog & Guides- What happens when a supplier invoices more than the quantity accepted?A receiving example that separates ordered, delivered, accepted and invoiced quantities before payment approval.Read article
- How should partial delivery change PO, receipt and invoice matching?Track each receipt and the open order balance while keeping invoice exceptions visible for human approval.Read article