[Due for payment 2026-07-30] Categories - No "Show GL codes when categorizing expenses" toggle for Expensifail account

[applause-bot]

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.4.43-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: #94596
Email or phone of affected tester (no customers): sdsjodijnsdojsosjio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Log in with Expensifail account.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories.
3. Click More.

Expected Result:

Settings button should be shown where "Show GL codes when categorizing expenses" toggle is present.

Actual Result:

Settings button is not shown. There is no way to enable "Show GL codes when categorizing expenses" toggle.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7215050_1784769254034.8.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7215050

[applause-bot]

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

[melvin-bot]

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

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

[MelvinBot]

Proposal

Please re-state the problem that we are trying to solve in this issue.

On Workspace Settings → Categories → More, the Settings option is missing, so there is no way to reach the new "Show GL codes when categorizing expenses" toggle added by #94596.

What is the root cause of that problem?

This is a collision between two PRs, not a bug inside #94596 itself.

• PR #95289 (Rules Revamp clean-up, merged 2026-07-06) removed the legacy Settings entry point from the Categories More dropdown for any account on the rulesRevamp beta. The dropdown item is gated at WorkspaceCategoriesPage.tsx:367:

  if (canWriteCategories && !isRulesRevampEnabled) {
      menuItems.push({ text: translate('common.settings'), onSelected: navigateToCategoriesSettings, ... });
  }

• PR #94596 (merged 2026-07-22) added the GL codes toggle only to the legacy settings page (DynamicWorkspaceCategoriesSettingsPage.tsx:132) — the page whose only entry point was already removed for rulesRevamp accounts.

Internal/Expensifail accounts on staging typically carry the all beta, so rulesRevamp resolves on for them → the Settings entry is hidden → the new toggle is orphaned with no reachable UI. The toggle gate !!policy?.glCodes is not the problem; a Control workspace with GL codes has policy.glCodes === true and the toggle would render fine if the page were reachable.

What changes do you think we should make in order to solve the problem?

The GL codes toggle needs a home in the Rules Revamp UI, where the other category settings (e.g. requiresCategory) moved. Recommended fix:

• Surface "Show GL codes when categorizing expenses" in the Rules Revamp individual-expense/category settings surface — e.g. IndividualExpenseRulesSectionRevamp.tsx / the require-fields rules pages — reusing the existing setPolicyShowCategoryGLCodes action and the same !!policy?.glCodes gate, so it is reachable for rulesRevamp accounts.

As a faster deploy-blocker unblock, WorkspaceCategoriesPage.tsx:367 could keep showing Settings (drop && !isRulesRevampEnabled), but that reintroduces the legacy entry point #95289 deliberately removed, so it should be confirmed with the Rules Revamp owners rather than treated as the final fix.

What alternative solutions did you explore? (Optional)

Reverting #94596 would remove the orphaned toggle but also drops the whole GL-code-in-picker feature; not preferred since only the entry point is missing.

Investigation details & evidence

• Settings dropdown gate: WorkspaceCategoriesPage.tsx:367 — canWriteCategories && !isRulesRevampEnabled. isRulesRevampEnabled = isBetaEnabled(CONST.BETAS.RULES_REVAMP) (line 91).
• When gate was added: commit 299090002 ("Remove legacy category and tag settings entry points for rules revamp") in PR Part 1 - [Rules Revamp] Clean-up and Polish  #95289, merged 2026-07-06 — flipped if (canWriteCategories) → if (canWriteCategories && !isRulesRevampEnabled). Its own test steps state Settings should be absent from the ⋯ menu when the rulesRevamp beta is on.
• Show GL code when selecting a category #94596 did not touch WorkspaceCategoriesPage.tsx — its changed files are the CategoryPicker, language files, API params/types, CategoryOptionListUtils.ts, actions/Policy/Category.ts, DynamicWorkspaceCategoriesSettingsPage.tsx, and types/onyx/Policy.ts.
• policy.glCodes (types/onyx/Policy.ts:2780) is a Control-plan capability set to true on corporate upgrade; distinct from the showCategoryGLCodes toggle value.

Related GL-code feature follow-ups (not duplicates of this entry-point bug): #96799, #96808, #96810.

To fully confirm the trigger on the specific Expensifail account, check its betas Onyx value (does rulesRevamp resolve on?) and whether rulesRevamp is explicitOnly in the server beta config.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/96816) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

[mollfpr]

The offending PR has been reverted in #96852. This should be resolved once the revert is deployed to staging.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

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]

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.