← Back to Work
Process file · Logistics Logistics

What’s inside: output checking · connections to your systems

Detention invoices checked against free-time clause and gate events

The question this file answersHow many detention invoices do we pay because checking them costs more than the charge?

Fits: shippers and forwarders auditing hundreds to thousands of carrier invoices a month.

Typical day

What the desk looks like today

Typical, from the logistics playbook. Each month a freight-audit desk works through carrier invoices in the hundreds or thousands, with detention lines buried among them. For each, a clerk finds the free-time clause in the contract, then the gate events, then compares by hand. It hurts at month-end, when statements arrive together.

What changes

What Monday looks like after

When the month-end carrier statements arrive, the auditor opens a list of the detention lines that do not add up — with the clause and the gate timestamps already beside the invoice line — rather than a stack of PDFs and three browser tabs. Lines that agree have moved on to payment without a person, and you can see how many did.

Typical, not a measured client result. Every figure here comes from the playbook source named below.

~50–65%

less manual checking on the carrier-invoice desk — Transporeon/project44 cases; detention lines are inside that desk, not measured separately

Before: a clerk argues detention from three screens. After: freight-audit cases report 50–65% less manual checking on the carrier-invoice desk — detention lines included, contract interpretation still human.

Where this number comes from

Transporeon and project44 case studies report 50–65% less manual audit effort on freight invoices; Ardent Partners “Freight Audit” (2023) puts best-in-class at 75%+ touchless; the logistics playbook uses 50–70%. Detention invoices are one line type on that desk — the range is not measured for them on their own, and it is not our measurement.

What we install

What we put in front of the systems you already run

Your TMS and AP system stay — CargoWise, SAP, Dynamics or the ones you run. The same three-way audit build as our carrier-invoice file, aimed at one charge type:

  1. detention invoices are read from the carrier’s mail or portal and each line’s container, dates and rate pulled out
  2. the dates are set against the free-time clause for that carrier and port, and against gate-in and gate-out events from the terminal feed
  3. lines that agree within your tolerance are approved into the payment run as drafts, and every line where the clock, the clause and the events disagree goes to the auditor with all three shown.
What stays human — and what this will not do

Contract interpretation. Force majeure. Customer disputes. A terminal that changes its rules.

What can go wrong — and what we do about it

Contracts that state free time differently per port, or that were renegotiated mid-year, need to be written down as rules first — that is audit work, not automation. Terminals with no data feed leave the clock unverifiable; those lines go to a person as now. The Transporeon/project44 range is for the carrier-invoice audit desk as a whole; force majeure and disputed clauses are outside it.

What it costs to get there

The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →

Scoped in the audit — the playbook has no estimate for this exact desk.

This is about you if…
What does this mean in euros?

That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.

Get your free savings estimate 60 seconds · no sales call Or write first → Map a logistics process like this one — free, 60 seconds →

Not a named Aperanda client. Process file · Logistics.

Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.

All process files