A rideshare electronic receipt may be one of the earliest dated records available after a trip. It can identify the completed service, locations, time and distance totals, and fee information shown to the customer. Preserve it promptly, but keep its role narrow: the receipt is a customer transaction record, not a complete history of the driver’s application status or every event surrounding a crash.

A rideshare receipt describes the completed service and fee fields shown in that record; it is not a complete app-status history, insurance determination, vehicle-location log, crash reconstruction, or fault finding.

Preserve the receipt in each available form

  • Original email or app record, downloadable file, print view, screenshot sequence, and any later corrected or reissued version
  • Sender, recipient account, trip or receipt identifier, message headers when available, displayed date and time, timezone, currency, and language
  • Full page or message before cropping, including links, map, route image, driver or vehicle summary, support reference, and footer
  • Export date, device, app or browser version, file name, and method used to save the record, with annotations stored only on a copy

Read the fields North Carolina law identifies

North Carolina General Statutes Chapter 20, Article 10A governs transportation network companies. Section 20-280.2 states that the company must send the customer an electronic receipt that includes the locations where the service started and ended, the total time and distance of the service, and an itemization and calculation of the total fee paid.

  • Start and end locations copied exactly as displayed, without converting a place label into a precise pickup or collision coordinate
  • Total time and distance recorded as receipt totals, with any displayed route, stop, wait, toll, tip, tax, surcharge, discount, or adjustment kept as a separate field
  • Fee line, amount, calculation description, currency, payment method label, refund, correction, and later adjustment preserved by version
  • Blank, truncated, estimated, rounded, or inconsistent field marked for follow-up rather than silently filled from memory

Separate trip-service timing from other app states

Article 10A defines TNC service as beginning when a driver accepts a ride request and ending at the later of completing the app transaction or all passengers exiting and completing unloading. A receipt may show totals or customer-facing timestamps without showing every underlying accept, arrive, wait, start, stop, cancel, logon, or logoff event. Keep those other app events in a separate timeline.

Do not treat a route image as raw location data

  • Record whether the receipt displays a stylized map, route line, address, neighborhood, point label, time, distance, or no route information
  • Preserve the original image dimensions and surrounding text; do not infer sampling rate, device accuracy, or exact vehicle path from appearance alone
  • Compare a displayed route with crash reports, photographs, messages, phone records, and exported trip data only after identifying each source and time basis
  • List conflicting locations or times as unresolved; a visual map and a system event may be generated from different data or processes

Keep receipt, identity, and insurance records distinct

The same Article requires customer-facing driver and vehicle information after a request is accepted, addresses records retained by the company, and sets insurance and information-exchange requirements. Those provisions concern different records. A receipt does not by itself establish which vehicle or driver was involved, whether the driver was logged on outside the trip, which policy responds, or what any coverage term means.

  • Driver photograph, name or identifier, vehicle description, and license plate compared with the app display and independent event records
  • Trip receipt kept separate from the crash report, insurer claim record, policy, coverage letter, app-status history, and support correspondence
  • Precise logon, logoff, and service times requested or exchanged under the applicable process rather than inferred from the receipt total
  • Questions about account, vehicle, driver, trip, policy, or location assigned to the source capable of answering that question

The related guide to preserving rideshare trip and app records after a North Carolina crash covers the broader app record, support communications, trip identifiers, exports, and status events. This page is limited to interpreting the electronic receipt.

Rosensteel Fleishman Car Accident & Injury Lawyers provides general record-review information for people who may later speak with a Charlotte rideshare accident lawyer. Identity, app status, insurance, preservation, fault, and legal consequences depend on the complete source set and individual review.

Source