Shipment completion control

Proof of delivery reconciliation checklist

A signature image or carrier status marked delivered can be useful evidence, but neither explains the whole transaction. The buyer still needs the correct shipment, delivery place, time, package scope, recipient role and exception record before operations closes the order or finance relies on the event.

Discuss delivery evidence View buyer resources

By MINJI Wholesale DeskUpdated August 9, 2026

Direct answer

The short version

Reconcile proof of delivery by opening one case for the shipment or delivery event and preserving the original carrier message, portal record, paper receipt, scan, image or electronic capture with source and retrieval time. Match carrier, tracking, consignment, shipment, order, invoice, package and transport references to the expected movement. Confirm delivery location, date, local time and time zone, event status and the role of the person or system acknowledging receipt without collecting unnecessary personal data. Identify exactly which packages and quantities the evidence covers; do not assume one signature proves every package in a multi-piece consignment. Compare shipped and delivery-confirmed package IDs, item or quantity data where available, carrier event history and consignee receiving record. Separate delivered without exception, partial delivery, shortage, damage, refused, unavailable recipient, alternate location, return to sender, attempted delivery and status-only events. A carrier scan can establish an event in its system but may not prove product condition, buyer acceptance, title transfer or contractual completion. Record visible notation, photos or timestamps under evidence and privacy policy, then obtain receiving confirmation or a qualified exception decision when the evidence conflicts. Link open damage, shortage, wrong destination, delay, invoice hold, replacement or claim cases and keep disputed quantity visible. Close only when every shipped package has a delivery, return, loss or other explained final status and downstream order, inventory and finance records reflect the same supported outcome.

Use this before requesting a quotation

Use delivery evidence carefully without granting it more meaning than it supports

Preserve and identify the delivery evidence

Assign a reconciliation case and capture the original file, scan, carrier API or portal payload, paper document or event screen with source, retrieval time and any later version. Record carrier, service, tracking or consignment number, shipment, order, invoice and delivery references. Keep machine event, human acknowledgement, signature, photo, location signal and free-text note as distinct evidence elements. Do not crop away package lists, timestamps or exception notation. If the carrier replaces a status, preserve the earlier event and correction. Restrict personal names, signatures, phone numbers, addresses and geolocation to authorized users and retention rules. A filename containing the order number is not enough; validate the identifiers inside the evidence and the expected carrier relationship. Detect one POD uploaded against several shipments and several proof files attached to the same event.

Match place, time, party and event

Compare destination address or facility, delivery point, date, local time, time zone, carrier route and status sequence with the shipment. Identify the recipient role such as consignee employee, receiving desk, authorized alternate or unattended process only when supported; avoid presenting a typed name as verified legal identity. UNECE IFTSTA structures transport status or status-change events and can carry references, date and time, party, location and package identity. Check that the delivery event follows collection and transport events and does not conflict with a later exception or return. Treat implausible chronology, wrong country, wrong facility, repeated timestamp, missing event code or a corrected scan as review signals. Where an alternate delivery place is permitted, link the authority and final consignee handoff. Do not infer time-zone conversion from browser display without recording the source zone.

Determine exact package and quantity scope

List every package or logistic-unit identity shipped and mark which the POD explicitly covers. For a master shipment with several cartons, determine whether the carrier evidence is consignment-level or package-level. Compare package count, weight only as a reasonableness signal, item and quantity where available, and the consignee receiving record. UNECE RECADV supports physical receipt and discrepancies in products, quantities, terms and packages. Separate shipped, carrier-delivered, consignee-received, accepted, damaged, short, refused, returned and unresolved quantities. Do not convert a clean signature into an item-level count when the document contains no count. If a pallet was broken or packages traveled under child tracking numbers, preserve the parent-child map. Investigate duplicate package identity and a package shown both delivered and in transit after the same event time.

Classify exceptions without rewriting facts

Use defined states for complete delivery, partial, shortage, overage, visible damage, concealed damage reported later, refusal, wrong address, recipient unavailable, secure alternate location, delivery attempt, loss, return and disputed status. Retain the carrier's original code and map it to the internal state rather than changing its wording. Record consignee notation, notice time, photos, count sheets, packaging condition and carrier response under policy. A blank exception field may mean no exception was recorded, not that the goods were inspected and perfect. Link a damage or shortage claim with the affected package and quantity while leaving unaffected packages closed where supported. Record reporting deadlines from the actual contract or carrier terms after qualified review; do not publish a universal claim window. Keep an attempted delivery distinct from completed delivery even if the route is operationally finished.

Resolve conflicting evidence

