[No QA] Docs updates for E/A#96146 Pay Consolidated Travel Billing balance by invoice

[MelvinBot]

Explanation of Change

Help site documentation for the Consolidated Travel Billing pay-by-invoice (net-30) settlement flow added in #96146.

That PR adds, for workspaces configured to pay their travel bill by invoice/wire (server-side invoiceTo), a Send invoice now button in place of Pay balance in the Consolidated Travel Billing section, new Current travel spend status messages for a queued/awaiting-payment invoice, and treats an unpaid invoice as an outstanding balance that blocks disabling Consolidated Travel Billing.

The existing Consolidated Travel Billing help articles only describe automatic recurring settlement and don't document paying/settling the current travel spend at all. This adds a new article, Pay Your Consolidated Travel Billing Balance, covering both the standard Pay balance flow and the pay-by-invoice Send invoice now variant, so admins can find guidance for either billing setup.

Notes:

• All UI labels (Consolidated Travel Billing, Current travel spend, Pay balance, Send invoice now, Travel) are taken verbatim from src/languages/en.ts in the source PR.
• The pay-by-invoice UI could not be verified in the live app because it is gated behind server-side configuration that doesn't exist on staging yet (as noted in the source PR's QA steps).

Fixed Issues

$

Source feature PR: #96146

Tests

Documentation-only change. No app code is modified.

1. Confirm the new article renders in the HelpDot preview under Travel → Consolidated Travel Billing.

• Verify that no errors appear in the JS console

Offline tests

N/A — documentation-only change.

QA Steps

None — documentation-only change. [No QA]

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

---

@blimpich, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

[OSBotify]

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

Updated articles:

• articles/travel/consolidated-travel-billing/Pay-Your-Consolidated-Travel-Billing-Balance