Separate site delivery, receipt and acceptance
Understand the problem
TL;DR — what you’ll learn
- Record physical delivery promptly, even when inspection or documentation remains incomplete.
- Distinguish custody, recorded receipt and acceptance for use so held material does not appear freely available.
- Reconcile delivered quantities into accepted, held, rejected or disputed quantities without overlaps.
- Define the accounting treatment separately with finance; operational acceptance alone does not determine every posting.
Twenty panels arrive at a construction site. Two have visible damage and three lack required documents. The driver needs a delivery acknowledgement, the storekeeper needs a stock record and the installation team wants to know how many panels it can use.
Those are three different decisions. A goods receipt process should preserve the physical fact of arrival while controlling release for use. If the system forces the storekeeper to choose between ignoring the delivery and accepting every panel, the process is missing a useful intermediate state.
Illustrative non-overlapping groups. Accepted panels have completed their required checks. Bars share a 20-panel scale.
Read the visual as text
Accepted: 15 panels. Available under the approved release process.. Damaged hold: 2 panels. Await authorised disposition.. Document hold: 3 panels. Await required records and verification..
Original explanatory visual: NextEdge Labs. Illustrative records, not client results.
- STEP 01Record physical arrival
Owner: Receiving team
Capture quantity, identity and visible condition.
- STEP 02Inspect and reconcile status
Owner: Quality + stores
Identify accepted, held and disputed portions without overlap.
- STEP 03Authorise release or disposition
Owner: Qualified quality owner
Retain inspection, document and exception evidence.
- STEP 04Reconcile stock and finance
Owner: Stores + finance
Align physical location, availability and policy-based postings.
Route that identified item for authorised release.
Keep it segregated and unavailable while the relevant issue is resolved.
Return path: Return to inspection review when missing evidence or corrective work is ready.
Read the workflow as text
1. Record physical arrival (Receiving team) → 2. Inspect and reconcile status (Quality + stores) → 3. Authorise release or disposition (Qualified quality owner) → 4. Reconcile stock and finance (Stores + finance). After step 2, ask: Are required checks and documents complete for this item? Yes: Route that identified item for authorised release. No: Keep it segregated and unavailable while the relevant issue is resolved. Return: Return to inspection review when missing evidence or corrective work is ready.
Workflow: NextEdge Labs. Apply the project’s actual authority and procedures.
Record custody before debating acceptance
Capture the delivery date and time, supplier, order line, delivery note, vehicle or consignment reference, quantity and unit of measure. Identify the receiving location and person. Record visible condition, shortages and supporting photographs where appropriate.
An acknowledgement of delivery should make any reservations clear under the project's procedure. It should not accidentally communicate acceptance of quality or completeness. The specific wording and contractual effect require the relevant commercial review; the operational objective is to preserve what arrived and what was observed.
Assign a stable receipt reference even if the ERP posting will follow later. Otherwise, material may sit on site without appearing in either stock or exception reports. Track the gap between physical arrival and system recording so late entries can be investigated.
Give inspection a clear quantity boundary
An inspection request should identify the items or lots under review, the applicable order specification and the required documents or tests. For tagged equipment, use the tag or serial identity. For bulk deliveries, use an appropriate lot or consignment boundary.
ERPNext's purchase receipt documentation distinguishes accepted and rejected quantities and associated warehouses. A project may also need a controlled hold status or location; that additional design should be tested rather than assumed to exist in every configuration.
The receiving team should know who can move material from hold to accepted stock and what evidence is required. A missing document may be resolved without changing the physical item. Damage may require repair, replacement or a formal disposition. These paths should remain distinguishable.
Reconcile the twenty-panel delivery
For the twenty-panel illustration, assume two panels are damaged and three different panels lack required documentation. Because the groups do not overlap, fifteen panels can be considered for acceptance once their checks pass, while five remain unavailable for installation.
Scroll horizontally to see all columns.
| Receipt outcome | Panels | Next action |
|---|---|---|
| Checks complete and accepted | 15 | Release under the approved process |
| Damaged and held for disposition | 2 | Record condition and obtain an authorised decision |
| Documentation incomplete | 3 | Obtain and verify required records |
| Total physically delivered | 20 | Reconcile to the delivery record |
If one damaged panel also lacks documents, simply subtracting two and three would double-count that panel. Use item identities or mutually exclusive quantity buckets to determine the actual split. Keep multiple reasons against an item while counting its physical quantity only once.
Suppose the three documentation holds are later resolved. Transfer those three into accepted stock with the release evidence. The original arrival record remains twenty; the accepted total becomes eighteen. The two damaged panels remain visible until their disposition and movement are completed.
Connect physical locations with system status
A hold in the system is weak if the material is mixed with available stock and can be issued casually. Use appropriate segregation, labels or location controls, taking account of the item's size and handling requirements. The storekeeper should be able to identify held material during a physical check.
Conversely, a fenced quarantine area is insufficient if the ERP counts its contents as available to material planning. Align physical location, stock status and issue permissions. Test any mobile or offline issue process as well as the desktop screen.
For partial acceptance, preserve the connection between accepted and held portions of the same delivery. Procurement needs that information when following up replacements or supplier credit. Accounts needs it when matching documents under the agreed finance policy.
Keep financial recognition as an explicit policy decision
A receipt may trigger an inventory or clearing-account entry in a configured ERP. That does not mean every physical delivery should use the same accounting treatment. Ownership terms, the nature of the item, acceptance conditions and the organisation's accounting policy can matter.
Finance should define how held, rejected, returned and service-related receipts are treated, including period-end cases. The receiving procedure should provide the evidence needed for that decision rather than asking stores staff to improvise journals.
Avoid treating a supplier invoice as proof that the delivery passed inspection. Equally, do not suppress a genuine receipt simply because the invoice has not arrived. The month-end accrual process should check existing receipt-related recognition before proposing an additional entry.
Resolve discrepancies through linked records
A shortage should remain linked to the order and delivery evidence. Record whether the supplier will replace it, issue a credit or dispute the count. An overdelivery needs a decision about custody, use and commercial acceptance before it becomes ordinary available stock.
For damaged items, preserve the initial condition record and the approved disposition. If a repair is permitted, record the required verification before release. “Supplier informed” is a follow-up action, not closure of the material exception.
Returns should reference the original receipt, quantity, reason and dispatch evidence. Reconcile the physical return with replacement supply or credit as applicable. A returned item should not remain counted as held stock on site after it has left.
Check the process at the boundary cases
Run a test delivery with partial acceptance, a missing certificate and a later return. Verify that the available quantity changes correctly at each step and that the receipt total can still be reconstructed. Then test a quantity conversion, such as pieces received against an order in sets.
At month-end, compare gate or delivery records with recorded receipts and open inspection holds. Investigate material physically present but absent from the system, as well as system stock that has been returned or consumed. Track the age and reason of holds so unresolved paperwork does not become permanent hidden inventory.
Give the site one reliable answer about availability
The receiving record should let the site answer three questions separately: what arrived, what is in its custody and what is permitted for use. That clarity supports installation planning, supplier follow-up and finance reconciliation.
- Capture physical delivery evidence at arrival.
- Reconcile quantities into non-overlapping operational statuses.
- Require authorised evidence for release from hold.
- Align storage locations and issue permissions with those statuses.
- Reconcile receipt exceptions, returns and accounting records at close.
Recognise this problem in your operation?
Tell us where the records or handovers break down. We can discuss the process, data and software questions worth examining first.
References and further reading
Sources checked 15 October 2026. The worked examples and diagrams are original editorial explanations, not client results.
- ERPNext documentation — Purchase ReceiptAccepted and rejected quantities, warehouses and quality inspection references
Product receipt behaviour.
Visual credits
Original explanatory visuals and workflow diagrams by NextEdge Labs. Labels and text equivalents are included in the page. Numerical scenarios are illustrative; diagrams preserve the project owner’s approval and exception decisions.