"Who has paid the deposit and who owes the balance?"
A group departure can have dozens of travellers, each at a different stage of payment.
Faas handles instalment payments, supplier bills and refunds for trips, and connects to your travel booking app through the integrations API so nothing is typed twice.
No card needed to start. Set up in minutes.

Customers pay a deposit, then a balance. Airlines, hotels and ground handlers each want money on their own dates. Tracking that in a spreadsheet works until the busy season.
Selling trips means holding other people's plans and money. Here is where the books get hard.
A group departure can have dozens of travellers, each at a different stage of payment.
Miss a supplier deadline and you can lose seats or rates.
Part is refundable, part is not, and the paper trail needs to be right.
Deposits arrive months early. It feels like profit, and it is not yet.
Save your payment terms as templates, such as 30% deposit and 70% before the trip. Faas works out each amount and due date and tracks every instalment. Customers pay from one pay link with FPX, card or e-wallet, and the invoice updates by itself.
Airline, hotel and ground costs go in as bills with their own due dates. Faas lists them in Bills to pay, sorted by date, with a reminder before each deadline. You see how much cash to keep before you pay.
Faas connects to travel booking apps through the integrations API. A booking app can push invoices, payments and expenses into Faas. Each push carries a source id, such as the booking number, and an idempotency key, so sending the same booking again never double-posts.
Raise a credit note against the original invoice for the part that is cancelled. Then choose Apply to offset another invoice for the same customer, or Refund to pay cash back. Supplier cancellations work the same way as debit notes.
Faas keeps double-entry books underneath, and your accountant sees the ledger, supplier ageing and a one-click Audit Pack. Faas does not manage itineraries or seats. Your booking app does that, and Faas does the money side.

The money follows the trip. Here is the path for one booking.
The booking is made in your travel booking app. The invoice, with a 30% deposit term, reaches Faas through the integrations API, or you create it by hand. The customer gets a pay link.
The customer pays by FPX. The invoice updates, the bank line matches and the balance shows as due later.
The airline and hotel invoices wait in Bills to pay with their due dates. Reminders come before each deadline.
Balance reminders go out. When everyone has paid, you see who owes you drop to zero for that trip.
Rules change.Confirm current rates and dates with the Royal Malaysian Customs Department, LHDN or your accountant. Faas explains ideas in plain words and does not give legal or tax advice.
These explain why a healthy bank balance can still hide a problem.
Two instalments of one price.
What the trip costs you to run.
Money in the bank is not always yours yet.
Deposits, balances and supplier costs, together in one place.