Missing Tag, Tax, Tax amount, Billable and Reimbursable on confirm page when opened from FAB

[jponikarchuk]

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

Action Performed:

Precondition:

• Run Onyx.merge('betas', ['newManualExpenseFlow']); in console.
• Enable Rules, Tags and Taxes in workspace settings.
• Set Billable default to Billable.
• Create a tag in Tags settings.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Click + > Create expense > Manual.
   → Tag, Tax, Tax amount, Billable and Reimbursable fields are shown on confirm page.
4. Close the RHP.
5. Open FAB > Create expense > Manual.

Expected Result:

Tag, Tax, Tax amount, Billable and Reimbursable fields will be shown on confirm page when opened from FAB.

Actual Result:

Tag, Tax, Tax amount, Billable and Reimbursable fields are missing on confirm page when opened from FAB.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #87920

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #87920 - "Feat: Manual expense flow UI refactor - r3" by @ChavdaSachin (High confidence)
Related Issues: #82586 (original issue this PR was fixing)

Recommendation: REVERT

PR #87920 introduced a regression where Tag, Tax, Tax amount, Billable, and Reimbursable fields are missing from the confirmation page when creating a manual expense from the FAB (global create), while they appear correctly when creating from workspace chat. Reverting this PR is the most straightforward fix since the bug is confined to this PR's changes.

Assigned: @ChavdaSachin (PR author), @ShridharGoel (approving reviewer), @puneetlath (approving reviewer) from highest-confidence causing PR only
Labels: No label changes needed — DeployBlockerCash is correctly applied as this is a frontend App bug.

Detailed Analysis

Evidence

• The melvin-bot comment on this issue directly flags PR Feat: Manual expense flow UI refactor - r3 #87920 as the likely cause.
• PR Feat: Manual expense flow UI refactor - r3 #87920 is listed in the StagingDeployCash checklist for version 9.3.74-1 and was merged on 2026-05-13, aligning with the bug appearing in version 9.3.74-0.
• The bug is staging-only and described as a new feature (Reproducible in production?: N/A - new feature), confirming the regression was introduced in this staging cycle.
• The issue is scoped to the newManualExpenseFlow beta, which is the exact feature this PR implements.

Verification

• The affected files are src/pages/iou/request/step/IOURequestStepConfirmation.tsx and src/components/MoneyRequestConfirmationListFooter/fieldGroups/TransactionDetailsFields.tsx, both of which are directly modified by PR Feat: Manual expense flow UI refactor - r3 #87920.
• The PR adds a new defaultParticipants memo in IOURequestStepConfirmation.tsx that attempts to resolve participants for the global-create (FAB) flow using transaction?.reportID. When opening from FAB, the transaction has no reportID set initially, so defaultParticipants returns an empty array.
• policyExpenseChatPolicyID is derived from transaction?.participants, defaultParticipants, and report. When both transaction?.participants and defaultParticipants are empty (as happens in the FAB flow before the user selects a participant), policyExpenseChatPolicyID is undefined.
• Without a valid policyExpenseChatPolicyID, the policy prop used in MoneyRequestConfirmationList is null/undefined, causing the field visibility logic to hide Tag, Tax, Billable, and Reimbursable fields.
• In contrast, when opening from workspace chat (+ button), the reportID is available on the transaction from the start (the workspace is the source report), so defaultParticipants resolves correctly and the policy fields appear.

Root Cause

PR #87920 changed how participants and the effective policy are determined on the confirmation page. The new defaultParticipants memo early-returns an empty array if transaction?.reportID is falsy, which is the case in the FAB/global-create flow before the user selects a participant. This leaves policyExpenseChatPolicyID as undefined, so the policy Onyx entry is never loaded, and all policy-dependent fields (Tag, Tax, Tax amount, Billable, Reimbursable) are hidden. The old code read policyExpenseChatPolicyID directly from the participants prop passed in from the parent, which was correctly populated for the workspace-chat case and was not expected to be empty for the FAB case.