An uploaded POD is not a checked POD

Most carrier portals release the credit note the moment a proof of delivery lands. That is one step too early — and it is the step where illegible CMRs and missing stamps get paid for.

The gap nobody names

Ask a dispatcher what a POD is worth and you get a precise answer: it is the paper that turns a finished drive into money. Ask the same person how their system treats it, and the answer is usually vaguer — the driver or the carrier uploads something, a green tick appears, and the credit note opens.

Between "something was uploaded" and "the delivery is proven" sits a step that most software skips: somebody has to read the document. A photograph of a dashboard with a corner of a CMR in it is an upload. So is page two of a three-page delivery note. So is last week's CMR sent against this week's transport. Each of them turns the tick green.

Why it costs real money

The cost shows up later, and never in the transport where it started. A client rejects an invoice because the POD is illegible. A claim arrives four months on and the stamp that would have settled it is not on the scan. An audit asks for delivery evidence and half the file is phone photos of the wrong page.

By then the carrier has been paid, the transport is archived, and the person who could have caught it — the dispatcher, in the ten seconds it takes to open a PDF — was never asked to look.

What checking actually requires

Not much, if the software is built for it. Four things:

  • A state that means "waiting for a human". Uploaded is not approved. The document sits in a queue that somebody owns.
  • A decision with two outcomes. Accept, and the money moves. Return, and it goes back — with a reason, in the carrier's language.
  • Reasons that are a list, not a sentence. Illegible, stamp missing, page missing, wrong document. A code can be translated and counted; a typed remark can only be read.
  • A new version, not a patch. A POD returned as illegible is not fixed by gluing another page onto it. The next upload starts a fresh document.

The order of the three steps

A delivery is documented by three things, and they are not independent: the times at each stop, the DPL where the goods require one, and the POD. The POD is the last of them, and it is the one that closes the transport.

Which means it can be refused until the other two are in. A carrier who uploads a POD before entering the stop times has skipped the part that proves waiting at the ramp — and that is the part demurrage is argued from. Refusing the upload costs the carrier ten seconds and saves the argument.

What the carrier should see

Nothing about this should feel like a rejection machine. The carrier did their job; the document simply has to be read. So the moment the upload succeeds they get a receipt, not silence:

Thank you for the POD. The POD is on review. As soon as we confirm it is correct, your credit note will be ready to download.

And when a POD does come back, it comes back saying what to do: the reason, the dispatcher's comment, and a clear instruction that the new POD replaces the returned one. The driver sees the same thing in the app, without a single figure — they are the only person who can re-shoot the page, so they are the person who needs to know.

What we changed in Cargon

The POD now has states of its own inside a completed transport: on review, accepted, or returned with a coded reason and a comment. The credit note waits for the decision, in the portal and on the server alike — there is no URL that hands it over early.

Uploading is refused until the times and, where required, the DPL are in; when it succeeds, the transport moves itself to completed. A returned POD starts a new version rather than being topped up. Every step is written to an audit trail: who decided what, from which surface, for what reason.

And a POD that has sat unread for three working days appears on the dispatcher's dashboard, because the failure mode of any review step is not a wrong decision — it is no decision at all.

The rule underneath

Software that says "done" before a person has looked is not saving anyone time; it is moving the work to the month where it is expensive. A tick that means "a file arrived" should not look like a tick that means "this delivery is proven". They are different facts, and only one of them is worth paying against.

← All articles