The depot rejection became an owned follow-up before invoice review.
Instead of reconstructing the return from email and depot notes, the operator sees the missed instruction, the required evidence and the review boundary in one case.
Sample case
One container, one chronology, one evidence pack.
A readable example of how DehireDesk controls a return exception without claiming to decide legal validity or payment liability.
Depot rejected return at 14:40.
The return attempt failed after the empty-return instruction changed. DehireDesk links the rejection to the container and creates a follow-up for the missing revised instruction.
- Original return instruction
Carrier instruction received with Depot A as the empty-return location.
- Depot rejection
Depot B rejected the return because the instruction had changed.
- Revised instruction
Changed depot instruction recorded and attached to the case.
- Successful dehire
Return/dehire event recorded with receipt evidence.
Context split across email, depot notes and invoice review.
The revised return instruction is not attached to the container record, and the invoice reviewer has to reconstruct the failed return chronology manually.
One case links the failed return to the missing instruction.
The system surfaces the evidence gap, creates the follow-up action and preserves a report-ready chronology for detention review.
Follow-up action
- Attach revised depot instruction.
- Confirm dehire receipt against recorded return.
- Hold detention invoice review until chronology is complete.
Billed period conflict
The detention invoice extends beyond the recorded return/dehire chronology. DehireDesk flags the inconsistency for human review.
No automatic liability decision
DehireDesk preserves facts and prompts review. Your team decides escalation, payment, credit request or dispute response.
Transparent calculation
- Availability date
- 18 Jul 2026
- Free days
- 5 calendar days
- Weekend setting
- Included
- Last free day
- 23 Jul 2026
Indexed files
- ANL-return-instruction-20Jul.pdf
- DepotB-rejection-note-21Jul.pdf
- ANL-revised-depot-22Jul.eml
- Dehire-receipt-TBSU1000007.pdf
Review boundary
DehireDesk flags the billed-period conflict and missing evidence. A human reviewer decides whether to escalate, request credit, pay or dispute.
Evidence pack output
Exportable record for detention review.
The evidence pack is the report-ready output: container details, deadline basis, event chronology, evidence index and invoice exceptions. It is designed to be inspected before your team decides whether to pay, dispute or request credit.
Evidence Report · TBSU1000007
Generated from the case chronology and attached evidence. Pending authorised review before sharing.
- Container details
- Line, vessel/reference, customer, owner
- Deadline calculation
- Free-time rule, excluded dates, last free day
- Event chronology
- Instruction, rejection, revision, dehire
- Evidence index
- Instruction PDF, depot note, dehire receipt
- Invoice exceptions
- Billed period extends beyond recorded return
- Report checksum
- SHA-256 recorded at approval