Pull Trip Date, Fare Total, and Route from Any DiDi Trip Screenshot
Most tools designed for Western rideshare receipts expect English labels at fixed pixel positions. DiDi screenshots use Chinese field labels and a fare structure that varies by city and service tier. Semantic AI reads every field by what its label means, not where it sits on the screen.
5-10s per screenshot · Up to 99% accuracy on printed text
Four Fields from Any DiDi Receipt
A DiDi receipt carries four data points for expense tracking. With Custom Column Extraction, you name columns in English, and the AI reads each Chinese label and captures the value, regardless of fare tier or city.
Appears at the top in YYYY-MM-DD format. The AI reads the Chinese label 行程日期 and captures the adjacent value.
The final amount after base fare, distance, time, dynamic pricing, and tolls. Define separate columns for subtotal and charged total.
Pickup and dropoff addresses above the Chinese map. Define a combined Route column or separate Pickup (起点) and Dropoff (终点) columns.
Total kilometers and trip duration below the route map. Also shown in the fare breakdown as per-km and per-minute charges.
Chinese Labels, Multi-Tier Pricing, and Dynamic Surcharges: DiDi Defies Template-Based Extraction
DiDi operates across 400+ cities in China and 14 other countries, with fare rules that vary by market. Its pricing combines base fare (起步价), per-km and per-minute rates, and dynamic pricing (动态调价) during peak demand. Template tools designed for English-language receipts have no logic for this layered structure.
Chinese Labels at Unpredictable Positions
DiDi's receipt uses Chinese labels such as 行程日期, 总金额, 起点, and 终点. Zonal OCR that looks for "Date" or "Total" at fixed coordinates finds nothing. On Reddit, a DiDi traveler asked "how exactly does the fare work?". The data is on the screen, but without label-aware reading, it stays stuck in the image.
Dynamic Pricing Changes Every Receipt
DiDi applies a dynamic pricing multiplier when demand outpaces supply, pushing the fare above the standard rate. The receipt shows the surge-adjusted total alongside the base fare breakdown. A template tool trained on standard fares reads the wrong value: the siloed subtotal instead of the total charged.
No Bulk CSV: Screenshots Are the Universal Record
DiDi offers no bulk trip data export. Business travelers reimbursing DiDi rides across China rely on screenshots as their only complete record. Once a trip scrolls off the in-app history, no other copy exists.
Semantic Reading Handles Any Language
Define Trip Date, Fare Total, Route, and Distance. The AI reads Chinese labels the same way it reads English ones, recognizing the relationship between a label and its value. 行程日期 and "Trip Date" both populate the same column correctly. No translation mapping or per-market configuration required.
One Column Set for All Service Tiers
Add a Dynamic Pricing Surcharge column alongside your standard fields. The AI reads the multiplier line when present and leaves it blank for non-surge trips. Upload Express (快车), Premier (专车), and Taxi (出租车) receipts together, and each screenshot becomes one row in the same spreadsheet with the same column structure.
Screenshots Work When App Exports Don't
For quarterly or annual expense reports, DiDi screenshots are the only complete record. The tool reads any clear screenshot the same way, whether from yesterday or six months ago, and extracts all fields into a spreadsheet row ready for Excel, CSV, or Google Sheets export.
From One DiDi Screenshot to a Spreadsheet Row
If you're logging DiDi trips for expense reimbursement or tracking travel costs across Chinese cities, here's how it works.
Upload the Screenshot
Upload the DiDi trip receipt, captured from the app's trip details, a forwarded WeChat image, or a screenshot from weeks ago. The receipt shows the route on a Chinese map, the fare breakdown with base + distance + time + dynamic pricing, and the total in CNY or local currency. JPG, PNG, or WebP.
Define Columns in English
Type Trip Date, Fare Total, Route, Distance, and optionally Dynamic Pricing Surcharge for surge-priced rides. The AI identifies each Chinese label, such as 行程日期, 总金额, 起点, 终点, and 里程, and maps them to your column names by meaning. No translation step needed.
Export the Row
The output lands as a spreadsheet row with date, fare total, route, distance, and any dynamic surcharge. Export to Excel or CSV, or push into Google Sheets via the add-on. Batch a month's receipts across multiple cities, and each trip becomes a row in the same file, roughly 18x faster than typing them by hand (about 3 minutes manual vs ~10 seconds here).
When DiDi Screenshot Extraction Works Best, and When to Be Cautious
When It Works Best
Clear DiDi app screenshots. High-contrast Chinese text gives the visual model clean input, equally reliable for Express, Premier, and Taxi receipts.
Batch processing across service tiers and cities. Upload Express, Premier, and Taxi receipts together, and the AI adapts to each layout independently. Beijing and Shenzhen receipts in the same batch each produce correct rows.
Recovering older trips for expense reports. Screenshots preserve ride data after the in-app history window expires, making them useful for quarterly or annual reconciliation.
When to Be Cautious
Compressed screenshots from messaging apps. WeChat or WhatsApp compression reduces resolution, so spot-check the dynamic pricing multiplier and toll charges from forwarded copies.
The route map is visual-only. The Chinese map graphic below the addresses is a rendered image, so only the text addresses printed above it are captured.
The tool extracts visible data, not derived metrics. Cost per kilometer, monthly totals by city, and tax deductions need your own post-processing of the raw per-trip fields.
Frequently Asked Questions
Can I extract data from DiDi trip screenshots that show dynamic pricing adjustments?
Yes. When DiDi's dynamic pricing multiplier is active on a trip, the receipt shows both the base fare and the adjusted total. Define Fare Subtotal for the pre-multiplier amount, Fare Total (总金额) for the final billed amount, and Dynamic Pricing Surcharge to capture the multiplier line. The AI reads each value by its Chinese label, so surge adjustments appear in their own column rather than silently inflating the base fare.
How does the AI handle Chinese-language field labels on DiDi screenshots?
DiDi's receipt screen uses Chinese labels such as 行程日期 (Trip Date), 总金额 (Fare Total), 起点 (Pickup), 终点 (Dropoff), and 里程 (Distance). The visual language model reads these by recognizing their visual text content and semantic relationship to adjacent values. You define column names in English, and the AI maps the Chinese label to your column based on what the label means, with no translation lookup or configuration needed.
Does this work with DiDi Express, Premier, and Taxi receipts, or only one service tier?
All three, in the same batch. Express (快车), Premier (专车), and Taxi (出租车) receipts share the same core fields such as Trip Date, Fare Total, Route, and Distance, even though their fare structures differ. Express uses a simple per-km rate, Premier adds a higher base fare and newer vehicles, and Taxi receipts show a metered estimate vs the actual fare. Define your columns once and the AI adapts to each tier's layout independently.
Can I batch DiDi trip screenshots with Uber and Lyft receipts in the same export?
Yes. Define one set of column names covering Trip Date, Fare Total, Route, and Distance. The AI processes DiDi, Uber, and Lyft receipts using the same definitions. Add a Platform column and the AI populates it from each screenshot's branding. See the rideshare screenshots overview for the full cross-platform setup.
Can I use this for DiDi trips taken outside China?
Yes. DiDi operates in 14 countries outside China, including Brazil, Mexico, Chile, Australia, and Japan. Receipts from international markets use local currency symbols and local-language labels, but the visual model reads field labels by meaning, so a Portuguese label for "Total" and a Chinese 总金额 both populate the same column. Define your column set in English and it works across any DiDi market without adjustments.
Related reading for rideshare trip tracking and expense management: Consolidating payment screenshots from Venmo, PayPal, Zelle, and Cash App into a single income log · How to batch odometer photos from Uber and Lyft shifts into Google Sheets for IRS-compliant mileage logs · Tax season mileage log guide for rideshare drivers
Compare with Lyft, a simpler US-only fare model without dynamic surcharges and multi-tier pricing
Back to rideshare & delivery screenshots overview, where you'll find all supported platforms