Bookings & Payments
From interestto journey.
A booking is the moment a commercial decision becomes an operational commitment. Rhlah records both halves of that moment once, and everything downstream reads it.
- Quote
- Booking
- Inventory hold
- Invoice
- Payment
- Ledger
Capabilities
What this engine doesand what it does not.
Each capability below carries its real status. Anything marked planned is modelled in the platform and not yet operating.
Quote to booking
Idempotent conversion: the same quotation cannot silently produce two bookings.
Travellers
Every person on the booking as an identity, with their own documents and requirements.
Booking items
Each service on the booking tracked individually, with its supplier and its own state.
Inventory holds
Allocation held atomically at confirmation and released when a booking lapses.
Invoices
Immutable versions — a corrected invoice is a new version, never an edited history.
Payment schedules
Deposits and instalments modelled as a plan, with what is due and what is overdue.
Double-entry ledger
Every financial movement posted as balanced entries you can trace to its source record.
Commissions
Agent and partner commissions derived from a versioned rule, not recalculated by hand.
Receivables
Aging analysis across customers, computed from the ledger rather than a report export.
Online payment capture
Card and wallet capture through a payment provider. Not yet connected — manual and bank transfer are recorded today.
Connected by design
Nothing here works alone.
This engine is authoritative for its own domain and reads everything else from the engine that owns it.
Packages
Bookings are assembled from versioned packages and catalogue products.
Inventory
Holds are placed against real allocation pools.
Documents
Requirements are derived per traveller as soon as the booking exists.
Journey
Confirmed bookings become part of a departure's operational plan.
Ready to run your business differently?
See how Rhlah can fit your Hajj & Umrah operation.