A scooter that costs $600 and lasts 18 months looks nothing like a scooter that costs $600 and lasts 6 weeks — but on a cash-basis income statement, they look identical. That gap between "money left the bank account" and "the asset is actually being consumed" is exactly where most micromobility rental operators lose track of whether they're making money. It's also why the early scooter-share giants burned through hundreds of millions of dollars while genuinely believing, for a while, that they were close to profitable.
If you're running (or starting) a fleet of rental e-bikes, e-scooters, or mopeds — for tourists, a campus, a hotel amenity, or a delivery contractor — the accounting isn't exotic. But it does require treating your fleet the way it actually behaves: a wasting physical asset that generates revenue in tiny, high-volume increments, with a maintenance and theft profile that eats into margin in ways a generic "equipment" account will hide from you.
Why Vehicles Are Assets, Not Inventory
The first bookkeeping decision that shapes everything downstream is where the vehicles themselves live on your books. A rental bike or scooter is not inventory — you're not selling it, you're renting out its use repeatedly. It belongs on the balance sheet as a fixed asset, depreciated over its useful life, not expensed the month you bought it.
That distinction matters because it changes when the cost hits your income statement. Expense the full $30,000 fleet purchase in month one, and your first quarter looks like a disaster while months four through eighteen look artificially profitable. Depreciate it properly, and each month carries its fair share of the cost — which is the only way to know whether a given month's ride revenue actually covered what the fleet cost you to own that month.
Useful life is not one number. Real-world data from shared-scooter operators shows just how wide the range is: early Bird scooters reportedly lasted as little as one to two months under heavy shared use, while Lime and Voi's later custom-built hardware — with swappable batteries, reinforced frames, and better waterproofing — pushed useful life to 2–3 years or more. E-bikes generally outlast scooters, often landing in a 3–5 year range for fleet-grade hardware, versus 2–3 years for scooters. Don't inherit a generic "5-year equipment" schedule from your accountant's default template — set useful life based on how your specific hardware performs under your specific utilization, and revisit it annually against actual retirement data.
Track vehicles individually, not as a lump "fleet" asset. Each bike or scooter should have its own asset ID, purchase date, and depreciation schedule (or at minimum, be grouped into purchase-date cohorts). Fleets don't retire uniformly — a batch bought in March and ridden hard in a hilly tourist district will wear out faster than a batch bought in June and deployed on a flat campus loop. Individual tracking is also what lets you calculate revenue per vehicle, which is the single most useful number in this business (more on that below).
The Real Cost Structure: It's Not Just the Hardware
The purchase price is the easy number. The bookkeeping mistake is treating it as the whole story. A realistic chart of accounts for a micromobility fleet needs to separate:
- Vehicle depreciation — the non-cash monthly cost of owning the hardware
- Battery replacement — often the single most expensive recurring line item; batteries typically don't last as long as the frame, and swappable-battery systems (which reduce charging downtime) shift this from "occasional" to "routine, budgeted" expense
- Maintenance & repair parts — tires, brakes, locks, drivetrain wear; track this separately from battery cost so you can see which is actually driving your repair budget
- Theft & loss — a real cost of doing business in this model, not a rare write-off; budget it as a percentage of fleet value based on your actual loss rate, not zero
- IoT/telematics & fleet software — the GPS, lock, and dashboard systems that track utilization; usually a recurring SaaS-style monthly cost
- Charging infrastructure & electricity — depreciate hardware (docks, charging stations) separately from the ongoing utility cost
- Insurance, permits, and registration — often billed annually; accrue monthly so one quarter doesn't absorb the whole year's cost
- Field ops labor — the people who rebalance, charge, and recover vehicles, which for many operators is the largest single expense after the fleet itself
Lumping all of this into one "equipment expense" account is the single most common bookkeeping shortcut that hides where money is actually going. Split it, and month-over-month trends tell you something: rising maintenance-parts spend against flat ride counts usually means aging or overused hardware, not bad luck.
Per-Ride Unit Economics: The Number That Actually Matters
Total revenue is a vanity metric in this business. The number that tells you whether the model works is revenue per vehicle per day, net of the variable costs of serving that ride.
The historical scooter-share data is a useful cautionary tale here. Early Bird economics reportedly ran close to $2.43 in average revenue per mile against roughly $2.55 in total costs per mile — a business that looked busy but was structurally losing money on every ride. Contrast that with markets where a well-utilized scooter generates revenue in the mid-to-high twenty-dollar range per vehicle per day; the difference between those two outcomes isn't the vehicle, it's utilization and cost discipline.
Build your own per-vehicle-per-day math:
- Gross revenue per vehicle per day = total rental revenue ÷ (fleet size × days in period)
- Variable cost per vehicle per day = (maintenance + charging/electricity + field ops labor allocated per vehicle + theft/loss reserve) ÷ (fleet size × days in period)
- Contribution per vehicle per day = (1) minus (2)
- Fixed cost per vehicle per day = (depreciation + insurance + software + fixed overhead) ÷ (fleet size × days in period)
A vehicle only pays for itself when contribution covers its allocated fixed cost. This is where "idle inventory is the enemy" stops being a slogan and becomes a bookkeeping fact: a bike parked and unused still accrues its full daily depreciation and insurance cost, with zero revenue to offset it. Two idle bikes for every one that's actually earning is a fleet that's arithmetically guaranteed to lose money, no matter how good your per-ride price looks in isolation.
Breakeven: What It Actually Takes
Breakeven for a rental fleet isn't a single "we need $X in revenue" number — it's a function of fleet size, utilization rate, and average revenue per ride, all of which trade off against each other. A smaller, highly utilized fleet can out-earn a larger, idle one while carrying less depreciation and theft risk. Before adding vehicles, run the math on whether the existing fleet is fully utilized; expanding an underutilized fleet just scales the losses.
A practical breakeven checklist:
- Rides per vehicle per day needed to cover that vehicle's allocated daily fixed + variable cost, at your actual average revenue per ride
- Seasonal reality — tourism and leisure fleets carry strong seasonality; a breakeven calculated on peak-season utilization will be wrong for the other eight months. Model a blended annual utilization rate, not a best-week number
- Fleet refresh timing — staggering purchases (rather than buying an entire fleet at once) smooths out both the depreciation expense and the capex cash outlay in later years, avoiding a cliff where a third of your fleet needs replacing simultaneously
- Damage deposits — these are a liability (a refundable customer deposit), not revenue, until forfeited under your damage policy; booking them as income the moment they're collected overstates revenue and misstates your balance sheet
Where This Model Diverges From a Typical Rental Business
A few things make micromobility bookkeeping genuinely different from, say, a tool-rental or car-rental shop:
- Volume, not duration. A single vehicle might generate 3–10+ separate billable transactions a day rather than one long-duration rental. Your point-of-sale/booking system needs to feed ride-level data into your books at a level of detail a generic invoicing tool wasn't built for — reconciling daily aggregate deposits against a platform-generated ride report (not individual transactions) is usually the workable middle ground.
- Placement matters as much as pricing. Because idle time is pure cost with no offsetting revenue, the operational decision of where to place a vehicle is effectively a financial decision. Revenue-per-vehicle reporting, broken out by zone or dock location if your software supports it, turns "which locations are worth the field-ops cost to service" into a bookkeeping question you can actually answer.
- Regulatory and permit costs are recurring, not one-time. Many cities that permit shared micromobility charge per-vehicle annual fees or require insurance minimums that scale with fleet size — budget these as a variable cost tied to fleet size, not a fixed annual line.
None of this requires complicated software. It requires a chart of accounts that reflects how the business actually works — assets that depreciate on a realistic schedule, costs split finely enough to spot trends, and a habit of checking revenue against cost at the level of a single vehicle, not just the whole fleet.
Keep Your Fleet's Books as Precise as Your Ride Data
If your fleet management software can already tell you utilization and revenue per vehicle, your accounting should be able to match that precision — not blur it back into one lump "equipment" line at tax time. Beancount.io offers plain-text accounting that's transparent, version-controlled, and easy to script against ride-export data, so your books can track fleet economics at the same granularity your operations dashboard does. Get started for free and see why developers and finance-minded operators are switching to plain-text accounting.