The most common procurement problems are the module's own guardrails talking: a release action refusing because nothing is pending, a receive action refusing because a required quantity is missing, or an auto-order quantity that only looks wrong until you read the arithmetic stored on the line. This page maps each symptom to its cause and fix.
This page remains text-only because the standard lists do not display the validation messages or backend three-way result described below. A generic Bills screenshot would look plausible but would not prove any of these conditions.
A goods receipt won't receive or post
- "Supplier Quantity is required for Goods Receipt Lines before receiving." Every unposted line needs the supplier quantity filled in before Perform Receive will run.
- "All Goods Receipt Lines have already been posted to Inventory." The receipt is done. If more goods are coming, release a new receipt from the order's remaining pending quantity.
- Received quantity isn't showing as available stock. If the item has Inspection On Receipt enabled, its received quantity is held under inspection until the inspection completes — that is the design, not a stuck posting. Run Perform Inspection, record findings, then Perform Inspection Complete.
- "No Goods Receipt Line requires inspection." The inspection actions only apply to lines whose item carries the inspection flag and which still have quantity pending inspection. If you expected an inspection, check the item's flag (configuration); if you didn't, skip straight past the inspection steps.
- "No Inspection Line found with pending completion." All inspection lines are already done — the inspection is complete and nothing is being held.
A bill is missing from a custom three-way result
The backend match counts a bill line only when PurchaseOrderLineId is present. The current receipt-side Release Bill path sets only GoodsReceiptLineId; those lines are omitted. Inspect the line links rather than the headers. Order-side Perform/Selective Release Invoice carries the purchase-order-line link and, when receipt lines exist, the receipt-line link as well. See the implementation reference.
An auto-order suggested an unexpected quantity
Don't guess — the line carries its own arithmetic. On a Forecasting line, recompute it from the stored snapshot:
projected = quantity available + pending shipments + pending purchase orders
− pending requisitions − pending sale orders
reorder point = lead time × average consumption + minimum order quantity
suggested = maximum order quantity − projectedWalk the inputs; one of these is nearly always the answer:
- A pipeline component is missing or unexpectedly zero — check the order header's include options (in-transit shipments, pending purchase orders, requisitions, open sale orders) and whether the document lines you expected carry the Exclude In Auto Order flag.
- Lead time or average consumption is stale — the reorder point moves with them; update the item's planning attributes.
- Minimum/maximum order quantity is wrong — the suggestion always fills to the maximum, so an inflated maximum inflates every suggestion.
- Several planning rows match the item — parameters are averaged across matching rows (branch-scoped plus unscoped, for example); remove or correct the row you forgot existed.
- An item is missing entirely — no planning attributes for this branch/partner, or a header ABC/FSN exclusion removed it.
After fixing inputs, run Generate Lines again — it replaces the lines with a fresh calculation. If the auto order refuses with "Purchase Order is already generated", that worksheet is closed; create a new auto order.
A release action refuses to run
- Requisition → order: "At least one Requisition Line with quantity greater than zero is required" — every line is fully released or zero-quantity.
- Receipt → bill: "No Goods Receipt Lines found to Release Bill" — every line is fully billed already.
- Any selective release rejects a quantity — you asked for more than that line's pending counter (pending quantity, or pending invoice quantity for bill releases). Enter at most what is pending.
- A purchase-order line looks less pending before goods are physically received — the current receipt aggregate sums
GoodsReceiptLine.OrderedQuantity. Releasing quantity onto a receipt can therefore reduce the purchase-order pending counter before Perform Receive updates actualReceivedQuantity. Inspect the receipt line and inventory ledger instead of treating the order counter as receipt proof.