Skip to content

Conversation

@TaduJR
Copy link
Contributor

@TaduJR TaduJR commented Jan 20, 2026

Explanation of Change

In Expensify Classic, users with US personal bank accounts can update their name, address, and phone number when this info is missing from the bank account. This is required for global reimbursement payments (e.g., GBP → USD) to succeed. NewDot was missing this flow entirely.

What this PR adds:

  • Detection: isPersonalBankAccountMissingInfo() checks bankAccount.additionalData for missing firstName, lastName, address fields, or companyPhone on US personal bank accounts in OPEN state

  • Visual indicator: Shows "Action required" badge with brick road indicator on affected bank account rows in Wallet (matching the existing partially-setup pattern). Three dots menu still works independently for
    deletion

  • Update flow: Tapping the row navigates to a new UpdatePersonalBankAccountPage that reuses the LegalNameStep, AddressStep, and PhoneNumberStep substeps from PR Change for personal bank account setup #75179. Steps with info already in the user's profile are automatically skipped

  • Confirmation & success: Custom UpdatePersonalInfoConfirmation shows a review screen (without bank routing/account numbers). On submit, a success screen with Fireworks animation confirms the update

    • API action: updatePersonalBankAccountInfo calls UpdatePersonalBankAccountInfo and optimistically updates BANK_ACCOUNT_LIST additionalData for all affected accounts + PRIVATE_PERSONAL_DETAILS. Form draft is
      preserved on failure so the user can retry
  • Translations: All 5 new keys added to all 10 language files

Fixed Issues

$ #76053
PROPOSAL: #76053 (comment)

Tests

Prerequisite: User with a US personal bank account missing personal info (name, address, or phone)

  1. Navigate to Settings > Wallet
  2. Verify the affected bank account row shows an "Action required" badge with a red brick road indicator
  3. Tap the bank account row — verify it navigates to the "Update bank account" flow (not the three dots menu)
  4. Tap the three dots menu on the same row — verify the deletion popover still opens separately
  5. Complete the update flow:
    • If name is missing: verify the "What's your legal name?" step appears
    • If address is missing: verify the "What is your address?" step appears
    • If phone is missing: verify the "What's your phone number?" step appears
    • Steps with info already in your profile should be automatically skipped
  6. On the confirmation screen, verify name, address, and phone are displayed correctly
  7. Tap an item to edit — verify it navigates back to the correct step in edit mode
  8. Tap Confirm — verify loading state appears
  9. On success: verify the "Bank account updated!" screen appears with Fireworks animation and a "Continue" button
  10. Tap Continue — verify it navigates back to Wallet
  11. Verify the "Action required" badge is gone from the bank account row
  12. If the user has multiple personal bank accounts missing info, verify completing the flow for one removes the badge from all of them
  • Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
Same as tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@TaduJR TaduJR requested review from a team as code owners January 20, 2026 18:46
@melvin-bot melvin-bot bot requested a review from dukenv0307 January 20, 2026 18:46
@melvin-bot
Copy link

melvin-bot bot commented Jan 20, 2026

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@melvin-bot melvin-bot bot requested review from trjExpensify and removed request for a team and trjExpensify January 20, 2026 18:46
@melvin-bot
Copy link

melvin-bot bot commented Jan 20, 2026

@dukenv0307 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot bot removed the request for review from a team January 20, 2026 18:46
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 04a4154be9

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@codecov
Copy link

codecov bot commented Jan 20, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 87.39% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
src/libs/BankAccountUtils.ts 100.00% <100.00%> (+25.00%) ⬆️
src/libs/Navigation/linkingConfig/config.ts 75.00% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 7.64% <0.00%> (-0.02%) ⬇️
src/pages/settings/Wallet/PaymentMethodList.tsx 0.00% <0.00%> (ø)
src/pages/settings/Wallet/WalletPage/index.tsx 0.00% <0.00%> (ø)
src/ROUTES.ts 12.82% <0.00%> (-0.05%) ⬇️
...rc/pages/settings/Wallet/PaymentMethodListItem.tsx 0.00% <0.00%> (ø)
... and 3 more
... and 50 files with indirect coverage changes

