Whose Problem Is the Short Delivery?
A delivery that does not match its order is everybody’s problem for a day and nobody’s by the end of the week. The receipt-match exception queues split every mismatch by the kind of problem it is, so each one lands with the person who can actually settle it.
On a Monday morning at a private hospital in Nakuru, four things go wrong with supplies, and none of them is unusual. The examination gloves arrive 20 cartons short. Three cartons of saline are crushed in the van. The linen supplier’s bill comes in at a higher price per set than the order agreed. And a delivery of theatre drapes due last Thursday has still not turned up. Separately, a consignment of syringes received three weeks ago has never been billed by the supplier at all.
Each of these is visible to somebody. The storekeeper saw the short gloves and the crushed saline. Accounts payable will notice the linen price when they try to pay. The drapes are a gap on the theatre manager’s shelf. Nobody notices the unbilled syringes until the supplier sends a statement in March. The problem is not that nobody can see the mismatches. It is that each one belongs to a different person, and a single list of “orders that do not match” belongs to nobody in particular.
One mismatch, five kinds of problem
Three-way matching compares what was ordered, what arrived and what was billed. In AWRA OpsHub that comparison already decides whether an order may be paid. The exception queues take the same comparison and split what it finds into five worklists, because the five need different people:
| Queue | Opens when | Usually settled by |
|---|---|---|
| Quantity variance | Received short or over the order, or billed for a different quantity than arrived | The buyer and the store |
| Receiving damage | Units were marked damaged when the delivery was checked in | The buyer, with the carrier or supplier |
| Price variance | The bill’s price differs from the agreed price | The buyer who agreed the price |
| Missing invoice | Goods were received, no bill has been entered, and the waiting window has passed | Accounts payable |
| Late delivery | The delivery date has passed and the order is not fully received | The buyer chasing the supplier |
An order lands in a queue once per kind of problem. The glove order sits in Quantity variance; if the gloves had also been billed at the wrong price, the same order would sit in Price variance as well, with its own row and its own decision.
What sets each queue off
Quantity and price variances are measured against tolerances the workspace sets, and both start at zero: one carton short is a variance until you decide otherwise. Why zero is the right place to start is the subject of every tolerance ships at zero. A price variance row carries the money at stake, the difference in price times the quantity billed, so a buyer can see which rows are worth a phone call.
The two time-based queues need no one to touch the order. Missing invoice opens once goods have been received, no supplier bill has been entered and the first receipt is older than the waiting window, fourteen days unless you change it. If an invoice file was uploaded to the order but never entered as a bill, the row says so, because that is a different chase. Late delivery opens the day after the order’s delivery date, or after a grace period you set. A check runs every morning, so on Monday the syringes are already in Missing invoice and the drapes in Late delivery before anyone has opened either order.
Short, over and damaged deliveries are announced the moment they are detected, in the bell and on the phone, to whoever raised the order and to the people who approve orders. They are announced once, when the row opens, not every time somebody looks at the order.
A list of everything that is wrong belongs to everybody, which in practice means nobody. Five short lists each have an owner.
Resolving is a decision, with a reason
Some mismatches are fixed at the source. The supplier sends the 20 missing cartons, the store receives them, and the Quantity variance row closes by itself, marked cleared so the record shows that nobody had to decide anything. Others are accepted as they are. The hospital may agree to pay the linen supplier’s new price because the contract allowed an adjustment. That is a resolve, and it needs a reason in words, recorded with the person and the time, and written to the audit log.
A resolved row stays resolved only while the facts it was resolved on stay the same. If the linen supplier then sends a second bill at yet another price, or another short delivery lands on the glove order, or the drapes’ delivery date is moved, the row reopens. A reason given for one situation does not carry over to a different one.
Resolving a row does not release a payment
The payment check reads the order’s match directly, not the queue. With the default setting, an order with a discrepancy cannot be paid. Paying past it is a separate override that needs its own permission and a written reason. The queue is where the mismatch is settled; the payment gate is where money is protected.
Monday morning, by queue
-
The storekeeper checks in the gloves and saline
Twenty cartons short and three marked damaged. Two rows open, and the buyer who raised the order gets a notice on her phone before the van has left.
-
The buyer calls the glove supplier
They will send the balance on Wednesday. She leaves the row open; it clears by itself when the balance is received.
-
The buyer settles the saline with the carrier
The carrier will credit the three cartons. She resolves the damage row with that reason.
-
Accounts payable opens Missing invoice
The syringes have waited 21 days. They email the supplier for the bill, and the row clears when it is entered.
-
The theatre buyer opens Late delivery
The drapes are four days late. He calls the supplier and moves on to the next row.
Each queue can be filtered by supplier and status, and every order can be re-checked on demand, singly or all at once. The queues work on the web and over the API, and open rows also feed the operations exception inbox described in Eleven Screens, One Inbox, where price and quantity variances rank as high severity.
The verdict
Matching tells you an order is wrong. The queues tell you what kind of wrong and whose desk it belongs on, open the time-based problems without anyone remembering to look, close what fixes itself, and make everything else a decision with a reason. The payment gate stays separate, so settling a queue never quietly releases money.
What AWRA OpsHub does today
- Five exception queues for price variance, quantity variance, missing invoice, late delivery and receiving damage, one row per order and kind of problem.
- Tolerances, a missing-invoice window and a late-delivery grace period set per workspace, starting at zero, fourteen days and zero days.
- A daily check that opens missing-invoice and late-delivery rows without anyone opening the order.
- Notices for short, over and damaged deliveries to the order’s author and the people who approve orders, sent once when the row opens.
- Cleared when the problem goes away, resolved only with a written reason, reopened when the facts change, with resolutions in the audit log.
- The payment gate kept separate, so resolving a row never releases a payment.
More we can add to your workspace
- Late delivery measured against the supplier’s promised date from their acknowledgement, alongside the date on the order. Commission it
- A debit note raised from a price-variance row, filled in with the difference. Commission it
- A carrier claim raised from a receiving-damage row, with the damaged lines and notes. Commission it
- Notices for the price-variance and missing-invoice queues to accounts payable. Commission it
Where we point you to a specialist
- We do not decide whether a price change was allowed under your contract with the supplier. The queue shows the difference and records the reason someone gave for accepting it; the commercial judgement stays with your buyer.
The promised-date check builds on a date the supplier already gives when they acknowledge an order, so it is the smallest of the four.
From a worklist to the next document
The queues find, route and record each mismatch. The natural next step is for each row to start the document that settles it.
Late against the promise
Measuring lateness from the date the supplier committed to, as well as the order date.
Debit note from a price row
One step from the variance to the note that recovers it.
Carrier claim from a damage row
The damaged lines and the receiving notes, ready to send.
Four questions for your receiving process
Who is told when a delivery arrives short?
What you will probably hear
The storekeeper writes it on the delivery note.
How to read it
Then the buyer finds out when the stock runs out. The person who raised the order should hear the same morning.
How do we find goods received but never billed?
What you will probably hear
From the supplier’s statement.
How to read it
That is months later, and the accrual has been wrong since. Received-but-unbilled should open by itself after a set number of days.
When someone accepts a price difference, where is the reason?
What you will probably hear
In an email.
How to read it
An auditor will ask for it on the order. Accepting a variance should require a reason recorded with the person and the date.
Does accepting a mismatch let the order be paid?
What you will probably hear
Yes, that is the point.
How to read it
Settling a worklist and releasing money are different decisions. Ask for the payment check to stay separate.
See purchase orders, receiving and matching
How orders are received, matched against bills and protected at payment.
Explore receiving and matchingFrequently asked questions
What are the receipt-match exception queues?
Five worklists that split every mismatch between an order, its deliveries and its bills by kind: price variance, quantity variance, missing invoice, late delivery and receiving damage. Each order appears once per kind of problem.
How long before a received order with no bill appears as a missing invoice?
Fourteen days after the first receipt by default. Each workspace can set the window between 1 and 365 days. A check runs every morning, so the row opens without anyone opening the order.
Who can resolve an exception?
Anyone who can approve purchase orders. Resolving needs a written reason, which is recorded with the person and the time and written to the audit log.
What happens if the supplier fixes the problem?
The row closes by itself and is marked cleared, so the record shows nobody had to decide it. A resolved row reopens if its facts change, such as a new bill price or another short delivery.
Does resolving an exception allow the order to be paid?
No. The payment check reads the order’s match directly. Paying past a discrepancy is a separate override that needs its own permission and a written reason.