Remove travelInvoicing beta by blimpich · Pull Request #92440 · Expensify/App

blimpich · 2026-06-02T21:52:15Z

Explanation of Change

Travel Invoicing was placed behind the travelInvoicing beta during its rollout. This removes that beta gate so Travel Invoicing is generally available: workspace admins can see and use it without being opted into the beta. Where it appears alongside an accounting integration (QuickBooks Online, QuickBooks Desktop, Xero, Sage Intacct, NetSuite), it remains gated by whether Travel Invoicing is actually configured for the workspace, so there is no change for workspaces that have not set it up.

This is the final step of the Travel Invoicing release sequence (Release 11.1). Paired with the Web-Expensify PR that removes the backend beta: https://github.com/Expensify/Web-Expensify/pull/53375

Fixed Issues

$ #78727
PROPOSAL: N/A

Tests

Updated existing unit tests to reflect the change. No new tests added.

Verify that no errors appear in the JS console

Offline tests

No changes to offline behavior.

QA Steps

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

– written by Claude on Ben's behalf

…InvoicingBeta

codecov · 2026-06-02T22:02:54Z

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 Δ
src/CONST/index.ts	`93.79% <ø> (ø)`
src/libs/TravelInvoicingUtils.ts	`82.97% <100.00%> (-0.36%)`	⬇️
src/components/BookTravelButton.tsx	`2.35% <0.00%> (ø)`
src/pages/settings/Wallet/PaymentMethodList.tsx	`0.00% <0.00%> (ø)`
...ng/intacct/export/DynamicSageIntacctExportPage.tsx	`0.00% <0.00%> (ø)`
...etsuite/export/NetSuiteExportConfigurationPage.tsx	`0.00% <0.00%> (ø)`
.../qbd/export/DynamicQuickbooksDesktopExportPage.tsx	`0.00% <0.00%> (ø)`
...xport/DynamicQuickbooksExportConfigurationPage.tsx	`0.00% <0.00%> (ø)`
...xero/export/DynamicXeroExportConfigurationPage.tsx	`0.00% <0.00%> (ø)`
...rc/pages/workspace/travel/BookOrManageYourTrip.tsx	`0.00% <0.00%> (ø)`
... and 7 files with indirect coverage changes

…InvoicingBeta

melvin-bot · 2026-06-03T16:32:48Z

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

blimpich · 2026-06-03T16:32:53Z

ignore the ping @trjExpensify @sobitneupane

pecanoro · 2026-06-03T16:59:54Z

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 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
- 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 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)
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
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- 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
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- 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 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 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.
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.
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

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

melvin-bot · 2026-06-03T17:14:32Z

@blimpich looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

blimpich · 2026-06-03T17:14:34Z

ignoring the reviewer checklist, not an emergency

OSBotify · 2026-06-03T17:37:25Z

✋ 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 · 2026-06-03T18:31:42Z

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

github-actions · 2026-06-03T18:37:27Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #92440.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-3d9430f51ba-59644ae-c222e02ab3449eadf64c7ee0b89adabb253c3d29/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-3d9430f-59644ae-f3d85ee3c63385f692362ca5796488c93228c8ac/index.html

Web 🕸️
https://92440.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-06-04T07:58:28Z

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

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

Bundle Size Analysis (Sentry):

Android
iOS

IuliiaHerets · 2026-06-04T09:17:47Z

Hi @blimpich. Any QA steps here?

cc @robertjchen @pecanoro

blimpich · 2026-06-04T16:47:13Z

@IuliiaHerets nope! Sorry forgot to put NO QA

OSBotify · 2026-06-05T17:52:02Z

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.99-9 🚀

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

blimpich added 3 commits June 2, 2026 14:46

Remove travelInvoicing beta

a4aa0f3

Merge remote-tracking branch 'origin/main' into blimpich-removeTravel…

925f1d8

…InvoicingBeta

Remove travelInvoicing beta gate from QBD export page

c70569b

melvin-bot Bot assigned blimpich Jun 2, 2026

Merge remote-tracking branch 'origin/main' into blimpich-removeTravel…

0fd9f0c

…InvoicingBeta

blimpich marked this pull request as ready for review June 3, 2026 16:32

blimpich requested review from a team as code owners June 3, 2026 16:32

melvin-bot Bot requested review from sobitneupane and trjExpensify and removed request for a team June 3, 2026 16:32

blimpich removed request for sobitneupane and trjExpensify June 3, 2026 16:33

robertjchen approved these changes Jun 3, 2026

View reviewed changes

pecanoro approved these changes Jun 3, 2026

View reviewed changes

blimpich merged commit 3d9430f into main Jun 3, 2026
37 of 39 checks passed

blimpich deleted the blimpich-removeTravelInvoicingBeta branch June 3, 2026 17:14

melvin-bot Bot added the Emergency label Jun 3, 2026

blimpich removed the Emergency label Jun 3, 2026

github-actions Bot mentioned this pull request Jun 3, 2026

Investigate workflow job failing on main: test / test (job 4) #92560

Closed

OSBotify mentioned this pull request Jun 4, 2026

Deploy Checklist: New Expensify 2026-06-04 #92626

Closed

100 tasks

melvin-bot Bot mentioned this pull request Jun 5, 2026

[Due for payment 2026-06-12] Travel Invoicing – Release 11.1: Remove beta #78727

Closed

Uh oh!

Conversation

blimpich commented Jun 2, 2026

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov Bot commented Jun 2, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

melvin-bot Bot commented Jun 3, 2026

Uh oh!

blimpich commented Jun 3, 2026

Uh oh!

pecanoro commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

melvin-bot Bot commented Jun 3, 2026

Uh oh!

blimpich commented Jun 3, 2026

Uh oh!

OSBotify commented Jun 3, 2026

Uh oh!

github-actions Bot commented Jun 3, 2026

Uh oh!

github-actions Bot commented Jun 3, 2026

Uh oh!

OSBotify commented Jun 4, 2026

Uh oh!

IuliiaHerets commented Jun 4, 2026

Uh oh!

blimpich commented Jun 4, 2026

Uh oh!

OSBotify commented Jun 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

codecov Bot commented Jun 2, 2026 •

edited by github-actions Bot

Loading

pecanoro commented Jun 3, 2026 •

edited

Loading