How to Set Up a Corporate Car Service Account: 2026 Guide

A corporate car service account is a set of agreed operating, payment, data, and support terms. It should not be treated as a synonym for credit, discounted pricing, a booking portal, preferred vehicles, reporting, integrations, or guaranteed availability.

This guide covers the setup decision after a provider is being considered. Executive assistants managing individual movements can use the executive assistant booking guide. Teams still comparing suppliers can use the travel manager selection guide; formal procurements can use the RFP guide.

1. Write the account requirements brief

Describe actual demand: markets, airport and non-airport trips, point-to-point and hourly use, traveler groups, typical booking lead times, accessible requests, after-hours needs, currencies, billing references, and expected users. Use recent approved trip records where available without publishing sensitive traveler data.

Separate required, preferred, and optional features. A requirement should include an acceptance method. For example, “invoice contains trip ID and cost center and passes a sample reconciliation” is testable; “great reporting” is not.

2. Build a feature confirmation matrix

Record “available,” “not available,” “requires configuration,” or “requires separate agreement.” Do not fill an unanswered cell with an assumption.

3. Confirm legal, insurance, and operating evidence

Ask the provider to identify the contracting entity, operating role, fulfillment model, service area, required licenses or permits, insurance evidence, subcontractors or affiliates, incident process, and current contact. Have qualified internal reviewers decide what evidence and limits apply.

A certificate, registration, or policy document should be checked for the named entity, dates, scope, exclusions, and verification contact. This guide does not state that Detailed Drivers holds a particular certification, limit, permit, or coverage.

4. Define user roles and approval rules

State who may create, approve, change, cancel, view traveler data, access invoices, dispute charges, export records, and administer users. Apply least privilege and require a backup for time-sensitive approvals. Document how new users are verified and how access is removed.

If delegated booking, cost centers, spending limits, traveler profiles, single sign-on, or approval workflows are needed, ask whether each feature exists and test it. Do not assume an “account” includes any of them.

5. Agree on payment and invoice mechanics

Confirm accepted payment methods, deposits, credit review, billing cycle, currency, taxes, tolls, parking, airport charges, waiting, overtime, cancellation, gratuity, credits, dispute timing, and authorized approvers. Account creation does not establish NET terms, a credit limit, or a discount.

Define the invoice unit and required fields: trip ID, traveler or approved alias, service date, origin and destination, service type, quoted amount, approved changes, itemized components, cost center, purchase order, currency, taxes, credits, and final total as applicable. Test a sample against the organization's reconciliation process.

6. Specify privacy and security requirements

The Federal Trade Commission's business cybersecurity guidance recommends keeping only needed data, limiting access, protecting sensitive information, securely disposing of data, planning for incidents, and addressing security in vendor contracts.

Ask what passenger, itinerary, payment, accessibility, and location data is collected; why; where it is processed; who can access it; which subprocessors receive it; how long it is retained; how it is deleted; and how incidents are communicated. Require evidence appropriate to the organization's risk, and have security or privacy reviewers assess it. A named framework does not itself prove compliance.

7. Design the accessibility request path

Define how a traveler or booker submits requested assistance, mobility-device dimensions, whether the traveler remains in it, lift or ramp need, companions, bags, communication preference, and accessible entrances. Limit access to people who need the information.

Account setup should identify the confirmation and escalation path, but each trip still needs its actual vehicle configuration and handoffs confirmed. Do not convert an accessibility profile into a standing assumption when needs can change.

8. Document service policies and exceptions

Detailed Drivers airport pickups include 45 minutes of complimentary waiting for domestic flights and 60 minutes for international flights, beginning at actual landing, with flight tracking. Non-airport pickups include 15 minutes. Overtime is billed for the actual additional minutes at the applicable per-minute rate for your selected vehicle.

The standard hourly minimum is 3 hours; a longer event minimum applies only when booking-confirmed. Sedan and SUV bookings receive a full refund when cancelled at least 24 hours before the scheduled pickup time. Sprinter bookings receive a full refund when cancelled at least 72 hours before the scheduled pickup time. Cancellations inside the applicable notice period are charged in full. Quoted all-in pricing includes gratuity, so an additional tip is optional.

Put those terms into booking examples and invoice tests. If the organization requests different terms, treat them as proposed changes until both parties accept them in writing.

9. Run a bounded pilot

Select representative scenarios without placing critical travel at unnecessary risk: an airport arrival, non-airport transfer, itinerary change, cancellation, hourly movement, accessibility request, after-hours contact, invoice correction, and user removal where relevant.

Before testing, define acceptance criteria, evidence owner, due date, and failure path. A successful trip does not prove invoice accuracy or data deletion; test each agreed control directly. Record defects, remediation, retest result, and open exceptions.

10. Accept, limit, or reject the setup

Create an implementation register with the final agreement, operating contacts, role matrix, booking guide, service policies, billing rules, security terms, accessibility path, escalation tree, pilot evidence, open risks, renewal or review date, and account closure procedure.

Accept only the features supported by written evidence and successful tests. Limit rollout where an open item has a controlled workaround. Reject or pause when a required control, service area, payment term, accessible configuration, or evidence requirement is not met.

Account setup checklist

1. Define demand, markets, trip types, users, and required outcomes.
2. Separate required, preferred, and optional features.
3. Verify the contracting entity, operating model, insurance, and permits.
4. Approve user roles, least-access rules, and removal process.
5. Confirm payment, credit, invoice, dispute, and credit mechanics.
6. Review data collection, subprocessors, retention, deletion, and incidents.
7. Define accessible-request confirmation and escalation.
8. Put service policies into booking and invoice examples.
9. Run representative pilot scenarios against written acceptance criteria.
10. Record accepted capabilities, limits, owners, review date, and closure steps.

Review corporate travel service, business transportation, and rate information. Submit representative itinerary requirements through reservations or use the contact page for account questions. Availability and features require written confirmation.

Frequently asked questions