[Due for payment 2025-09-17] Expense - Wrong max tax amount, error when saving tax in self DM expense

[nlemma]

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.2.2-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 TestRail: #69155
Email or phone of affected tester (no customers): dsjionsjosdijdso@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Account has self DM.
• Create a default workspace and enable Taxes.

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Track a manual expense.
4. Open the transaction thread.
5. Click Tax.
6. Select 5% tax rate.
7. Click Tax amount.
8. Hit Enter.
9. The error shows that "Maximum tax amount is MYR 0.00", which is incorrect because tax rate is not 0%.
10. Change the amount to 0 and save it.
11. "Unexpected error editing this expense. Please try again later." shows up.

Expected Result:

In Step 9, it will not show "Maximum tax amount is MYR 0.00" because tax rate is 5%.
In Step 11, no error will show up when saving 0.00 tax amount.

Actual Result:

In Step 9, error shows that "Maximum tax amount is MYR 0.00", which is incorrect because tax rate is not 0%.
In Step 11, "Unexpected error editing this expense. Please try again later." shows up.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6936476_1757102723599.Screen_Recording_2025-09-06_at_04.02.35.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @jliexpensify

[melvin-bot]

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

[melvin-bot]

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

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