Skip to content

[Due for payment 2026-04-17] [Awaiting Checklist Completion] [$500] Distance - Tax rate & tax amount field are different when selected for the first and second time #73413

Closed

Description

@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.37-8
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #73391
Email or phone of affected tester (no customers): sdjiosdjnosdjoisdjoi1@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:
For Taxes,

  • Set Set Workspace currency default and Foreign currency default to 5% tax rate.
  • Create 5%, 10% and 15% tax rate.

For Distance rates,

  • Enable Track tax.
  • Create 2 more rates in addition to the default rate - 0.70, 1.00 and 2.00
  • For each distance rate, configure tax rate and tax reclaimable as below:
    Distance rate 0.70:
  • Tax rate: 5%
  • Tax reclaimable amount: any amount
    Distance rate 1.00:
  • Tax rate: 10%
  • Tax reclaimable amount: DO NOT enter amount
    Distance rate 2.00:
  • Tax rate: 15%
  • Tax reclaimable amount: any amount.
  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Taxes.
  3. Delete Tax rate 15%.
  4. Go to workspace chat.
  5. Click + > Track distance > Manual.
  6. Enter amount > Next.
  7. Click Rate.
  8. Select Distance rate 1.00.
  9. Click Rate.
  10. Select Distance rate 2.00.
    → Tax rate field shows the default tax rate. Tax amount is not zero.
  11. Click Rate.
  12. Click on the same Distance rate 2.00.
    → Tax rate field becomes blank. Tax amount changes to zero after reselecting the same rate.

Expected Result:

In Step 10 and 12, when selecting the same distance rate without tax rate and with tax reclaimable, Tax rate and Tax amount field should remain the same.

Actual Result:

When selecting the same distance rate without tax rate and with tax reclaimable,

  • in Step 10, Tax rate field shows the default tax rate. Tax amount is not zero.
  • in Step 12, Tax rate field becomes blank. Tax amount changes to zero after reselecting the same rate.

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

Bug6983106_1761300462891.2.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021991226149384448495
  • Upwork Job ID: 1991226149384448495
  • Last Price Increase: 2025-11-25
  • Automatic offers:
    • cretadn22 | Contributor | 109634496
Issue OwnerCurrent Issue Owner: @Ollyws

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 24, 2025
  2. melvin-bot commented on Oct 24, 2025

    @melvin-bot

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

  3. melvin-bot commented on Oct 24, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 24, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 24, 2025

    @github-actions
    Contributor

    👋 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.
  6. twisterdotcom commented on Oct 24, 2025

    @twisterdotcom
    Contributor

    Okay wow, hello Hourly.

  7. twisterdotcom commented on Oct 24, 2025

    @twisterdotcom
    Contributor

    Okaty, this is an INCREDIBLY niche flow right? Should we block the deploy on this? I'm all for fixing it, but I think it's unlikely to have larger effects? Maybe @roryabraham can speak to it more.

  8. twisterdotcom commented on Oct 24, 2025

    @twisterdotcom
    Contributor

    Seems this is being handled: #73309

  9. 79 remaining items

  10. garrettmknight commented on Dec 18, 2025

    @garrettmknight
    Contributor

    Payment summary confirmed.

  11. trjExpensify commented on Dec 23, 2025

    @trjExpensify
    Contributor

    approved $250 for @Ollyws

  12. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    ReviewingHas a PR in review
    on Apr 10, 2026
  13. changed the title [-][Awaiting Checklist Completion] [$500] Distance - Tax rate & tax amount field are different when selected for the first and second time[/-] [+][Due for payment 2026-04-17] [Awaiting Checklist Completion] [$500] Distance - Tax rate & tax amount field are different when selected for the first and second time[/+] on Apr 10, 2026
  14. melvin-bot commented on Apr 10, 2026

    @melvin-bot

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

  15. melvin-bot commented on Apr 10, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.57-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-04-17. 🎊

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

  16. melvin-bot commented on Apr 10, 2026

    @melvin-bot

    @Ollyws / @cretadn22 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]

  17. melvin-bot commented on Apr 10, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions