[Payment due @dmkt9] Allow manual reimbursement workspaces to set and use a preferred payer

[NikkiWines]

Explanation of Change

Updates the UI so that manual/indirect payment workspaces (reimburseManual) can now use a preferred payer, the same way direct payment workspaces (reimburseYes) already could.

Fixed Issues

$ Part 2 of 2 for https://github.com/Expensify/Expensify/issues/637864
PROPOSAL: N/A internal

Tests

Setup

1. Create a workspace with 2+ admins (Admin A, Admin B) and 1 employee
2. Ensure "Make or track payments" is enabled
3. Ensure no bank account is connected

Test 1: Payer picker in manual mode

1. Log in as Admin A and navigate to Workspace Settings → Workflows
2. Under "Payments" confirm that a Payer field appears (no bank account needed)
3. Tap Payer → confirmadmins list shows
4. Select Admin B → confirm Payer field updates Admin B's name

Test 2: Only the designated payer sees Pay GBR

1. Have the employee submit an expense report and have Admin A approve it
2. Log in as Admin B (designated payer)
3. Confirm they see a GBR on the Inbox page and a Pay button next to the workspace chat
4. Confirm they see a Pay option on the report preview
5. Log in as Admin A (non-payer)
6. Confirm they do not see a GBR on the Inbox pay and a Pay button next to the workspace chat
7. Confirm the do see a Pay option on the report preview, like the payer does.

(Payer left, Non-Payer right)

8. Open the report as Admin B (payer) and confirm the Next Steps message says: Waiting for you to pay expenses. and the option to pay the report
9. Open the report as Admin A (non-payer) and confirm the Next Steps message says Waiting for <Admin B> to pay expenses. and confirm they do see the option to pay the report

(Payer left, Non-Payer right)

Test 3: Home Action Items

1. Log in as Admin B (payer) and open the Home page
2. Confirm you see an item under For you notifying you to pay the report
3. Log in as Admin A (non-payer) and open the Home Page
4. Confirm you do not see an item under For you to pay the report

(Payer left, Non-Payer right)

Test 4: Spend Page Action Items

1. Log in as Admin B (payer) and open the Spend page
2. Confirm you see an item under Ready to Pay notifying you to pay the report
3. Log in as Admin A (non-payer) and open the Home Page
4. Confirm you do not see an item under Ready to pay to pay the report

(Payer left, Non-Payer right)

Test 5: Switching payers with bank account requires sharing

1. Log in as Admin A and set yourself as the payer for the workspace
2. Connect a bank account
3. Switch the payer to Admin B (who has not had the bank account shared) and press "Save"
4. Confirm you see the modal stating that you'll need to share the bank account to continue
5. Disconnect the bank account under Workflows
6. Refresh the page
7. Set Admin B as the payer and confirm no modal appears
8. Reconnect to the bank account
9. Confirm the payer is automatically switched to Admin A

• Verify that no errors appear in the JS console

Offline tests

Offline behaviors are unchanged from current behaviors

QA Steps

Same as test steps

• 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 any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • 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)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• 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)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• 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.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• 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

MacOS: Chrome / Safari

Screen.Recording.2026-06-17.at.18.30.07.mov

[melvin-bot]

@mjasikowski Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[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/libs/PolicyUtils.ts	77.17% <100.00%> (-0.05%)	⬇️
src/libs/ReportPreviewActionUtils.ts	92.92% <100.00%> (+0.06%)	⬆️
src/libs/ReportPrimaryActionUtils.ts	93.10% <100.00%> (+0.02%)	⬆️
src/libs/actions/IOU/ReportWorkflow.ts	79.16% <100.00%> (+<0.01%)	⬆️
src/hooks/useResetBankAccountModal.tsx	0.00% <0.00%> (ø)
src/libs/ReportUtils.ts	86.15% <92.85%> (-0.01%)	⬇️
...s/workspace/members/WorkspaceMemberDetailsPage.tsx	0.00% <0.00%> (ø)
src/components/KYCWall/BaseKYCWall.tsx	27.48% <0.00%> (ø)
...ctions/ReimbursementAccount/resetUSDBankAccount.ts	58.82% <50.00%> (-2.72%)	⬇️
...c/pages/workspace/upgrade/WorkspaceUpgradePage.tsx	39.36% <0.00%> (-0.22%)	⬇️
... and 3 more
... and 14 files with indirect coverage changes

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6bac69bd50

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[NikkiWines]

Let's have a C+ review this too, I'll ask in the room

[NikkiWines]

conflicts resolved! This oxfmt check failing appears to be due to a style change, applied the fix in a single comment, so it's easy to review so I'm going to commit it to another branch so tha it doesn't make our changes here harder to review

[NikkiWines]

@mjasikowski once more please 🙇

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[github-actions]

🚧 mjasikowski has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #92787.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-0089f8d12d3-163e75a-09c9c5b4ef34a5e22121d06788e6c9a4035d3ec2/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-0089f8d-163e75a-13b87723a63404f874decf6c092a99976786c786/index.html

Web 🕸️
https://92787.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/mjasikowski in version: 9.4.29-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[MelvinBot]

📝 Help site review — changes required

This PR lets manual/indirect payment (reimburseManual, "Mark as Paid") workspaces set and use a preferred Authorized payer, which previously required a connected bank account. The Payer field now appears on the Workflows tab whenever Payments is enabled, and only the designated payer is prompted to pay.

The existing help article Workspace-Workflows.md documented Mark as Paid but didn't mention that an authorized payer can now be set without a bank account, so a docs update is warranted.

Draft PR: #95525

What the docs PR changes

Updated docs/articles/new-expensify/workspaces/Workspace-Workflows.md:

• Added How to choose an authorized payer without a connected bank account — the Payer field is now available when Payments is enabled, even with no bank account.
• Added What happens after you set an authorized payer — only the authorized payer is prompted to pay (payment reminder in the Inbox and a Pay button next to the workspace chat); other admins can still pay a report but aren't prompted.
• Added authorized payer, mark as paid, and payer keywords.

UI labels verified against the current App UI / language files, following HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md.

@NikkiWines, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

[lanitochka17]

Deploy Blocker #95535 was identified to be related to this PR.

[jponikarchuk]

Deploy Blocker #95561 was identified to be related to this PR.

[lanitochka17]

Deploy Blocker #95626 was identified to be related to this PR.

[OSBotify]

🚀 Deployed to staging by https://github.com/mjasikowski in version: 9.4.31-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[OSBotify]

🚀 Deployed to production by https://github.com/grgia in version: 9.4.31-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android

[melvin-bot]

🤖 Payment issue created: #95678