Expense - Split expense is missing Edit split page, can be split again and again

[jponikarchuk]

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.10-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #80010
Email or phone of affected tester (no customers): sjdiosjndoijdosjs@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Open the expense report.
5. Click More > Split > Save.
6. Open any split.
7. Click Amount.
8. Close Amount page.
9. Click More.
10. Click Split.

Expected Result:

In Step 7, Edit split page will open.
In Step 10, there will be no Split option for split expense.

Actual Result:

In Step 7, Amount page opens.
In Step 10, split expense can be split again.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @CortneyOfstad (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.

[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: #80010 - "fix: Split label is not removed from Amount field when unreported split expense is submitted" by @samranahm (High confidence)
Related Issues: #78907 (the issue that PR #80010 was attempting to fix)

Recommendation: REVERT

PR #80010 should be reverted. While it successfully removed the "Split" label when an expense is submitted to a report, it introduced a critical regression that breaks the core split expense functionality.

Labels: Keeping DeployBlockerCash - this is a frontend bug that requires reverting an App PR.

📋 Detailed Analysis

Evidence

PR #80010 modified the isExpenseSplit() function in src/libs/TransactionUtils/index.ts to return false when a transaction has been added to a real report (lines 2591-2594):

const isAddedToReport = !!transaction?.reportID && transaction.reportID !== CONST.REPORT.SPLIT_REPORT_ID && transaction.reportID !== CONST.REPORT.UNREPORTED_REPORT_ID;
if (isAddedToReport) {
    return false;
}

This logic causes the function to incorrectly return false for split expenses that have been added to a workspace report, even though they are still split expenses.

Verification

The reproduction steps perfectly match the consequences of this change:

1. Missing Edit split page: When clicking "Amount" on a split expense in a workspace report, the code checks isExpenseSplit (via getOriginalTransactionWithSplitInfo on line 2623). Because the transaction has a real reportID, isExpenseSplit returns false, so the UI shows the regular "Amount" page instead of "Edit split".

2. Can split again: The isSplitAction function (in src/libs/ReportSecondaryActionUtils.ts) only checks for isBillSplit but not isExpenseSplit. Since isExpenseSplit now returns false, the split option remains available, allowing users to split an already-split expense.

The PR was merged on 2026-01-27 at 02:13:06 UTC and the bug was reported on 2026-01-27 at 20:20:46 UTC, confirming the timeline matches.

Root Cause

The change was too broad. It correctly identified that split expenses submitted to reports should not show the "Split" label in the amount description, but the implementation broke the fundamental identification of split expenses throughout the codebase. The isExpenseSplit function is used in multiple places to determine split expense behavior, not just for displaying the label.