[Due for payment 2026-05-26] Expense - Missing Billable row when expense is non-reimbursable

[mitarachim]

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.3.76-0
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 BrowserStack: #90411
Email or phone of affected tester (no customers): sdsdjoijdoisnjodis@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Enable Rules in workspace settings.
• Set Billable default to Billable in Rules settings.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create a non-reimbursable, billable expense.
4. Open the report.

Expected Result:

Billable row will be present in the expense report.

Actual Result:

Billable row is not present in the expense report when expense is not reimbursable. It is present only when the expense is reimbursable.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7157864_1779185147390.2.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @hoangzinh

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #90411

[melvin-bot]

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

[github-actions]

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #90411 - "Hide redundant Reimbursable rows; show '· Non-reimbursable' on Amount" by @mukhrr (High confidence)
Related Issues: #89548 (the issue that PR #90411 was fixing)

Recommendation: REVERT

PR #90411 introduced a logic regression that hides the Billable breakdown row when an expense is simultaneously non-reimbursable and billable. Reverting this PR will restore the correct behavior immediately.

Assigned: @mukhrr (PR author), @hoangzinh (approving reviewer), @rlinoz (approving reviewer)
Labels: DeployBlockerCash kept (App PR is the cause). No label changes made.

Detailed Analysis

Evidence

• The bug is staging-only and not reproducible in production, consistent with it being introduced by a PR in the current staging cycle.
• PR Hide redundant Reimbursable rows; show "· Non-reimbursable" on Amount #90411 is present in the StagingDeployCash checklist (issue Deploy Checklist: New Expensify 2026-05-19 #91039) and was merged on 2026-05-18.
• The melvin-bot also identified this PR as the cause.
• The issue specifically manifests with a workspace that has "Billable default" set to Billable in Rules — precisely the scenario that involves a non-zero billableTotal.

Verification

The affected file is src/components/ReportActionItem/MoneyReportView.tsx.

PR #90411 modified this file (confirmed via gh pr view 90411 --json files).

The change introduced in MoneyReportView.tsx:

const isSingleNonReimbursableExpense =
  isSingleTransactionReport(report, transactions) &&
  transactions.at(0)?.reimbursable === false;
const shouldShowBreakdown =
  !isSingleNonReimbursableExpense &&
  (!!nonReimbursableSpend || !!billableTotal || (!!taxTotal && isTaxEnabled));

Before the PR, shouldShowBreakdown was:

const shouldShowBreakdown =
  nonReimbursableSpend || !!billableTotal || (!!taxTotal && isTaxEnabled);

Root Cause

The !isSingleNonReimbursableExpense guard short-circuits the entire shouldShowBreakdown expression to false when the report has exactly one non-reimbursable transaction — even when billableTotal is non-zero (i.e., the expense is also marked as billable).

The original intent of the PR was to avoid showing redundant "Out of Pocket" and "Company Spend" breakdown rows when a report contains only a single non-reimbursable expense (since the total row already conveys that information). However, the guard was applied too broadly: it also suppresses the Billable row, which provides distinct and non-redundant information.

The fix should scope the isSingleNonReimbursableExpense guard to only suppress the non-reimbursable/reimbursable split rows, not the Billable row. However, since reverting is simpler and safer, that is the recommended action.