From the MYBA contract,
to the end-of-charter report.
Scyllastar automates the full charter lifecycle. MYBA contract parsing, charter fee and APA allocation, real-time expense tracking, charterer signature at every step, top-up requests, and one-click end-of-charter reconciliation. Built for yacht managers and captains who run professional operations.
The full charter lifecycle
The journey starts with a MYBA E-Contract

The industry standard, systematically validated
The MYBA contract is the benchmark charter agreement for yachting professionals. With Scyllastar, every e-contract is imported and systematically validated using the MYBA API. The system automatically extracts charter fees, APA amounts, and key dates. Zero manual data entry is required—ensuring your charter lifecycle begins on a flawless contractual and financial foundation.
Under Scyllastar engine, a powerful Yacht Charter integration
Then Scyllastar expense workflow connects the charterers, the captain, AI processes and finance in one system. Nothing falls through the cracks — every euro is accounted for, before it moves! As a results, charterers navigating with Scyllastar are more relaxed, and impressed by the professionalism. Below you can find an illustration of the end-of-charter report that can be provided to the guest at any point during the charter, increasing the quality of the communication and the luxury impression.
The end-of-charter report

The APA worflow
Charter booking
MYBA contract imported via API, charter fees and APA auto-parsed and pre-filled into the right accounts
Funds allocation
Incoming wire split automatically between charter fees and APA accounts
APA activation
Isolated card account funded and ready for onboard expenses
Expenses signature
The crew scan receipts on mobile, charterer signs off each expense, APA balance updated live
Low APA alerts
When the APA balance drops below a defined threshold, an alert is trigered. Top-up before running dry!
End-of-charter report
The captain generates the recap, the charterer signs, full charter archived with every receipt and transaction
Where Charter Management meets Yacht Accounting & Finance
Every charter is meticulously tracked as a standalone financial event—from incoming charter fees to outgoing APA expenses. But Scyllastar goes beyond individual bookings to provide ultimate financial clarity. Month by month, your charter revenue and APA expenditures are displayed seamlessly alongside your broader Yacht Finance & Accounting Module and operational running costs. Experience one unified financial dashboard with absolutely zero need for manual reconciliation.
FAQ
What is yacht charter software
Yacht charter software manages the full lifecycle of a yacht charter — from contract import to end-of-charter reconciliation. It handles charter fee allocation, APA tracking, charterer signatures, and financial reporting in one platform.
What is a MYBA contract and does Scyllastar parse it automatically?
The MYBA contract is the industry-standard charter agreement used across the Mediterranean and beyond. Scyllastar imports it via broker API and automatically extracts charter fees, APA amounts, and key dates — no manual data entry required.
How does Scyllastar manage APA during a charter?
Scyllastar funds a dedicated APA account at the start of each charter. Expenses are logged on mobile, receipts scanned, and the charterer signs off daily. Learn more about how APA works →
What happens when the APA runs low?
Scyllastar triggers an automatic alert when the APA balance drops below a defined threshold, so the captain can request a top-up through the broker before the account runs dry — avoiding any end-of-charter dispute.
Can I manage multiple charters simultaneously?
Yes. Each charter has its own isolated financial workspace. You can run several charters in parallel across your fleet with no risk of mixing accounts or transactions.
See it live!
Whether you are a captain, a yacht manager, a yacht owner…
30 minutes is all it takes to understand whether Scyllastar fits your operations
No commitment, no setup required.