Mileage Tracking

Mileage Tracking

Record trips, vehicles, and mileage reimbursement data using the mileage flows currently exposed by Stareceipt clients.

Last updated: 2026-06-14

Overview

Stareceipt's mileage feature lets you record vehicle trips alongside receipt-based expenses so travel activity can live in the same product surface. Current shared code proves mileage support for:

  • trip records,
  • vehicle records,
  • active tracking sessions,
  • reimbursement amounts and currency fields,
  • rate-region based quoting,
  • browser foreground GPS tracking plus app-only background tracking differences.

Mileage write actions and map-backed actions are available on Plus, Premium, and Business plans. Free and Core users can still view saved historical mileage records, but cannot create, edit, delete, track, search places, calculate routes, manage vehicles, or load map views.


Current entry flows

When the active ledger has mileage access, current shared clients expose two broad mileage flows:

  1. Manual trip entry: create a trip with dates, start/end labels, distance, purpose, optional category, and optional vehicle.
  2. Tracking session: start an active mileage session, append points while moving, then complete the trip later.

Current shared Web code explicitly documents that foreground GPS tracking is available in the browser, while continuous background tracking remains app-only.

Plan access

CapabilityFreeCorePlusPremiumBusiness
View saved mileage overview, trip history, and vehicle listYesYesYesYesYes
Add, edit, or delete mileage tripsNoNoYesYesYes
Manage mileage vehiclesNoNoYesYesYes
Foreground/background GPS trackingNoNoYesYesYes
Place search, reverse geocoding, and route calculationNoNoYesYesYes

Mileage access is evaluated for the active ledger. If a ledger owner shares a higher-tier entitlement with the ledger and your personal plan is lower, Stareceipt uses the higher eligible entitlement for that ledger.

Maps providers and cost controls

Stareceipt uses platform-appropriate maps services for mileage. Current iOS app builds use Apple MapKit for visible mileage maps, place search, reverse geocoding, and route calculation before falling back to server-side providers where needed. Android keeps Google Maps Android SDK for visible maps. Server-side mileage maps calls are entitlement-gated, use short-lived provider caching where allowed, and avoid real-time traffic routing for reimbursement distance estimates.

Saved trip labels, distances, route points, purpose, reimbursement amount, and currency are Stareceipt records. Provider responses used to resolve addresses or routes are not treated as a permanent cross-user maps database.

What a mileage trip stores

Shared mileage APIs and UI models include fields such as:

FieldNotes
Trip dateThe business date of the trip
Start / end labelsHuman-readable place labels
DistanceStored in meters internally and rendered by client
PurposeShared clients use explicit purpose values such as business, commute, and personal
VehicleOptional vehicle association
Category / notesOptional metadata
Reimbursement amountStored separately from raw distance
Currency codeReturned with overview and trip responses
Rate region codeUsed by the mileage quote / reimbursement logic

Reimbursement logic

Shared mileage services expose quote and reimbursement fields driven by rate_region_code, tax_year, distance, and currency. This page does not hardcode CRA, IRS, or custom rates because the actual applicable rate configuration depends on the deployment and current backend data.

Viewing mileage

Current shared clients expose mileage-specific overview data such as:

  • total distance,
  • business / personal / other distance splits,
  • estimated reimbursement,
  • trip history,
  • vehicle lists.

For Free and Core accounts, these views are read-only and do not initialize map widgets. Text fields such as saved labels, distance, purpose, reimbursement amount, and currency remain visible for historical records.

Mileage can also appear in report items alongside regular receipt-based reporting flows.

Tips

  • Log trips on the same day so labels, purpose, and route context stay accurate.
  • If you rely on reimbursement calculations, verify the current rate region and currency shown by your deployment.
  • Upgrade to Plus or higher before using GPS tracking, route calculation, or place search.
  • Prefer the mobile app when you need continuous tracking behavior beyond the browser foreground session.

RECEIPT