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 - Mark as paid requires account validation #71251
Version Number: 9.2.18-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:#70106 Email or phone of affected tester (no customers):sdjoidsjnodsiojsni1o@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Account is new and not validated.
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Click Submit.
Click Approve.
Click Pay.
Click Mark as paid.
Expected Result:
The expense will be paid without account validation.
Actual Result:
The expense cannot be paid without account validation.
👋 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.
I can see the logic in not needing to validate an account to just mark something as paid, but I think that for consistency (and in edge cases like a new signup being added to an account as an admin or something), this is expected behavior. Closing this out.
Hello @roryabraham QA team found account validation is not required if we paid from Reports.
We think the behavior should be the same, right?
Or is this something we should flag as an issue?
Activity
melvin-bot commentedon Sep 24, 2025
Triggered auto assignment to @sonialiap (
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 Sep 24, 2025
Triggered auto assignment to @grgia (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 24, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Sep 24, 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:
roryabraham commentedon Sep 24, 2025
I can see the logic in not needing to validate an account to just mark something as paid, but I think that for consistency (and in edge cases like a new signup being added to an account as an admin or something), this is expected behavior. Closing this out.
mitarachim commentedon Sep 25, 2025
Hello @roryabraham QA team found account validation is not required if we paid from Reports.
We think the behavior should be the same, right?
Or is this something we should flag as an issue?
Screen.Recording.2025-09-25.at.08.13.29.mp4