Skip to content

[Due for payment 2026-04-14] Expense - New split shows wrong amount which leads to higher total amount #82455

Closed

Description

@lanitochka17

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.19-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: #81626
Email or phone of affected tester (no customers): josdijosdjodniosnjd@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:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense with amount -10.00.
  4. Open the expense report.
  5. Click More > Split.
  6. Edit the first split amount to -20.00.
  7. Click Save.
  8. Open any split.
  9. Click Amount.
  10. Click Add split.

Expected Result:

The new split amount will be 0.00 as it redistributes to match the total amount.

Actual Result:

The new split amount is 20.00, which makes the total amount MYR 20.00 greater than the original expense.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7077214_1771009539334.3.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 13, 2026
  2. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 13, 2026
  3. melvin-bot commented on Feb 13, 2026

    @melvin-bot

    @blimpich recently merged #81626, but they are OOO right now, so I'll auto-assign someone else.

  4. melvin-bot commented on Feb 13, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra (External)

  5. melvin-bot commented on Feb 13, 2026

    @melvin-bot

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

  6. melvin-bot commented on Feb 13, 2026

    @melvin-bot

    Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.

  7. melvin-bot commented on Feb 13, 2026

    @melvin-bot

    Triggered auto assignment to @MarioExpensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  8. melvin-bot commented on Feb 13, 2026

    @melvin-bot

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

  9. 56 remaining items

  10. melvin-bot commented on Apr 7, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  11. melvin-bot commented on Apr 7, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.53-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-04-14. 🎊

    For reference, here are some details about the assignees on this issue:

    • @ShridharGoel requires payment through NewDot Manual Requests
    • @ikevin127 requires payment through NewDot Manual Requests
  12. melvin-bot commented on Apr 7, 2026

    @melvin-bot

    @ShridharGoel / @ikevin127 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  13. melvin-bot commented on Apr 7, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  14. ikevin127 commented on Apr 14, 2026

    @ikevin127
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: N/A - Result of the original design

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue: https://github.com/Expensify/Expensify/issues/625148

    Regression Test Proposal

    1. Open a workspace chat in the app.
    2. Create an expense with amount -$10.00 (negative).
    3. Open the expense report and tap More > Split.
    4. Edit the first split amount to -$20.00 (more than total).
    5. Save the split.
    6. Open any of the 2 generated splits and tap on the Amount field.
    7. Tap Add split to create a new split.
    8. Verify: The newly created split amount is $0.00.
    9. Verify: The first split remains -$20.00.
    10. Verify: When pressing Save, user gets 🔴 Please enter a valid amount before continuing. validation error.

    Note

    The auto-redistribution issues caused by editing previously existing splits AFTER adding the new ones are out of scope for this regression test.

    Do we agree 👍 or 👎.

    Zapier Logs Run ID: 00040eee-a685-a302-3d1f-fc104922c9d4
  15. ShridharGoel commented on Apr 14, 2026

    @ShridharGoel
    Contributor

    @ikevin127 Thanks for adding the checklist

  16. melvin-bot commented on Apr 14, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  17. mallenexpensify commented on Apr 16, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @ikevin127 paid $250 via Upwork
    Contributor+: @ShridharGoel due $250 via NewDot

    ^ Test case created

    Thx!

  18. quinthar commented on Apr 21, 2026

    @quinthar
    Contributor

    Approved $250 to @ikevin127

  19. garrettmknight commented on Apr 27, 2026

    @garrettmknight
    Contributor

    $250 approved for @ShridharGoel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions