[due for payment 2026-02-18] [$250] Per diem-Destination field on confirm page is blank when at least two workspaces have per diem

[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.8-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: #79939
Email or phone of affected tester (no customers): sdjiondjosjsojos11@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:

Precondition:

• Create two workspaces - A and B.
• Import per diem rates to both workspaces (can use the same per diem rates).

1. Go to staging.new.expensify.com
2. Open FAB > Create expense > Per diem.
3. Select Workspace A.
4. Select any data and proceed to confirm page.

Expected Result:

On confirm page, Destination field should be populated with the selected destination.

Actual Result:

On confirm page, Destination field is blank.

This issue only happens when there are at least two workspaces with per diem rates.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7056802_1769212595670.7.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022014955813299882706
• Upwork Job ID: 2014955813299882706
• Last Price Increase: 2026-01-31

[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.

[paulnjs]

Proposal

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

On confirm page, Destination field is blank.

What is the root cause of that problem?

The getIOURequestPolicyID function only looked for participants with isSender: true (used for invoices) to extract the policyID:

App/src/libs/actions/IOU/index.ts

Lines 11365 to 11368 in 6c2f68d

	function getIOURequestPolicyID(transaction: OnyxEntry<OnyxTypes.Transaction>, report: OnyxEntry<OnyxTypes.Report>): string | undefined {
	// Workspace sender will exist for invoices
	const workspaceSender = transaction?.participants?.find((participant) => participant.isSender);
	return workspaceSender?.policyID ?? report?.policyID;

• When creating a per diem expense, user selects Workspace A in IOURequestStepPerDiemWorkspace. The transaction's participant is set with isPolicyExpenseChat: true and policyID: workspaceA.id (but NOT isSender: true)
• User selects a destination from Workspace A's per diem rates
• On the confirmation page, getIOURequestPolicyID is called
• Since isSender is NOT set, workspaceSender is undefined
• The function falls back to report?.policyID which may be Workspace B's ID
• The confirmation page uses Workspace B's policy to look up the destination
• Since the destination (customUnitRateID) was selected from Workspace A, it doesn't exist in Workspace B's rates
  => Result: Destination field is blank

This only happens when there are 2+ workspaces with per diem rates because the fallback report?.policyID could be from a different workspace.

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

Update getIOURequestPolicyID to also check for isPolicyExpenseChat participants:

function getIOURequestPolicyID(transaction, report) {
    // Workspace sender will exist for invoices
    const workspaceSender = transaction?.participants?.find((participant) => participant.isSender);
    if (workspaceSender?.policyID) {
        return workspaceSender.policyID;
    }

    // For per diem and other policy expense chat transactions, use the policyID from the participant
    const policyExpenseChatParticipant = transaction?.participants?.find((participant) => participant.isPolicyExpenseChat);
    if (policyExpenseChatParticipant?.policyID) {
        return policyExpenseChatParticipant.policyID;
    }

    return report?.policyID;
}

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.

[melvin-bot]

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

[melvin-bot]

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

[joekaufmanexpensify]

Pending proposal review from @Pujan92

[cretadn22]

🚨 Edited by proposal-police: This proposal was edited at 2026-01-28 12:03:19 UTC.

Proposal

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

When creating a per diem expense across multiple workspaces that have per diem rates enabled, the Destination field appears blank on the confirmation page despite the user having selected a valid destination.

What is the root cause of that problem?

The isSender flag is not being set to true when selecting a participant for a per diem request.

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

Lines 33 to 41 in 531bea2

	setMoneyRequestParticipants(transactionID, [
	{
	selected: true,
	accountID: 0,
	isPolicyExpenseChat: true,
	reportID: policyExpenseReportID,
	policyID: policy?.id,
	},
	]);

In getIOURequestPolicyID, we filter participants based on the isSender flag. However, since this flag is never set in IOURequestStepPerDiemWorkspace, the function doesn't work as expected

App/src/libs/actions/IOU/index.ts

Lines 11458 to 11462 in 531bea2

	function getIOURequestPolicyID(transaction: OnyxEntry<OnyxTypes.Transaction>, report: OnyxEntry<OnyxTypes.Report>): string | undefined {
	// Workspace sender will exist for invoices
	const workspaceSender = transaction?.participants?.find((participant) => participant.isSender);
	return workspaceSender?.policyID ?? report?.policyID;
	}

As a result, the confirmation page cannot load the policy’s per diem rates. Because the selected customUnitRateID does not exist in the resolved policy rates, the destination name cannot be resolved and is displayed as blank.

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

Set isSender to true when setting the participant for a per diem request.

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

Lines 33 to 41 in 531bea2

	setMoneyRequestParticipants(transactionID, [
	{
	selected: true,
	accountID: 0,
	isPolicyExpenseChat: true,
	reportID: policyExpenseReportID,
	policyID: policy?.id,
	},
	]);

What alternative solutions did you explore? (Optional)

N/A