Repository navigation
Description
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.78-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 BrowserStack: #76636
Email or phone of affected tester (no customers): jsodijsodnsdojoij2@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Money Requests
Action Performed:
Precondition:
- Account has self DM.
- Create two workspaces - A and B.
- Workspace A is the default workspace.
- Enable Taxes for workspace A and B.
- Workspace B has tax rate 15% (as long as workspace A does not have the same rate).
- Go to staging.new.expensify.com
- Go to self DM.
- Create an expense with default rate 0%.
- Click Submit it to someone.
- Select workspace B.
- On confirm page, click Tax field and select tax rate 15%.
- Click RHP back button.
- Select workspace A.
- On confirm page, click Tax amount field and click Enter.
→ Error shows up because tax amount is larger than the maximum tax amount. - Click RHP back button.
- Click Create expense.
- Open the submitted expense.
→ Expense can be submitted despite having tax amount larger than the limit.
Also, the same issue could happen with the steps listed here. Let's make sure we test that flow as well when we test the fix PR.
Expected Result:
In Step 9, after changing back to workspace A, Tax rate and Tax amount field should reset.
Actual Result:
In Step 9, after changing back to workspace A, Tax rate field changes to a different rate (originally it was 0%, then changed to 5%). Tax amount field does not reset and it still retains at the amount that is equivalent to 15% rate from workspace B, which is now beyond the 5% rate limit.
In Step 12, the submitted expense can be submitted to workspace despite having tax amount larger than the limit.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
Activity
melvin-bot commentedon Dec 13, 2025
Triggered auto assignment to @johncschuster (
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 commentedon Dec 13, 2025
👋 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:
melvin-bot commentedon Dec 13, 2025
Triggered auto assignment to @nkuoch (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 13, 2025
💬 A slack conversation has been started in #expensify-open-source
nkuoch commentedon Dec 14, 2025
Maybe coming from #76636?
koko57 commentedon Dec 15, 2025
I will check it today cc @cristipaval @parasharrajat
koko57 commentedon Dec 15, 2025
@cristipaval - should the value reset, like it's suggested
or should we show an error?
39 remaining items
cristipaval commentedon Dec 29, 2025
yeah, making it a Weekly in the meantime
dylanexpensify commentedon Jan 6, 2026
nice
dylanexpensify commentedon Jan 13, 2026
Ongoing
dylanexpensify commentedon Jan 20, 2026
Same
dylanexpensify commentedon Jan 27, 2026
@koko57 how're we doing?
koko57 commentedon Jan 28, 2026
@dylanexpensify didn't have time to work on this one - I was busy with Per diem field. Now I need to jump into BBA project, so I don't have capacity today
koko57 commentedon Feb 2, 2026
I'll have some capacity this week to continue with this issue. Looking into it today
koko57 commentedon Feb 4, 2026
I have 2 PRs in active review, one of them for Create Per Diem, so I need to leave it for later. Will get back to it as soon as it will be possible
koko57 commentedon Feb 9, 2026
I've opened a draft PR for this issue: #81888, but I need to test it thoroughly and complete the checklist. I'll do it tomorrow
koko57 commentedon Feb 10, 2026
Because we base the differentiation on the tax value and the tax id we have one edge case that the name will be displayed differently (it will be the tax rate name of the chosen policy when submitting). But it doesn't result in submitting the expense with error. I explained it in the test steps
PR opened for review
cristipaval commentedon Mar 4, 2026
this is in prod