Reports - "Rate not valid for this workspace" error when inline editing distance track expense

[jponikarchuk]

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.3.62-1
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: #83127
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11 / Chrome
App Component: Search

Action Performed:

Prerequisite: Account has Self DM.
Prerequisite 2: Account has at least one workspace.

1. Open the staging.new.expensify.com website.
2. Navigate to Self DM.
3. Create a map distance expense.
4. Navigate to "Reports" > "All Expenses"
5. Click on the "Date" cell on transaction row of the just created expense.
6. Edit to any different date.
7. Note that a "Rate not valid for this workspace" error appears on expense preview.

Expected Result:

No error should appear after inline editing any cell on a distance expense from Self DM.

Actual Result:

"Rate not valid for this workspace" error displayed after inline editing a distance expense from Self DM.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #83127

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #83127 - "Add inline editing to transaction table cells on desktop" by @mohammadjafarinejad (High confidence)
Related Issues: N/A

Recommendation: REVERT

The inline editing feature introduced by PR #83127 is triggering a spurious "Rate not valid for this workspace" (customUnitOutOfPolicy) violation when a date is edited inline for a distance expense created from Self DM. The fix requires changes to the App-side policy context logic in useTransactionInlineEdit.ts.

Assigned: @mohammadjafarinejad (PR author), @ahmedGaber93 @puneetlath (approving reviewers) from highest-confidence causing PR only
Labels: DeployBlockerCash kept (Frontend bug — App PR introduced the issue). No label changes made.

Detailed Analysis

Evidence

• PR feat: Add inline editing for tables on desktop #83127 introduced useTransactionInlineEdit, TransactionInlineEdit.ts, and the EditableCell infrastructure enabling inline editing of date, merchant, description, category, and amount from the Search table.
• The bug is reproducible only on staging (version 9.3.62-1) and the issue body states "N/A - new feature, doesn't exist in prod", matching the merge date of April 21, 2026 (item Move the keyChanged trigger to after persistent storage is set #14 in the StagingDeployCash chronological list).
• The melvin-bot auto-assigned this PR as the cause and linked it in its comment.

Verification

• PR feat: Add inline editing for tables on desktop #83127 modifies src/hooks/useTransactionInlineEdit.ts, src/libs/actions/TransactionInlineEdit.ts, and src/libs/actions/IOU/UpdateMoneyRequest.ts — all directly involved in the inline editing flow that triggers the error.
• src/libs/actions/IOU/UpdateMoneyRequest.ts contains the updateMoneyRequestDate function, which dispatches UPDATE_MONEY_REQUEST_DATE using getUpdateTrackExpenseParams for Self DM track expenses.
• The customUnitOutOfPolicy error message ("Rate not valid for this workspace") is displayed as a transaction violation when the customUnitRateID on a distance transaction is no longer valid for the resolved policy.

Root Cause

In useTransactionInlineEdit.ts, the policy value is resolved via usePolicyForTransaction using reportPolicyID (the policy attached to the parent report). For a Self DM distance expense, reportPolicyID is undefined or points to a personal/non-workspace policy, while the transaction's customUnitRateID was issued by the user's active workspace policy (activePolicyID). When editTransactionDateInline triggers violation re-evaluation after the API write, the rate ID on the distance transaction is validated against the wrong policy, producing the customUnitOutOfPolicy violation. The mismatch between the activePolicyID used for policyCategories/policyTags (line 134-135 of useTransactionInlineEdit.ts) and the policy object from usePolicyForTransaction (which uses reportPolicyID) is the inconsistency introduced by this PR.

[trjExpensify]

@ahmedGaber93 I can't repro this, can you?

2026-04-24_13-43-51.mp4