The Problem: A 72-Hour Blind Spot
Every container that enters the Port of Mombasa begins accruing free time the moment it is discharged. That free time — typically 4 to 7 days depending on cargo type and shipping line terms — is the window within which a freight forwarder must clear the goods or begin paying demurrage.
The problem is not that operations teams are unaware of this. They are. The problem is that the data confirming when free time began, and how much remains, lives in three different systems — the KPA Terminal Operating System, the shipping line's online portal, and the freight forwarder's internal manifest — and these systems are reconciled manually, once a day at best, two days late at worst.
By the time a finance manager generates the weekly liability report, the demurrage clock has already run. The invoice arrives 10 days later. The money is gone.
Anatomy of the Leak
Where documentation fails
The TOS gate-out record is generated the moment a truck exits the terminal. This record contains the container number, the gate-out timestamp, and the vessel reference. It is the most important document in the demurrage calculation. It is also the document that reaches the freight forwarder's operations desk the latest.
The forwarder's operations team typically learns of gate-out through a WhatsApp message from the truck driver, or a phone call from the client asking about delivery status. Neither channel produces a timestamped record that can be cross-referenced against the shipping line's free-time calculation.
"We knew the container had left the port. We just didn't know exactly when — and that 18-hour difference was the difference between a valid contest and an invoice we had to pay."
— Operations Manager, Mombasa-based clearing and forwarding firm
The 72-Hour Intervention Window
Shipping lines operating at Mombasa — MSC, Maersk, CMA CGM — typically allow demurrage charge disputes within 5–7 days of invoice generation. The invoice is generated 5–10 days after gate-out. This creates a real contest window of approximately 72 hours from the point a finance team first sees the invoice.
The contest requires: the TOS gate-out timestamp, the delivery order date, and evidence of any port delays attributable to terminal operations rather than the consignee. All three documents exist. None of them are in the same system. Assembling them manually takes 4–6 hours — longer than the window allows for a high-volume clearing desk.
The Diagnostic Framework: Mapping the Leak in Your Operation
To quantify your specific demurrage exposure, the diagnostic runs three checks against your current document flow: First, the TOS reconciliation gap — how many hours between gate-out event and forwarder system update. Second, the free-time monitoring protocol — does your operations system alert before free time expires or after. Third, the contest document assembly time — how long to produce the three required documents from a standing start.
Operations with a TOS reconciliation gap above 24 hours, no automated free-time alert, and contest assembly time above 90 minutes are in the highest-risk bracket. The intervention required is document synchronisation, not process redesign.
The synchronisation architecture
The architecture uses three data feeds: a KPA EDI integration for gate movement events, shipping line API polling for free-time balance, and a forwarder manifest webhook for delivery order timestamps. These feeds write to a single reconciliation table that generates alerts 48 hours before free time expiry and assembles contest documents in under 3 minutes.
What This Intervention Is Not
This is not a case for replacing your freight management system. It is not a case for AI in the broad sense. It is a case for a document synchronisation layer — a narrow, specific piece of automation that solves one problem completely and does not touch anything else.
The intervention scope is 3 weeks. The annual value — for a firm handling 300 TEUs/month at an average demurrage exposure of $400/container — is $144,000 in recovered charges and avoided fees. The implementation cost is a fraction of that.
Request a Peer-Level Methodology Review
If the demurrage pattern in this analysis resembles what you are experiencing, the next step is a 30-minute conversation between two people who understand the operational context — not a sales pitch. The Business Intelligence Audit takes 5 minutes to complete and maps your specific waste zones before we speak.
Begin Intelligence Audit →