Warehouse Overreceipts

Four options, each with tradeoffs.

Six goals grouped by Buyers, Warehouse, Requesters, and Payables. Tags rate options against goals to visualize the tradeoffs.

How Oracle handles overreceipts

Two decisions: how much can be recorded as received, and how much can be invoiced without a matching hold.

1. Receiving checks the physical; Payables checks the financials

An overreceipt means recording more than the ordered quantity. A physical overshipment is different: boxes can be on the dock even when Oracle rejects the excess receipt. Receiving that extra also does not increase the PO’s ordered quantity.

Fusion pairs an Over-receipt Tolerance Percent with an Over-receipt Action. For 100 ordered and 5% tolerance, the threshold is 105 total units; the action determines what happens above that threshold.

2. Where receiving tolerances are entered

Defaulting priority: PO setting → item in the ship-to organization → supplier site → receiving organization. The percentage and action each default separately. If you enforce blind receiving, then the action is also ignored.

Two easy-to-miss settings: Receipt Close Tolerance controls automatic receipt closing, not permission to overreceive. Also review blind receiving: it ignores quantity receipt tolerances! [3] [1]

3. WMS has its own receiving controls

In Oracle WMS Cloud, Shipment Types define overreceipt warning/error percentages and whether validation uses the PO, inbound shipment, or both. With Line Level Tolerance enabled, review Warning % and Error % on PO Detail and/or IB Shipment Detail. When both are checked, WMS uses the lower warning and error thresholds. Without the flag, Shipment Type tolerances apply.

Treat WMS enforcement and Fusion receipt confirmation as an end-to-end design; apply the same settings in both to avoid confusion. WMS setup [5] · line-level controls [6]

4. Which invoice holds can result?

Define matching tolerance sets in Manage Invoice Tolerances. Assign quantity- and amount-based defaults in Manage Invoice Options for the invoice BU, with supplier-site assignments for exceptions. These are separate from the supplier site’s receiving controls. [7] [8]

2-way compares PO and invoice; 3-way adds receipts; 4-way adds inspection acceptance. Match approval level is separate from the invoice match option of PO versus receipt. [9]

Percentages are entered as numbers: 5 means 5%, so use 0.05 in the formulas. Enabled checks operate independently; both percentage and maximum-unit holds can apply. [8] [10]

For amount-based matching, the corresponding codes are AMT ORD, MAX AMT ORD, AMT REC, and MAX AMT REC. Unit-price differences can produce PRICE; inspection shortfalls can produce QUALITY. Neither is a generic “overreceipt hold.” Invoice Validation applies matching holds; after correcting the cause, revalidate to reassess them. [10]

Zero is not disabled. An enabled percentage tolerance of 0 allows no variance. An enabled percentage tolerance of null allows unlimited variance. [8]

Practical implication: receiving all may remove one obstacle to invoice matching, but it does not authorize increasing the order or paying for unwanted extras. Conversely, recording only ordered quantity leaves Warehouse with real boxes and follow-up work.

Before raising a PO or recording another receipt, check the match, cumulative invoices, duplicate billing, UOM, and kit/component lines. A hold describes a failed comparison, not its root cause. For investigation and cross-team resolution, see Resolving Match Exception Invoice Holds in Oracle Fusion.

Try a shipment

See the receiving action, modeled invoice holds, and dollars above the PO. This example attempts to receive the full arrived quantity.

Additional design considerations