The question this page answers
What could a delivery, a hold or a sync not settle on its own, and what do you decide?
What you see
An exception is one thing the record could not settle by itself, standing in a queue with the sentence the record wrote on it. There are eight kinds, each one word in the Finding column: Over and Short, a delivery that brought more or fewer units than the order asked; Unknown item, units nobody ordered; Oversell, an order asking for more than is free on the shelf; Return mismatch, a return that came back against a different quantity; Sync disagreement, a warehouse count the ledger cannot explain; Unmatched line, an EDI line naming no product; and Cancelled after send, an order cancelled once the warehouse had it.
For ordinary purchase receipts, the queue stands on Record delivery, under Exceptions, because that is where the goods arrive: every row opened on one of this order's own deliveries, and every row about a product on this order at the warehouse it lands at. With no active findings it reads No active exceptions. Its columns are Finding, What happened, Units and Opened. What happened is the record's own sentence, character for character. Units is the quantity the finding turns on, and reads Not counted for a kind that counts none. The figure row under the queue shows Decisions and Units in question.
What to do
Open a row. The drawer repeats the finding and lays out its own figures by name: Ordered, Expected, Delivered, Over, Short, On the shelf, Not covered, Warehouse counts, Ledger, Booked as a correction. Under them stand the decisions this row takes, each a word: Accept, Close it short, Keep it open, Match it, Reject, It shipped anyway, It was stopped. Any decision may carry a note; Match it on an unmatched line and Accept on an unknown item also need the product, chosen from this order's lines. The consequence stands before the one button, which reads the chosen decision's word, and what the decision did reads back where the button was, in numerals under their own names, with Back to the delivery. Keep it open decides nothing: the note joins the row and the row stays in the queue. Any other decision takes the row out of the queue without a reload. Every decision needs a read and write seat.
When it fails
The exception was not put down.
That is the sentence when the server names no reason; its own sentence shows where it gives one. A queue that cannot be read shows Exceptions unavailable, with a Retry button when allowed.
Bill evidence
Bill matching on the supplier order shows quantity, price, currency and charge evidence. A finding in dispute reads Disputed, and one waiting on a supplier credit reads Await credit; both are flagged as needing attention. If the bill evidence cannot be read, the section says Bill evidence unavailable and offers a refresh.
Follow-up
Open an exception to add a comment, assign an eligible person, set a due time and severity, or snooze it until a chosen time. Due time and snooze are separate. These changes retain their dated history and do not resolve the finding. Show snoozed items to resume follow-up. Access is checked against the affected records; assignment never grants access.
Commitment tasks
Order exceptions in Tasks uses the selected commitment. View orders keeps that scope; Planning tasks returns to the worklist. Counts remain absent until the complete queue is known. Snoozed findings stay available through their control.