Feature Area: Laytime Calculations / SOF Processing

Impact: All users managing vessel and barge demurrage claims in the Claims Manager

Video Walkthrough: video  


Contact support@voyagerportal.com to configure your bookmarked events — if you don't reach out, current behavior is unchanged and all events are included. 

Overview

Companies can now configure which SOF events are relevant to laytime calculation and statement display (bookmarked SOF events). This is a visibility layer only — every event is still parsed and stored; configuring your relevant events simply controls what's surfaced as important during calculation and negotiation. Previously, teams often deleted valid events from the parser to shorten the statement to make it easier for third parties to read — now you can keep every event and simply control what's surfaced, with nothing lost for analytics. And instead of manually reviewing every parsed SOF to catch the events your calculation and analytics depend on, missing ones are flagged automatically. 

How It Works

  • Configurable at the company level, separate options for vessel claims and barge claims

  • Bookmarking will only apply to port calls created after the configuration is set

  • All events in the parser can be configured to be bookmarks. Events can additionally be marked to alert if missing

  • Demurrage statements (timeline format) filter to show only relevant events; event-based statements are unaffected, as they already show only calculation events 

  • In the laytime calculator, bookmarked events display normally; non-relevant events appear dimmed 

  • Events used in your contract are always included in the calculation, regardless of configuration

  • The SOF validator flags a banner alert when a configured event is missing from the parsed SOF, so the user can add it or ignore the alert. These alerts also appear in the SOF parser screen

Future Additions

  • Dedicated filter to hide non-relevant events entirely in the laytime calculator 

  • Apply new configurations to existing port calls. 

  • Conditional logic - e.g. alert if a load commence AND a discharge commence is missing