Skip to content

Expense - Tax selected on created rule is not displayed on confirm page of distance expense #100544

Open

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.73-3
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: #99420
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Use an expensifail account.
Prerequisite 2: Account has a workspace with "Rules", "Taxes" and "Distance Rates" enabled.
Prerequisite 3: Have at least one non default tax rate created.
Prerequisite 4: "Tax track" enabled on distance rates.

  1. Open the staging.new.expensify.com website.
  2. Navigate to "Workspaces" > Workspace > "Rules"
  3. Click on "Add Rule" > "Apply expense defaults" > "Category"
  4. On "Category" select "Car"
  5. On "Tax" select any non default rate and save the rule.
  6. Navigate to workspace chat.
  7. Start the creation of a map distance expense.
  8. Once you reach confirm page, note that "Car" is shown as category, but "Tax" field still shows default tax rate.
  9. Finish the expense creation flow.
  10. Open the just created expense.
  11. Note that now, "Tax" field correctly shows the rate selected as rule.

Expected Result:

While creating a distance expense, "Tax" field on confirm page should already show the tax rate selected for the category during the rule creation.

Actual Result:

"Tax" field on confirm page of a distance expense, still shows default tax rate despite a rule being created for the used category.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7253656_1788800715859.Tax_Rule_8.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7253656

Issue OwnerCurrent Issue Owner: @Krishna2323

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 7, 2026
  2. applause-bot commented on Sep 7, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/6bbd6e377c79c034ce410f9879c8e81ceee4e18bf7cf7dfaf1042ab35cea002e

  3. melvin-bot commented on Sep 7, 2026

    @melvin-bot

    @JS00001 recently merged #99420, but they are OOO right now, so I'll auto-assign someone else.

  4. github-actions commented on Sep 7, 2026

    @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.
  5. melvin-bot commented on Sep 7, 2026

    @melvin-bot

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

  6. melvin-bot commented on Sep 7, 2026

    @melvin-bot

    @JS00001 @situchan you have been assigned to this deploy blocker because you reviewed the offending PR: #99420

  7. MelvinBot commented on Sep 7, 2026

    @MelvinBot
    Contributor

    ⚠️ A setup step failed before I could start. This is usually a temporary issue — try again in a few minutes, and if it persists post in #melvinbot-ai.

    Run details

  8. melvin-bot commented on Sep 7, 2026

    @melvin-bot

    @Krishna2323 you have been assigned to this deploy blocker because you authored the offending PR: #99420

  9. 36 remaining items

  10. melvin-bot commented on Oct 2, 2026

    @melvin-bot

    @Krishna2323 Huh... This is 4 days overdue. Who can take care of this?

  11. melvin-bot commented on Oct 3, 2026

    @melvin-bot

    @Krishna2323 Huh... This is 4 days overdue. Who can take care of this?

  12. Krishna2323 commented on Oct 5, 2026

    @Krishna2323
    Contributor

    Not overdue. @ShridharGoel any updates on the BE PRs?

  13. JS00001 commented on Oct 8, 2026

    @JS00001
    Contributor

    @Krishna2323 the BE PRs are merged, will be deployed hopefully today

  14. melvin-bot commented on Oct 8, 2026

    @melvin-bot

    @Krishna2323 Whoops! This issue is 2 days overdue. Let's get this updated quick!

  15. JS00001 commented on Oct 9, 2026

    @JS00001
    Contributor

    The BE PR is on production @Krishna2323

  16. Krishna2323 commented on Oct 9, 2026

    @Krishna2323
    Contributor

    Thanks, will check this soon.

  17. Krishna2323 commented on Oct 12, 2026

    @Krishna2323
    Contributor

    @situchan PR is ready for review: #101674

  18. removed their assignment
    on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions