[Insights] Reports-Expense on Sunday is not displayed in groupby list

[mitarachim]

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.11-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #80684
Email or phone of affected tester (no customers): ndk.2303+224@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11 Home/Chrome
App Component: Search

Action Performed:

1. Open https://staging.new.expensify.com/
2. Create an expense (Date: on a Sunday of a week that has not any expense; ex: 7 Sep, 2025)
3. Navigate to Reports
4. Go to Expense section
5. Click on Filter
6. Click on 'Group by' section
7. Select 'Week' and view result
8. Expand the week group that contains the expense

Expected Result:

Expense should be shown on the list of group

Actual Result:

The date of expense (Sep 7, 2025) is grouped in the previous week group (Aug 31 - Sep 6, 2025).
When the row is expanded, the expense is not displayed.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7060819_1769654599148.Sunday_expense_not_shown.mp4

Bug7060819_1769654451891.Sunday_expense_is_misssing.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #80684

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

Triggered auto assignment to @brianlee-expensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[shubham1206agra]

@neil-marcellini @cristipaval @lakchote Another BE issue as I can see the query is correct from FE