A supplier can deliver less than ordered, deliver in several shipments or send an unexpected extra quantity. A single received checkbox cannot express those situations. Scope receiving around order lines and traceable quantities.
Related service: CRM, ERP and web application development- 01Identify the approved order line.
- 02Record the delivered quantity and unit.
- 03Review differences and condition.
- 04Accept the permitted receipt.
- 05Keep or close the remaining commitment.
SECTION 01
Separate the quantity states that matter
Specify the unit on every line and whether the order allows partial delivery. If goods need inspection, arrival and acceptance can be different events. The remaining commitment should be calculated from the approved rule, not from a manually typed overall order status.
Microsoft's receipt documentation provides a concrete example of receiving against purchase orders. Use it to frame questions, not to imply that every product follows identical settings. Decide how the application handles excess quantities, missing references and receipts against cancelled lines. An ordinary receiver should not obtain authority to increase the purchase commitment merely by entering a larger delivery.
SECTION 02
Illustrative example: twenty ordered and twelve received
Suppose a team orders twenty units. Twelve arrive, two of which require review because of visible damage. The system records twelve physically received, ten accepted and two awaiting a decision. The remaining supplier commitment depends on the approved treatment of those two units. This is an illustrative scenario.
A later delivery must reference the same order line without replacing the first receipt. If the supplier cannot deliver the balance, purchasing can close or revise that remainder with a reason. The warehouse should not clear it just to remove an item from its receiving queue. Both teams need a view of the outstanding decision.
SECTION 03
Test corrections as well as normal deliveries
Begin with one receiving workflow and the current purchasing system as the authoritative order source. Existing receipt functionality may already meet the need. A custom receiving interface is useful only if it preserves those controls and provides a clearer workflow for the team.
Ask the agency to demonstrate a duplicate delivery reference, a reversed receipt, an excess quantity and two people receiving against the same remainder. Reconcile accepted quantities back to their receipts and approved order. Database transaction controls help coordinate simultaneous updates, but operational acceptance requires evidence that the line cannot be over-consumed under the actual business rule. Include an exception owner and a clear correction path in the first release.
SECTION 04
Frequently asked questions
Does a partial receipt close the order?
Only if an authorized decision closes the remaining commitment. Otherwise the order should continue showing what is outstanding.
Can damaged goods count as available stock?
Not automatically. Agree the inspection and disposition process, and distinguish arrival from accepted, usable inventory.
What prevents duplicate receipts?
Use stable references and a defined repeat-submission rule, then test reruns and simultaneous entry against the same order line.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Product receipt against purchase ordersMicrosoft Learn
- Transaction isolationPostgreSQL
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy