You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-04-20] [Due for payment 2026-03-31] [Merge] Enable users to select tax rate when merging expenses, auto-calculate tax amount. #70058
When merging two expenses that have tax rates selected, we'll do the following:
To ensure there are no conflicts between the user selecting a tax rate and a tax amount that doesn’t compute, we’ll only allow users to select ‘tax rate’ in the details to keep.
Where tax rates for the two expenses differ, allow the user to select the tax rate in the details page.
Show the resulting tax in the confirm page, applying the tax rate to the selected amount.
This method can still result in some conflicts, but they also exist on Classic:
The selected tax rate could be invalid based on the workspace the selected report is on.
The selected tax rate could conflict with category rules for tax rates.
Manual Test Steps
Create two expenses with different expense amounts and tax rates
More > Merge
Select one of the tax rates and an amount in the details selector page
In the cofirm page, ensure that the rate and amount are used to calculate the resulting tax amount.
changed the title [-][Due for payment 2026-03-31] [Merge] Enable users to select tax rate when merging expenses, auto-calculate tax amount.[/-][+][Due for payment 2026-04-20] [Due for payment 2026-03-31] [Merge] Enable users to select tax rate when merging expenses, auto-calculate tax amount.[/+]on Apr 13, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.58-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@hoangzinh 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]
Activity
melvin-bot commentedon Sep 8, 2025
Triggered auto assignment to @RachCHopkins (
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.RachCHopkins commentedon Sep 11, 2025
Can someone tell me please, who is the C+ on this one?
dominictb commentedon Sep 11, 2025
I'll implement this while @hoangzinh is the C+.
melvin-bot commentedon Sep 15, 2025
@hoangzinh Whoops! This issue is 2 days overdue. Let's get this updated quick!
89 remaining items
melvin-bot commentedon Apr 10, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Apr 10, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
jponikarchuk commentedon Apr 10, 2026
Deploy Blocker #87616 was identified to be related to the PR #84769 that attempted to fix this issue.
lanitochka17 commentedon Apr 10, 2026
Deploy Blocker ##87640 was identified to be related to the PR ##84769 that attempted to fix this issue.
melvin-bot commentedon Apr 10, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-][Due for payment 2026-03-31] [Merge] Enable users to select tax rate when merging expenses, auto-calculate tax amount.[/-][+][Due for payment 2026-04-20] [Due for payment 2026-03-31] [Merge] Enable users to select tax rate when merging expenses, auto-calculate tax amount.[/+]melvin-bot commentedon Apr 13, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 13, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.58-9 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-20. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 13, 2026
@hoangzinh 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]