78309: Added top Spenders default report

[abbasifaizan70]

Explanation of Change

This PR will add a new default report called Top Spenders to the Reports page.

Fixed Issues

$ #78309
PROPOSAL: #78309 (comment)

Tests

Test 1: Verify Role-Based Visibility and Section Display

1. Log in as a user who is a regular member (not admin/auditor/approver) on all workspaces
2. Navigate to the Reports page
3. Verify the "Insights" section does NOT appear in the LHN
4. Have a workspace admin assign you an Admin, Auditor, or Approver role
5. Refresh the page
6. Verify the "Insights" section now appears above the "Explore" section in the LHN
7. Verify "Top spenders" is listed under the Insights section with a MoneyBag icon
8. Verify the section order is: To-do → Accounting → Saved → Insights → Explore

Test 2: Verify Top Spenders Query Execution and Data Display

1. As an admin/auditor/approver, navigate to the Reports page
2. Click on "Top spenders" in the Insights section
3. Verify the search query displays: type:expense group-by:from date:last-month sort-by:groupTotal sort-order:desc
4. Verify results show expenses grouped by person (submitter) with avatar, name, number of expenses, and total amount
5. Verify only expenses from last month are shown
6. Verify results are sorted by total amount in descending order (highest spender at top)
7. Apply a workspace filter and verify results update to show only that workspace's top spenders
8. Click on a grouped row and verify individual expenses expand correctly

Test 3: Verify Empty State and Cross-Platform Compatibility

1. As an admin on a workspace with no expenses from last month, click "Top spenders"
2. Verify empty state displays title "Nothing to show" and subtitle "Try adjusting your search criteria or creating something with the + button."
3. Test on mobile web (hamburger menu), desktop app, iOS app, and Android app
4. Verify on each platform that:
5. Insights section appears correctly in the navigation
6. Top spenders report loads and displays results properly
7. Empty state renders correctly when no data exists
8. Change language to Español and verify translations show "Información" (section) and "Mayores gastadores" (report name)

• Verify that no errors appear in the JS console

Offline tests

same as tests.

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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • 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

Android: Native

Screen.Recording.2026-01-01.at.7.41.38.PM.mov

Android: mWeb Chrome

Screen.Recording.2026-01-01.at.7.36.30.PM.mov

---

Screen.Recording.2026-01-01.at.7.37.25.PM.mov

iOS: Native

Screen.Recording.2026-01-01.at.7.26.24.PM.mov

---

Screen.Recording.2026-01-01.at.7.27.14.PM.mov

iOS: mWeb Safari

Screen.Recording.2026-01-01.at.6.59.48.PM.mov

---

Screen.Recording.2026-01-01.at.6.59.07.PM.mov

MacOS: Chrome / Safari

Test Case # 01

Screen.Recording.2026-01-05.at.4.15.10.PM.mov

---

Test Case # 02

---

Test Case # 03

---

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

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/CONST/index.ts	83.47% <ø> (ø)
src/libs/SearchQueryUtils.ts	69.73% <100.00%> (ø)
...nents/Search/SearchPageHeader/SearchFiltersBar.tsx	68.12% <0.00%> (ø)
src/libs/SearchUIUtils.ts	59.32% <88.23%> (+0.40%)	⬆️
... and 7 files with indirect coverage changes

[melvin-bot]

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

[puneetlath]

@mananjadhav have you had a chance to do an initial review?

[github-actions]

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

[mananjadhav]

I was out sick, I'll start reviewng the PR .

[mananjadhav]

Left small comments.

[mananjadhav]

@abbasifaizan70 Can you confirm if it is working for all the platforms? I can see the screencasts are missing for all except web.

[abbasifaizan70]

@mananjadhav added screenshots for other platforms and resolved feedback as well. Thanks

[mananjadhav]

@abbasifaizan70 Responded to the comments.

[abbasifaizan70]

@mananjadhav solved feedback.

[mananjadhav]

@abbasifaizan70 I think you missed my comment here and here

[abbasifaizan70]

@abbasifaizan70 I think you missed my comment here and here

@mananjadhav Really sorry, I missed your comment earlier—I’ve replied in the thread now. Thanks!

[mananjadhav]

@abbasifaizan70 Thanks for the changes. Checking.

But quick things:

1. The screenshots for the platforms are not updated with the latest cion.
2. The screenshots for Android doesn't look like Android emulator? Can you post the full recording?
3. The screenshot for iOS is broken.

I think it'll be best to add videos instead for all the platforms and not just screenshots.

[abbasifaizan70]

@abbasifaizan70 Thanks for the changes. Checking.

But quick things:

1. The screenshots for the platforms are not updated with the latest cion.
2. The screenshots for Android doesn't look like Android emulator? Can you post the full recording?
3. The screenshot for iOS is broken.

I think it'll be best to add videos instead for all the platforms and not just screenshots.

Sure, let me update all with Vidoes. Thanks

[trjExpensify]

Right, the Top Spenders report should remain sorted by the groupTotal when you change the other filter. 👍

[abbasifaizan70]

@puneetlath @trjExpensify Update the short-by consistency issue. Please have a look. Thanks for your feedback.

Screen.Recording.2026-01-07.at.2.28.34.PM.mov

[trjExpensify]

Video looks good to me 👍

[puneetlath]

@mananjadhav can you give the PR a review?

[mananjadhav]

I reviewed the code. I am currently testing it. Basic test on web looks okay. I'll finish the checklist by IST morning.

[puneetlath]

Great, thanks!

[mananjadhav]

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
• I verified tests pass on all platforms & I tested again on:
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I verified proper code patterns were followed (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 verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• 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
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• 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 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.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

android-top-spenders.mov

Android: mWeb Chrome

mweb-chrome-top-spenders.mov

iOS: HybridApp

ios-top-spenders.mov

iOS: mWeb Safari

mweb-safari-top-spenders.mov

MacOS: Chrome / Safari

web-top-spenders.mov

[puneetlath]

Nice job!

[OSBotify]

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.2.96-1 🚀

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

[lanitochka17]

@abbasifaizan70 Should be with unreported expenses? Think about unreported expenses not being displayed on “Top Spender” is that only admin/approver of a workspace is able to see that section and that section only appears with workspace creation

[abbasifaizan70]

@lanitochka17 No, unreported expenses shouldn't show in "Top Spenders" - and that's intentional.
Unreported expenses are personal/private. Admins and approvers can only see expenses that have been submitted to their workspace. Showing someone's private expenses to a workspace admin would be a privacy issue.
That's also why the section only appears for admins/approvers on a paid workspace - it's meant to show "who's spending the most on my workspace," not everyone's personal expenses.

[lanitochka17]

@abbasifaizan70 thanks for your clarifying

[OSBotify]

🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.96-6 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.96-6 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.96-6 🚀

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