You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-04-14] Wallet - Action required is shown when legal name is already filled #86803
Version Number: 9.3.51-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:#80020 Email or phone of affected tester (no customers):snodijosdnjoijiosnj@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.2 / Chrome App Component: User Settings
Action Performed:
Go to staging.new.expensify.com
Go to Account > Wallet.
Click Add bank account.
Click Get reimbursed.
Select United States > Next.
Click Log into your bank.
Complete Plaid flow.
Select bank account, add legal name, address and phone, then click Confirm.
Click Continue.
Go to Account > Profile.
→ Legal name is filled in Private details section.
Go to Account > Wallet.
Click on the added personal account.
Expected Result:
No Action required will appear because Legal name is already filled in Private details section.
Actual Result:
Action required appears when Legal name is already filled in Private details section.
Clicking on the bank account opens Legal name page again.
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #80020 - "feat: Update option missing for Personal Bank Accounts in ND compared to Classic" by @TaduJR (High confidence) Related Issues: None
Recommendation: REVERT
PR #80020 should be reverted. The implementation has a logic flaw where isPersonalBankAccountMissingInfo() only checks the bank account's additionalData fields, but does not consider the user's privatePersonalDetails (Profile data).
Labels: No label changes needed - this is a Frontend bug, so DeployBlockerCash should remain.
Detailed Analysis
Evidence
The issue states that after completing the Plaid flow where legal name was filled (step 10 confirms "Legal name is filled in Private details section"), the bank account still shows "Action required" when it should not.
"Steps with info already in your profile should be automatically skipped"
"If the user has multiple personal bank accounts missing info, verify completing the flow for one removes the badge from all of them"
This indicates the system should check the user's profile data, not just individual bank account data.
Verification
File: src/libs/BankAccountUtils.ts (lines 60-78)
The isPersonalBankAccountMissingInfo() function only checks accountData.additionalData:
changed the title [-]Wallet - Action required is shown when legal name is already filled[/-][+][Due for payment 2026-04-14] Wallet - Action required is shown when legal name is already filled[/+]on Apr 7, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.52-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@chuckdries The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Mar 31, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #80020
melvin-bot commentedon Mar 31, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 31, 2026
👋 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:
OSBotify commentedon Mar 31, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #80020 - "feat: Update option missing for Personal Bank Accounts in ND compared to Classic" by @TaduJR (High confidence)
Related Issues: None
Recommendation: REVERT
PR #80020 should be reverted. The implementation has a logic flaw where
isPersonalBankAccountMissingInfo()only checks the bank account'sadditionalDatafields, but does not consider the user'sprivatePersonalDetails(Profile data).Labels: No label changes needed - this is a Frontend bug, so
DeployBlockerCashshould remain.Detailed Analysis
Evidence
The issue states that after completing the Plaid flow where legal name was filled (step 10 confirms "Legal name is filled in Private details section"), the bank account still shows "Action required" when it should not.
According to the test steps in PR #80020:
This indicates the system should check the user's profile data, not just individual bank account data.
Verification
File:
src/libs/BankAccountUtils.ts(lines 60-78)The
isPersonalBankAccountMissingInfo()function only checksaccountData.additionalData:Where
hasOwnerName,hasOwnerAddress, andhasOwnerPhonecheck fields like:additionalData?.firstNameandadditionalData?.lastNameadditionalData?.addressStreet,additionalData?.addressCity, etc.additionalData?.companyPhoneFile:
src/pages/settings/Wallet/UpdatePersonalBankAccountPage.tsx(lines 129-138)The update flow correctly falls back to
privatePersonalDetails:File:
src/pages/settings/Wallet/InternationalDepositAccount/PersonalInfo/utils/getSkippedStepsPersonalInfo.tsDuring bank account creation, steps are skipped if data exists in
privatePersonalDetails:Root Cause
When a user adds a personal bank account via Plaid:
privatePersonalDetails), the legal name step is skippedadditionalDatafields with this informationisPersonalBankAccountMissingInfo()runs, it only checksadditionalDataand finds it missingThe function should check
privatePersonalDetailsas a fallback, similar to how the update flow and creation flow already do.OSBotify commentedon Mar 31, 2026
Label Update: Removed
DeployBlockerlabel. This is a Frontend bug affecting the App deploy only, soDeployBlockerCashremains.2 remaining items
melvin-bot commentedon Apr 1, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
m-natarajan commentedon Apr 1, 2026
Not Repro, Windows 10 / chrome, v9.3.51-7
bandicam.2026-04-01.18-18-53-109.mp4
[-]Wallet - Action required is shown when legal name is already filled[/-][+][Due for payment 2026-04-14] Wallet - Action required is shown when legal name is already filled[/+]melvin-bot commentedon Apr 7, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 7, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.52-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-04-14. 🎊
melvin-bot commentedon Apr 7, 2026
@chuckdries The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
melvin-bot commentedon Apr 7, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)