What proof of delivery actually costs you when it arrives on paper

A truck tips its last pallet at 09:40 on Monday. The consignee signs, the driver folds the sheet into the door pocket, and everything about that job is finished except the money. The invoice leaves your office on Friday — if Friday is a good day. The delivery took four hours. The paperwork took four days.

Nothing went wrong. That is the point. This is the fully successful case, and it still sits in a queue, because the document that says delivered is a physical object travelling at the speed of a driver’s next visit to the depot.

Follow one sheet of paper

Write down what happens to a signed delivery note in your operation. For most carriers running on paper it looks like this:

1. Signed at the tailgate, Monday 09:40.
2. Into the door pocket, the sun visor, or a folder that lives in the cab.
3. Handed in when the driver is next at the depot — on a week-long loop, that means Friday; for a subcontractor, whenever they get round to it.
4. Or: photographed at the kitchen table on Sunday evening and sent to a dispatcher’s phone as eleven images with no booking numbers on them.
5. Somebody opens that inbox, reads the handwriting, and matches each sheet to a booking.
6. The invoicing run happens on whatever is matched by then.

Six steps, and at least three are batches — work that happens on a cycle rather than on arrival. Batches create the lag and also hide it: no single step feels slow.

Count the queues, not the days

Resist the urge to look up an industry average for days-to-invoice. It tells you nothing about your operation, and the number you need you can work out this afternoon from three intervals:

• Hand-back interval — how often paper physically reaches the office.
• Matching interval — how often someone processes what has arrived.
• Invoicing interval — how often you actually raise invoices.

A delivery is roughly equally likely to fall at any point in a cycle, so on average it waits about half of each interval it sits in, and at worst the whole of each. Weekly hand-back, twice-weekly matching and weekly invoicing gives an average of several days and a worst case of well over a week — and the worst case is not exotic, it is simply Monday’s delivery on a driver who does not come in until Friday.

Two things follow. The driver is usually not the bottleneck; the matching step is, because it scales with volume and is done by someone who has five other jobs. And shortening one interval while leaving the others alone buys almost nothing — if paper arrives daily but you invoice on Fridays, you have moved the queue, not drained it.

The honest measurement takes twenty minutes: put last month’s delivery dates next to their invoice dates and look at the distribution rather than the average. The tail is where the cash is.

The photograph of a signed paper sheet is the villain

Almost every carrier reaches the same intermediate step: the driver photographs the signed note and sends it in. It feels like digitisation. It is a fax with extra steps.

• It carries no structured data. An image has no booking number, no customer, no line items — every one has to be read by a human and typed. You have sped up the document’s transport, not the work.
• Its timestamp is wrong. The file is stamped when the photograph was taken, not when the goods changed hands. As evidence of when delivery happened, a Sunday photo of a Monday signature says nothing.
• It arrives out of band. Messaging apps and personal email sit outside your system of record, so the office cannot see what has not arrived. That is the expensive part: a dispatcher cannot distinguish not delivered yet from delivered, paper still in a cab, and the customer asking for a POD on Thursday gets a phone call rather than an answer.

What the receipt is legally for

Worth knowing, because it changes where the deadline actually sits.

Under the CMR Convention, which governs international carriage of goods by road, the consignee is entitled on arrival to require the carrier to deliver the goods against a receipt (Article 13.1). Swedish domestic carriage mirrors it: 20 § of lag (1974:610) om inrikes vägtransport gives the recipient the same right.

The receipt matters for more than the invoice. Under Article 30.1, if the consignee takes delivery without duly checking the condition of the goods with the carrier and without sending reservations — at delivery for apparent damage, and within seven days, Sundays and public holidays excepted, for damage that is not apparent — taking delivery is prima facie evidence that the goods were received in the condition described in the consignment note.

Read that as an operational fact rather than as legal advice: the evidentiary moment is at the tailgate, and the seven-day clock runs from delivery, not from the day the sheet reaches your office. If a damage claim lands on Thursday and your record of Monday is a photograph taken on Sunday, the conversation becomes one about your document handling instead of about the goods.

The statutory deadline is probably not what is holding you

Worth knowing so you do not over-rotate on it. For intra-EU supplies of goods the invoice must be issued no later than the 15th of the month following delivery, and the same date applies to intra-EU services under the main rule. For ordinary domestic sales, Swedish VAT law names no fixed date; the standard is customary business practice.

So for most domestic work, nobody is fining you for invoicing slowly. The cost is commercial: payment terms start when the invoice is issued, not when the goods arrive, so every day of lag is a day of your working capital financing your customer. It compounds at month end, where a delivery on the 30th that misses your cut-off rolls into the next cycle entirely.

What a digital POD has to do to actually close the gap

Being an app is not sufficient. The test is whether the capture releases the job for invoicing without anyone retyping anything:

1. Captured against the booking, not next to it. Signature, photos and printed name attach to the stop, not to an email thread.
2. A structured completion event — status, time, who, where — visible in the office within seconds, so late and missing stop looking the same.
3. Failure is a first-class outcome. A refused delivery with a reason and a photo is something you can re-plan around. A missing sheet is not.
4. Invoicing reads it directly. If the delivery event is not what makes the booking billable, you have digitised the paper and kept the queue.

And the trade-offs, honestly. Some customers will still want a stamped paper copy, so budget for a period of running both. A signature on glass proves that someone signed, not who — the photo, the printed name and the location carry the weight, and that was equally true of the scrawl on paper. Adoption is the real project, not the software: a driver app slower than a pen at the tailgate will lose to the pen, and it should. And invoicing on the delivery day exposes pricing errors on the delivery day — a new problem in month one, a benefit from month two.

Start by measuring your own three intervals. The queue that needs draining first is probably not the one you would have guessed.

navichain captures proof of delivery in the driver app, on the phone the driver already carries: signatures, photos and failed-delivery reasons taken at the stop, with per-stop cargo manifests so the driver confirms the right goods, plus a digital CMR a third party can verify from a QR code without calling you. It is the same record the office and the invoicing run read — no photograph to match, nothing to retype. Two driver seats per vehicle are included, every feature is on every plan, and pricing starts at 995 kr a month — see the platform page and the pricing page. Related reading: eCMR and eFTI on 9 July 2027, getting drivers to use the app, and invoicing on the delivery day.