Seafarerops
In production at a reefer fleet and a Manila manning principal

Wages, allotments and owner statements that reconcile

Crew payroll is not office payroll with a different calendar. Rank, nationality, CBA, overtime codes, leave wages, seniority and family allotments all move at once, often across three currencies in a single month.

Schedule a demo Read the case study

What was breaking

A month could contain contract articles, overtime captured at sea, leave wages, seniority and family allotments in a second currency. Each principal wanted a statement in its own shape. Masters built wages on board, often offline; the agency adjusted the same period from a different file. There was no clean carry forward into the next month and no ledger an owner could audit without a reconstruction from email.

In the box

  • CBA and principal aware wage articles held as contract logic, frozen at onboarding
  • Onboard wage entry by the Master, with ordered offline to online replay
  • Automatic transfer of open wage balances into the next month
  • Multi-currency ledger: earn, allot and settle without informal rate notes
  • Owner statements and manning invoices from the same ledger as the payslip
  • Every adjustment carries a reason, an actor and a timestamp

What changed for the operator

Impact is stated in operational terms: what stopped happening, what became visible, and what the desk or the Master could do without a link.

One ledger per seafarer

Payslip, owner statement and agency invoice no longer disagree because they are no longer built in three places.

Works as the manning office

Multiple principals and CBAs share the platform without a separate payroll workbook per owner.

Offline does not mean late

Wage sheets raised at sea post in order when the vessel reconnects. Nothing is re-keyed.

Clean month end

Balances roll forward. Close is a review of exceptions, not a rebuild of the month.

Offline behaviour. Earnings, overtime and deductions raised by the Master queue on the vessel and replay in order when the link returns, with conflict rules instead of silent overwrites of shore edits.

Questions we are asked

  • Can one agency run several principals with different CBAs?

    Yes. Wage articles follow the contract and the principal, so a single desk serves multiple owners from one platform.

  • How are allotments handled across currencies?

    Earn, allot and settle sit on one multi-currency ledger, so a family allotment in a second currency does not depend on an informal rate note.

  • Is the ledger auditable?

    Every adjustment records a reason, an actor and a timestamp, and owner statements draw from the same ledger as the payslip.

Start with a complimentary assessment

A working session against your fleet, flag mix and manning model. We map where you are today, where the record breaks, and what an honest roadmap looks like. No charge, and no obligation to go further.

Schedule a demo How the assessment works

What you leave with

  • A map of where crew, wage and report data currently breaks
  • Which module earns its place first, and why
  • A staged roadmap with a proof of concept scoped to one area
  • An indicative cost envelope before you commit anything

The rest of the stack

Modules share one employee, vessel and voyage record. Take only the lines you need.

Crew recruitment

Application to owner approval on one pipeline

See the product

Crew onboarding

Joining packs, documents and the vessel snapshot

See the product

Reporting, online and offline

Noon, voyage, incident and QSMS with store-and-forward

See the product

Ship scheduling

Port rotation, berth windows and plan versus actual

See the product

Container management

Bay plan to gate-out, reefer and dry boxes

See the product