Proof of delivery process flowchart (ePOD capture to invoice)

What the proof of delivery process flowchart (epod capture to invoice) process is

Proof of delivery is the evidence half of a delivery. Moving the goods is the shipping job; the proof is the record that says who took them, when, in what condition and on whose authority. The trigger is the vehicle arriving at the delivery point, and the chart below follows one consignment from that moment to the point where the record is closed: the check that an authorised recipient is actually there, the signature, one-time PIN or leave-safe photograph that captures the handover, the damage or shortage annotated on the receipt before anyone signs it, the electronic POD synced back off the handheld, the completeness check that catches an unreadable name or a missing piece count, the POD filed against the delivery order and published to the customer, the invoice released against it, and the dispute window in which that same record is retrieved as evidence.

This chart is deliberately narrow. It is not the shipping process, which ends where this one begins: carrier and service selection, labels and export documents, the load check against the manifest and the collection are all upstream of the first box here. It is also not the delivery exception process, which takes a flagged exception through customer notification, reattempt or reroute, replacement or refund, the carrier claim and the root-cause review. This chart hands off to both: a delivery nobody can accept leaves it at 'Return to depot for redelivery', and a dispute the record cannot answer leaves it as a credit and a carrier claim. Keeping the boundary visible matters because POD is the evidence layer underneath both of those processes, and an organisation that models it inside them ends up with no single answer to what its delivery record must contain. Carriage terms, claim windows and record retention differ by jurisdiction and by contract, so treat this as a starting point to adapt to your own terms of carriage and review with whoever advises you on them.

Four decisions carry the process. 'Authorised recipient available?' settles the branch that produces most of the exceptions, and it sits in the driver's lane because the driver is the only person who can answer it in the moment. 'Damage or shortage at the door?' sits in the recipient's lane on purpose: condition is what the recipient is accepting, and once the vehicle has gone the annotation cannot be added. 'POD complete, legible and matched?' is the quality gate in the dispatch lane, and it is the one most POD processes leave out entirely, which is why they discover a defective record weeks later during an invoice query. 'Delivery disputed by the customer?' is what the whole capture chain exists to answer, and it sits with the customer rather than with finance because the dispute arrives from outside.

What this flowchart covers

In this template

• Five swimlanes (Driver / carrier, Customer / recipient, Dispatch, Customer service and Finance / billing) across six phases: delivery attempt, identity and capture, condition and exceptions, upload and match, release and billing, and disputes and retention
• An "Authorised recipient available?" decision at the door, with an unattended branch that asks "Leave-safe authorised on the order?" and sends anything without a customer instruction to "Return to depot for redelivery" rather than letting the driver decide on the pavement
• Capture modelled as a real choice rather than a signature box: "ID or PIN required for this consignment?" routes age-restricted, controlled and high-value consignments through a one-time PIN or identity check before the step that captures the recipient's signature on the device
• Condition captured while it can still be captured, with "Damage or shortage at the door?" leading to "Annotate the POD and photograph the damage" in the driver's lane, so the annotation and the photographs exist on the receipt before it is signed and the vehicle released
• A completeness gate most POD processes skip: "POD complete, legible and matched?" checks the synced record against the delivery order and loops through "Re-capture the missing POD detail" until it passes, instead of discovering the defect during an invoice query
• The commercial half, where "Release the invoice on the matched POD" makes the record a billing trigger, "Exception recorded on the POD?" bills the delivered quantity rather than the picked one, and "POD evidence answers the dispute?" decides between closing the dispute and issuing a credit

When to use this template

• You are rolling out electronic proof of delivery and need the process agreed before the handheld screens, capture rules and portal are configured
• Customers are querying invoices and nobody can produce a legible POD quickly enough, so the record is settling arguments after they have already cost money
• Drivers, dispatch and finance disagree about what a valid delivery record contains, and the disagreement only surfaces when a claim or a deduction arrives
• You are moving invoicing onto a POD trigger and need the completeness and exception checks drawn before billing depends on them
• An auditor or a large customer has asked for a documented description of how delivery is evidenced, matched and retained

How it works

1. Rename the lanes to your roles

   Replace Driver / carrier, Customer / recipient, Dispatch, Customer service and Finance / billing with the roles that genuinely exist in your organisation. If you use a third-party carrier, the driver lane belongs to them and the handoff is a data feed rather than a conversation, which usually changes where the completeness check has to sit.

2. Define who counts as an authorised recipient

   Write your rule onto the first decision: a named signatory only, anyone at the address, a reception or security desk, a neighbour, a site contact on a construction project. State what the driver does when the person present is not on the list, and whether the customer can authorise a substitute by phone while the vehicle is there.

3. Set the capture rule for each consignment type

   Decide which orders need more than a signature. Age-restricted goods, controlled substances, high-value electronics and cash on delivery usually need an identity check or a one-time PIN. Encode the rule in the order system so the handheld asks for it, rather than relying on the driver to remember which consignments are different.

