[Due for payment 2026-04-03] [$250] Expense - Confirm page shows Amount field with 0.00 amount when receipt is scanning

[mitarachim]

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.3.7-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #76595
Email or phone of affected tester (no customers): jsiodjosjdnisojso@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Go offline.
4. Create a scan expense.
5. Click Submit it to someone.
6. Enter merchant > Next.

Expected Result:

Confirm page will not show Amount field because receipt is scanning.

Actual Result:

Confirm page shows Amount field with 0.00 amount when receipt is scanning.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7055992_1769122262790.6.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022014521192763163659
• Upwork Job ID: 2014521192763163659
• Last Price Increase: 2026-01-30

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Triggered auto assignment to @kadiealexander (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.

[MobileMage]

Proposal

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

When creating a scanned expense offline, the amount field incorrectly displays "0.00" on the confirmation page instead of being hidden. The amount field should remain hidden while the receipt is being processed and only become visible once the scan completes with a value.

What is the root cause of that problem?

The issue is in the isScanRequest function in src/libs/TransactionUtils/index.ts. It uses lodashHas(transaction, 'iouRequestType') to check if the property exists, but this returns true even when iouRequestType is explicitly set to undefined.

When buildOptimisticTransactionAndCreateDraft in src/libs/actions/TransactionEdit.ts creates a new transaction, if initialTransaction is missing iouRequestType, the destructured value becomes undefined and the new transaction is created with iouRequestType: undefined.

Then in isScanRequest:

1. lodashHas returns true (property exists)
2. undefined === CONST.IOU.REQUEST_TYPE.SCAN is false
3. The function returns false instead of falling through to the receipt-based detection logic

This causes getRequestType to return MANUAL instead of SCAN, making shouldShowSmartScanFields evaluate to true in IOURequestStepConfirmation.tsx, which incorrectly shows the amount field.

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

Modify the isScanRequest function to check if iouRequestType is defined (not just if the property exists) by changing:

lodashHas(transaction, 'iouRequestType') to transaction?.iouRequestType !== undefined

This ensures that when iouRequestType is undefined, the function falls through to the receipt-based detection logic (!!transaction?.receipt?.source && transaction?.amount === 0) which correctly identifies scan requests.

What alternative solutions did you explore? (Optional)

[kadiealexander]

Android <> iOS swap

[jliexpensify]

This is a bug, when you go offline, we should say scanning:

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022014521192763163659