@TaduJR TaduJR marked this pull request as draft January 20, 2026 19:08
* This is used to show "Action required" badge for existing accounts that need updates
* to enable global reimbursement payments.
*/
function isPersonalBankAccountMissingInfo(accountData: AccountData | undefined, privatePersonalDetails: OnyxEntry<OnyxTypes.PrivatePersonalDetails>): boolean {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checking privatePersonalDetails here is incorrect. OldDot shows the update button when it's missing fields on the bankAccount additionalData specifically. See
https://github.com/Expensify/Web-Expensify/blob/main/site/class/bankAccount.js#L240

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chuckdries Thanks for the feedback! I don't have access to Web-Expensify repo.

In NewDot, BankAccountAdditionalData doesn't have personal info fields (legalFirstName, addressStreet, phoneNumber) - these only exist on PrivatePersonalDetails.

From the issue discussion, @joekaufmanexpensify mentioned that "completing one account saves info to all (stored in Profile)" - which aligns with checking privatePersonalDetails.

Could you clarify:

  1. What specific fields does OldDot check on bankAccount.additionalData or share the source code for that section?
  2. Should we add these fields to BankAccountAdditionalData type, or is checking privatePersonalDetails the correct approach for NewDot?

Happy to adjust the implementation based on your guidance.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I forgot that repo is private, sorry about that! The BankAccountAdditionalData interface is incomplete. I'll look up what it should be and get back to you tomorrow :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, turns out there's actually a bunch of fields that can be on that object that I don't think are relevant. Here's a diff you can apply that'll add the relevant fields to BankAccount

diff --git a/src/types/onyx/BankAccount.ts b/src/types/onyx/BankAccount.ts
index 54581f3a071..bb807e7b663 100644
--- a/src/types/onyx/BankAccount.ts
+++ b/src/types/onyx/BankAccount.ts
@@ -38,6 +38,21 @@ type BankAccountAdditionalData = {
         /** Powerform files */
         achAuthorizationForm?: FileObject[];
     };
+
+    /** City of the business's address */
+    addressCity?: string;
+
+    /** State of the business's address */
+    addressState?: string;
+
+    /** Business's street address */
+    addressStreet?: string;
+
+    /** Zip code of the business's address */
+    addressZipCode?: string;
+
+    /** Phone number of the company */
+    companyPhone?: string;
 };
 
 /** Model of bank account */

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chuckdries can you please take a look at the comment above? Thanks

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay on this all, I will check tomorrow

Copy link
Contributor

@chuckdries chuckdries Feb 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @TaduJR, thanks again for your patience. I wanted to make sure I was right before I replied this time :)

  • the owner's name is stored in the firstName and lastName fields on the BankAccountAdditionalData object
  • the owner's personal phone number is stored in the companyPhone field
  • you're right about the comments being confusing, I was tripped up reading the existing code because we reuse this interface for personal and business bank accounts. We can just change the comments to be "State of the bank account owner's address", etc.

I just noticed that UpdatePersonalBankAccountInfo does not take a phone number parameter. I'll file a ticket to get that added

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @chuckdries! I've updated the code based on your feedback:

  • Added firstName and lastName to BankAccountAdditionalData type
  • Updated isPersonalBankAccountMissingInfo to check accountData.additionalData fields (firstName, lastName, addressStreet, addressCity, addressState, addressZipCode, companyPhone) instead of privatePersonalDetails

Let me know if you need anything else!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds great, thanks! The required changes to UpdatePersonalBankAccountInfo were just merged moments ago, they'll become available on staging in the next few days. I will ping you here when that happens 👍

@dukenv0307
Copy link
Contributor

@TaduJR Any update here?

@dukenv0307
Copy link
Contributor

kindly bump @TaduJR

@dukenv0307
Copy link
Contributor

Bump @TaduJR

@TaduJR
Copy link
Contributor Author

TaduJR commented Jan 27, 2026

Bump @TaduJR

Hi @dukenv0307

Already replied 3 days ago.

We are awaiting for clarifications on this #80020 (comment)

@dukenv0307
Copy link
Contributor

@TaduJR Ah I see now. Thank you

…-option-missing-for-Personal-Bank-Accounts-in-ND-compared-to-Classic
Add missing fields to BankAccountAdditionalData type:
- addressCity, addressState, addressStreet, addressZipCode
- companyPhone
…-option-missing-for-Personal-Bank-Accounts-in-ND-compared-to-Classic
…-option-missing-for-Personal-Bank-Accounts-in-ND-compared-to-Classic
…missing bank account info

Per reviewer feedback, isPersonalBankAccountMissingInfo now checks
accountData.additionalData fields (firstName, lastName, address, companyPhone)
instead of privatePersonalDetails, matching OldDot behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants