Skip to content

Bank account - Copy of ID is missing in the beneficial owner flow #75969

Closed

Description

@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: v9.2.63-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: #75527
Email or phone of affected tester (no customers): applausetester+ag241125@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Windows 11/ Chrome, Samsung S23FE/ Chrome, iPhone 13 Mini/ iOS 26.1
App Component: Workspace Settings

Action Performed:

Precondition: Have global reimbursements beta enabled
Have a workspace with the EUR currency set.

  1. Navigate to https://staging.new.expensify.com/
  2. Go to workspace settings > Workflows > Add bank account
  3. In Step 1 select Italy
  4. Go through the flow up to Step 4 in the following steps
  5. Check Yes when asked if you're the beneficial owner
  6. Go through the flow up to the "Upload additional documentation" page
  7. In the "What is your country of citizenship?", select "Germany"

Expected Result:

The "Upload additional documentation" page requires uploading proof of beneficial owner, copy of ID, proof of address, and codice fiscale/ Tax ID.

Actual Result:

The "Upload additional documentation" page requires uploading proof of beneficial owner, proof of address, and codice fiscale/ Tax ID, but the section for "copy of ID" is not available.

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

1.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 25, 2025
  2. melvin-bot commented on Nov 25, 2025

    @melvin-bot

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

  3. melvin-bot commented on Nov 25, 2025

    @melvin-bot

    Triggered auto assignment to @tgolen (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. github-actions commented on Nov 25, 2025

    @github-actions
    Contributor

    👋 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.
  5. melvin-bot commented on Nov 25, 2025

    @melvin-bot

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

  6. MrMuzyk commented on Nov 25, 2025

    @MrMuzyk
    Contributor

    I think the testing scenario is not correct here. I believe copy of ID document was only needed for GBP workspace when beneficial owner isn't a UK citizen.

    I didn't change the currency requirement in the PR. The change I've introduced to logic of requested files checks beneficial owner nationality instead of address.

    cc @madmax330 @hungvu193

  7. madmax330 commented on Nov 25, 2025

    @madmax330
    Contributor

    What @MrMuzyk said is correct, we only need the file if the owner isn't a UK citizen so we should be good here

  8. melvin-bot commented on Nov 25, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions