Voyager is evolving fast, and we’ve been pushing the platform in three directions this year. Managing claims is now more intuitive and faster than ever; we’ve improved how the platform unlocks integrations and third-party reach; and transformed how data analytics is run inside the system.
The platform’s breadth has also changed, and Voyager is now cargo and claims agnostic, so the same desk runs demurrage and barge claims, detention and other non-demurrage types, across wet, dry and project cargo voyages.
That gives the desk a single platform to work across every step and claim type, from transcribing SoF events to negotiating the claim and answering for the exposure at month end.
Claims Manager Redesign
The redesigned Claims Manager screen changes the approach on how you manage and visualise claims on the platform through dynamic filters and column management, whether you handle demurrage or non-demurrage claims.
View all your claims in a single, scrollable list. Each claim is a distinct row, displaying key information at a glance. Combine filters like Claim Type, Status, Assignee, and Counterparty to create the perfect view for your current task, and perform key tasks directly from the table.
One screen now holds every claim detail operators need: No more time lost searching for documents or claim details on long email threads, and a simple way to analyze and manage your claims workload at scale.
Our latest release also includes a UI change on the claims screen: Now port-call cards will surface the cargo behind them, so you can easily find the right one without opening the port call. On claims with many port calls, some carrying a dozen cargos or more, that lookup used to mean opening, editing, and scrolling back to find where you’d been, for every port call you needed to check.
That matters most in rebill setup, where the whole task is matching the right charterer to the right port call across a long list. Now that match happens from the claim screen itself, so your desk moves straight from spotting the port call to setting up the rebill, instead of losing its place in the claim on every check.
Cargo details in port call cards on the Claims Manager UI.
Self-Service Dashboards & Reports
Create and customize your own visualisations over your claims data, so what you see matches the way your company actually reports claims across the board.
In practice that means a view of demurrage per port, per country, per cargo, per counterparty, or whichever cut your management asks for, built once and shared with the people who need it.
Self-service dashboards are a paid feature, so talk to your account manager if you’d like personalised reports unlocked for your team.
Editing a chart on a “Net Settled Exposure” report.
Automatically Tag Statement of Facts
Handling a complex Statement of Facts is now a quick review rather than a build. Gangs, holds, cranes, cargoes and barges are tagged automatically as the SoF is parsed, so your analysts adjust what is already there instead of starting from nothing.
Every tag stays editable right up to the calculation, which keeps the review in your hands and the exceptions where your team wants them.
This expands the automation behind the SoF parser, and ensures your team can focus on reviewing and tag adjustments instead of creating and assigning them from scratch.
Enhanced Claims Submission Portal
Now third party users can access a one-time password protected page to submit claims directly to Voyager, which can be re-used by the counterparty over time. The submission form has also been updated to account for different counterparty requirements and non-demurrage claims as well.
On submission, the counterparty will receive a confirmation email carrying its own protected link, which they use to add supporting documents and comments, enabling for quick interactions during the negotiation process through email and the in-app Voyager chat.
How to set up the third party claim submission portal.
In-app Chat Engagement
Interact with counterparties directly through the claim’s in-app chat. External comments are shared with the counterparty who submitted the claim, where they can reply and attach documents. Everything stays on the claim with a timestamp and a sender against it, and you can control what the counterparty sees through internal and external notes.
Counterparties need no account and no portal access, since the exchange runs through the same one-time-password link they submitted with. This is phase one of our negotiation work, scoped to externally submitted claims for now.
Example interaction with internal and external comments.
New Public API for Demurrage Claims
The Claims Public API lets you work with demurrage claims from your own systems. List, read, create, update and delete claims, manage the port calls under them including events, cargoes and time ranges, write invoice information and statuses back, and filter by date range, voyage ID and other attributes.
Your custom fields are in it too, readable and writable and usable as query parameters, so a field you defined in the Claims Manager is a field your other systems can filter on as well.
Governance & Data Health
Processing a claim accurately depends on the data sitting behind it. We’ve focused a lot of this year on data quality, and that means establishing a consistent layer of governance around how claims are managed in the system.
Now Voyager carries configurable parameters that let each company decide the level of information a claim must hold and when it is allowed to move:
Custom and mandatory fields. Create your own custom fields and establish what information is required before a claim can be settled, at claim, port call or cargo level. Settlement is blocked until those fields are filled, and new companies start with a default set already required.
A blocked settlement with nine missing mandatory fields.
Claim statuses. We’ve updated claim statuses to reflect how a claim actually ends. No Claim and Withdrawn close a file without payment against a structured reason: contract terms, a trader or charterer concession, an operational compromise. A claim’s status can also lock based on pre-defined field values, avoiding accidental status changes after a claim reaches a certain state.
Bookmark events. Choose which SoF events are surfaced on statements and in the laytime calculator. Every event is still parsed and stored, and missing ones can be flagged. It applies to port calls created after you configure it, so your history is left alone. See the walkthrough.
How to bookmark specific events in your SoFs and set up alerts.
Multi Vessel Claims. For charterers running transshipment or double-bottom voyages, a claim no longer has to be split in two. Claims can now carry any number of vessels, and you can assign an owning vessel to each port call inside the claim.
Operation rates. Load and discharge rates can now be set at a cargo-level within a port call, matching how your charter party reads.
Broker-level mapping. Brokers sit at claim and cargo level, sortable in the list and audited in the claim timeline.
Commissionable claims. Non-demurrage claims split commissionable from non-commissionable amounts, so gross and net agree downstream.
These changes are what make a claim accurate and auditable. Reach out to our team if you’d like guidance on setting up mandatory fields, status locking, custom fields or bookmarked events.
Coming Next: Contract Management
Our next development cycle will involve redesigning how we manage and interpret contracts in Voyager, applying LLM reasoning to modulate contract clauses inside the system automatically.
This changes how teams manage claim exposure, turning their attention to contracts optimization and settlement instead of manually transcribing statement of facts events from a pdf and calculating laytime on a spreadsheet.
Keep an eye out for the next releases and talk with our team if you’d like to get a sneak peek into our product roadmap.