Turo's earnings export tells you what you were paid, not what you made. How to turn trip and payout data into per-vehicle numbers you can actually run a fleet on.
Turo will show you what it paid you. That is a genuinely different question from what your fleet earned, and confusing the two is how operators end up running unprofitable vehicles for months without noticing.
Turo’s earnings data is built around trips and payouts: trip dates, trip price, Turo’s share under your earnings plan, guest reimbursements, and the resulting payout.
That’s revenue-side only. It contains nothing about:
Which means the export cannot answer the only question that matters at fleet scale: is this specific car making money? It can only tell you the car produced revenue, which every car does.
Payouts don’t map cleanly to months. Turo batches payouts on its own schedule. A single deposit can cover several trips, some of which started in the previous month. If you book revenue when the deposit lands, your monthly numbers drift away from the activity that produced them, and owner statements stop matching reality.
Book against trip end date instead, and treat the deposit as settlement rather than as the revenue event.
Aggregate hides the losers. In our experience most ten-car fleets with healthy total revenue are carrying at least one car that loses money. At the aggregate level they’re invisible, subsidized by the performers. You only see them when revenue and costs are attributed per vehicle — per VIN, not per fleet.
Whatever tooling you use, the target is the same. Every dollar in and out lands against a specific vehicle, and:
Get those five right and per-vehicle P&L, company financials, and owner statements all fall out of the same data — and therefore agree. Get them wrong and you maintain three separate spreadsheets that diverge a little more each month.
Viable up to a handful of cars, and worth understanding even if you later automate:
The failure point is rarely the first month. It’s month seven, when a claim opened in month five pays out, a guest reimbursement was rebilled late, and nothing ties out — with no audit trail explaining why.
FleetPilot connects Turo — along with Ride, HQ, or Wheelbase — plus the bank account the fleet actually runs on. From there, trips, payouts, platform fees, repairs, tolls, and claims get matched to the right vehicle and the right owner automatically.
The result is one vehicle-aware ledger producing a company P&L, true profit for every VIN, and owner statements from the same underlying data — so they come from one dataset rather than needing to be reconciled against each other. The first 10 active vehicles are free.
Exact screens change as the product does; if anything here doesn’t match what you see, the in-app flow is authoritative.
Whatever route you take, validate with these:
If the last one fails, nothing upstream is trustworthy yet. That’s the subject of how to build a Turo owner statement.
No. It shows trip price, Turo's share, and payouts. It contains nothing about repairs, cleaning, tolls, financing, insurance, or depreciation, so it cannot tell you whether a vehicle is profitable.
Payouts are batched and timed on Turo's schedule, so one deposit can span several trips and two calendar months. Reconciling requires matching deposits back to the individual trips inside them, which is why trip-level rather than payout-level data matters.
Turo uses "co-host" to mean two completely different things, and conflating them costs owners and operators real money. Here's how the programs differ, what each split actually pays, and what you need in place to run this as a business.
A walkthrough for producing an owner statement that survives questions: what to pull, what order to show it in, and the reconciliation check to run before you send it.
FleetPilot turns your Turo, direct rental, and vehicle expense data into a seamless end-of-month owner payout process.
Start free