Skip to content

[Home Page] Surface overdue invoice awareness on Home in New Expensify - #100604

Merged
yuwenmemon merged 10 commits into
Expensify:mainfrom
software-mansion-labs:@adamgrzybowski/overdue-invoice
Sep 16, 2026
Merged

yuwenmemon merged 10 commits into
Expensify:mainfrom
software-mansion-labs:@adamgrzybowski/overdue-invoice

Conversation

@adamgrzybowski

Copy link
Copy Markdown
Contributor

Explanation of Change

  • Adds a "Time sensitive" row on Home, shown to billing owners only, reading "Pay your invoice by [due date] to avoid service interruption" with a Review button.
  • Clicking Review takes the billing owner to the Spend page filtered to Invoices.

Fixed Issues

$ #100140
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Sign in as a billing owner whose subscription invoice is within the billing grace period (payment past due, still within grace).
  2. Go to Home and confirm the "Time sensitive" section shows a row: "Pay your invoice by [date] to avoid service interruption" with an orange Review button and the invoice icon.
  3. Click Review and verify you land on the Spend page filtered to Invoices.
  • 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
Screen.Recording.2026-09-08.at.16.39.03.mov

@melvin-bot

melvin-bot Bot commented Sep 8, 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

@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

Needs the parrot 🙏

@adamgrzybowski
adamgrzybowski marked this pull request as ready for review September 8, 2026 14:56
@adamgrzybowski
adamgrzybowski requested review from a team as code owners September 8, 2026 14:56
@melvin-bot
melvin-bot Bot requested review from brunovjk, dylanexpensify and shawnborton and removed request for a team September 8, 2026 14:56
@melvin-bot

melvin-bot Bot commented Sep 8, 2026

Copy link
Copy Markdown

@shawnborton @brunovjk One of you needs to 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 removed the request for review from a team September 8, 2026 14:56
@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

@MelvinBot can you trigger polyglot parrot?

@MelvinBot

MelvinBot commented Sep 8, 2026 •

Copy link
Copy Markdown
Contributor

I can't trigger it — my token isn't allowed to dispatch workflows (403 Resource not accessible by personal access token), so someone with write access on Expensify/App has to kick it off.

Why it never ran on its own: this PR comes from a fork (software-mansion-labs/expensify-app-fork), and the job skips every fork PR:

.github/workflows/generateTranslations.yml:18

if: ${{ github.event_name == 'workflow_dispatch' || !github.event.pull_request.head.repo.fork }}

Both runs on your branch show skipped for that reason, even though src/languages/en.ts is in the diff: 34241751836, 34240745237.

To run it manually, an engineer with write access can either use the Generate static translations workflow → Run workflow → paste this PR's URL, or run:

gh workflow run generateTranslations.yml --repo Expensify/App \
  -f PULL_REQUEST_URL=https://github.com/Expensify/App/pull/100604

The workflow_dispatch path bypasses the fork check and checks out your head SHA, so it will parrot the translations back here as a comment.


view run · view recording

@shawnborton

Copy link
Copy Markdown
Contributor

I gotchu

@OSBotify

This comment has been minimized.

@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: f940655810

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

@codecov

codecov Bot commented Sep 9, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
...iveSection/hooks/useTimeSensitiveOverdueInvoice.ts 100.00% <100.00%> (ø)
...e/TimeSensitiveSection/items/PayOverdueInvoice.tsx 100.00% <100.00%> (ø)
...ome/TimeSensitiveSection/useTimeSensitiveItems.tsx 75.75% <100.00%> (-0.11%) ⬇️
... and 1501 files with indirect coverage changes

@flaviadefaria
flaviadefaria requested review from flaviadefaria and removed request for dylanexpensify September 9, 2026 13:56
flaviadefaria
flaviadefaria previously approved these changes Sep 9, 2026

@flaviadefaria flaviadefaria 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.

LGTM!

@brunovjk

brunovjk commented Sep 9, 2026 •

Copy link
Copy Markdown
Contributor

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 proper code patterns were followed (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 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)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • 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
    • 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 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.
  • 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
100604_android_native.mov
Android: mWeb Chrome
100604_android_web.mov
iOS: HybridApp
100604_ios_native.mov
iOS: mWeb Safari
100604_ios_web.mov
MacOS: Chrome / Safari
Screen.Recording.2026-09-16.at.11.49.03.mov
Screen.Recording.2026-09-16.at.11.48.26.mov

@brunovjk

brunovjk commented Sep 10, 2026 •

