[$250] Incorrect report start date reflects in report title, date displays previous day

[lanitochka17]

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.2.12-3
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: #69147
Email or phone of affected tester (no customers): applausetester+ck91125@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition: Account setup for BETA access on OD

1. Navigate to staging.new.expensify.com
2. Go to Workspaces settings page
3. Go to Reports section
4. Edit Default report title with:
   {report:type} - {report:total} from {report:policyname} on {report:startdate}
5. Save the formula
6. Create new report via FAB
7. Add at least one expense transaction
8. Observe the report title - Start date shows previous day
9. Go back to expense preview & back to details page
10. Observe correct date get reflected

Expected Result:

On step 8 - Correct current report date should display. In may case, date should be 2025-09-11, but it shows as 2025-09-10

Actual Result:

1. Incorrect report start date reflects in report title, date displays previous day
2. Also, "Custom" word missing in report title. Title displayed as "Expense Report - USD$X.XX from [WorkspaceName] on [StartDate]".
   Note: Issue happens with "Test case 7 - Transactions" scenario too the report formula "Report from {report:startdate}" - Incorrect transaction dates which are previous dates are reflected when submitting expenses in offline mode (Please check the arttached mweb recording)

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6942173_1757630434495.Recording__4.mp4

Bug6942173_1757635396555.Screenrecording_09-11-2025_19-49-20_1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @suneox

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021968726932100348110
• Upwork Job ID: 1968726932100348110
• Last Price Increase: 2025-09-25

[melvin-bot]

Triggered auto assignment to @heyjennahay (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.

[melvin-bot]

Triggered auto assignment to @aldo-expensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

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

[neil-marcellini]

This only happens under a beta. It's not the deploy blocker.