Demurrage claims are built on Statement of Facts data.

Proteus extracts every event from your SoFs automatically and feeds clean numbers into your laytime calculation. Source-traced. Audit-ready. In seconds, not hours.

See how it works ↓

Every day uncompensated is $27,000 walking out the door.

Demurrage rates on chemical tankers and dry bulkers run $21,500 to $50,000 a day, pro rata. Across a ten-vessel fleet with 24 voyages each, that's 240 potential claims a year — every one of them a negotiation about hours and minutes recorded in a Statement of Facts.

Most demurrage under-claims aren't because the claim is weak. They're because nobody had time to reconcile five SoFs across three ports, apply the charter party's deduction rules, and submit before the 60-day bar ran out.

The math is simple: if you're missing one $25,000 claim per month because of data-entry bottlenecks, that's $300,000 a year. Proteus costs a small fraction of that.

From SoF PDF to submitted claim — in one workflow.

Proteus is two connected tools. Most customers start with the first, then adopt the second once they see how clean the data is.

1

Automated Statement of Facts extraction

Upload any SoF — typed, scanned, handwritten, bilingual. Proteus extracts every event with a source citation back to the exact line in the source document. Export to Excel or CSV for your existing laytime tool. Learn more about SoF extraction →

2

Auto-demurrage calculation

Once your SoF events are in Proteus, the calculator applies the charter party deduction rules — SHINC/SHEX, reversible laytime, weather at half-rate, proration for part cargoes — and produces a source-linked laytime statement ready to submit. Every number traces back to the SoF line that generated it.

You can use just step one and keep your existing calculation workflow. Or you can use both and run the whole voyage inside Proteus.

Built for the SoFs you actually get.

Demurrage analysts don't lose time on clean typed SoFs. They lose time on the weird ones.

  • Typed tables

    From well-run modern ports with structured SoF tables.

  • Scanned & stamped documents

    From Paradip, Kandla, and other ports where the SoF is still pen-and-ink with overlapping signatures and mixed date formats.

  • Bilingual Chinese/English

    From Zhangjiagang, CJK, Lianyungang, and other terminals that issue tables in both languages.

  • HTML-rendered agent SoFs

    From Morocco and other digitized terminals where the SoF is delivered as a structured web export.

  • Handwritten & mixed date formats

    DD/MM/YYYY, MM/DD/YYYY, 09-July-2024, 0800 LT, 10H10. Proteus normalizes them all.

  • Commingled pages

    SoF tables buried inside scans with cover pages, Master's remarks, cargo manifests, and correspondence. Proteus isolates the SoF pages automatically.

  • Multi-tender NORs

    Notices tendered two, three, or four times after rejection or re-inspection. Every tender captured in sequence.

  • Letters of protest & disputed remarks

    Master's and receiver's remarks that contradict each other on the same document, captured side by side for review.

If your analyst can read it, Proteus can extract it.

Extracted event
timestamp: 2024-07-15T08:00:00Z
event: End of sea passage
SoF page 2, line 7

When the counterparty disputes your numbers, show your working.

About 20% of laytime calculations end in dispute. When they do, you don't argue about memory — you produce the source. Every event Proteus extracts links to the exact line in the source SoF, and the auto-demurrage calculation inherits that provenance all the way to the final statement.

No black-box extraction. No “trust the AI.” Just faster typing, with the source one click away.

Try Proteus on one SoF.

No login. No commitment. One real document from one real voyage. Upload the SoF, see what Proteus extracts, decide if the accuracy meets your standard. If it does, run a full laytime calculation. If it doesn't, you've lost five minutes.

Frequently asked questions

Does Proteus file the demurrage claim for me?
No. Proteus produces the source-traced laytime statement. You still submit the claim through your normal channel, with Proteus’s export as supporting documentation.
Which charter party forms does Proteus recognize?
ASBATANKVOY, BPVOY5, ExxonMobil VOY2012, VEGOILVOY, plus bespoke rider clauses layered on top (OCP COA, ATLAS COA, Nova Carriers, Glencore 2019, and custom amendments).
How does Proteus handle reversible vs. non-reversible laytime?
Both, with automatic netting across ports for reversible terms when you use the auto-demurrage calculator on top of extracted events.
What about multi-charterer proration?
Supported inside the auto-demurrage calculator. Enter each charterer's cargo quantity and Proteus prorates waiting time, berth time, and deductions.
Is the 60-day time bar a hard stop?
Most COAs: yes. Late filing waives the claim entirely. Proteus is built for the teams who can't miss it because they're handling multiple vessel close-outs in the same week.
Is my data confidential?
Your documents stay in your tenant. Proteus doesn’t train on your data. Charter parties and Statements of Facts are never shared across customers.
What does it cost?
Try Proteus free on one SoF first. If the accuracy works on your documents, pricing is a single conversation based on your SoF volume.

Stop letting claims slip past the 60-day bar.

Built by Greywing. Used by operations teams running chemical tanker, dry bulk, and product tanker voyages.