Copy link
Copy Markdown
Contributor

@adamgrzybowski Could you confirm that OWNER_OF_POLICY_UNDER_INVOICING is intentionally used here instead of OWNER_OF_POLICY_UNDER_INVOICING_OVERDUE? My understanding is that this alert is meant to warn the billing owner before the grace period expires, based on the “Pay your invoice by [date] to avoid service interruption” copy.

Apart from that, everything looks good to me. I'm finishing up recording the videos for all the platforms. Done :D

@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

@brunovjk, that's how I understood the issue, but to be extra safe, let's summon @flaviadefaria and @shawnborton.

Is this alert meant to warn the billing owner before the grace period expires? Or after? We assumed that before.

@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

Hmm, but I guess we should keep the alert after and probably change the copy (or not?)

@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

@flaviadefaria, ready to test, but we will need 🦜 once again.

@shawnborton, you were my good spirit last time with translations, so if I could ask you for a favor 🙏

BTW it would be great to get some accounts with real overdue issues to test this code

@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 1c9ccac0..f9431d9d 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -990,7 +990,12 @@ const translations: TranslationDeepObject<typeof en> = {
             },
             addVirtualCardPersonalDetails: {title: 'Fügen Sie Ihre Daten hinzu, um Ihre Expensify Karte anzuzeigen und zu verwenden.', subtitle: 'Expensify Karte', cta: 'Hinzufügen'},
             enterSignerInfo: {title: 'Unterzeichnerdaten erforderlich', subtitle: ({bankAccountLastFour}: {bankAccountLastFour: string}) => `Bankkonto ${bankAccountLastFour}`},
