Billing · Controls · Reporting
Corporate chauffeur accounts.
One invoice, tagged the way your finance team already thinks.
An account should make the car invisible to everyone except the passenger. Bookers book, journeys land pre-tagged, and finance receives one document a month they can post without re-keying. No cards, no expense claims, no receipts in a drawer.
A conversation, then you are live.
No minimum spend, no joining fee, no contract you have to grow into.
Setting up takes one conversation. We agree who can book, what journeys should be tagged with, whether anything needs approval above a threshold, and where the invoice goes. That configuration is applied once and then nobody thinks about it again.
Your first journeys can run the same week. Most accounts start narrow — one team, or the airport runs — and widen once the travel manager has seen a month of invoices land in the shape they asked for.
If you already have a chauffeur supplier, keep them. Running alongside an incumbent is normal, and usually starts with whatever they handle least well. We would rather earn the rest of the volume than ask you to switch everything on the strength of a meeting.
Everything the account does.
Named bookers
Added by you, scoped by you. Assistants book for anyone; individuals book for themselves.
Cost-centre tagging
Captured at booking, carried to the invoice. Free text, a fixed list, or pulled from your systems.
Firm pricing
Quoted before confirmation and unchanged on the invoice. No surge, no post-hoc adjustment.
One monthly invoice
Itemised by journey, passenger, cost centre and VAT. Thirty-day terms as standard.
Approval thresholds
Journeys above a value you set wait for a sign-off before they are confirmed.
Travel-manager view
Every journey the company has taken this month, filtered by department, in one place.
Calendar-native booking
The meeting moves, the car moves. No cancellation, no rebooking, no phone call.
API and events
Journeys and invoices pushed into your own finance or travel platform as they happen.
Credit-backed punctuality
A late collection on a confirmed booking is credited. The rule is published, not implied.
The invoice is the product.
Most of the pain in corporate travel is not the journey. It is the fortnight afterwards.
One invoice a month, itemised by journey, passenger, cost centre and VAT. The figure against each journey is the figure that was quoted when it was booked — firm pricing means the reconciliation is a formality rather than an investigation.
Waiting time within the agreed allowance, tolls and the congestion charge are inside the quoted price rather than appended afterwards. Where an overrun does apply, it is charged at a published rate that was agreed at account setup.
If you would rather not handle a document at all, the API emits an event per journey and per invoice, so the data arrives in your finance platform continuously. Several of our accounts have never opened a PDF from us.
Accounts and billing, answered.
Is there a minimum spend or a joining fee?
+
No to both. An account exists so your people can book without a card and your finance team gets one invoice — it is not a contract you have to earn. We would rather you started with four journeys a month and grew.
What are your payment terms?
+
Thirty days from invoice as standard, on a monthly billing cycle. Longer terms are agreed case by case at account setup rather than negotiated later against an overdue balance.
Can we tag journeys to cost centres, matters or deal codes?
+
Yes, and at the point of booking rather than in a reconciliation afterwards. The field can be free text, a fixed list you supply, or pulled from your own systems through the API. Whatever you tag with appears as a column on the invoice.
Can we control who is allowed to book?
+
Named bookers are added by you and can be scoped — some book only for themselves, assistants book for anyone, travel managers see everything. Approval thresholds can be set so a journey above a value needs a sign-off before it is confirmed.
How does VAT appear on the invoice?
+
Itemised per journey, with the VAT element separated and the invoice structured so it can be posted without anyone re-keying. If you need a specific layout for your finance system, we will match it.
Can journeys go straight into our expense or finance platform?
+
Yes. Our API emits an event per journey and per invoice, so travel data lands in your system as it happens rather than as a PDF at month end. Most finance teams take the invoice feed and leave the rest.
What if we already have a chauffeur supplier we like?
+
Keep them. A number of our accounts run us alongside an incumbent, usually starting with the journeys the incumbent handles least well — airports, roadshows, or anything that moves at short notice. We would rather win the rest than ask you to switch on faith.
Open an account.
Tell us roughly what you spend on car travel now and how your finance team wants it cut. We will come back with the account structure and firm prices on your real routes.
hello@blackfleet.dev