Programme concept
The guest signs nothing. The charge goes to the room.
A programme concept for properties: the hotel books transportation or luggage service and the charge reaches the guest folio rather than the guest's card.
Available on requestFor transportation companies, DMCs, hotels and FBOs.
Part of Hotel Luggage Services · all services
What this service handles
Bill-to-room is the arrangement every concierge wants and most transportation vendors cannot support. The guest asks for a car, the desk arranges it, and the charge appears on the folio like room service — no card handed over at the kerb, no expense claim, no separate receipt.
VaultPac's account model already holds the half that matters: charges belong to an account rather than to a booking, so a property account can carry every guest movement and be settled in one place.
Posting directly to a guest folio through a property management system is a planned capability, not a live integration. Today the same commercial outcome is achieved through a property account and agreed settlement — which most properties find is the whole of what they wanted. We would rather describe it exactly than sell an integration that does not exist yet.
Typical movement
- Property account established Charges collect against the property, not the guest
- Desk books for the guest Transportation, luggage or both
- Service runs Guest hands over nothing
- Charges settled with the property For onward posting to the folio
Who uses this service
- Hotels and resorts
- Concierge and front office teams
- Revenue and commercial managers
- Serviced apartments and residences
- Property groups standardising vendors
How VaultPac coordinates it
Every booking is a trip. A trip carries trip services, and each service breaks into the individual movements that actually have to happen — which is why the people and the bags do not have to travel the same way.
- Trip
- Trip services
- Individual movements
-
Account billing
Charges belong to an account rather than to a single booking, so one programme can carry several contacts, cards and cost centres.
-
Passenger movement
Sedan, SUV, Sprinter, minibus and coach movements priced and dispatched by the transportation engine.
-
Luggage movement
Bags booked as their own movement, with their own route, their own timing and their own proof.
-
Trip → Trip Services → Movements
One trip holds every service on it, and each service breaks into the individual movements that have to happen. A single booking can carry people and bags on different vehicles and different clocks without becoming two bookings.
-
Dispatch monitoring
Every movement on one board while it runs, so a late arrival is seen rather than reported.
-
Bill-to-room posting Planned
Charges posted to a hotel folio rather than collected from the guest.
Capabilities marked Planned are designed and in progress but not live yet. They are listed so you know what is coming, not so you book on them.
What runs this movement
Assignment reads the passenger count and the bag count, so the vehicle that arrives fits both. Larger movements run several.
-
Executive sedan
-
SUV
-
Cargo vehicle
Why VaultPac for this
- Account-level billing already exists, so the commercial half of bill-to-room works today.
- Transportation and luggage settle on the same account rather than through two vendors.
- Honest about the integration: folio posting is planned, account settlement is live.
Important
- Direct posting to a guest folio through a property management system is a planned capability, not a live integration. Current arrangements settle through a property account.
Questions
Can you post directly to our PMS?
Not today. Direct folio posting is a planned capability. What works now is a property account that collects the charges and settles with you, which achieves the same thing for the guest.
Next step
Plan bill-to-room with us
Tell us the shape of the movement — dates, numbers, where it starts and where it has to end. We come back with an operating plan and a price, not a form letter.