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
[$250] Expense-Mark as paid button is not shown for the IOU receiver. #81955
👋 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.
Classification: Backend bug / NEEDS INVESTIGATION Causing PR: Unable to identify from frontend changes (Medium confidence) Related Issues: None found
Recommendation: NEEDS INVESTIGATION
After reviewing the StagingDeployCash PRs and the codebase, I cannot find a clear frontend PR that would cause this issue. The Mark as paid button visibility is controlled by the canIOUBePaid function in src/libs/actions/IOU/index.ts, which checks whether the current user is the payer (manager) of the IOU report.
Key finding: For a 1:1 IOU (person-to-person money request), the button should show for the RECEIVER (the person who needs to be paid back), determined by checking if iouReport.managerID === currentUserAccountID.
Since this bug:
Only occurs on staging (not production)
Affects a core IOU feature that has no recent frontend changes
The button visibility logic has not been modified in the staging deploy
This suggests the issue is most likely:
A backend bug where the managerID field is not being set correctly on newly created IOU reports on staging
OR a data inconsistency on the staging environment
Labels: Keeping BOTH DeployBlockerCash and DeployBlocker until the root cause is confirmed, as we cannot rule out either frontend or backend issues.
Next steps needed:
Backend team to verify managerID is being set correctly on IOU report creation
QA to provide a specific test case report ID to investigate the actual data
Check if this affects only new IOUs or also existing ones
@mitarachim@jliexpensify@neil-marcellini - Could you please provide a specific IOU report ID from staging where the button is missing? This will help determine if the issue is with how the data is being set by the backend versus how the frontend is reading it.
changed the title [-]Expense-Mark as paid button is not shown for the IOU receiver.[/-][+][$250] Expense-Mark as paid button is not shown for the IOU receiver.[/+]on Mar 12, 2026
📣 @situchan 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖
Activity
melvin-bot commentedon Feb 10, 2026
Triggered auto assignment to @jliexpensify (
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 Feb 10, 2026
Triggered auto assignment to @neil-marcellini (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 10, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Feb 10, 2026
👋 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:
OSBotify commentedon Feb 10, 2026
Investigation Summary
Classification: Backend bug / NEEDS INVESTIGATION
Causing PR: Unable to identify from frontend changes (Medium confidence)
Related Issues: None found
Recommendation: NEEDS INVESTIGATION
After reviewing the StagingDeployCash PRs and the codebase, I cannot find a clear frontend PR that would cause this issue. The Mark as paid button visibility is controlled by the canIOUBePaid function in src/libs/actions/IOU/index.ts, which checks whether the current user is the payer (manager) of the IOU report.
Key finding: For a 1:1 IOU (person-to-person money request), the button should show for the RECEIVER (the person who needs to be paid back), determined by checking if iouReport.managerID === currentUserAccountID.
Since this bug:
This suggests the issue is most likely:
Labels: Keeping BOTH DeployBlockerCash and DeployBlocker until the root cause is confirmed, as we cannot rule out either frontend or backend issues.
Next steps needed:
@mitarachim @jliexpensify @neil-marcellini - Could you please provide a specific IOU report ID from staging where the button is missing? This will help determine if the issue is with how the data is being set by the backend versus how the frontend is reading it.
13 remaining items
melvin-bot commentedon Mar 12, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @suneox (
External)[-]Expense-Mark as paid button is not shown for the IOU receiver.[/-][+][$250] Expense-Mark as paid button is not shown for the IOU receiver.[/+]melvin-bot commentedon Mar 12, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022031910653359059569
melvin-bot commentedon Mar 12, 2026
📣 @situchan 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖
jliexpensify commentedon Mar 12, 2026
Sorry @suneox - just needed automation to create an Upworks job
jliexpensify commentedon Mar 12, 2026
Payment Summary
Please accept: Upwork job
situchan commentedon Mar 30, 2026
@jliexpensify I accepted offer
jliexpensify commentedon Mar 30, 2026
Paid and job closed!