Route planning and proof of delivery: from stop to invoice

Dispatch means forming runs from a set of open orders and putting them into a sequence. In smaller companies that sequence lives in the head of one person who knows the area. It works remarkably well — until that person is on holiday, a vehicle breaks down or an urgent order arrives at short notice. The purpose of structured dispatch is therefore not to replace the experienced dispatcher but to record their knowledge so that a stand-in can build the same run at comparable quality.

Ordering by shortest driving distance alone falls short. What decides the day are the side conditions: fixed delivery windows, goods-in opening hours, access restrictions, the unloading equipment required, the loading sequence in the vehicle and collections such as empties or pallet exchanges. If the loading sequence is ignored, goods have to be restacked at every stop. Those minutes appear in no distance calculation, yet they add up noticeably over a day.

A second point is frequently underrated: the run needs an unambiguous identifier that everything else hangs on later — status updates, records, invoicing, reporting. Without that bracket the parts sit side by side and have to be brought together by hand in the office. The run number is the key by which planning and evidence find each other later.

A proof of delivery is the evidence that particular goods were handed over at a particular time at a particular place. It is needed when an invoice is disputed, when a client audits the delivery, when damage is reported or when accounting looks for the document behind a revenue entry. What matters is therefore not the form — paper or screen — but completeness and the link to the order.

Many digital records fail not on the technology but on missing details. A photograph of goods left on site proves that something was left, but not what was handed over or to whom. A signature without a printed name leaves open who signed. A timestamp without an order reference is worthless when a case is clarified. The following list has proven itself as the minimum content.

A signature on a screen is not legally equivalent to a qualified electronic signature. For day-to-day evidence of handover it is usually sufficient in practice, because the record is assessed together with the timestamp, the order reference and the log. Which requirements apply in a specific contractual relationship should be clarified with your own legal adviser and with your main clients before the switch. The technical route there is the orderly capture and filing of records.

Many companies apply the rule that nothing is invoiced until the proof of delivery is on file. Commercially that is sound, because an invoice without evidence leads to credit notes and rework as soon as questions arise. The consequence, however, is that the return of the paperwork sets the pace of invoicing. As long as the record lies on the passenger seat, accounting can do nothing — no matter how well organised it is.

If the record instead reaches the leading system when the stop is completed, the bottleneck moves. The invoice can be issued the next day, partial deliveries are already marked as such, and cases needing clarification are visible before the invoice run rather than after it. The record is therefore not the end of the delivery but the beginning of invoicing. That is the real lever: not driving faster, but being able to invoice earlier.

The path from record to invoice runs through a connection between the systems. It need not be large: in many cases it is enough to hand completed deliveries over to the invoicing system, plus a return message stating which items were invoiced. What matters is that each delivery arrives exactly once and that a repeated transmission does not create a second item.

The most common cause of failed rollouts is the assumption of continuous network coverage. Coverage gaps persist along trunk roads, in halls, underground car parks and older industrial estates (Bundesnetzagentur). A capture flow that needs a connection at the decisive moment is rightly rejected by the people using it. The record has to be created locally on the device and stay valid even if transmission only becomes possible two hours later.

Three technical requirements follow from that: a local queue on the device, an unambiguous record identifier assigned at the moment of capture, and a transmission that recognises and discards a repeated delivery of the same record. Without the third requirement, duplicate records appear as soon as a device resends after an interruption — and duplicate records create duplicate postings in the invoicing system.

When choosing devices, stay sober: ruggedness, battery life across a full shift, controls large enough to operate with gloves and a simple replacement procedure in case of failure weigh more heavily than processing power. The rest is a question of the workflows behind the scenes, not of the hardware.

Not every piece of evidence can be replaced in the short term. Dangerous goods documentation, certain consignment notes in cross-border traffic and individual official documents are subject to their own formal rules, and some clients insist contractually on a signed paper copy. That is no reason to postpone the switch: the digital record covers the normal case, paper remains for the named exceptions and is marked as an exception.

The view on company size should be just as honest. With two vehicles and short runs that return to the yard daily, the return journey of the paperwork is not a meaningful bottleneck — there, clean matching in the office pays off more than equipping vehicles with devices. The benefit grows with the number of stops, the length of the runs and the number of clients with their own evidence requirements. Anyone wanting to prove that for their own operation measures the days between delivery and invoice first and sets the interest effect and the clarification effort against it.