Skip to content

[NO QA] NetSuite Travel Invoicing — move setting up and mirror company card sub-page format#89297

Merged
blimpich merged 6 commits intomainfrom
blimpich-netSuiteMoveTravelInvoicingUp
Apr 30, 2026
Merged

[NO QA] NetSuite Travel Invoicing — move setting up and mirror company card sub-page format#89297
blimpich merged 6 commits intomainfrom
blimpich-netSuiteMoveTravelInvoicingUp

Conversation

@blimpich
Copy link
Copy Markdown
Contributor

@blimpich blimpich commented Apr 30, 2026

Explanation of Change

Addresses two UX issues with the NetSuite Travel Invoicing export setting. See this slack thread for details.

Here's what changed:

  1. Moves the Travel Invoicing row up so it sits directly below "Export company card expenses as" on the main export config page — previously it was buried below invoice and tax settings.
  2. Updates the Travel Invoicing sub-page to mirror the company card sub-page format: a static, non-editable "Export as: Journal entries" row (with helper text) followed by the payable account picker. This makes it explicit that travel expenses always export as JEs.

Adds a travelDescription translation key to all 10 language files

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/631291
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

N/A — UI-only reordering and display change.

QA Steps

  • 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 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 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

Screen.Recording.2026-04-30.at.12.02.41.PM.mov

@blimpich blimpich requested review from a team as code owners April 30, 2026 18:34
@melvin-bot melvin-bot Bot requested review from FitseTLT and heyjennahay and removed request for a team April 30, 2026 18:35
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 30, 2026

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

@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 f5ac8049..d432d1af 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -4823,8 +4823,9 @@ ${amount} für ${merchant} – ${date}`,
 
                             Wenn du für jede Karte einen bestimmten Lieferanten festlegen möchtest, gehe zu *Einstellungen > Domains > Firmenkarten*.
                         `),
-                        travelDescription: 'Travel expenses will export as journal entries to the NetSuite account specified below.',
+                        travelDescription: 'Reisekosten werden als Journaleinträge in das unten angegebene NetSuite-Konto exportiert.',
                     },
+                    travelDescription: 'Reisekosten werden als Journaleinträge in das unten angegebene NetSuite-Konto exportiert.',
                 },
                 expenseReportDestinationConfirmDescription:
                     'Wenn Sie die Export-Einstellung für Unternehmenskarten auf Spesenabrechnungen umstellen, werden NetSuite-Lieferanten und Buchungskonten für einzelne Karten deaktiviert.\n\nKeine Sorge, wir speichern Ihre bisherigen Auswahlen, falls Sie später wieder zurückwechseln möchten.',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index f37ceb79..0c466db3 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -4833,8 +4833,9 @@ ${amount} pour ${merchant} - ${date}`,
 
                             Si vous souhaitez définir un fournisseur spécifique pour chaque carte, accédez à *Paramètres > Domaines > Cartes d’entreprise*.
                         `),
-                        travelDescription: 'Travel expenses will export as journal entries to the NetSuite account specified below.',
+                        travelDescription: 'Les frais de voyage seront exportés sous forme d’écritures de journal vers le compte NetSuite indiqué ci-dessous.',
                     },
+                    travelDescription: 'Les frais de voyage seront exportés sous forme d’écritures de journal vers le compte NetSuite indiqué ci-dessous.',
                 },
                 expenseReportDestinationConfirmDescription:
                     'Si vous basculez le paramètre d’exportation de carte société vers les notes de frais, les fournisseurs NetSuite et les comptes de comptabilisation pour les cartes individuelles seront désactivés.\n\nNe vous inquiétez pas, nous conserverons vos sélections précédentes au cas où vous souhaiteriez revenir en arrière plus tard.',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index a0383f4d..fcd2d9f1 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -4807,8 +4807,9 @@ ${amount} per ${merchant} - ${date}`,
 
                             Se desideri impostare un fornitore specifico per ogni carta, vai su *Impostazioni > Domini > Carte aziendali*.
                         `),
