[Due for payment 2026-01-30] [$250] Report-'it's not here' page appears when open scan expense in ND after unreport in OD

[nlemma]

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: v9.2.90-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: #76701
Email or phone of affected tester (no customers): ndk.2303+171@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Critical User Impact
Device used: Windows 11 Home/Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Log in to the same account on OD and ND.
• Account has a workspace.
• The Individual WS is set as the default on OD.

1. Go to staging.new.expensify.com
2. Go to Reports > Expenses.
3. Go to OD with the same account.
4. In OD Create a reported scan expense.
5. Go back to ND tab and wait for the scan expense to show up.
6. While the receipt is still scanning, go back to OD and unreported the scan expense.
7. Go to ND, in Reports > Expenses page, click on the scan expense

Expected Result:

Scan expense details page is opened

Actual Result:

'It's not here' page is opened

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7040120_1767260451433.not_here_page_when_open_scan_report_in_Report_page.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022008261433800129740
• Upwork Job ID: 2008261433800129740
• Last Price Increase: 2026-01-05
• Automatic offers:
• linhvovan29546 | Reviewer | 110105206

Issue Owner

Current Issue Owner: @linhvovan29546

[melvin-bot]

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

[samranahm]

Proposal

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

Report-'it's not here' page appears when open scan expense in ND after un-report in OD

What is the root cause of that problem?

When a transaction is unreported in Old Dot, the transaction's reportID is updated to CONST.REPORT.UNREPORTED_REPORT_ID 0 . The shouldShowNotFoundPage logic in TransactionReceiptModalContent.tsx is checking if moneyRequestReportID !== transaction?.reportID, which became true for unreported transactions, incorrectly triggering the "not found" page.

App/src/pages/media/AttachmentModalScreen/routes/TransactionReceiptModalContent.tsx

Lines 166 to 168 in 634b5ce

	const shouldShowNotFoundPage =
	isTrackExpenseReportValue || isDraftTransaction || transaction?.reportID === CONST.REPORT.SPLIT_REPORT_ID || readonly ? !transaction : moneyRequestReportID !== transaction?.reportID;

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

Updated the shouldShowNotFoundPage logic to explicitly allow unreported transactions by adding an additional condition

const shouldShowNotFoundPage =
    isTrackExpenseReportValue || isDraftTransaction || transaction?.reportID === CONST.REPORT.SPLIT_REPORT_ID || readonly
        ? !transaction
        : moneyRequestReportID !== transaction?.reportID && transaction?.reportID !== CONST.REPORT.UNREPORTED_REPORT_ID;

here

App/src/pages/media/AttachmentModalScreen/routes/TransactionReceiptModalContent.tsx

Lines 166 to 168 in 634b5ce

	const shouldShowNotFoundPage =
	isTrackExpenseReportValue || isDraftTransaction || transaction?.reportID === CONST.REPORT.SPLIT_REPORT_ID || readonly ? !transaction : moneyRequestReportID !== transaction?.reportID;

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[cosmicvulpes]

Proposal

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

When a scan expense is unreported in OldDot while still scanning, clicking on that expense in NewDot's Reports > Expenses page shows the "It's not here" page instead of opening the expense details.

What is the root cause of that problem?

For unreported expenses, item.reportID is "0" and item.report is undefined.

In createAndOpenSearchTransactionThread

App/src/libs/SearchUIUtils.ts

Lines 1590 to 1593 in 634b5ce

	const reportActionID = moneyRequestReportActionID ?? iouReportAction?.reportActionID;
	const transaction = !reportActionID ? getTransactionFromTransactionListItem(item) : undefined;
	const transactionViolations = !reportActionID ? item.violations : undefined;
	transactionThreadReport = createTransactionThreadReport(item.report, {reportActionID} as OnyxTypes.ReportAction, transaction, transactionViolations);

Two issues:

1. transaction is only passed when !reportActionID - but unreported transactions have a valid reportActionID, so transaction becomes undefined
2. Passing {reportActionID} loses originalMessage.type: "track" needed for track expense detection

In createTransactionThreadReport

App/src/libs/actions/Report.ts

Lines 1412 to 1415 in 634b5ce

	// Determine if we need selfDM report (for track expenses or unreported transactions)
	const isTrackExpense = !iouReport && ReportActionsUtils.isTrackExpenseAction(iouReportAction);
	const isUnreportedTransaction = transaction?.reportID === CONST.REPORT.UNREPORTED_REPORT_ID;
	const selfDMReportID = isTrackExpense || isUnreportedTransaction ? findSelfDMReportID() : undefined;

without this data:

Both checks fail → selfDMReportID is never fetched → function returns undefined → navigation goes to /search/view/undefined.

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

In createAndOpenSearchTransactionThread, pass transaction data when isFromSelfDM is true, and use the full item.reportAction:

const shouldPassTransactionData = !reportActionID || isFromSelfDM;
const transaction = shouldPassTransactionData ? getTransactionFromTransactionListItem(item) : undefined;
const reportActionToPass = iouReportAction ?? item.reportAction ?? ({reportActionID} as ReportAction);
transactionThreadReport = createTransactionThreadReport(item.report, reportActionToPass, transaction, ...);

This ensures createTransactionThreadReport can detect unreported/track expenses and create the thread in self DM.

What alternative solutions did you explore? (Optional)

N/A

Screen.Recording.2026-01-02.at.1.30.35.PM.mp4

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @linhvovan29546 (External)

[linhvovan29546]

@cosmicvulpes's proposal LGTM!

🎀 👀 🎀 C+ reviewed