IMOS X - Dry Claims Workflow for Demurrage Claims

Introduction

IMOS X Claims CoCaptain for the dry bulk market provides an end-to-end demurrage claims workflow supported by AI to ingest, classify, and extract key data points. This workflow reduces the time to process a claim for analysts, provides greater visibility into demurrage exposure earlier in the process, and provides greater confidence in the agreed amount for both parties in the claim negotiation.

Workflow

Do one of the following:
- Navigate to the Claims workspace and open an existing demurrage claim.
- Or select Create Claim and choose either Deduction or Time Counting. The example shown in this article uses the Time Counting method.
Following the standard claims workflow, input your claims details into the fields provided, including: Itinerary, Voyage, Cargo, and AP/AR claim type.

Note: In the Clauses area, the Reversible checkbox is deselected. Many dry claims are non-reversible due to the nature of the claim, so these claims are constructed or generated on a per-port basis.

Select the Despatch Rate to see the source documents it was extracted from and ensure its accuracy.

Extraction Details for the Despatch Rate

If needed, you can manually override the rate provided, as shown in the following image.

In the Details section, review the following fields:
- Recorded % - The percentage of time counted toward laytime
- Used Time - The amount of used laytime
- Remarks - A text field you can use to add additional comments

Review the Invoices and Related Claims sections as you would in the standard claims workflow.

Frequently Asked Questions

FAQs

Will the AI extract different information from dry bulk documents?

Yes. In addition to standard claims data, the AI now extracts:

Despatch rates from charter parties

Why am I seeing multiple suggested claims for one voyage?

Dry bulk cargoes are typically non-reversible, meaning laytime is calculated separately for each port call rather than combining all ports into one calculation. The system automatically generates a suggested claim for each port as it's completed.

Can I edit the despatch rate manually?

Yes. You can manually adjust the despatch rate when editing your claim, and the system will recalculate the despatch amount accordingly. The despatch rate is saved when you save the claim.

What additional information do I see when viewing a time-counting claim?

Time counting claims show additional columns in the activity grid:

% - The percentage of time counted toward laytime (e.g., 0% for holidays, 100% for working time)
Duration - The actual elapsed time of the activity
Deduction - The prorated time (Duration × Percentage) that counts toward used laytime

These percentages automatically update as you adjust activities, and the system recalculates used time in real-time.

What's the difference between time counting and deduction calculation methods?

These are two different approaches to calculating laytime:

Time Counting (common in dry bulk): Only counts valid working time from the start. Interruptions like holidays and weekends are excluded immediately and don't count toward used laytime.
Deduction (common in tankers): Counts all time first, then deducts non-working periods afterward.

How does the system know which calculation method to use?

The system determines the calculation type based on:

First priority: If your voyage has a voyage template, it reads the laytimeCalcMethod field
Second priority: If no template exists, it uses your tenant's preferredCalcType setting
Default: If neither exists, it defaults to the deduction method. Your administrator can configure the preferred calculation type in the Claims module settings.

Will IMOS X automatically create suggested claims for my dry bulk voyages?

Yes. The system checks your voyage's cargo settings to determine if claims should be generated:

For non-reversible dry cargo (typical): Suggested claims are generated per port as each port call is completed
For reversible cargo: A single suggested claim is generated for the entire voyage. The system determines this automatically based on the laytimeReversible flag on your cargo.