Skip to content

[Due for payment 2025-07-22] [Fix CP'd] Expense - System message when paid with bank account is different in LHN and thread #66005

@jponikarchuk

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: 9.1.80-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #65296
Email or phone of affected tester (no customers): applausetester+ds90nu2@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Workspace is set up with bank account.
  • Admin invites member to the workspace.
  • Member has a personal bank account.
  1. Go to staging.new.expensify.com
  2. [Member] Submit an expense with amount more than $100 to the workspace chat.
  3. [Member] Click Submit on the expense preview.
  4. [Admin] Open the expense report.
  5. [Admin] Click Approve and Pay by bank account.
  6. [Admin] Right click on paid system message > Reply in thread.

Expected Result:

  • LHN preview willl show the same message as the expense report - paid with bank account 1111
  • Paid system message thread header will show the same message as the parent message - paid with bank account 1111

Actual Result:

  • LHN preview shows "paid amount with bank account 1111", expense report shows "paid with bank account 1111".
  • Paid system message thread header shows "paid with wallet", when the parent message is "paid with bank account 1111".

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

Issue OwnerCurrent Issue Owner: @JmillsExpensify

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions