Skip to content

Reports - Paid expenses show up under pay search if receiver didn't setup bank account #64601

Closed

Description

@vincdargento

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.1.69-2
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 TestRail: #62657
Email or phone of affected tester (no customers): nathanmulugetatesting+4122@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 11 / Chrome
App Component: Search

Action Performed:

Pre conditions:

  • Workspace connected with a VBA
  1. Navigate to staging.new.expensify.com
  2. Create an expense in the workspace chat
  3. Submit and Approve the expense
  4. Pay the expense via Expensify (not elsewhere)
  5. Navigate to reports > Pay

Expected Result:

Only items that can be paid are shown under pay search

Actual Result:

Already paid items where receiver didn't setup bank accounts are shown

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

bug.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 Jun 19, 2025
  2. melvin-bot commented on Jun 19, 2025

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (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. github-actions commented on Jun 19, 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.
  4. melvin-bot commented on Jun 19, 2025

    @melvin-bot

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

  5. melvin-bot commented on Jun 19, 2025

    @melvin-bot

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

  6. self-assigned this
    on Jun 19, 2025
  7. 9 remaining items

  8. JS00001 commented on Jun 26, 2025

    @JS00001
    Contributor

    BE changes are in for this, waiting on those, then FE changes will go in

  9. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    @CortneyOfstad, @JS00001 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  10. JS00001 commented on Jun 30, 2025

    @JS00001
    Contributor

    FE changes are on staging

  11. CortneyOfstad commented on Jul 1, 2025

    @CortneyOfstad
    Contributor

    Thanks @JS00001!

  12. melvin-bot commented on Jul 3, 2025

    @melvin-bot

    @CortneyOfstad @JS00001 this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  13. JS00001 commented on Jul 3, 2025

    @JS00001
    Contributor

    Close to prod deploy

  14. JS00001 commented on Jul 7, 2025

    @JS00001
    Contributor

    Deployed to prod, will be paid by #64688

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

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions