18 Aug Port Dues Collection Is a Records Problem, Not a Rates Problem
A port runs on records. Every vessel call, every shift worked, every crane hour, every connection made at a berth leaves a trace somewhere in the day’s activity — usually in whichever system happened to be closest to the work. Port dues collection depends entirely on those traces, which is why it is an operations problem long before it is a finance one.
Those records exist to keep the operation moving, and they do that job well enough. The difficulty starts when the same records are asked to do a second job nobody designed them for: telling the authority what it is owed. Ports bill for services delivered every day — labor, berthing, bunkering, power, port calls, storage. Many of those billable events are recorded by the parties being billed, or by operators working alongside them, and reported back afterward. The authority invoices from that report. If the report is incomplete, the invoice is incomplete, and nobody downstream ever finds out.
Self-Reported Is Not the Same as Reconciled
This is not a story about bad actors. It is a story about record-keeping under operational pressure.
A terminal operator working a heavy vessel call is not maintaining a billing ledger. They are moving cargo. Labor hours get logged at the end of a shift from memory. A crane runs longer than planned and the extension is captured on somebody’s notepad. Power draw at a berth is estimated because the meter reading happened at the wrong moment. Each of those is a small, defensible gap, and the authority has no independent way to see any of them. Multiply small gaps across a year of vessel calls and the number stops being small.
Where the Money Actually Goes Missing
Port dues collection tends to fail in the same places, at ports of very different sizes.
Services delivered outside the standard scope — an extra shift, an unplanned move, an additional connection — go missing most often, because they sit outside the routine billing template. Time-based charges are next, because start and stop times are the hardest things to reconstruct after the fact. Then there are the charges that get raised, disputed, and quietly written off, not because they were wrong but because nobody could produce the record to defend them. A charge you cannot evidence is functionally a charge you did not make.
What an Auditable Record Changes
The fix is not a higher tariff or a tougher collections posture. It is an independent record of billable events, captured from operations as they happen and reconciled against what gets invoiced.
When the authority holds its own timestamped record of what moved, when, and for how long, three things change. Invoices reflect what occurred rather than what was remembered. Disputes get shorter, because the conversation moves from recollection to record. And the finance team can close a period without a reconciliation exercise that depends on other people’s paperwork arriving on time. The tariff does not change. The collection rate does.
It is worth being clear about what this is not. It is not a monitoring exercise aimed at tenants, and it does not require operators to file anything additional. The record is assembled from activity the terminal is already producing. Framed that way, the conversation with operators tends to go better than authorities expect, because an independent record cuts both ways — it also settles the disputes where the operator was right.
The Operations Data Is Already There
Here is the part worth emphasizing: the data required to build that record is the same data the operation already generates.
Gate transactions, vessel call timings, equipment movements, labor assignments, and berth occupancy all exist somewhere in the day’s activity. They are usually scattered across systems that were never asked to talk to one another, and none of them were designed with an invoice in mind. Connecting them is not a new data collection project. It is a matter of routing what already exists into a record the authority controls — which is also, not coincidentally, the same connection that makes the operation more predictable to run.
Three Questions Finance Should Ask Operations
The exposure surfaces quickly under direct questioning.
First: for each billable service, who records the event, and does the authority have any independent confirmation of it? Second: how many charges were raised and then written off last year, and how many of those were dropped for lack of evidence rather than lack of merit? Third: how long does it take to close a billing period, and how much of that time is spent waiting on records from somebody else?
If those answers are uncomfortable, the gap is not a policy problem. It is a records problem, and records problems are solvable.
Start With One Revenue Line
There is no need to reconcile everything at once, and authorities that try usually stall. Pick the single charge type that generates the most disputes or the most write-offs, and build an independent record for that one line. Run it for a quarter alongside the existing process and compare what the two produce.
That comparison is the business case, and it tends to make itself. Once one revenue line is defensible, extending the same discipline to the next one is a much easier conversation — with operations, with the terminal operators, and with the board. That is how port dues collection actually improves: one defensible line at a time.
About the Author
Sergei Smirnov works on port community solutions for Kalé Info Solutions North America, supporting port authorities and terminal operators across the United States and Canada.