Ground transportfinance can read.

A corporate ground transportation programme is a single agreement under which an organisation books all of its chauffeur travel, rather than leaving employees to arrange and expense rides individually. It centralises booking, pricing, policy, reporting and payment across every market the organisation travels to, so travellers book through a controlled channel, finance receives one consolidated invoice, and the travel or security team can see journeys while they are happening.

Send us your organisation name, roughly how many travellers you have and which markets they travel to. A twenty-minute conversation establishes whether you need a self-serve or a managed account, after which the account is configured with your cost centre structure, policy rules and invoicing entity. The first ride can usually happen the same day the account is approved.

No minimum spend and no lock-in contract at any size. Self-serve accounts can be opened and used immediately. Managed and programme accounts have a written agreement covering service levels and rates, but it does not commit you to a volume.

One invoice per period, itemised by traveller, journey, date and cost centre, issued in the currency you account in regardless of where the rides took place. Payment terms are agreed when the account opens. Individual travellers never pay and never file an expense claim for a booked ride.

Yes. Limits by vehicle class, route, spend or seniority are applied at the point of booking rather than enforced afterwards. Bookings that fall outside policy can be blocked outright or routed to a named approver, and the rules can differ by traveller group, by market or by both.

Yes, and it is one of the most used features on the platform. Arrangers book for anyone they are authorised for. The traveller receives the chauffeur details and the tracking link directly, while the confirmation, the receipt and any changes stay with the arranger.

Spend by cost centre, market, traveller and vehicle class, alongside punctuality and completion data. Reports can be scheduled to your inbox on whatever cadence you want, downloaded from the portal, or pulled through the API into your own reporting stack.

Yes. Where you already have a TMC, ground transport can be booked inside the workflow your agents already use rather than in a separate system. That arrangement is set up jointly with your TMC, and it does not require your travellers to change anything.

Yes, covering quoting, booking, tracking and reporting, so ground transport can sit inside your own travel tooling or intranet. Integration is a matter of weeks rather than months. Companies embedding RYDES into a customer-facing product should look at strategic partnerships instead.

Because rides are pre-booked, the vehicle, the operator and the named chauffeur are known before the journey begins. Active journeys are visible in real time to the roles you authorise, so your travel or security team can see where a traveller is while they are travelling rather than reconstructing it from an expense claim afterwards. Access is role-based rather than open to everyone on the account.

Yes. Rides in any market can be consolidated onto one invoice in your accounting currency. Organisations with multiple legal entities can also have separate invoicing entities and currencies within the same programme, reported together.

Invoices are issued to meet the requirements of the invoicing entity's jurisdiction, with the tax detail your finance team needs to reclaim where reclaim is available. This is one of the larger hidden savings of a programme, because per-ride receipts from mixed suppliers are frequently unusable for reclaim.

Negotiated rates are available above an agreed volume and are set out in writing. We do not discount by reducing what the operator is paid, because a chauffeur underpaid on your account is a chauffeur who does not turn up on it. Savings come from consolidation and administrative cost rather than from squeezing supply.

Managed and programme accounts have service levels written into the agreement, covering response times, escalation routes and reporting cadence. They are set against what your programme actually needs rather than a standard sheet, and they are reviewed at whatever interval you want to review them.

Traveller data is used to deliver the rides you book and is shared with the local operator only to the extent needed to complete a journey. Access within your own account is role-based. Our handling of personal data is set out in the privacy policy, and specific contractual data terms can be agreed as part of a programme agreement.

Yes. Multi-vehicle event and roadshow programmes are quoted separately because they need a coordinator and a vehicle plan, but they are delivered under the same account and appear on the same invoice with the same cost centre coding.