When carrier status, signature, geolocation, consignee receiving, customer message and inventory record disagree, freeze automatic closure for the affected scope. Request the original event details through validated channels and verify shipment identity before sharing sensitive information. Build a timeline of pickup, transit, out-for-delivery, delivery, exception, return and customer notice. Check for reused tracking numbers, split consignments, transshipment, neighbor or alternate facility delivery and a duplicate order. Assign an owner and next evidence date. Do not accuse a carrier, driver, employee or customer of misconduct from one mismatch. Decide the supported operational state, claim action and financial hold through authorized review. Preserve unresolved status rather than forcing the order to delivered merely to clear a dashboard backlog.

Align order, inventory and finance records

Update shipment and order completion only for the packages and quantities supported by the reconciliation. Link returned or refused goods to reverse logistics and actual warehouse receipt. Keep loss, damage, shortage, replacement and credit cases open until their separate evidence and settlement steps complete. Review invoice release, revenue or payment effects with qualified finance owners under the agreement and applicable rules; delivery evidence alone does not prescribe accounting. Prevent both original and replacement shipment from closing the same demand without a visible reason. Reconcile carrier freight invoice accessorials or service claims to the event timeline without assuming the POD establishes liability. Notify the customer or supplier using approved facts and protect signatures and contact information. Record which system is authoritative for each state rather than copying a single delivered flag everywhere.

Close the case and monitor quality

Close only after all shipped package IDs have one explained outcome, the consignee result is recorded, exceptions have owners or final decisions, and order, inventory, replacement, claim and finance dependencies agree. Keep open and close dates, reviewer and evidence list. Monitor POD availability, reference match, package coverage, status correction, partial-delivery rate, exception notation, reconciliation cycle and unresolved age. Compare carrier and route populations only after controlling for service and shipment type. Sample clean automated matches against consignee receiving records and sample receiving records back to carrier evidence. Recurring wrong reference, missing child package, time-zone, unreadable signature or late file issues should produce a carrier-data or internal process correction. Do not reward speed that closes unsupported delivery; measure both cycle time and later reversal.

Reusable buyer brief

Proof of delivery reconciliation record

Case ID, evidence type, source, retrieval time and original file:
Carrier/service, tracking, consignment, shipment, order and invoice IDs:
Expected and recorded delivery place, date, time and time zone:
Recipient role, acknowledgement method and privacy controls:
Master and child package IDs, shipped count and POD coverage:
Carrier-delivered, consignee-received and accepted quantities:
Status sequence, original codes, corrections and chronology check:
Damage, shortage, refusal, alternate location or other exception:
Receiving record, photos/notes, customer notice and carrier response:
Conflict decision, owner, next evidence date and authority:
Order, inventory, return, replacement, claim and finance updates:
Final outcome by package, reviewer, metrics and close date:

Fill only the details relevant to your request

Before you send the request

Questions buyers often ask

What should proof of delivery be matched against

Match it to carrier and tracking references, shipment and order IDs, destination, event time, package identities and the consignee receiving outcome.

Does a signature prove every item arrived undamaged

No. It may support a delivery event, but package scope, count, condition and product acceptance require the evidence actually recorded and the receiving process.

How is partial delivery reconciled

Mark each package and quantity as delivered, missing, damaged, refused, returned or unresolved, then close only the supported portion and retain linked exceptions.

Can an order close from a carrier delivered scan

Only if the defined control accepts that evidence for the covered scope and no conflicting event exists; contractual and financial effects still require their own rules.

Keep the request specific

Proof of delivery is evidence, not a universal determination of acceptance or liability

The legal and commercial effect of a signature, photo, scan, geolocation, carrier event or consignee receiving record depends on the contract, transport terms, privacy rules and jurisdiction. This operational checklist does not determine title, risk transfer, revenue, payment entitlement or claim liability. Use qualified legal and finance review where those questions matter. Collect only necessary recipient data, protect signatures and addresses, and avoid publicly exposing delivery evidence. Retain the carrier's original event and any correction so a later dispute can distinguish system status from physical receipt.

Send this checklist on WhatsApp

Editorial method

How this guide was prepared

MINJI preserves the original delivery evidence, validates movement identity and chronology, determines package and quantity scope, classifies exceptions and then reconciles downstream records. UNECE IFTSTA provides transport-status event structure, RECADV provides physical receipt and discrepancy structure, and GS1 EPCIS supports identified-object shipping and receiving events. The method deliberately separates carrier status, consignee receipt, product acceptance and contractual effect.

UNECE UN/EDIFACT — International Multimodal Status ReportPrimary status-event structure covering movement references, event time, party, location, conveyance and package identity.
UNECE UN/EDIFACT — Receiving Advice MessagePrimary goods-receipt structure for packages, quantities, physical state and discrepancies against despatch or order information.
GS1 — EPCIS and CBV 2.0.1 StandardPrimary event-data standard for identified objects, location and business context across shipping, transport and receiving.

Ready with the key details

Discuss a wholesale request

Send the product reference, estimated quantity and destination so the conversation starts with useful context.

Continue on WhatsApp