Skip to content

[Due for payment 2026-01-13] [Payment due] [Splits in NewDot] Add 'Split by percentage' to the split expense table for new splits #72228

Closed

Description

@garrettmknight

Follow up to Expense Splitting in NewDot

[Figma]
[Predesign]

Feature Description

Implement a ‘Split by percentage’ flow that does the following:

  1. Creates two split options at the top of the split table: Amount (this is the existing split method) and Percentage (this is the new one)
  2. When the user taps 'Percentage' we'll change the view of the split table like so"
  • The input on individual splits will be a percentage between 0 and 100. We'll accept whole percentage values. i.e. 5%, not 5.5%
  • The initial percentage values will be the split amount / the original amount.
  • When users change a percentage on a split, we'll update the amount of the split to the original transaction amount X the percentage.

Important Notes:

  • We'll maintain the logic and copy for our current warnings/errors on saving splits where the sum of the splits differs from the original transaction amounts.
  • We're beginning with Amount and Percentage as modes, but we'll add Date later.
Image

Manual Test Steps

Enabling Percentage Mode:

  1. Submitter creates an expense for $200.
  2. Submitter taps 'Split' from the 'More' menu. Two even splits are created in the Split table, each for $100.
  3. Submitter taps 'Add Split'. The new split is set to $0.
  4. Submitter taps 'Split by percentage'
  5. Verify the Split by percentage page shows, with existing amounts and resulting percentages:
  • Split 1: $100 / 50%
  • Split 2: $100 / 50%
  • Split 3: $0 / 0%

Changing Percentages:

  1. After step 6 above, change the percentage of Split 3 to 25%
  • Verify that the amount for Split 3 is $50
  • Verify that an error shows noting that the total is $50 more than the original amount
  1. Change the percentage of Split 1 to 25%
  • Verify that the amount for Split 1 is $50
  • Verify the 'over' error from the previous step is removed.
  1. Save
  • Verify the splits are correctly created for the amounts listed in the split table

Automated Tests

Issue OwnerCurrent Issue Owner: @garrettmknight

Activity

  1. melvin-bot commented on Oct 9, 2025

    @melvin-bot

    Current assignee @garrettmknight is eligible for the NewFeature assigner, not assigning anyone new.

  2. melvin-bot commented on Oct 9, 2025

    @melvin-bot

    ⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

  3. melvin-bot commented on Oct 9, 2025

    @melvin-bot

    Triggered auto assignment to Design team member for new feature review - @shawnborton (NewFeature)

  4. shawnborton commented on Oct 9, 2025

    @shawnborton
    Contributor

    Mocks look correct to me if I remember where we last left off. Let me know if you need anything though.

  5. garrettmknight commented on Oct 9, 2025

    @garrettmknight
    ContributorAuthor

    Sorry, created and then didn't update. My boy @dubielzyk-expensify is on this one.

  6. dubielzyk-expensify commented on Oct 13, 2025

    @dubielzyk-expensify
    Contributor

    Replied to your comment in Figma 👍

  7. changed the title [-]Add 'Split by percentage' to the split expense table for new splits[/-] [+][Splits in NewDot] Add 'Split by percentage' to the split expense table for new splits[/+] on Oct 13, 2025
  8. 32 remaining items

  9. changed the title [-][Payment due] [Splits in NewDot] Add 'Split by percentage' to the split expense table for new splits[/-] [+][Due for payment 2026-01-13] [Payment due] [Splits in NewDot] Add 'Split by percentage' to the split expense table for new splits[/+] on Jan 6, 2026
  10. melvin-bot commented on Jan 6, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.93-1 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-01-13. 🎊

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

  11. melvin-bot commented on Jan 6, 2026

    @melvin-bot

    BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  12. trjExpensify commented on Jan 6, 2026

    @trjExpensify
    Contributor

    Payment summary here is correct.

  13. parasharrajat commented on Jan 6, 2026

    @parasharrajat
    Member

    We can close this issue now.

  14. garrettmknight commented on Jan 7, 2026

    @garrettmknight
    ContributorAuthor

    $750 approved for @ikevin127

  15. parasharrajat commented on Mar 19, 2026

    @parasharrajat
    Member

    Payment requested as per #72228 (comment)

  16. twisterdotcom commented on Mar 23, 2026

    @twisterdotcom
    Contributor

    Confirming Payment Summary. @parasharrajat paid via New Expensify

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 productionNewFeatureSomething to build that is a new item.WeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions