FOM (Ferry Operator Manager) is Ferry VN's management software for high-speed ferry operators: timetables, counter and agent sales, voyage operations, manifests, QR boarding and revenue reconciliation in one system.
- operators connected to Ferry VN
- 15+
- agencies on the Ferry VN network
- 150+
- manifest forms: Form 48, Form 61, Circular 80 list
- 3
- tier-1 agents and sub-agents, each with its own account and ledger
- 2 tiers
Figures as of November 2026
How does an operator build timetables and create voyages?
The operator sets up ports, routes, vessels and seat layouts once, then builds a schedule template for each route so FOM generates voyages on the running days.
- Templates by weekday, with skipped dates and extra trips
- Preview of new, existing, skipped and conflicting voyages
- Seat layouts per deck, versioned, seat numbers fixed per vessel
- Departure calendar by month, week, day or list
- Swap the vessel or cancel a voyage when needed
How does the ticket counter sell, take payment and refund?
Counter staff sell on a six-step POS screen, take cash, bank transfer or card POS, then print a ticket with a digitally signed QR code.
- Seat holds with a countdown, extend or release
- Passengers typed in, imported from Excel or looked up; duplicate IDs blocked
- Deposits accepted; A4 tickets or 80 mm receipts
- Sales shifts: opening float, cash count, explained differences, sign-off
- Cancellation fee and refund quoted before confirmation
How do operators run voyages, file manifests and scan QR tickets?
The operations board gathers the day's voyages. Dispatchers file the manifest before departure; staff scan the QR code on each ticket with a phone at the quay.
- Operations board filtered by status, route or warnings
- Manifest on Form 48, Form 61 or Circular 80, as XLSX, PDF, CSV
- Every manifest filing is an immutable version
- Boarding without a connection once voyage data is downloaded, then auto-sync
- Post-voyage reconciliation: boarded, not scanned, scanned twice
How are agents, credit limits and commission managed?
Each agent sells from its own account and ledger, and the amount is debited straight from the available balance. The operator sets limits and commission per agent.
- Immutable ledger tracking balance, credit limit and frozen amount
- Available balance = balance + limit − frozen
- Commission as a fixed amount per ticket or a percentage
- Settlement: deduct commission at sale or settle periodically
- Suspended agents have every sale rejected until reopened
How do agent top-ups and revenue reconciliation work?
Agents top up by bank transfer or a manual request. Accountants import the bank statement to match top-ups, then export revenue reports and reconciliation statements.
- Bank transfer with the reference NAP plus agent code
- Import Excel or CSV statements, dry run before committing
- Unmatched rows wait for manual matching; each transaction tops up once
- Manual top-ups and adjustment entries need a second person's approval
- Export by day, staff, route, vessel, channel, VAT, commission to Excel or CSV
The order for setting up and running an operator on FOM.
- 01
Set up the catalog and fares
Create ports, routes, vessels, seat layouts and ticket types, then VAT rates and a fare matrix by route and ticket type. Check prices with the simulator before opening sales.
- 02
Build the timetable and generate voyages
Create a schedule template, preview it, then generate voyages and open them for sale. Watch held seats on the seat-hold monitor.
- 03
Sell through the counter and agents
Cashiers open a shift and sell at the counter; agents sell from their own account or through the Agent API. Every ticket carries a digitally signed QR code.
- 04
Run the voyage, file the manifest, scan tickets
Dispatchers file the manifest, move the voyage to boarding and scan QR codes at the quay. On departure, tickets not scanned become no-shows.
- 05
Close shifts and reconcile
Managers sign off shifts; accountants reconcile bank and agent accounts, run revenue, VAT and commission reports and track e-invoices.
| Excel, Zalo and separate tools | FOM | |
|---|---|---|
| Seat status | Sold seats reconciled by hand between spreadsheets or messages | Every seat is free, held, sold or blocked; holds expire |
| Timetable | Schedule retyped for each day | Schedule templates generate voyages by weekday, with preview, skipped dates and extra trips |
| Passenger list | A file assembled from several sources before departure | Manifest on Form 48, Form 61 or Circular 80, exported as XLSX, PDF, CSV, every filing a version |
| Boarding | Checking against paper lists or photos | Signed QR scanning on a phone, works offline, boarded and not-scanned reconciliation |
| Agent credit and top-ups | Balances and top-ups kept in spreadsheets or chat groups | An account and immutable ledger per agent; bank statements matched on the NAP reference |
| Cashier shifts | End-of-day cash checked on paper | Open and close shifts, cash count, difference explained, manager or accountant sign-off |
Frequently asked questions
How is FOM different from Ferry VN's agency dashboard?
FOM is the operator's system: timetables, counter sales, agent management, voyage operations and revenue reconciliation. The B2B Dashboard is the agency's tool for selling tickets across operators and managing credit.
Which roles use FOM and how are permissions assigned?
FOM has roles for head-office administrators, office managers, cashiers, accountants, operations staff, agency staff and API applications. A role is only a default bundle; a menu that does not appear means the account lacks that permission.
How do agents and OTAs with their own systems connect to FOM?
Through the version 1 Agent API, authenticated with OAuth 2.0. The operator issues an API application per agent, choosing its scopes, requests per minute and maximum concurrent holds. There is a separate sandbox, orders are duplicate-safe, and webhooks are signed.
Does QR boarding work without a connection?
Yes, once the device has downloaded the voyage's data while online. QR signatures are verified on the device and scans sync when the connection returns. A ticket cancelled after the download is caught only at sync, so reconciliation flags it separately.
Which manifest forms does FOM use and how is a manifest filed?
FOM supports Form 48 (maritime), Form 61 (inland) and the Circular 80 list, in an official and a captain's version, as XLSX, PDF or CSV. After the vessel departs, the manifest is locked and a final version is produced.
How are cancellations and refunds handled?
FOM quotes the cancellation fee under the operator's rules and the refund amount, with an expiry time. Once boarding starts, cancelling or changing tickets needs a manager's approval. Refunds go out in cash during an open shift, by bank transfer, or as agent account credit.
Does FOM issue e-invoices?
Yes. FOM issues e-invoices through MISA meInvoice, as invoices created from a cash register, and supports adjustment and replacement. The operator configures its MISA account and invoice series; accountants follow status and resend failed invoices.
Related documentation
For
For ferry operators
The operators page explains how an operator puts its tickets in front of Ferry VN's agent network and OTA channels, and how to partner with us.
See the operators pageMore from Ferry VN
B2B DashboardThe tool agencies use to sell tickets across operators and manage customers, credit and multi-tier agency networks.
Online bookingTravelers book on Web, App or Telegram/Zalo Mini App.
API · SDK · MCPOTAs and technology partners embed ferry ticketing in their own products through the API, SDK and MCP server.
Last updated:
15+ operators are connected to Ferry VN. Leave your details and the Ferry VN team will get in touch to learn how you run today and how FOM would be set up.