[Awaiting payment 2026-02-04][$250] Multi scan - Receipts show different workspace on confirm page, but created in same workspace

[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.2.60-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exp #63434 and #73634
Email or phone of affected tester (no customers): nisdjonisjdososjojo@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

1. Go to staging.new.expensify.com
2. Create two workspaces.
3. Create an empty report in each workspace chat.
4. Open FAB > Create expense > Scan.
5. Upload a receipt.
6. On confirm page, click RHP back button.
7. Upload another receipt.
8. On confirm page, click Report field.
9. Select the other report from another workspace.
10. Click navigation arrow on confirm page.
    → To field on the first and second receipt show different workspace.
11. Click Create expense.

Expected Result:

In Step 11, both receipts should be submitted to different workspace as shown on the confirm page.

OR

In Step 10, To field on both receipts should be the same.

Actual Result:

In Step 10, To field on the first and second receipt show different workspace.

In Step 11, both receipts are submitted to the same workspace when confirm page in Step 10 shows different workspace for both receipts.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7008086_1763544072120.22.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021994470642006384853
• Upwork Job ID: 1994470642006384853
• Last Price Increase: 2025-12-05
• Automatic offers:
• situchan | Contributor | 109740562

Issue Owner

Current Issue Owner: @greg-schroeder

[melvin-bot]

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

[dmkt9]

Proposal

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

In Step 10, To field on the first and second receipt show different workspace.

In Step 11, both receipts are submitted to the same workspace when confirm page in Step 10 shows different workspace for both receipts.

What is the root cause of that problem?

1. When the "Report" field is changed, we only update the participants of the transaction that was modified.
   

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

   Lines 88 to 95 in a7c2526

   	setTransactionReport(
   	transaction.transactionID,
   	{
   	reportID: item.value,
   	participants,
   	},
   	true,
   	);

   
   This differs from when we change the "To" field (receipt), where the participants of all transactions are updated accordingly.
   

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

   Lines 227 to 234 in a7c2526

   	if (transactions.length > 0) {
   	for (const transaction of transactions) {
   	setMoneyRequestParticipants(transaction.transactionID, val);
   	}
   	} else {
   	// Fallback to using initialTransactionID directly when transaction object isn't loaded yet
   	setMoneyRequestParticipants(initialTransactionID, val);
   	}

2. When clicking "Confirm" to create a money request, we rely solely on the participant, report, and policy values of the currently focused transaction.
   

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

   Lines 539 to 544 in a7c2526

   	const participant = selectedParticipants.at(0);
   	if (!participant) {
   	return;
   	}
   	const {parentChatReport, policyParams} = getMoneyRequestContextForParticipant(participant, report);

   
   As a result, even if the "To" field appears different across transactions, they will all be submitted to the same report as the focused transaction.

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

TEST BRANCH

Update all transactions when the "Report" field is changed, similar to how we currently handle it in IOURequestStepParticipants.

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

Line 64 in a7c2526

const [optimisticTransactions] = useOnyx(ONYXKEYS.COLLECTION.TRANSACTION_DRAFT, {
    selector: transactionDraftValuesSelector,
    canBeMissing: true,
});
const transactions = useMemo(() => {
    const allTransactions = optimisticTransactions && optimisticTransactions.length > 1 ? optimisticTransactions : [transaction];
    return allTransactions.filter((value): value is Transaction => !!value);
}, [transaction, optimisticTransactions]);

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

Lines 88 to 95 in a7c2526

	setTransactionReport(
	transaction.transactionID,
	{
	reportID: item.value,
	participants,
	},
	true,
	);

transactions.forEach((transactionItem) =>
    setTransactionReport(
        transactionItem.transactionID,
        {
            reportID: item.value,
            participants,
        },
        true,
    ),
);

2025-11-20.11-41-17.mp4

What alternative solutions did you explore? (Optional)

If the expected behavior is to submit to different reports, then we need to retrieve the individual report, policy, and participant values for each transaction inside the requestMoney function of IOURequestStepConfirmation.
ALTERNATIVE TEST BRANCH

[melvin-bot]

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

[melvin-bot]

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

[situchan]

Taking over as C+
https://expensify.slack.com/archives/C02NK2DQWUX/p1764592369997389?thread_ts=1764157955.604609&cid=C02NK2DQWUX