-            payOverdueInvoice: {title: ({date}: {date: string}) => `Bezahlen Sie Ihre Rechnung bis zum ${date}, um Serviceunterbrechungen zu vermeiden`, cta: 'Überprüfen'},
+            payOverdueInvoice: {
+                title: ({date}: {date: string}) => `Bezahlen Sie Ihre Rechnung bis zum ${date}, um Serviceunterbrechungen zu vermeiden`,
+                cta: 'Prüfen',
+                dueSoonTitle: ({date}: {date: string}) => `Bezahlen Sie Ihre Rechnung bis zum ${date}, um eine Unterbrechung des Dienstes zu vermeiden`,
+                overdueTitle: 'Ihre Zahlung ist überfällig, bitte begleichen Sie Ihre Rechnung',
+            },
         },
         discoverSection: {
             title: 'Entdecken',
diff --git a/src/languages/el.ts b/src/languages/el.ts
index a0b4f8cf..868b7f16 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -1033,7 +1033,12 @@ const translations: TranslationDeepObject<typeof en> = {
                 title: 'Απαιτούνται στοιχεία υπογράφοντος',
                 subtitle: ({bankAccountLastFour}: {bankAccountLastFour: string}) => `Τραπεζικός λογαριασμός ${bankAccountLastFour}`,
             },
-            payOverdueInvoice: {title: ({date}: {date: string}) => `Πληρώστε το τιμολόγιό σας έως ${date} για να αποφύγετε τη διακοπή της υπηρεσίας`, cta: 'Έλεγχος'},
+            payOverdueInvoice: {
+                title: ({date}: {date: string}) => `Πληρώστε το τιμολόγιό σας έως ${date} για να αποφύγετε τη διακοπή της υπηρεσίας`,
+                cta: 'Έλεγχος',
+                dueSoonTitle: ({date}: {date: string}) => `Πληρώστε το τιμολόγιό σας έως ${date} για να αποφύγετε τη διακοπή της υπηρεσίας`,
+                overdueTitle: 'Η πληρωμή σας έχει λήξει, παρακαλούμε εξοφλήστε το τιμολόγιό σας',
+            },
         },
         freeTrialSection: {
             title: ({count}: {count: number}) => ({
diff --git a/src/languages/es.ts b/src/languages/es.ts
index ff40ffd4..116a4038 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -986,7 +986,12 @@ const translations: TranslationDeepObject<typeof en> = {
                 personalSubtitle: 'Billetera',
             },
             enterSignerInfo: {title: 'Se necesita la información del firmante', subtitle: ({bankAccountLastFour}: {bankAccountLastFour: string}) => `Cuenta bancaria ${bankAccountLastFour}`},
-            payOverdueInvoice: {title: ({date}: {date: string}) => `Paga tu factura antes del ${date} para evitar la interrupción del servicio`, cta: 'Revisar'},
+            payOverdueInvoice: {
+                title: ({date}: {date: string}) => `Paga tu factura antes del ${date} para evitar la interrupción del servicio`,
+                cta: 'Revisar',
+                dueSoonTitle: ({date}: {date: string}) => `Paga tu factura antes del ${date} para evitar la interrupción del servicio`,
+                overdueTitle: 'Tu pago está vencido, por favor paga tu factura',
+            },
         },
         freeTrialSection: {
             title: ({count}: {count: number}) => ({
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index e9979551..dd71f77d 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -993,7 +993,12 @@ const translations: TranslationDeepObject<typeof en> = {
             },
             addVirtualCardPersonalDetails: {title: 'Ajoutez vos informations pour voir et commencer à utiliser votre Carte Expensify.', subtitle: 'Carte Expensify', cta: 'Ajouter'},
             enterSignerInfo: {title: 'Informations du signataire requises', subtitle: ({bankAccountLastFour}: {bankAccountLastFour: string}) => `Compte bancaire ${bankAccountLastFour}`},
-            payOverdueInvoice: {title: ({date}: {date: string}) => `Payez votre facture avant le ${date} pour éviter une interruption de service`, cta: 'Examiner'},
+            payOverdueInvoice: {
+                title: ({date}: {date: string}) => `Payez votre facture avant le ${date} pour éviter une interruption de service`,
+                cta: 'Examiner',
+                dueSoonTitle: ({date}: {date: string}) => `Payez votre facture avant le ${date} pour éviter une interruption de service`,
+                overdueTitle: 'Votre paiement est en retard, veuillez régler votre facture',
+            },
         },
         discoverSection: {
             title: 'Découvrir',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index b98e32ab..da2debf8 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -991,7 +991,12 @@ const translations: TranslationDeepObject<typeof en> = {
             },
             addVirtualCardPersonalDetails: {title: 'Aggiungi i tuoi dati per visualizzare e iniziare a usare la tua Carta Expensify.', subtitle: 'Carta Expensify', cta: 'Aggiungi'},
             enterSignerInfo: {title: 'Informazioni del firmatario necessarie', subtitle: ({bankAccountLastFour}: {bankAccountLastFour: string}) => `Conto bancario ${bankAccountLastFour}`},
-            payOverdueInvoice: {title: ({date}: {date: string}) => `Paga la tua fattura entro il ${date} per evitare l’interruzione del servizio`, cta: 'Rivedi'},
+            payOverdueInvoice: {
+                title: ({date}: {date: string}) => `Paga la tua fattura entro il ${date} per evitare l’interruzione del servizio`,
+                cta: 'Rivedi',
+                dueSoonTitle: ({date}: {date: string}) => `Paga la tua fattura entro il ${date} per evitare l’interruzione del servizio`,
+                overdueTitle: 'Il tuo pagamento è in ritardo, ti preghiamo di saldare la fattura',
+            },
         },
         discoverSection: {
             title: 'Scopri',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 761971f7..07f68ec7 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -978,7 +978,12 @@ const translations: TranslationDeepObject<typeof en> = {
             },
             addVirtualCardPersonalDetails: {title: 'Expensify カードを表示して利用を開始するには、ご自身の情報を追加してください。', subtitle: 'Expensify カード', cta: '追加'},
             enterSignerInfo: {title: '署名者情報が必要です', subtitle: ({bankAccountLastFour}: {bankAccountLastFour: string}) => `銀行口座 ${bankAccountLastFour}`},
-            payOverdueInvoice: {title: ({date}: {date: string}) => `サービス中断を防ぐために、${date} までに請求書をお支払いください`, cta: '確認'},
+            payOverdueInvoice: {
+                title: ({date}: {date: string}) => `サービス中断を防ぐために、${date} までに請求書をお支払いください`,
+                cta: 'レビュー',
+                dueSoonTitle: ({date}: {date: string}) => `サービス中断を防ぐため、${date}までに請求書をお支払いください`,
+                overdueTitle: 'お支払いの期限が過ぎています。請求書をお支払いください。',
+            },
         },
         discoverSection: {
             title: '発見',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 6b385b0d..9fe6dd34 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -989,7 +989,12 @@ const translations: TranslationDeepObject<typeof en> = {
             },
             addVirtualCardPersonalDetails: {title: 'Voeg je gegevens toe om je Expensify Kaart te bekijken en te gebruiken.', subtitle: 'Expensify Kaart', cta: 'Toevoegen'},
             enterSignerInfo: {title: 'Ondertekenaargegevens vereist', subtitle: ({bankAccountLastFour}: {bankAccountLastFour: string}) => `Bankrekening ${bankAccountLastFour}`},
-            payOverdueInvoice: {title: ({date}: {date: string}) => `Betaal je factuur vóór ${date} om onderbreking van de service te voorkomen`, cta: 'Beoordelen'},
+            payOverdueInvoice: {
+                title: ({date}: {date: string}) => `Betaal je factuur vóór ${date} om onderbreking van de service te voorkomen`,
+                cta: 'Beoordelen',
+                dueSoonTitle: ({date}: {date: string}) => `Betaal je factuur vóór ${date} om onderbreking van de service te voorkomen`,
+                overdueTitle: 'Je betaling is achterstallig, betaal alsjeblieft je factuur.',
+            },
         },
         discoverSection: {
             title: 'Ontdekken',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index ab8c66e0..a0c03464 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -997,7 +997,12 @@ const translations: TranslationDeepObject<typeof en> = {
             },
             addVirtualCardPersonalDetails: {title: 'Dodaj swoje dane, aby wyświetlić i zacząć używać swojej Karty Expensify.', subtitle: 'Karta Expensify', cta: 'Dodaj'},
             enterSignerInfo: {title: 'Wymagane dane podpisującego', subtitle: ({bankAccountLastFour}: {bankAccountLastFour: string}) => `Konto bankowe ${bankAccountLastFour}`},
-            payOverdueInvoice: {title: ({date}: {date: string}) => `Opłać fakturę do ${date}, aby uniknąć przerwy w świadczeniu usług`, cta: 'Przegląd'},
+            payOverdueInvoice: {
+                title: ({date}: {date: string}) => `Opłać fakturę do ${date}, aby uniknąć przerwy w świadczeniu usług`,
+                cta: 'Przejrzyj',
+                dueSoonTitle: ({date}: {date: string}) => `Opłać fakturę do ${date}, aby uniknąć przerwy w świadczeniu usługi`,
+                overdueTitle: 'Twoja płatność jest zaległa, zapłać proszę swoją fakturę',
+            },
         },
         discoverSection: {
             title: 'Odkryj',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index f798bad1..3154f319 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -989,7 +989,12 @@ const translations: TranslationDeepObject<typeof en> = {
             },
             addVirtualCardPersonalDetails: {title: 'Adicione seus dados para visualizar e começar a usar seu Cartão Expensify.', subtitle: 'Cartão Expensify', cta: 'Adicionar'},
             enterSignerInfo: {title: 'Informações do signatário necessárias', subtitle: ({bankAccountLastFour}: {bankAccountLastFour: string}) => `Conta bancária ${bankAccountLastFour}`},
-            payOverdueInvoice: {title: ({date}: {date: string}) => `Pague sua fatura até ${date} para evitar interrupção do serviço`, cta: 'Revisar'},
+            payOverdueInvoice: {
+                title: ({date}: {date: string}) => `Pague sua fatura até ${date} para evitar interrupção do serviço`,
+                cta: 'Revisar',
+                dueSoonTitle: ({date}: {date: string}) => `Pague sua fatura até ${date} para evitar interrupção do serviço`,
+                overdueTitle: 'Seu pagamento está atrasado, por favor pague sua fatura',
+            },
         },
         discoverSection: {
             title: 'Descobrir',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 6349fe39..dfbdc4ce 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -953,7 +953,12 @@ const translations: TranslationDeepObject<typeof en> = {
             },
             addVirtualCardPersonalDetails: {title: '添加你的详细信息以查看并开始使用 Expensify 卡。', subtitle: 'Expensify 卡', cta: '添加'},
             enterSignerInfo: {title: '需要签署人信息', subtitle: ({bankAccountLastFour}: {bankAccountLastFour: string}) => `银行账户 ${bankAccountLastFour}`},
-            payOverdueInvoice: {title: ({date}: {date: string}) => `请在 ${date} 前支付发票以避免服务中断`, cta: '审核'},
+            payOverdueInvoice: {
+                title: ({date}: {date: string}) => `请在 ${date} 前支付发票以避免服务中断`,
+                cta: '审核',
+                dueSoonTitle: ({date}: {date: string}) => `请在 ${date} 前支付您的发票,以避免服务中断`,
+                overdueTitle: '您的付款已逾期,请支付您的发票',
+            },
         },
         discoverSection: {
             title: '发现',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@shawnborton

Copy link
Copy Markdown
Contributor

I don't think I have a policy that has bad billing, so unfortunately I can't test.

@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

In that case, we need a review, and we are good to go @brunovjk . The logic is quite simple, so I don't expect many problems

@brunovjk

brunovjk commented Sep 15, 2026 •

Copy link
Copy Markdown
Contributor

Great! Reviewing ASAP.

Great, everything looks good to me. I updated the screenshot videos.

@brunovjk brunovjk 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.

LGTM

@melvin-bot

melvin-bot Bot commented Sep 16, 2026

Copy link
Copy Markdown

We did not find an internal engineer to review this PR, trying to assign a random engineer to #100140 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot
melvin-bot Bot requested a review from yuwenmemon September 16, 2026 14:54
@yuwenmemon
yuwenmemon merged commit 3b8dfe3 into Expensify:main Sep 16, 2026
36 of 38 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/yuwenmemon in version: 9.4.81-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Yes — help site changes were required. Draft PR: Docs updates for E/A#100604 overdue invoice alert on Home (Expensify/App#101375) — labeled HelpDot, assigned to adamgrzybowski.

This PR added a new user-facing surface that the help site did not describe: a Time sensitive row on Home, shown to the Workspace owner when a subscription invoice is unpaid, with a Review button that opens invoices on the Spend page.

Two articles needed updating:

Article Why it needed a change
Expensify-Home-Overview.md Its list of conditions that trigger the Time sensitive section did not include an unpaid subscription invoice. Added both copy variants, the Review destination, and two FAQ entries (who sees it, what happens if ignored).
Fix-a-Billing-Issue.md It said Account > Subscription was the only place a Workspace owner sees a billing problem. There is now a second surface, so I added a Where to see an unpaid invoice on Home section and updated the Your payment is past due row and the "how to confirm it's resolved" list.
UI label verification and one pre-existing naming issue I fixed

I verified every label against the live web UI before writing:

  • Home section heading is exactly Time sensitive — no hyphen. This matches homePage.timeSensitiveSection.title in src/languages/en.ts:1013.
  • Navigation tabs are Home, Inbox, Spend, Workspaces, Account.
  • The alert button is Review, per the payOverdueInvoice.cta string this PR added.

Expensify-Home-Overview.md was writing this section as "Time-sensitive" in six places, which violates the exact-UI-label rule in docs/HELPSITE_NAMING_CONVENTIONS.md. Since that article is the one documenting the section, I corrected it there and made the affected headings task-based per docs/HELP_AUTHORING_GUIDELINES.md Section 2.

Follow-up worth noting, not included in the docs PR: seven other articles still say "Time-sensitive" (the Global Reimbursement set, Unlock-a-Business-Bank-Account.md, Validate-a-Business-Bank-Account.md, Fix-a-Broken-Company-Card-Feed-Connection.md, Manage-Personal-Cards.md, and the two Transitioning articles). Sweeping those is unrelated to this PR, so I left them alone rather than widening the diff.

Audience claim: I documented the alert as Workspace-owner-only based on useTimeSensitiveOverdueInvoice reading only ownerBillingGracePeriodEnd, which the hook comment states is set for the policy owner. That is code-based, not verified against a live owner account — the test account had no subscription, so the alert state was not reproducible.

Checks run: npm run spell-changed (cspell) passed with 0 issues on both files. npx prettier --check could not run here — the config resolved to a parent directory and failed on a missing @trivago/prettier-plugin-sort-imports module. That is an environment limitation, not a finding; CI will run it.


@adamgrzybowski, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

@jponikarchuk

Copy link
Copy Markdown

@adamgrzybowski @brunovjk @shawnborton Could you please share additional steps how can we get the account with billing owner whose subscription invoice is within the billing grace period. Do you happen to have an account like that to share?

@shawnborton

Copy link
Copy Markdown
Contributor

cc @flaviadefaria do you have a way to test this?

Copy link
Copy Markdown
Contributor

@adamgrzybowski @brunovjk @shawnborton Could you please share additional steps how can we get the account with billing owner whose subscription invoice is within the billing grace period. Do you happen to have an account like that to share?

I know a customer who’s in this situation, so I can check their account in Supportal using the test build. Other than that, I’m not quite sure how we’d test this.

@flaviadefaria

Copy link
Copy Markdown
Contributor

Checked that user's account, and it looks good:

image

Clicking the row also correctly filters for Invoices on the Spend page.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.4.81-1 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.4.81-1 🚀

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

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.

10 participants