When you run other people's cars, the accuracy and timeliness of the monthly statement is the relationship. FleetPilot automatically pulls every Turo and Ride trip and every direct rental — Wheelbase, HQ Rentals, etc — into one professional owner statement, applies the split line by line for each channel and gives your co-hosts a portal to self-serve their requests and find their next vehicle to add to your fleet.
Turo trips, direct rentals, expenses and bank activity reconciled into a branded statement per owner. Review in one click, send to the owner's portal with the payout.
14-day free trial · No credit card required
Owners don't care which channel a booking came from — only that the number is right and the deposit matches. Every source below lands in one ledger, matched to a vehicle and an owner.
Trips imported and matched to the VIN; Turo's share and reimbursements as their own lines.
Earnings CSV import and Turo email parser — trip price, Turo's share, reimbursements, delivery, tolls and mileage overage, per trip, matched to the VIN.
Gross trip revenue, Turo's share, reimbursements, and the split per line.
Ride bookings and payouts imported and matched to the vehicle, fees separated.
Ride payouts and bookings imported per rental — revenue, add-ons, Ride's fees — matched to the VIN.
Ride revenue per vehicle as its own line, fees separated, split applied.
Direct bookings read straight from Wheelbase — Wheelbase stays your reservation system.
FleetPilot reads your Wheelbase reservations, add-ons, fees and payouts. Wheelbase stays your booking system.
Direct-booking revenue by unit and owner, reconciled to the bank payout.
Reservation and payment data in for counter and fleet operators.
Reservation and payment data from HQ Rentals, for counter and fleet operators.
Reservation revenue and fees per vehicle, split by owner.
Medium-term and recurring rentals you bill through Stripe, landing on the right vehicle.
Monthly and recurring rentals you book yourself — rideshare drivers, corporate, extended contracts — billed through Stripe and matched to the vehicle.
Direct-rental revenue per vehicle, net of processing fees, split like any other channel.
RV payouts, add-ons and fees imported per booking and matched to the unit.
Outdoorsy payouts per booking — rental income, add-ons, mileage and generator charges, fees — matched to the unit.
Per-unit RV revenue, fees separated, owner's share on every line.
Plaid bank feeds, receipt OCR and Stripe payouts cover every expense and every owner payment.
Plaid bank feeds for every cost, receipt OCR, and Stripe for owner payouts.
Itemized expenses per unit, deductions from the owner's share, and the payout — sent with the statement.
Turo, Ride, Wheelbase, Outdoorsy and HQ Rentals handle listings, bookings, vetting and deposits. FleetPilot picks up after the booking — ledger, per-unit P&L, statements, payouts, taxes. Nothing to switch off.
Same document, named for who's reading it. FleetPilot sends one per owner, from one ledger.
Sample statement — Summit Auto Fleet, June 2026.
| Unit | Channels | Gross | Owner share |
|---|---|---|---|
2023 Tesla Model Y Car | Turo | $2,940 | $1,764 |
2022 Ford Bronco Car | Turo + Wheelbase | $3,410 | $2,046 |
2021 Winnebago View RV · Class C | Outdoorsy | $5,880 | $3,528 |
2020 Airstream Bambi RV · trailer | Wheelbase direct | $2,260 | $1,356 |
| Payout to owner · sent via Stripe | $14,490 | $8,694 | |
The monthly, per-vehicle accounting an operator sends the owner of a car or RV they manage: revenue from every channel (Turo and direct rentals), platform fees, reimbursements, itemized expenses, the split applied line by line, and the amount owed — matching the payment the owner receives.
Yes. Turo trips and direct rentals from Wheelbase, HQ Rentals or your own site are matched to the vehicle and owner and shown on one statement, with the channel on every line — one number for the month, not two spreadsheets.
Yes. FleetPilot reads Wheelbase reservations, add-ons, fees and payouts into the same ledger as your Turo and Outdoorsy income, so direct-booking revenue appears on the statement per unit and owner. Wheelbase stays your booking system; FleetPilot handles the accounting after the booking.
Yes. Outdoorsy payouts are matched to the unit with fees, add-ons and mileage or generator charges itemized, and any Wheelbase direct rentals for the same unit are shown alongside as one combined number.
Yes — same document, named for who receives it: a co-hosting statement for the owner whose car you run, an investor statement for a partner who funded several units. FleetPilot generates one owner statement per owner from one ledger.
Yes. Every unit is a VIN, an owner, a channel mix and a P&L — so an owner with a Turo car and an Outdoorsy RV gets one statement, one portal login, and one Stripe payout.
No. They handle listings, reservations, guest vetting, deposits and booking-time insurance. FleetPilot picks up after the booking — ledger, per-unit P&L, owner statements and payouts, tax reporting. You keep them and add FleetPilot on top.
Review the auto-drafted statement, approve it, and FleetPilot sends it to the owner's portal and pays out through Stripe Connect. Lines link back to the trip, booking or receipt behind them.
Connect your channels and bank accounts, and FleetPilot builds the ledger behind them — company financials, per-vehicle P&L, and owner statements that always agree.