The POD paperwork that stops invoices slipping
What a proof of delivery document is, what it should include, and how UK haulage firms can stop missing PODs delaying invoices.
If invoices keep slipping, the problem is often not pricing, credit control or the customer. It is the gap between the job being done and the office having a usable POD. In a small haulage business, that gap can be one driver’s paperwork on a passenger seat, one missing signature, or one delivery note that never makes it from the cab to accounts.
A good proof of delivery document does one simple job. It proves the work happened, in a form your customer accepts and your accounts team can invoice against without chasing three people first. When that proof is late, unclear or missing, cash moves late as well.
What a proof of delivery document is in day-to-day haulage
In practical UK haulage terms, a POD is the record that confirms the load was delivered, or that delivery was attempted, at a particular place, on a particular date and time, with the relevant exceptions noted. It is not just a signed bit of paper for the file. It is the handover point between operations and invoicing.
On a straightforward pallet delivery, that might be a delivery note signed by the consignee. On container work, it may include container number, arrival and departure times, site references, waiting time, and any issue affecting container turnaround. On a multidrop route, each stop needs its own clear proof. On a backload, the pickup and the delivery each need their own trail. If a subcontractor is involved, you still need the same standard of evidence if you are billing the customer in your own name.
Operators rely on PODs because they answer the first questions that come in after the wheels stop turning. Was it delivered? Who signed? What time was it tipped? Were there damages? Was there a refusal? Was there waiting time? Did the driver arrive in slot? Did the site impose conditions that changed the job?
Customers rely on them for their own internal controls. Many of your customers cannot release payment until they can match your invoice to their purchase order, booking reference or goods received process. If your proof of delivery document does not line up with what their traffic desk, warehouse team or accounts team expects to see, the invoice sits.
Your accounts team, even if that is one person in the office or the owner doing it at night, relies on PODs because they turn a completed movement into a billable movement. Without that handover, the invoice gets delayed, queried or raised incorrectly. That is how jobs done on Tuesday end up invoiced a fortnight later.
In the UK, there is no single statutory form of POD for general haulage. What matters is whether the record is good enough for the contract, the customer’s process, and any dispute that follows. If you are moving internationally, other documents may sit alongside it, including CMR on applicable journeys, but day-to-day domestic haulage still lives or dies on whether the delivery evidence is complete and accessible.
What information a POD needs to be useful
A technically completed POD is not always a useful one. “Signed by customer” is not enough if nobody can read the name, there is no time, and the delivery location is one of six units on an estate.
For a POD to be usable in disputes, customer queries and invoicing, we need a few basics every time.
First, it needs to tie clearly to the job. That means your job number, customer reference, booking or order number where relevant, collection and delivery points, vehicle registration, trailer if relevant, and the driver’s name or ID. If you do container work, add the container number, size and type. If the movement is linked to a port or shipping line process, those references need to be there too.
Second, it needs the delivery event itself. Date, arrival time, departure time where that matters, recipient name, signature or equivalent confirmation, and the exact delivery location. On many sites, “delivered to customer” tells you nothing. “Bay 4, Unit C, signed by J Smith, 10:42” is what settles arguments.
Third, it needs exceptions recorded properly. Damaged goods, short delivery, refused goods, site delays, failed delivery, wrong booking reference, no one available to receive, seal broken, packaging compromised. If the load was accepted with remarks, those remarks need to be legible and attached to the same record. A clean signature on one page and the damage note on another page that never comes back to the office is how claims start.
Fourth, it needs supporting evidence where the job calls for it. Photos matter on damaged freight, refused deliveries, inaccessible sites, unsafe unloading conditions and container condition issues. Time stamps and location data are useful where customers challenge waiting time, detention, demurrage, or arrival within a booking slot. The point is not to collect data for its own sake. It is to capture what someone will ask for later.
Fifth, it needs to be readable by accounts. That sounds obvious, but it is where many PODs fail. If the delivery note number is smudged, the signature is on the wrong page, and the waiting time is written as “45?” in the margin, someone in the office has to ring the driver, ring the customer, or guess. Guessing creates credit notes. Chasing creates delay.
A useful proof of delivery document also needs to match your charging model. If you bill waiting time after a free period, the POD must show the actual times and, ideally, the reason. If you bill for redelivery, attempted delivery or handball, the POD needs the note that supports it. If you are charging for timed delivery, out of hours attendance or a failed collection, the evidence has to be captured at the point the event happens, not reconstructed later from memory.
Why paper PODs go missing and cost money
Paper does not usually fail in one dramatic moment. It fails in small, ordinary ways throughout the day.
The first failure point is the cab. The driver gets a signature, puts the paperwork on the passenger seat, then takes another job. By the end of the shift there are six sets of papers mixed together, one coffee stain, one page torn off for a gatehouse, and one POD still in the door pocket on Friday night. Nobody set out to lose it. It just did not get handed over cleanly.
The second failure point is the traffic office. A driver drops paperwork in a tray at 18:30 when the planner is dealing with a breakdown, a late-running collection and the six o’clock phone call from a customer asking where their delivery is. The paperwork sits until tomorrow. Tomorrow becomes next week if the invoice run depends on someone manually checking every page.
The third failure point is accounts. They have the signed note, but not the rate confirmation. Or they have the delivery note, but cannot read the booking reference the customer needs on the invoice. Or the POD is there, but the waiting time that should have been billed is not. So the invoice is held back while someone asks operations what happened.
This is where paper starts costing money. Not because paper itself is expensive, but because delay and uncertainty are expensive.
Cash comes in later because invoices go out later. Queries take longer because the office cannot put its hands on the document straight away. Chargeable extras are missed because they were noted on paper but never transferred into the invoice. Drivers get interrupted with calls asking what happened on jobs they did three days ago. The customer gets two versions of the story because traffic remembers one thing and the paperwork shows another.
For container operators, the cost can be sharper. If a POD does not clearly show arrival, departure and site delay, you are in a weaker position when discussing waiting time, demurrage or detention-related costs with the customer. If the paperwork around a quay move, warehouse slot or empty return is incomplete, it becomes harder to defend what happened to container turnaround.
Paper also creates double handling. One person writes the job details onto the delivery note. Another person reads that note and keys them into the TMS or the invoice. If anything is unclear, they stop and ask. We see this all the time in firms that are running good operations but poor handovers. The work is done. The proof exists. It just is not where it needs to be, in a usable form, at the right time.
When ePOD is better than paper
ePOD is better than paper when the main problem is speed, legibility and handover. It is not better because it is fashionable. It is better because it gets the evidence from the job into the office without waiting for a driver to return with a stack of paper.
At the job, ePOD can capture the recipient name, signature, time, date, photos, notes and status in one record. It can tie that record straight back to the planned job, so accounts are not matching scraps of paper to a spreadsheet later. If a load is refused, damaged or delayed, the driver can record the reason there and then. If there is a query at 16:00, the office can see what happened before the vehicle is back in the yard.
That matters on ordinary general haulage jobs, and even more on work with tight booking slots, customer callovers and multiple references. It also matters when you are using a subcontractor and need the delivery evidence back promptly enough to bill your own customer without waiting days for paperwork.
For container work, ePOD helps when the details that matter are operational, not just administrative. Arrival and departure times, site notes, container references, and photos of condition or seal status are far more useful when captured as part of the live job record than scribbled later. If you want to see what good capture looks like in practice, our POD and delivery note handling page shows the workflow.
That said, ePOD is only better if the process is clear. A bad process on a phone is still a bad process.
Drivers still need to know when to mark a job delivered, when to mark it attempted, what to photograph, and what notes to add for chargeable events. The office still needs rules for what can be invoiced automatically and what needs checking. If a customer insists on its own paper stamp as well as digital confirmation, that needs to be part of the brief. Some sites still want a physical note handed in at the gatehouse. ePOD does not remove customer requirements. It stops your own business losing control of the evidence.
The best results come when ePOD is linked to the rest of the job flow. If the same system plans the work, briefs the driver, tracks progress and captures delivery, there is less rekeying and less ambiguity. That is why we built Logivo to connect those steps, including live driver progress against the job, so the office is not piecing the day together from calls and messages.
How to tighten up POD handling without making the day harder
Most firms do not need a big implementation project to improve POD handling. They need a shorter, cleaner path from completed job to invoice.
Start by deciding what a “complete POD” means for your business. Write it down in one page. For example, every completed delivery must have the job reference, customer reference where applicable, recipient name, signature or delivery confirmation, date, time, and exception notes if anything was not straightforward. For container jobs, add container number, arrival and departure times, and any waiting or site issue. If the job has no complete POD, it is not ready for invoicing.
Next, separate standard jobs from exceptions. A clean, straightforward delivery should not sit in the same queue as a refused load with damage photos and a rate dispute. Give the office a simple rule. Standard completed jobs can move straight to invoice review. Exceptions go into a short list for traffic to resolve the same day.
Then shorten the handover. If you still use paper, do not wait for the end of the week. Set a daily cut-off for drivers to hand in PODs, and a daily check in the office to match them to completed jobs. If a driver finishes away from base, require a photo of the signed note on the day, even if the original follows later. It is not perfect, but it is better than silence.
Make references mandatory at the point of planning. A lot of POD trouble starts before the vehicle moves. If the booking reference, PO number or site contact is missing from the job, the driver cannot record it properly later. A TMS should help here by carrying the job details through to the driver and back to the office, rather than asking someone to type the same information twice. We cover that problem more directly in how to stop keying delivery notes into invoices twice.
Train for the awkward jobs, not just the easy ones. Most disputes do not come from clean deliveries. They come from refused loads, late arrivals, damages, no one on site, and “we were kept waiting for ages”. Give drivers a clear checklist for those cases. Who to call. What to photograph. What words to use in the note. Whether to get the refusal in writing. That takes less time than reconstructing the story later.
Use one owner for the gap between delivered and invoiced. In many small firms, that gap belongs to everyone and therefore to no one. Make one person responsible for checking that completed jobs have usable PODs and have moved on for billing. That can be the owner, the traffic office or accounts, but it should be explicit.
Finally, remove avoidable rekeying. The more often job details are copied from WhatsApp to paper, paper to spreadsheet, and spreadsheet to invoice, the more chances there are for delay and error. A simple TMS with ePOD does not need a consultant or a long project to be useful. It needs to let the driver complete the job properly, let the office see it immediately, and let accounts invoice from the same record.
That is the practical reason we built Logivo the way we did. We plan jobs, brief drivers, capture PODs and help close the gap between the delivery happening and the invoice going out. If your current process still depends on chasing paper around the cab and the office, that gap will keep swallowing days. If you want to tighten it up without making the day harder, get in touch with us.
Is a proof of delivery document the same as an invoice?
No. A proof of delivery document shows the job was completed and records what happened on site. The invoice is the request for payment that usually follows once the POD is checked.
What should a driver put on a POD if there is a problem at delivery?
The driver should record the issue clearly at the time: shortages, damage, refusal, waiting time, site delays or anything else that affects the job. A vague signature on its own is rarely enough.
Does a POD always need a signature?
Usually a signature is the clearest proof, but the real requirement is evidence the delivery happened. Depending on the customer and job, names, times, photos and site notes may also matter.
What is the difference between POD and ePOD?
POD is the proof itself. ePOD is that proof captured digitally, usually on a phone or device, with details such as signature, time, notes and photos available back in the office straight away.
Why do customers still ask for a POD after the job is done?
Because their own accounts team may not release payment without it, or because there is a query over quantity, timing or condition. If you cannot produce the POD quickly, your invoice can sit there.