The case study states:
The company often receives a higher quantity of produce items than ordered because vendors allow for spoilage/damage during transit.
The company wants to allow over-receipt only for produce but not for non-produce items.
In Dynamics 365 Business Central, this requirement is handled by Over-Receipt Codes:
You define a code with a tolerance percentage (e.g., 5% or 10%).
The code can be assigned to specific items (e.g., produce) or vendors.
This allows receiving slightly more than ordered, while blocking over-receipt for other items.
Why not the other options?
B. Payment Tolerance % → relates to differences in payment amounts (e.g., customer underpaying by a few cents), not receiving inventory.
C. Default Deferral Template → used to defer revenue/expense recognition over time, unrelated to item receipt.
D. Dampener Quantity → used in demand planning/MRP to avoid unnecessary changes to supply orders; not for receiving more items.
So the correct configuration is Over-Receipt Code with Tolerance %.
[Reference:, Allow Over-Receipt in Purchase Orders, , , ]
Submit