Loading
Because a booking changes. The party size moves, a room is upgraded, a flight shifts, and each change touches the itinerary, the price and the payment schedule in three different places.
The version the client has, the version operations are working to and the version finance is billing are all slightly different, and the discrepancy surfaces at the balance.
The quote is the itinerary, priced from the rate card, and version history records what changed between v3 and v4 and who asked for it. The confirmed version is what everything downstream reads.
Deposits and balances are scheduled in Books from that version, so a due date is a record with an owner rather than a row in a spreadsheet.
It does not book inventory. It holds the client, the enquiry, the priced itinerary and the money; the reservations happen wherever they happen now.
And it will not price a package for you. It applies the rate card you maintain, including seasonality, but the commercial decisions in it are yours.
Balance due dates appear as work with a clock, not as a monthly reminder somebody set. Payment state is on the same record the operations team is reading, so nobody confirms a supplier against an unpaid balance by accident.
When an itinerary changes after confirmation, the schedule changes with it rather than being re-keyed.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes — deposit and staged balances, scheduled in Books from the confirmed itinerary.
Yes, with a line-level diff between each version and the reason for the change.
Yes, as one booking with a party, or linked bookings where each party pays separately.
Half an hour on your own numbers is usually enough to say whether Flow is the right place to start.