4. State what a complete POD must contain

   List the fields: printed name as well as signature, piece count actually handed over, time stamp, position, photographs, and any annotation of damage or shortage. This list is what the completeness gate checks against, and it is also what you will hand a carrier or a customer when a claim is assessed months later.

5. Agree the damage and shortage wording

   Give drivers and recipients the words to use. An annotation naming the packages affected, the nature of the damage and the quantity short is evidence; a blanket note that the load is subject to inspection is routinely refused. Agree who is called from the door when the recipient wants to refuse part of a consignment.

6. Wire the POD to the invoice and the credit

   Decide whether the invoice is released automatically on a matched POD or reviewed first, what happens to a line the receipt says was short, and who may authorise the credit. Also set how long a customer has to raise a dispute before the delivery is treated as accepted, and where that window is stated to them.

7. Walk it against a real disputed delivery

   Take two recent deliveries, one clean and one that went to a claim, and trace them through the chart. Ask what evidence you actually had, how long it took to find, and which box would have produced it. Any step people describe that is not drawn, or drawn but skipped in practice, is the finding worth acting on before you publish it.

Frequently asked questions

What are the steps in a proof of delivery process?

The driver arrives at the delivery point and checks whether an authorised recipient is available. If nobody is in, dispatch checks for a leave-safe instruction: with one the driver photographs the location and label; without one the consignment returns to the depot for redelivery. Where a recipient is present, the driver checks them against the delivery note, takes a PIN or identity check if the consignment requires it, and captures the signature. Damage or shortage is annotated on the receipt and photographed before it is signed. The electronic POD is synced, checked for completeness and a match to the order, re-captured if anything is missing, filed against the delivery order and published to the customer. It then releases the invoice, with a credit where the receipt records an exception. A dispute sends the POD back as evidence; if it does not answer, a credit is issued and a carrier claim opened.

What is the difference between a proof of delivery and a bill of lading?

A bill of lading is issued at the start of the journey. In the United States, 49 CFR 373.101 requires a for-hire, non-exempt motor carrier to issue a receipt or bill of lading for property tendered for interstate or foreign transportation, showing the consignor and consignee, the origin and destination, the number of packages, a description of the freight and, where it affects the rating, the weight, volume or measurement; the carrier keeps a record of it as prescribed in 49 CFR part 379. It is the carrier's receipt for the goods and evidence of the contract of carriage. A proof of delivery is the other end: the record that the consignment was handed over at destination, to whom, when and in what condition. In road haulage the two are often the same piece of paper, but they answer different questions. The bill of lading says what was accepted for carriage; the POD says what arrived.

Is an electronic signature on a proof of delivery legally valid?

In the United States, the Electronic Signatures in Global and National Commerce Act of 2000 gives a signature, contract or record legal effect that is not denied merely because it is in electronic form. In the European Union, Regulation (EU) No 910/2014, the eIDAS Regulation, provides that an electronic signature is not denied legal effect or admissibility as evidence solely because it is electronic, while a qualified electronic signature has the equivalent legal effect of a handwritten one. In practice, delivery disputes are rarely won on the form of the signature. They are won on the surrounding record: the printed name of the person who signed, the piece count they accepted, the time stamp and position, the photographs and any annotation. Capture those alongside the signature and keep them together, because a signature retrieved without its context proves very little on its own.

How long do you have to note damage on a delivery receipt?

It depends on the carriage regime, and the deadline at the door is far shorter than the one for the claim. Under the CMR Convention, which governs most international road carriage in Europe, a consignee who takes the goods without checking their condition with the carrier must send reservations at the latest at the time of delivery where the loss or damage is apparent, and within seven days, Sundays and public holidays excepted, where it is not; compensation for delay is payable only if a reservation is sent in writing within twenty-one days of the goods being placed at the consignee's disposal. In the United States, 49 U.S.C. 14706(e) sets minimums a carrier must allow rather than fixed deadlines: at least nine months from delivery to file a claim and two years from written disallowance to sue. Concealed damage windows are set by the carrier's own bill of lading or tariff.

How long should proof of delivery records be kept?

Long enough to outlive both the claim window and the accounting record it supports: the longer of the two, not a single number. Claim periods run from delivery, so a record destroyed at the end of a financial year can disappear while a claim against it is still live. In the United States the Carmack minimum alone allows nine months to file and two years from a written disallowance to sue, and under 49 CFR 370.9 a carrier has 120 days to pay, decline or make a firm written settlement offer. On top of that sit commercial and tax retention rules, which are set by your own jurisdiction. Set one retention period per record type, apply it to the whole capture trail rather than to the signature image alone, and state who may delete a POD early. Storing the images and losing the metadata is the common failure: an archive nobody can search inside an hour is, for dispute purposes, no archive at all.