Skip to content

Add Paid by search filter UI, table column, sorting, and export - #98326

Open
c3024 wants to merge 14 commits into
Expensify:mainfrom
c3024:chaitanya/670393-payer-search-filter
Open

Add Paid by search filter UI, table column, sorting, and export#98326
c3024 wants to merge 14 commits into
Expensify:mainfrom
c3024:chaitanya/670393-payer-search-filter

Conversation

@c3024

@c3024 c3024 commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

  • Adds a new paidBy: filter (also typable as paid-by:, like expense-type:) to the advanced filters and filter bar as a multi-select user filter for expense, expense report, invoice, and trip searches. It matches the user who actually paid a report. The existing payer: filter (the responsible payer, powering the Pay to-do) is unchanged and stays hidden from the filters UI, per the Slack naming decision.
  • Adds a Paid by column to expense report search views, derived from the actor of the latest payment report action in the snapshot (same pattern as First approver), with sorting and CSV export support.

Fixed Issues

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

Tests

  1. Sign in as a workspace member who has paid reports.
  2. Go to Reports > Expense reports and open the columns picker. Enable the Paid by column.
  3. Verify the Paid by column shows the person who paid each paid report and is blank for unpaid reports.
  4. Click the Paid by column header and verify the rows sort by that name.
  5. Open Filters, choose Paid by, select one or more users, and apply.
  6. Verify the results only include reports paid by the selected users (unpaid reports never match), and the filter bar shows a Paid by chip.
  7. Select the paid reports and click on Export from the selected drop down > Current View. Verify the exported file has a Paid by column with the name of the user who paid.
Screen.Recording.2026-08-17.at.3.41.21.PM.mov
  • Verify that no errors appear in the JS console

Offline tests

NA

QA Steps

Same as tests.

  • 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

The payer filter is now shown in the advanced filters and filter bar as a
multi-select user filter, and a Payer column is available on expense report
search views. The column is derived from the actor of the latest payment
report action returned in the search snapshot, matching how First approver
is derived, and is sortable and exportable.
@melvin-bot

melvin-bot Bot commented Aug 11, 2026

Copy link
Copy Markdown

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 ts-node ./scripts/generateTranslations.ts --help

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

@codecov

codecov Bot commented Aug 11, 2026

Copy link
Copy Markdown

c3024 added 8 commits August 12, 2026 13:12
Matches the backend gate on report status, so canceled or reopened reports fall back to having no payer column value.
The payer filter keeps its existing responsible-payer meaning (hidden
from the filters UI as before) and the payment-actor work moves to a
new paidBy filter key, table column, and translations. The paid-by
syntax also accepts paid-by: like the other multi-word keys.
@c3024 c3024 changed the title Add Payer search filter UI, table column, sorting, and export Add Paid by search filter UI, table column, sorting, and export Aug 12, 2026
@quinthar quinthar removed the #migrate label Aug 13, 2026
@melvin-bot

melvin-bot Bot commented Aug 17, 2026

Copy link
Copy Markdown

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

c3024 added 2 commits August 17, 2026 18:21
…r-search-filter

# Conflicts:
#	src/libs/SearchParser/autocompleteParser.js
#	src/libs/SearchParser/searchParser.js
@c3024
c3024 marked this pull request as ready for review August 18, 2026 11:37
@c3024
c3024 requested review from a team as code owners August 18, 2026 11:37
@melvin-bot
melvin-bot Bot requested a review from hoangzinh August 18, 2026 11:37
@melvin-bot

melvin-bot Bot commented Aug 18, 2026

Copy link
Copy Markdown

@hoangzinh 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]

@melvin-bot
melvin-bot Bot requested review from joekaufmanexpensify and removed request for a team August 18, 2026 11:37
Comment thread src/libs/SearchUIUtils.ts Outdated
const formattedTo = !shouldShowBlankTo ? temporaryGetDisplayNameOrDefault({passedPersonalDetails: toDetails, translate, formatPhoneNumber}) : '';
const formattedFirstApprover = firstApproverAccountID ? temporaryGetDisplayNameOrDefault({passedPersonalDetails: firstApproverDetails, translate, formatPhoneNumber}) : '';

// The paid-by user is the actor on the latest payment action; blank until the report is paid.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ CONSISTENCY-16 (docs)

Comments should read like plain, natural sentences. This comment joins two clauses with a semicolon instead of using two separate sentences, which CONSISTENCY-16 flags.

Split it into two sentences:

// The paid-by user is the actor on the latest payment action. It stays blank until the report is paid.
const lastReimbursedAction = lastReimbursedActionByReportID.get(reportItem.reportID);

Reviewed at: 03abca5 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 03abca58f7

ℹ️ 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".

const FILTER_COMPONENT_MAP: Partial<Record<SearchFilter['key'], React.ComponentType<DropdownProps>>> = {
[CONST.SEARCH.SYNTAX_FILTER_KEYS.FROM]: UserDropdown,
[CONST.SEARCH.SYNTAX_FILTER_KEYS.TO]: UserDropdown,
[CONST.SEARCH.SYNTAX_FILTER_KEYS.PAID_BY]: UserDropdown,

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve paid-by IDs for the user dropdown

When a Paid by filter is applied, getDisplayValue() does not classify PAID_BY/PAID_BY_NOT with the other user filters, so it joins the account-ID array into a string before this mapping passes it to UserDropdown. useFilterUserValue() explicitly returns no names for non-array input, leaving the Paid by filter chip/dropdown value blank even though the filter is active. Preserve the ID array for both paid-by keys as is done for From and To.

Useful? React with 👍 / 👎.

Comment thread src/libs/SearchUIUtils.ts
Comment on lines +5422 to +5425
[CONST.SEARCH.SYNTAX_FILTER_KEYS.PAID_BY]: {
labelKey: 'search.filters.paidBy',
icon: 'MoneyBag',
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Render paid-by values through the user formatter

Adding Paid by to FILTER_VIEW_MAP makes it appear in the applied-filters list on the save-search page, but SearchSavePage.FilterValue does not recognize this key as a user filter. Consequently, saving a search with Paid by selected displays raw account IDs rather than the users' names; route PAID_BY through FilterUserValue alongside From, To, Attendee, and Assignee.

Useful? React with 👍 / 👎.

@shawnborton

Copy link
Copy Markdown
Contributor

Let us know when you have videos to review.

@joekaufmanexpensify joekaufmanexpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great addition. Excited for this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants