[Export Templates] Add Basic IS Templates as export options

[NikkiWines]

cc: @francoisl

Depends on #62340 (was reverted)
Depends on #65246 (was reverted)
Depends on #65931 - merged!!

Explanation of Change

Adds two default IS templates as options for exporting reports. If whole reports are not selected then the All levels - report export option will not be available.

Fixed Issues

$ #58315
PROPOSAL: N/A

Tests

1. Create a new account and create a workspace on that account
2. Create a report with two expenses on it
3. Create another report with one expense on it

Reports > Expenses

4. Navigate to the Reports page > Expenses
5. Select 1 expense and click the 1 selected button, then Export
6. Confirm you see the Basic Export and All Data - expense level options
7. Select all of the transactions and click the x selected button, then Export
8. Confirm you see the Basic Export, All Data - expense level options
9. Select the All Data - expense level option and confirm you see a modal that states your export has begun
10. Confirm you receive a message from concierge with your export file containing the details of your expense

Reports > Reports

11. Navigate to the Reports page > Reports
12. Select one expense from each report and click the 2 selected button, then Export
13. Confirm you see the Basic Export, All Data - expense level options
14. Select the All Data - expense level option and confirm you see a modal that states your export has begun
15. Confirm you receive a message from concierge with your export file containing the details of your expenses

---

16. Select one report and click the x selected button, then Export
17. Confirm you see the Basic Export, All Data - expense level, AND All Data- report level options
18. Select the All Data - expense level option and confirm you see a modal that states your export has begun
19. Confirm you receive a message from concierge with your export file containing the details of your expenses
20. Select the All Data - report level option and confirm you see a modal that states your export has begun
21. Confirm you receive a message from concierge with your export file containing the details of your report

---

22. Select all items, and click the x selected button, then Export
23. Confirm you see the Basic Export,All Data - expense level, AND All Data- report level options

---

Reports > Single Report View

26. Click into the report with 2 expenses from the Reports > Reports view
27. Select one expense and click on the 1 selected button, then Export
28. Confirm you see the Basic Export and All Data - expense level options
29. Select the All Data - expense level option and confirm you see a modal that states your export has begun
30. Confirm you receive a message from concierge with your export file containing the details of your expense

---

31. Select both expenses and click on the 2 selected button, then Export
32. Confirm you see the Basic Export,All Data - expense level, AND All Data- report level options
33. Select the All Data - report level option and confirm you see a modal that states your export has begun
34. Confirm you receive a message from concierge with your export file containing the details of your report

Inbox > Report

35. Navigate to your inbox and find the report with two expenses on it
36. Select one expense and click on the 1 selected button, then Export
37. Confirm you see the Basic Export and All Data - expense level options
38. Select the All Data - expense level option and confirm you see a modal that states your export has begun
39. Confirm you receive a message from concierge with your export file containing the details of your expense

---

39. Select both expenses and click on the 2 selected button, then Export
40. Confirm you see the Basic Export,All Data - expense level, AND All Data- report level options
41. Select the All Data - report level option and confirm you see a modal that states your export has begun
42. Confirm you receive a message from concierge with your export file containing the details of your report

---

42. Unselect all expenses, click on the More button and then Export
43. Confirm you see the Basic Export,All Data - expense level, AND All Data- report level options

• Verify that no errors appear in the JS console

Offline tests

1. Go offline
2. Repeat the same steps are you would online and confirm you see the modal notifying you that your export has begun
3. Go back online
4. Confirm you get a message from concierge with your exported file

QA Steps

Same as test 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
  • MacOS: Desktop
• 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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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 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.
• 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

#64616 (comment)

MacOS: Desktop

[NikkiWines]

@francoisl this is basically ready for a first round of reviews, I'm just keeping it as a draft because it's dependant on #62340 which hasnt been merged yet

[melvin-bot]

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

[NikkiWines]

@alitoshmatov @francoisl friendly bump here 🙇

[github-actions]

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

[parasharrajat]

@NikkiWines, I don't see a confirmation alert on iOS after clicking export. It works fine on all other platforms.

[NikkiWines]

I'll try and reproduce the issue on my simulator now

[NikkiWines]

@parasharrajat thanks for all the reviews! I've fixed the bug and double-checked it still works on web and mweb

Simulator.Screen.Recording.-.iPhone.15.-.2025-08-05.at.02.15.18.mp4

[parasharrajat]

Screenshots

🔲 iOS / native

05.08.2025_12.27.23_REC.mp4

🔲 iOS / Safari

05.08.2025_12.22.10_REC.mp4

🔲 MacOS / Desktop

01.08.2025_21.51.26_REC.mp4

🔲 MacOS / Chrome

01.08.2025_21.49.58_REC.mp4

🔲 Android / Chrome

05.08.2025_00.32.44_REC.mp4

🔲 Android / native

05.08.2025_00.28.26_REC.mp4

[parasharrajat]

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 tests pass on all platforms & I tested again on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • 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.js 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 form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label 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.
• 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.

🎀 👀 🎀 C+ reviewed

[melvin-bot]

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

✋ 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]

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.1.90-0 🚀

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

[github-actions]

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.1.90-11 🚀

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