Expense - Category, tag, tax, total column are not aligned correctly

[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.66-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #88296
Email or phone of affected tester (no customers): josdjnosdjionjsdonjisod@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 tag and taxes in workspace settings.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create two expense with category, tag and tax.
4. Open the report.

Expected Result:

Category, tag and tax column will be aligned correctly.

Actual Result:

Category, tag and tax column are not aligned correctly.

Same issue also happens with Total column in IOU report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

View all open jobs on GitHub

[melvin-bot]

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

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

[JS00001]

@Krishna2323 another blocker

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #88296 - "Update report details view to use compact desktop table styles" by @Krishna2323 (High confidence)
Related Issues: #86203

Recommendation: REVERT

PR #88296 introduced a new shouldRemoveTotalColumnFlex flag and substantially reworked the table layout styles for the compact desktop report view. The column misalignment on MacOS/Chrome in staging (v9.3.66-1) directly matches the scope of changes in this PR — both the table header and the transaction rows were restyled, and any mismatch in how the column flex/width is applied between the header and rows would produce the misalignment seen in the screenshots.

Assigned: @Krishna2323 (PR author), @JS00001, @luacmartins, @situchan (approving reviewers)
Labels: No label changes needed — DeployBlockerCash is correct (staging-only frontend bug in Expensify/App); DeployBlocker is not present and should not be added.

Detailed Analysis

Evidence

• The bug reports category, tag, and tax columns not aligned correctly in the IOU/expense report on desktop (MacOS Chrome), which is exactly the layout path changed in PR Update report details view to use compact desktop table styles #88296.
• The issue is reproducible on staging (v9.3.66-1) but not on production, confirming it was introduced in this staging release cycle.
• melvin-bot automatically assigned PR Update report details view to use compact desktop table styles #88296 to this deploy blocker issue, indicating it was identified as the most recently merged PR in the affected area.
• PR Update report details view to use compact desktop table styles #88296 is entry Reorder arguments so that path and keyPattern are next to each other #30 in the StagingDeployCash chronological order, merging on 2026-05-01 — well within this staging cycle.

Verification

• Affected files per the bug report: the report detail column layout for category, tag, tax, and total on desktop web.
• PR Update report details view to use compact desktop table styles #88296 modifies:
  • src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx — reworks the table header container styles and removes gap2 between grouped transactions
  • src/components/MoneyRequestReportView/MoneyRequestReportTableHeader.tsx — adds shouldRemoveTotalColumnFlex prop
  • src/components/MoneyRequestReportView/MoneyRequestReportTransactionItem.tsx — passes shouldRemoveTotalColumnFlex to row items
  • src/components/TransactionItemRow/index.tsx — passes shouldRemoveTotalColumnFlex through to getReportTableColumnStyles for TOTAL_AMOUNT, TOTAL_PER_ATTENDEE, and ORIGINAL_AMOUNT columns
  • src/components/MoneyRequestReportView/MoneyRequestReportGroupHeader.tsx — reworks group header height and padding

Root Cause

The getReportTableColumnStyles function in src/styles/utils/index.ts at line 1929 applies flex1 to the total/amount columns unless shouldRemoveTotalColumnFlex is true. PR #88296 passes shouldRemoveTotalColumnFlex to the row items (MoneyRequestReportTransactionItem) and the table header (MoneyRequestReportTableHeader), removing the flex1 flex grow from those columns. However, the group header (MoneyRequestReportGroupHeader) does not receive this flag — meaning the group header row may lay out its columns at a different width than the data rows and the table header, producing the visible misalignment between category, tag, tax, and total columns.