[NO QA] Add a multiple receipt addendum to FAQ

[greg-schroeder]

Explanation of Change

Adding a small addendum to the FAQ for this article to accommodate multiple receipt uploads

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/465282

QA Steps

1. Go to help.expensify.com
2. Navigate to Expensify Classic > Integrations > Accounting Integrations > Indirect Accounting Integrations
3. Verify that the article has new content added and there are no formatting errors

PR Author Checklist

• [x] I linked the correct issue in the ### Fixed Issues section above
• [x] I wrote clear testing steps that cover the changes made in this PR
  • [x] I added steps for local testing in the Tests section
  • [x] I added steps for the expected offline behavior in the Offline steps section
  • [x] I added steps for Staging and/or Production testing in the QA steps section
  • [x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • [x] 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)
  • [x] 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).
• [x] I included screenshots or videos for tests on all platforms
• [x] I ran the tests on all platforms & verified they passed on:
  • [x] Android / native
  • [x] Android / Chrome
  • [x] iOS / native
  • [x] iOS / Safari
  • [x] MacOS / Chrome / Safari
  • [x] MacOS / Desktop
• [x] 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)
• [x] I followed proper code patterns (see Reviewing the code)
  • [x] 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)
  • [x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • [x] I verified that comments were added to code that is not self explanatory
  • [x] 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.
  • [x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • [x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • [x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • [x] 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.
  • [x] 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.
  • [x] I verified the JSDocs style guidelines (in STYLE.md) were followed
• [x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• [x] I followed the guidelines as stated in the Review Guidelines
• [x] 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)
• [x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• [x] 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
• [x] I verified that if a function's arguments changed that all usages have also been updated correctly
• [x] If a new component is created I verified that:
  • [x] A similar component doesn't exist in the codebase
  • [x] All props are defined accurately and each prop has a /** comment above it */
  • [x] The file is named correctly
  • [x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • [x] The only data being stored in the state is data necessary for rendering and nothing else
  • [x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    • [x] 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)
  • [x] All JSX used for rendering exists in the render method
  • [x] 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
• [x] If any new file was added I verified that:
  • [x] 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
• [x] If a new CSS style is added I verified that:
  • [x] A similar style doesn't already exist
  • [x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))
• [x] 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.
• [x] 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)
• [x] 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.
• [x] 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.
• [x] 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.
• [x] 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.
• [x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

  Screenshots/Videosundefined

[melvin-bot[bot]]

Concierge reviewer checklist:

• [ ] I have verified the accuracy of the article
  • [ ] The article is within a hub that makes sense, and the navigation is correct
  • [ ] All processes, screenshots, and examples align with current product behavior.
  • [ ] All links within the doc have been verified for correct destination and functionality.
• [ ] I have verified the readability of the article
  • [ ] The article's language is clear, concise, and free of jargon.
  • [ ] The grammar, spelling, and punctuation are correct.
  • [ ] The article contains at least one image, or that an image is not necessary
  • [ ] I have verified the formatting of the article
  • [ ] The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
  • [ ] The article has proper text spacing and breaks for readability.
  • [ ] I have verified the article has the appropriate tone and style
  • [ ] The article's tone is professional, friendly, and suitable for the target audience.
  • [ ] The article's tone, terminology, and voice are consistent throughout.
  • [ ] I have verified the overall quality of the article
  • [ ] The article is not missing any information, nor does it contain redundant information.
  • [ ] The article fully addresses user needs.
  • [ ] I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @laurenreidexpensify

[melvin-bot[bot]]

@ishpaul777 @laurenreidexpensify 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]

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://a3cb3875.helpdot.pages.dev ⚡️

[melvin-bot[bot]]

Concierge reviewer checklist:

• [ ] I have verified the accuracy of the article
  • [ ] The article is within a hub that makes sense, and the navigation is correct
  • [ ] All processes, screenshots, and examples align with current product behavior.
  • [ ] All links within the doc have been verified for correct destination and functionality.
• [ ] I have verified the readability of the article
  • [ ] The article's language is clear, concise, and free of jargon.
  • [ ] The grammar, spelling, and punctuation are correct.
  • [ ] The article contains at least one image, or that an image is not necessary
  • [ ] I have verified the formatting of the article
  • [ ] The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
  • [ ] The article has proper text spacing and breaks for readability.
  • [ ] I have verified the article has the appropriate tone and style
  • [ ] The article's tone is professional, friendly, and suitable for the target audience.
  • [ ] The article's tone, terminology, and voice are consistent throughout.
  • [ ] I have verified the overall quality of the article
  • [ ] The article is not missing any information, nor does it contain redundant information.
  • [ ] The article fully addresses user needs.
  • [ ] I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @bfitzexpensify

[melvin-bot[bot]]

@Pujan92 @ @bfitzexpensify 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]

[greg-schroeder]

Oops, yes, thanks @ishpaul777!

[Pujan92]

@laurenreidexpensify Plz remove me from reviewer, Thanks!

[greg-schroeder]

@laurenreidexpensify Okay. I edited one word to make it apply to "all" receipts instead of "both".

[laurenreidexpensify]

@greg-schroeder nice thanks, but it still says both in the last sentence?

From there, simply upload the combined PDF to the expense to capture both.