One ledger for every channel: website, agency, kiosk and on board

What does "one booking flow" mean?

In BORA, Sales is the booking flow itself, wherever it happens. A passenger on the Passenger website, an agent on the Agency portal and a crew member selling on board all write into the same flow.

Underneath, Reservation turns each sale into one reservation object — created, amended, cancelled or refunded through one flow, with the invoice raised from the same record. A ticket is therefore the same thing however it was sold: valid at the same ramp, refundable on the same terms, counted the same way.

Which channels write into it?

The passenger website, a multi-brand storefront. The Agency portal, which applies each agency's terms, credit and settlement. The booking console, a self-service kiosk at the terminal. Cash desks, where cashiers take cash and card against an open shift. The On-board PoS, which sells tickets and goods at sea. And GDS, which brings bookings from maps, travel apps and aggregators back in as the same object as a direct sale.

How do payments end up in one place?

BORA's Payment gateway takes online banking, cash, Apple Pay, Google Pay and agency tickets, each authorised on its own rails, and settles every method into the same ledger — whether the sale was made at the port or at sea — reconciling it against the sale automatically.

At the desk, a shift closes and reconciles against records that already exist, so end-of-shift cash-up is a check rather than a separate count to merge into the books. Channel commissions from GDS partners reconcile into the ledger the same way.

What is the ledger underneath?

BORA's Ledger is double-entry accounting: an immutable journal where every sale, refund and settlement posts an entry, with customer and credit accounts kept in balance. Nothing is edited in place; a correction is a new entry, so the financial record is auditable end to end.

Because everything lands in one place, Reporting reads passenger volumes, vehicle counts and revenue by route and season from live operations rather than from exports at the end of a period. There is nothing to merge, because nothing was ever separate.

What does this not replace?

The operator's accounting system. Ledger and Payment gateway feed it through an API and standard exports rather than replacing it.

Ledger is also not yet the single source of truth for credit limits: credit-limit enforcement still reconciles against operational records. And Payment gateway does not hold card data beyond what the connected terminal's PCI scope allows.