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
Expense - LHN shows "Paid x with bank account", expense report shows "paid with wallet" #65129
Version Number: 9.1.72-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:#56838 Email or phone of affected tester (no customers):applausetester+280604kh@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.
Go to staging.new.expensify.com
[Member] Submit an expense with amount more than $100 to the workspace chat.
[Member] Click Submit on the expense preview.
[Admin] Click Approve and Pay by bank account.
[Member] Open expense report.
Expected Result:
Expense report preview in LHN will show the same message as the paid system message in the expense report.
Actual Result:
LHN shows "Paid x with bank account".
Expense report shows "paid with wallet".
👋 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.
Feat standardize pay button #56838: Touches payment/settlement logic and ReportActionsUtils altering how paid-with messages are constructed, so it can cause the bank-account vs wallet text mismatch between LHN and report.
Use tripdata payload to get reservations setup #64891: Modified MoneyRequestView, the component that renders the in-report payment system message, so its new logic could mis-identify the payment source and show “wallet” while the unchanged LHN preview still shows the correct bank account text.
Issue not reproducible on Windows 11/ Chrome in v9.1.72-10, but there is an error message (Unexpected error. Please try again later.) We used accounts that were previously set up with a bank account.
Activity
melvin-bot commentedon Jun 28, 2025
Triggered auto assignment to @isabelastisser (
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.melvin-bot commentedon Jun 28, 2025
Triggered auto assignment to @aldo-expensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jun 28, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jun 28, 2025
👋 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:
BlameGPT commentedon Jun 30, 2025
Possible culprit PRs for this issue
If not above, check these
aldo-expensify commentedon Jun 30, 2025
The cause: #56838
The PR causing this is being reverted here: #65192
melvin-bot commentedon Jun 30, 2025
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.
aldo-expensify commentedon Jun 30, 2025
This is now saying
paid with Expensifyso the revert fixed it:IuliiaHerets commentedon Jun 30, 2025
Issue not reproducible on Windows 11/ Chrome in v9.1.72-10, but there is an error message (Unexpected error. Please try again later.) We used accounts that were previously set up with a bank account.
65129-Web-2.mp4
fix Expensify#65129: update copies