You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$175] Day is not mentioned first in Dutch on Sub page #106463
Version Number: 9.5.35-1 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:#105867 Email or phone of affected tester (no customers):applausetester+en@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Macbook Pro 2023 / Tahoe 26.4.1 App Component: User Settings
Action Performed:
Access staging.new.expensify.com
Sign into a valid account with a subscription
Change Language to Dutch and check the next subscription payment
Expected Result:
Subscription and verify the subscription end date reads in German order, for example 20. Juni 2026.
Actual Result:
Sub. date reads the month first (In this case December)
The report also mixes languages: Dutch should read “1 december 2026” for the next payment in December, not use the German example “20. Juni 2026.”
What changes do you think we should make in order to solve the problem?
No additional implementation is currently warranted. Retest with a subscription-enabled account on a build confirmed to contain the existing fix. If that passes, mark this issue as already addressed.
The QA-linked Localize long dates read from UTC values explicitly excludes next billing. Its association with this report does not establish an introduced regression.
An earlier deployment notice said the fix had not yet reached staging. This supports—but does not prove—a build-version explanation.
Confidence: High that the inspected code contains the targeted fix; deployed behavior remains unverified.
Signed-in access and selecting Nederlands succeeded. The account had no Subscription entry, so next-payment formatting could not be verified. No purchase or payment data was added.
Step
Status
Access signed-in AppAuthenticated Home and Profile were accessible.
✅
Change language to NederlandsRead-back confirmed Nederlands and Dutch labels; Deutsch was not selected.
✅
Verify Dutch next-payment dateBlocked: Subscription was absent from the account menu; date ordering remains unverified.
❌
Next Steps for Contributor+ team: Retest the existing fix before requesting another implementation. To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin’s proposal.
which uses Intl.DateTimeFormat(dateFnsLocale?.code ?? 'en-US', {year: 'numeric', month: 'long', day: 'numeric', timeZone: 'UTC'}). For Dutch (nl), Intl.DateTimeFormat formats the date as 1 december 2026 (day first).
When an active subscription has an endDate, it still uses format(..., CONST.DATE.MONTH_DAY_YEAR_ORDINAL_FORMAT, {locale: dateFnsLocale}). MONTH_DAY_YEAR_ORDINAL_FORMAT is hardcoded as MMMM do, yyyy, forcing month-first formatting across all languages including Dutch and German.
What changes do you think we should make in order to solve the problem?
In src/pages/workspace/DynamicWorkspaceOverviewPlanTypePage.tsx:
Replace the hardcoded format(..., CONST.DATE.MONTH_DAY_YEAR_ORDINAL_FORMAT, ...) with DateUtils.formatToLongDate(parseISO(privateSubscription.endDate), dateFnsLocale) so that subscription renewal dates always follow the localized component ordering for Dutch, German, Spanish, etc.
In src/pages/settings/Subscription/CardSection/utils.ts:
Please re-state the problem that we are trying to solve in this issue.
On the Settings > Subscription page (and Workspace > Plan Type page), when the application language is set to Dutch (Nederlands), the subscription payment and renewal dates are displayed with the month first (e.g. december 1, 2026) instead of adhering to the Dutch date format with the day first (e.g. 1 december 2026).
What is the root cause of that problem?
There are two core factors contributing to this behavior:
Staging Build Deployment Timing:
In src/pages/settings/Subscription/CardSection/utils.ts (getNextBillingDate), date formatting previously relied on format(nextBillingDate, CONST.DATE.MONTH_DAY_YEAR_FORMAT, {locale: dateFnsLocale}), which strictly enforced US month-first ordering (CONST.DATE.MONTH_DAY_YEAR_FORMAT).
PR #105869 migrated getNextBillingDate to delegate to DateUtils.formatToLongDate(nextBillingDate, dateFnsLocale). In DateUtils.formatToLongDate, memoizedCreateLongDateFormatter(dateFnsLocale?.code ?? 'en-US') uses Intl.DateTimeFormat with {year: 'numeric', month: 'long', day: 'numeric', timeZone: 'UTC'}, which formats Dutch (nl) dates correctly as 1 december 2026.
When an active subscription has an endDate, it formats the renewal date with CONST.DATE.MONTH_DAY_YEAR_ORDINAL_FORMAT ('MMMM do, yyyy'). This hardcodes month-first ordering regardless of dateFnsLocale, reproducing the exact same bug on the workspace plan type screen for Dutch, German, etc.
What changes do you think we should make in order to solve the problem?
In src/pages/workspace/DynamicWorkspaceOverviewPlanTypePage.tsx:
Update autoRenewalDate calculation to use locale-aware long date formatting:
This ensures consistent localized day-first ordering for Dutch (1 december 2026), German, Spanish, etc., while preserving US conventions where appropriate.
In src/pages/settings/Subscription/CardSection/utils.ts:
What alternative solutions did you explore? (Optional)
Creating custom date-fns format strings per locale, but delegating to DateUtils.formatToLongDate is the standardized, memoized pattern across the app using Intl.DateTimeFormat.
Tests
Go to Settings > Preferences > Language and select Nederlands.
Go to Settings > Subscription.
Verify the next payment date in the subtitle displays day-first (e.g. 1 december 2026 rather than december 1, 2026).
Go to Workspace Settings > Overview / Plan Type with an active subscription.
Verify the renewal date also displays day-first in Dutch.
Switch language back to English and verify dates display in standard US format (December 1, 2026).
Please re-state the problem that we are trying to solve in this issue.
On the Subscription page, when the app language is set to Dutch (nl), the subscription renewal / end date displays the month first instead of the day first (e.g. displaying month before day rather than "20 december 2026").
What is the root cause of that problem?
In the subscription details components (src/pages/settings/Subscription/), the subscription renewal date is formatted using a hardcoded date format (such as CONST.DATE.MONTH_DAY_YEAR_FORMAT / 'MMMM d, yyyy') or DateUtils.formatToReadableString without applying locale-aware date ordering for Dutch (nl), where standard convention requires day-first formatting (d MMMM yyyy).
What changes do you think we should make in order to solve the problem?
In src/libs/DateUtils.ts, ensure subscription date formatting utilizes date-fns/format with locale support or uses a localized date formatter (e.g. formatToLongDate(date, preferredLocale)):
For Dutch (nl), use day-first pattern ('d MMMM yyyy').
For English (en), preserve month-first pattern ('MMMM d, yyyy').
In src/pages/settings/Subscription/SubscriptionDetails.tsx and related subscription size/pricing cards, pass preferredLocale into the date formatting helper so the renewal date dynamically formats according to the selected user language.
What alternative solutions did you explore? (Optional)
Hardcoding a one-off string replacement in the subscription card: Rejected because date formatting should follow Expensify's centralized i18n date utility architecture.
What automated tests can you add to prevent this from re-occurring?
In tests/unit/DateUtilsTest.ts:
Add a unit test verifying that formatting a date with locale 'nl' places the day first (e.g. '20 december 2026') and with locale 'en' formats with month first (e.g. 'December 20, 2026').
Activity
applause-bot commentedon Nov 10, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/862410b6fc477f6109eb7386eaa7530d20d7f25c61e8fe502b8d59b050acc42c
https://platform.applause.com/services/links/v1/external/3f15203075466267972810924b7f9307fea36381d441106f64eb8d3f32b3acbd
melvin-bot commentedon Nov 10, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @TaduJR (
External)[-]Day is not mentioned first in Dutch on Sub page[/-][+][$175] Day is not mentioned first in Dutch on Sub page[/+]melvin-bot commentedon Nov 10, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022120085437561400453
MelvinBot commentedon Nov 10, 2026
Proposal
What is the root cause of that problem?
The next-payment date previously used a fixed month-first format, translating the month name without changing its position.
This is already addressed in merged Localize readable long dates and the next billing date. The fix is present in the inspected code; whether it reached the reported build remains unverified.
The report also mixes languages: Dutch should read “1 december 2026” for the next payment in December, not use the German example “20. Juni 2026.”
What changes do you think we should make in order to solve the problem?
No additional implementation is currently warranted. Retest with a subscription-enabled account on a build confirmed to contain the existing fix. If that passes, mark this issue as already addressed.
Code evidence and alternative explanations
CardSection.tsx:137–143.getNextBillingDate:213–218now delegates to the locale-awareformatToLongDate:1187–1208, rather than imposing month-first ordering.Confidence: High that the inspected code contains the targeted fix; deployed behavior remains unverified.
Related tracking: Fix localization: dates not being localized correctly and Display formats hardcode US date and time conventions.
Web verification evidence
🤖 Web test steps verification results:⚠️ partial
Signed-in access and selecting Nederlands succeeded. The account had no Subscription entry, so next-payment formatting could not be verified. No purchase or payment data was added.
Access signed-in App
Authenticated Home and Profile were accessible.Change language to Nederlands
Read-back confirmed Nederlands and Dutch labels; Deutsch was not selected.Verify Dutch next-payment date
Blocked: Subscription was absent from the account menu; date ordering remains unverified.Next Steps for Contributor+ team: Retest the existing fix before requesting another implementation.
To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin’s proposal.
view run
kevinjosh10 commentedon Nov 10, 2026
Proposal
What is the root cause of that problem?
There are two distinct parts to this issue:
Staging Build Version / Missing Merge Window:
src/pages/settings/Subscription/CardSection/utils.ts(getNextBillingDate), the date formatting previously used:CONST.DATE.MONTH_DAY_YEAR_FORMAT).Localize readable long dates and the next billing date) migratedgetNextBillingDateto use:Intl.DateTimeFormat(dateFnsLocale?.code ?? 'en-US', {year: 'numeric', month: 'long', day: 'numeric', timeZone: 'UTC'}). For Dutch (nl),Intl.DateTimeFormatformats the date as1 december 2026(day first).9.5.35-1. Commit history shows tag9.5.35-1was built prior to PR Localize readable long dates and the next billing date #105869 being merged into staging.Unlocalized Date Formatting in
DynamicWorkspaceOverviewPlanTypePage.tsx:src/pages/workspace/DynamicWorkspaceOverviewPlanTypePage.tsx:107-109:endDate, it still usesformat(..., CONST.DATE.MONTH_DAY_YEAR_ORDINAL_FORMAT, {locale: dateFnsLocale}).MONTH_DAY_YEAR_ORDINAL_FORMATis hardcoded asMMMM do, yyyy, forcing month-first formatting across all languages including Dutch and German.What changes do you think we should make in order to solve the problem?
src/pages/workspace/DynamicWorkspaceOverviewPlanTypePage.tsx:format(..., CONST.DATE.MONTH_DAY_YEAR_ORDINAL_FORMAT, ...)withDateUtils.formatToLongDate(parseISO(privateSubscription.endDate), dateFnsLocale)so that subscription renewal dates always follow the localized component ordering for Dutch, German, Spanish, etc.src/pages/settings/Subscription/CardSection/utils.ts:getNextBillingDatedelegates toDateUtils.formatToLongDate(nextBillingDate, dateFnsLocale)as introduced in PR Localize readable long dates and the next billing date #105869.1 december 2026is correctly displayed on Settings > Subscription in Dutch (nl).What alternative solutions did you explore? (Optional)
None needed; using
DateUtils.formatToLongDateensures consistentIntl.DateTimeFormatlocalized date ordering everywhere subscription dates are shown.Tests
1 december 2026).Contributor details
Your Expensify account email: lkevinjosh10@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~0131dae36abcf59374
melvin-bot commentedon Nov 10, 2026
✅ Contributor details stored successfully. Thank you for contributing to Expensify!
melvin-bot commentedon Nov 10, 2026
✅ Contributor details stored successfully. Thank you for contributing to Expensify!
jmquero92 commentedon Nov 10, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
On the Settings > Subscription page (and Workspace > Plan Type page), when the application language is set to Dutch (Nederlands), the subscription payment and renewal dates are displayed with the month first (e.g.
december 1, 2026) instead of adhering to the Dutch date format with the day first (e.g.1 december 2026).What is the root cause of that problem?
There are two core factors contributing to this behavior:
Staging Build Deployment Timing:
src/pages/settings/Subscription/CardSection/utils.ts(getNextBillingDate), date formatting previously relied onformat(nextBillingDate, CONST.DATE.MONTH_DAY_YEAR_FORMAT, {locale: dateFnsLocale}), which strictly enforced US month-first ordering (CONST.DATE.MONTH_DAY_YEAR_FORMAT).getNextBillingDateto delegate toDateUtils.formatToLongDate(nextBillingDate, dateFnsLocale). InDateUtils.formatToLongDate,memoizedCreateLongDateFormatter(dateFnsLocale?.code ?? 'en-US')usesIntl.DateTimeFormatwith{year: 'numeric', month: 'long', day: 'numeric', timeZone: 'UTC'}, which formats Dutch (nl) dates correctly as1 december 2026.9.5.35-1was built before PR Localize readable long dates and the next billing date #105869 landed in the release branch.Hardcoded Month-First Formatting in
DynamicWorkspaceOverviewPlanTypePage.tsx:src/pages/workspace/DynamicWorkspaceOverviewPlanTypePage.tsx:107-109:endDate, it formats the renewal date withCONST.DATE.MONTH_DAY_YEAR_ORDINAL_FORMAT('MMMM do, yyyy'). This hardcodes month-first ordering regardless ofdateFnsLocale, reproducing the exact same bug on the workspace plan type screen for Dutch, German, etc.What changes do you think we should make in order to solve the problem?
In
src/pages/workspace/DynamicWorkspaceOverviewPlanTypePage.tsx:autoRenewalDatecalculation to use locale-aware long date formatting:1 december 2026), German, Spanish, etc., while preserving US conventions where appropriate.In
src/pages/settings/Subscription/CardSection/utils.ts:CardSectionUtils.getNextBillingDatedelegating toDateUtils.formatToLongDate(nextBillingDate, dateFnsLocale)as introduced in PR Localize readable long dates and the next billing date #105869.What alternative solutions did you explore? (Optional)
Creating custom date-fns format strings per locale, but delegating to
DateUtils.formatToLongDateis the standardized, memoized pattern across the app usingIntl.DateTimeFormat.Tests
1 december 2026rather thandecember 1, 2026).December 1, 2026).Contributor details
Your Expensify account email: jmquero92@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~01ca8ad8ce36b9eceb
melvin-bot commentedon Nov 10, 2026
Details
TassioSales commentedon Nov 10, 2026
Contributor details
Your Expensify account email: tassiolucian.ljs@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~0179cdc82689f205c7
Proposal
Please re-state the problem that we are trying to solve in this issue.
On the Subscription page, when the app language is set to Dutch (
nl), the subscription renewal / end date displays the month first instead of the day first (e.g. displaying month before day rather than "20 december 2026").What is the root cause of that problem?
In the subscription details components (
src/pages/settings/Subscription/), the subscription renewal date is formatted using a hardcoded date format (such asCONST.DATE.MONTH_DAY_YEAR_FORMAT/'MMMM d, yyyy') orDateUtils.formatToReadableStringwithout applying locale-aware date ordering for Dutch (nl), where standard convention requires day-first formatting (d MMMM yyyy).What changes do you think we should make in order to solve the problem?
src/libs/DateUtils.ts, ensure subscription date formatting utilizesdate-fns/formatwith locale support or uses a localized date formatter (e.g.formatToLongDate(date, preferredLocale)):nl), use day-first pattern ('d MMMM yyyy').en), preserve month-first pattern ('MMMM d, yyyy').src/pages/settings/Subscription/SubscriptionDetails.tsxand related subscription size/pricing cards, passpreferredLocaleinto the date formatting helper so the renewal date dynamically formats according to the selected user language.What alternative solutions did you explore? (Optional)
What automated tests can you add to prevent this from re-occurring?
In
tests/unit/DateUtilsTest.ts:'nl'places the day first (e.g.'20 december 2026') and with locale'en'formats with month first (e.g.'December 20, 2026').melvin-bot commentedon Nov 10, 2026
✅ Contributor details stored successfully. Thank you for contributing to Expensify!
expensify-chore-bot commentedon Nov 17, 2026
@TaduJR 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
expensify-chore-bot commentedon Nov 19, 2026
@TaduJR Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!