-                        travelDescription: 'Travel expenses will export as journal entries to the NetSuite account specified below.',
+                        travelDescription: 'Le spese di viaggio verranno esportate come registrazioni contabili sull’account NetSuite specificato di seguito.',
                     },
+                    travelDescription: 'Le spese di viaggio verranno esportate come registrazioni contabili sull’account NetSuite specificato di seguito.',
                 },
                 expenseReportDestinationConfirmDescription:
                     'Se passi l’impostazione di esportazione delle carte aziendali a note spese, i fornitori NetSuite e i conti di registrazione per le singole carte verranno disabilitati.\n\nNon preoccuparti, salveremo comunque le tue selezioni precedenti nel caso volessi tornare indietro più tardi.',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 86aec4dc..8a2e4090 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -4765,8 +4765,9 @@ ${integrationName === CONST.ONBOARDING_ACCOUNTING_MAPPING.other ? 'あなたの'
 
                             各カードごとに特定の取引先を設定したい場合は、*設定 > ドメイン > 会社カード* に移動してください。
                         `),
-                        travelDescription: 'Travel expenses will export as journal entries to the NetSuite account specified below.',
+                        travelDescription: '出張費は、以下で指定された NetSuite アカウントに仕訳としてエクスポートされます。',
                     },
+                    travelDescription: '出張費は、以下で指定された NetSuite アカウントに仕訳としてエクスポートされます。',
                 },
                 expenseReportDestinationConfirmDescription:
                     '会社カードのエクスポート設定を経費レポートに切り替えると、個々のカードに対するNetSuiteのベンダーおよび転記勘定は無効になります。\n\nご安心ください。後で元に戻したくなった場合に備えて、以前の選択内容は引き続き保存されます。',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 1ff76699..d6051ceb 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -4800,8 +4800,9 @@ ${amount} voor ${merchant} - ${date}`,
 
                             Als je voor elke kaart een specifieke leverancier wilt instellen, ga dan naar *Instellingen > Domeinen > Bedrijfspassen*.
                         `),
-                        travelDescription: 'Travel expenses will export as journal entries to the NetSuite account specified below.',
+                        travelDescription: 'Reiskosten worden geëxporteerd als journaalposten naar de hieronder opgegeven NetSuite-rekening.',
                     },
+                    travelDescription: 'Reiskosten worden geëxporteerd als journaalposten naar de hieronder opgegeven NetSuite-rekening.',
                 },
                 expenseReportDestinationConfirmDescription:
                     'Als je de exportinstelling voor bedrijfskaarten wijzigt naar onkostendeclaraties, worden NetSuite-leveranciers en boekingsrekeningen voor individuele kaarten uitgeschakeld.\n\nMaak je geen zorgen, we bewaren je vorige selecties voor het geval je later weer wilt terugschakelen.',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 9c1a8a57..3ec1d290 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -4791,8 +4791,9 @@ ${amount} dla ${merchant} - ${date}`,
 
                             Jeśli chcesz ustawić konkretnego dostawcę dla każdej karty, przejdź do *Ustawienia > Domeny > Karty firmowe*.
                         `),
-                        travelDescription: 'Travel expenses will export as journal entries to the NetSuite account specified below.',
+                        travelDescription: 'Wydatki na podróże służbowe zostaną wyeksportowane jako zapisy księgowe na konto NetSuite wskazane poniżej.',
                     },
+                    travelDescription: 'Wydatki na podróże służbowe zostaną wyeksportowane jako zapisy księgowe na konto NetSuite wskazane poniżej.',
                 },
                 expenseReportDestinationConfirmDescription:
                     'Jeśli zmienisz ustawienie eksportu firmowych kart płatniczych na raporty wydatków, dostawcy NetSuite i konta księgowe przypisane do poszczególnych kart zostaną wyłączone.\n\nNie martw się, nadal zachowamy Twoje poprzednie wybory na wypadek, gdybyś później chciał(a) wrócić do poprzednich ustawień.',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index a10c94d0..1230941d 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -4794,8 +4794,9 @@ ${amount} para ${merchant} - ${date}`,
 
                             Se quiser definir um fornecedor específico para cada cartão, vá em *Configurações > Domínios > Cartões Corporativos*.
                         `),
-                        travelDescription: 'Travel expenses will export as journal entries to the NetSuite account specified below.',
+                        travelDescription: 'As despesas de viagem serão exportadas como lançamentos contábeis para a conta NetSuite especificada abaixo.',
                     },
+                    travelDescription: 'As despesas de viagem serão exportadas como lançamentos contábeis para a conta NetSuite especificada abaixo.',
                 },
                 expenseReportDestinationConfirmDescription:
                     'Se você alterar a configuração de exportação de cartão corporativo para relatórios de despesas, os fornecedores do NetSuite e as contas de lançamento para cartões individuais serão desativados.\n\nNão se preocupe, ainda vamos salvar suas seleções anteriores caso queira voltar para a configuração anterior depois.',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 314ae4af..9c37125a 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -4685,8 +4685,9 @@ ${amount},商户:${merchant} - 日期:${date}`,
 
                             如果你希望为每张卡设置特定供应商,请前往 *设置 > 域 > 公司卡*。
                         `),
-                        travelDescription: 'Travel expenses will export as journal entries to the NetSuite account specified below.',
+                        travelDescription: '差旅报销将作为日记账分录导出到下方指定的 NetSuite 账户。',
                     },
+                    travelDescription: '差旅报销将作为日记账分录导出到下方指定的 NetSuite 账户。',
                 },
                 expenseReportDestinationConfirmDescription:
                     '如果您将公司卡导出设置切换为报销单,单张卡片对应的 NetSuite 供应商和入账科目将被停用。\n\n别担心,我们会继续保存您之前的选择,以便您日后需要时切换回去。',

Note

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

View workflow run

Comment thread src/languages/de.ts Outdated
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 30, 2026

Codecov Report

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

Files with missing lines Coverage Δ
...etsuite/export/NetSuiteExportConfigurationPage.tsx 0.00% <0.00%> (ø)
...xport/NetSuiteTravelInvoicingConfigurationPage.tsx 0.00% <0.00%> (ø)
... and 38 files with indirect coverage changes

@FitseTLT
Copy link
Copy Markdown
Contributor

@blimpich Let me know if I should review or remove me from reviewers list Thx

@blimpich blimpich removed the request for review from FitseTLT April 30, 2026 19:03
@blimpich
Copy link
Copy Markdown
Contributor Author

No need for review, thank you @FitseTLT !

@blimpich
Copy link
Copy Markdown
Contributor Author

asking for spanish copy confirmation here: https://expensify.slack.com/archives/C01GTK53T8Q/p1777576469912859

@blimpich blimpich requested review from rlinoz and stitesExpensify and removed request for rlinoz April 30, 2026 19:21
@blimpich
Copy link
Copy Markdown
Contributor Author

updated spanish copy after confirmation

@blimpich blimpich merged commit 798fa34 into main Apr 30, 2026
42 of 43 checks passed
@blimpich blimpich deleted the blimpich-netSuiteMoveTravelInvoicingUp branch April 30, 2026 21:25
@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.

@github-actions
Copy link
Copy Markdown
Contributor

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

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/blimpich in version: 9.3.65-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot
Copy link
Copy Markdown
Contributor

🤖 Docs review complete. Changes in this PR do require a help site update.

What changed: The PR moves the Travel Invoicing setting higher on the NetSuite export configuration page and adds an explicit "Export as: Journal entries" display on the Travel Invoicing sub-page. The existing help site doc (Configure-Netsuite.md) lists all export settings but omits Travel Invoicing entirely.

Draft PR created: #89328

  • Adds a Travel Invoicing bullet to the NetSuite export settings section

Note: I was unable to add the PR to GitHub project 196 due to token permissions. Please add it manually.

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.

5 participants