[$250] Workspace - "Workspace currency not supported" help link does not show supported currencies

[izarutskaya]

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.66-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @gijoe0295
Slack conversation (hyperlinked to channel name): #expensify_bugs

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Set workspace currency to one that is not supported by global reimbursements (VND or SGD for example)
3. Go to Workflows > Add bank account
4. Tap "list of supported currencies" hyperlink in "Workspace currency not supported" modal

Expected Result:

The help site should contain information about supported currencies
Or the help site in the modal should be https://help.expensify.com/articles/new-expensify/wallet-and-payments/Enable-Global-Reimbursement that already has that information

Actual Result:

The hyperlinked help site https://help.expensify.com/articles/new-expensify/wallet-and-payments/Connect-a-Business-Bank-Account does not contain information about supported currencies

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

Screen.Recording.2026-04-29.at.11.21.34.mov

Recording.3728.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @dangrous

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022051318847826774287
• Upwork Job ID: 2051318847826774287
• Last Price Increase: 2026-05-04

[MelvinBot]

Proposal

What is the root cause of that problem?

The "Workspace currency not supported" modal links to the wrong help article. The modal's "list of supported currencies" hyperlink uses CONST.CONNECT_A_BUSINESS_BANK_ACCOUNT_HELP_URL, which points to the "Connect a Business Bank Account" article — that article does not list supported currencies.

The correct target is the "Enable Global Reimbursement" article, which explicitly lists the supported currencies (USD, CAD, GBP, EUR, AUD).

Code references

• The URL constant is defined at CONST/index.ts:1222 as https://help.expensify.com/articles/new-expensify/expenses-&-payments/Connect-a-Business-Bank-Account
• The English translation using it is at en.ts:6502: Your workspace is set to an unsupported currency. View the <a href="...">list of supported currencies</a>.
• All 10 language files reference the same constant
• The correct article at Enable-Global-Reimbursement.md lists supported currencies on line 10-15

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

Update the value of CONNECT_A_BUSINESS_BANK_ACCOUNT_HELP_URL in src/CONST/index.ts to point to the Enable Global Reimbursement article: https://help.expensify.com/articles/new-expensify/wallet-and-payments/Enable-Global-Reimbursement. This constant is only used in the yourWorkspace translation strings, so changing its value won't break anything else.

Alternatively, if the existing constant name feels misleading after the URL change, create a new constant (e.g., GLOBAL_REIMBURSEMENT_SUPPORTED_CURRENCIES_URL) and update all 10 language files to reference it instead.

What alternative solutions did you explore? (Optional)

An alternative would be to update the "Connect a Business Bank Account" help article itself to include supported currencies. However, that article serves a different purpose (bank account connection steps), and the Enable Global Reimbursement article already has the correct content, so updating the link is the simpler and more correct fix.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @ikevin127 (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022051318847826774287

[wildan-m]

Proposal

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

In the Workflows section of a workspace whose currency is not supported by global reimbursements (e.g. VND, SGD), tapping "Add bank account" opens a modal that says: "Your workspace is set to an unsupported currency. View the list of supported currencies." The "list of supported currencies" hyperlink points to the Connect a Business Bank Account help article, which only documents US bank accounts and does not list which currencies are supported. Users following the link cannot find the information the modal promised.

What is the root cause of that problem?

The hyperlink in the modal is generated from the bankAccount.error.yourWorkspace translation, which embeds CONST.CONNECT_A_BUSINESS_BANK_ACCOUNT_HELP_URL:

App/src/languages/en.ts

Line 6502 in 54a5b1b

yourWorkspace: `Your workspace is set to an unsupported currency. View the <a href="${CONST.CONNECT_A_BUSINESS_BANK_ACCOUNT_HELP_URL}">list of supported currencies</a>.`,

That constant is defined here and points to the Connect a Business Bank Account article:

App/src/CONST/index.ts

Line 1222 in 54a5b1b

CONNECT_A_BUSINESS_BANK_ACCOUNT_HELP_URL: 'https://help.expensify.com/articles/new-expensify/expenses-&-payments/Connect-a-Business-Bank-Account',

The Connect a Business Bank Account article scope is explicitly limited to US bank accounts, so it does not enumerate the currencies supported by global reimbursements. The article that actually lists the supported currencies and explains how to enable reimbursements in non-USD currencies is Enable Global Reimbursement (https://help.expensify.com/articles/new-expensify/wallet-and-payments/Enable-Global-Reimbursement). The link text ("list of supported currencies") and the modal context (workspace currency not supported) both point to the Enable Global Reimbursement article being the correct destination, but the constant was wired to the wrong article.

The constant is consumed only by the bankAccount.error.yourWorkspace translation key (verified via repo-wide search), so changing where it points has no other UI side effects.

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

Update the help URL embedded in the "Workspace currency not supported" modal so that the "list of supported currencies" hyperlink points to the Enable Global Reimbursement help article, which actually lists the supported currencies and walks the user through enabling reimbursements in those currencies.

Concretely, change the value of CONST.CONNECT_A_BUSINESS_BANK_ACCOUNT_HELP_URL to https://help.expensify.com/articles/new-expensify/wallet-and-payments/Enable-Global-Reimbursement. Because the constant is used only by this one translation key, no other call sites need to be touched. The constant name itself is internal; renaming it (for example to ENABLE_GLOBAL_REIMBURSEMENT_HELP_URL) is optional cleanup that can be done in the same PR — preferable, since the new value no longer matches the old name. All ten language variants of bankAccount.error.yourWorkspace reference the same constant, so every locale picks up the corrected link automatically without translation churn.

After the change, opening the modal on a workspace with an unsupported currency and tapping the link lands the user on the Enable Global Reimbursement article, which clearly enumerates the supported currencies (USD, CAD, GBP, EUR, AUD, SGD) — matching what the link text promises.

Compare branch: https://github.com/Expensify/App/compare/main...wildan-m:App:wildan/89516-fix-currency-help-link?expand=1

What alternative solutions did you explore? (Optional)

Replacing the link text and target with a per-locale rewrite of the entire sentence was considered but rejected — the modal copy itself is fine, only the destination URL is wrong, and a one-constant change avoids touching ten translation files.

Adding a new constant alongside the existing one (instead of repurposing it) was also considered, but since the existing constant has exactly one consumer and that consumer is the broken link, repurposing keeps the diff minimal and removes the risk of the old, incorrect URL lingering for some future caller to accidentally reuse.

[oqildev]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[github-actions]

⚠️ @oqildev Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.

[wildan-m]

Proposal updated — added compare branch with implementation.