Scan - Scanning fails for normal receipts without currency symbol

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.2.47-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #74455
Email or phone of affected tester (no customers): slottwo1a@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Launch the app
2. Tap FAB → Create Expense → Scan
3. Upload a distance receipt
4. Select Self DM as recipient and create the expense
5. Note: Scan detects local currency and shows amount successfully
6. Tap + icon → Create Expense → Scan
7. Upload a normal receipt without currency symbol (e.g., “Total: 150.00”)
8. Select Self DM as recipient and create the expense
9. Note: Scanning failed — amount not shown

Expected Result:

App should detect the numeric amount from normal receipts and automatically assign the correct currency based on location (same as distance receipts)

Actual Result:

Scanning fails for normal receipts without currency symbol — amount not extracted
Distance receipts are successfully detected and currency applied correctly

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6997704_1762577399586.Screenrecorder-2025-11-08-10-16-15-105.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @joekaufmanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[ShridharGoel]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Scanning fails for normal receipts without currency symbol

What is the root cause of that problem?

Every scan entry point builds a gpsPoint object with {lat, long} and the GPSPoint type itself only exposes those two fields. Because the API payload serializes this object as-is, SmartScan never receives a lng field, which means it cannot map the receipt to a country/currency. The same pattern is repeated in the confirmation step, the scan step (native and web), the share sheet etc.

App/src/pages/iou/request/step/IOURequestStepConfirmation.tsx

Lines 926 to 932 in 5dc4f0c

	if (userLocation) {
	trackExpense(selectedParticipants, {
	lat: userLocation.latitude,
	long: userLocation.longitude,
	});
	return;
	}

What changes do you think we should make in order to solve the problem?

1. Extend the shared GPSPoint type in src/libs/actions/IOU.ts so it contains both lng and a legacy optional long. This lets us keep backward compatibility with any server code that still reads long, while giving SmartScan the lng prop it expects.
2. Update every place that constructs a GPS point (scan step on web and native, confirmation step, share sheet) so we populate both keys. This is the only information SmartScan needs to infer the currency.
3. Keep the rest of the request payloads and flows unchanged; once the correct lng makes it into receiptGpsPoints, the backend can detect the amount/currency just like it already does for distance receipts.

Updated snippet for reference:

const gpsPoint = {
    lat: successData.coords.latitude,
    lng: successData.coords.longitude,
    long: successData.coords.longitude, // legacy field kept for safety
};

Pass lng from the calling code points.

Example from IOURequestStepScan:

(successData) => {
    const policyParams = {policy};
    const gpsPoint = {
        lat: successData.coords.latitude,
        lng: successData.coords.longitude,
        long: successData.coords.longitude,
    };
    createTransaction(files, participant, gpsPoint, policyParams, false, true);
},

[joekaufmanexpensify]

Hmm, I just tested this with a few different receipts with no currency and it worked fine for me. Closing as this doesn't appear to be consistently reproducible