NetSuite: let admins pick the account that currency conversion fees post to

[ishpaul777]

Explanation of Change

When a cross-border reimbursement runs and the company is paying the currency conversion cost, Integration-Server posts an extra journal entry that debits an expense account the admin chooses. The setting and the OldDot picker for this already shipped in Web-Expensify#55599. This PR adds the equivalent picker to the NewDot NetSuite Advanced page.

The picker sits on the Advanced page next to the Collection Account setting, and is only shown when Sync Reimbursed Reports is on (the journal entry only posts alongside a bill payment) and the globalReimbursementFX beta is enabled. The option list reads options.data.expenseAccounts, which Integration-Server syncs; the App side does not need to filter by account type since that list is already pre-filtered server-side.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/672454
PROPOSAL:

Tests

1. Enable the globalReimbursements and globalReimbursementFX betas for your account.
2. Connect a policy to NetSuite and run a sync, so that options.data.expenseAccounts is populated.
3. Open the policy's NetSuite connection settings and go to the Advanced tab.
4. Turn on Sync Reimbursed Reports and confirm a Currency Conversion Fee Account row appears below Collection Account.
5. Tap the row, pick an account from the list, and confirm it saves.
6. Return to the Advanced page and confirm the selected account name is displayed.
7. Turn off Sync Reimbursed Reports and confirm the Currency Conversion Fee Account row is hidden.

• Verify that no errors appear in the JS console

Offline tests

1. Turn off your network connection.
2. Open the Currency Conversion Fee Account picker and select an account.
3. Confirm the selection is applied optimistically and shows a pending state until back online.
4. Restore the network connection and confirm the selection persists (or reverts with an error if the write fails).

QA Steps

Same as Tests section above.

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-08-26.at.1.36.50.PM.mov

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx bun ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx bun ./scripts/generateTranslations.ts --compare-ref main

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/CONST/index.ts	92.59% <ø> (ø)
src/SCREENS.ts	100.00% <ø> (ø)
src/libs/API/types.ts	100.00% <ø> (ø)
...gation/linkingConfig/RELATIONS/WORKSPACE_TO_RHP.ts	100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts	66.66% <ø> (ø)
src/libs/actions/connections/NetSuiteCommands.ts	16.32% <100.00%> (+1.38%)	⬆️
src/ROUTES.ts	26.59% <0.00%> (-0.03%)	⬇️
...gation/AppNavigator/ModalStackNavigators/index.tsx	6.31% <0.00%> (-0.01%)	⬇️
src/libs/PolicyUtils.ts	79.13% <0.00%> (-0.19%)	⬇️
...ounting/netsuite/advanced/NetSuiteAdvancedPage.tsx	0.00% <0.00%> (ø)
... and 1 more
... and 14 files with indirect coverage changes