[No QA] Helpsite: create nested billing folder structure and add articles by stephanieelliott · Pull Request #95101 · Expensify/App

stephanieelliott · 2026-07-01T23:23:27Z

Master tracking issue: https://github.com/Expensify/Expensify/issues/635904
Section sub-issue: https://github.com/Expensify/Expensify/issues/639996
Content QA performed here: https://github.com/Expensify/Expensify/issues/654293

Explanation of Change

Created new billing article and file structure. Will add remaining articles in a followup PR.

Fixed Issues

$
PROPOSAL:

Tests

Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as tests.

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

merge main

Add section folders with ordered navigation and move existing billing articles into their new paths. Co-authored-by: Cursor <cursoragent@cursor.com>

Corrected capitalization and phrasing for clarity in the billing section.

… View-Your-Plan-and-Subscription.md

codecov · 2026-07-02T00:40:37Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 183 files with indirect coverage changes

…space-Plan.md

…ntrol-Plans.md

Updated the article to reflect current pricing for Collect and Control Workspaces, including subscription rates, annual pricing, and localized pricing. Added details on billing eligibility and how the Expensify Card discount works.

VictoriaExpensify · 2026-07-02T06:49:32Z

+| Workspace plan | Subscription | Price |
+| -------------- | ------------ | ----- |
+| **Collect** | Pay-per-use | **$5** per unique member/month |
+| **Control** | Annual | **$18** per member included in your subscription size/month, plus **$36** per active member above your subscription size/month |


Should have an * here to show the footnote referenced

VictoriaExpensify · 2026-07-02T07:02:47Z

+ - Your subscription payment is overdue.
+ - A payment dispute is preventing the charge from being processed.
+
+For instructions on resolving a specific billing issue, see [Fix a Billing Issue](/articles/new-expensify/billing-and-subscriptions/manage-billing/resolve-billing-issues/Fix-a-Billing-Issue).


This same line and URL is already on row 14

VictoriaExpensify · 2026-07-02T11:13:26Z

+ - **Annual**, which includes a 12-month commitment with discounted pricing.
+ - **Pay-per-use**, which bills month-to-month with no annual commitment.


I feel like the new Collect plan introduces a third subscription type here, which is member-based...or something. I just don't think this is quite captured through Pay Per Use because you aren't paying based on usage. I think Collect is explained well further down, but the way this section is worded sounds like we are explaining all the subscription types, but one is missing.

The alternative would be to make this section the Control Subscription Types and then make the section below specific to Collect subscriptions types where the member-based sub is introduced

VictoriaExpensify · 2026-07-02T11:23:23Z

+order: 6
+---
+
+# Understand Workspace Ownership and Billing Permissions


I wonder if somewhere in ths article you want to mention that a workspace owner can own multiple workspaces and that, to prevent double billing, it's best practice, in most instances, to ensure all workspaces have the same billing owner

Rename billing overview and glossary articles, move plans content into Explore Plans Subscriptions and Pricing, and nest Manage Subscription and Manage Billing under Manage Your Subscription and Billing with redirects for old URLs. Co-authored-by: Cursor <cursoragent@cursor.com>

Reorder billing hub cards and sidebar items so permissions and terms appear before plans and manage sections. Co-authored-by: Cursor <cursoragent@cursor.com>

Co-authored-by: Cursor <cursoragent@cursor.com>

Treat sections with subsections as section cards instead of article links, and render nested subsection content in the sidebar for Manage Your Subscription and Billing. Co-authored-by: Cursor <cursoragent@cursor.com>

…our-subscription-and-billing/manage-billing/resolve-billing-issues/Understand-Why-Billing-Issues-Occur.md

…our-subscription-and-billing/manage-billing/resolve-billing-issues directory

OSBotify · 2026-07-03T03:05:55Z

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

Updated articles:

Merge pull request #95100 from Expensify/main

233db29

merge main

stephanieelliott self-assigned this Jul 1, 2026

stephanieelliott and others added 10 commits July 1, 2026 13:28

Reorganize Billing & Subscriptions hub into subfolders.

fa2d5c6

Add section folders with ordered navigation and move existing billing articles into their new paths. Co-authored-by: Cursor <cursoragent@cursor.com>

Create How-Subscriptions-Plans-and-Billing-Work.md

5111e99

Create Understand-Billing-Terms-and-Definitions.md

f60b52e

Create Understand-Workspace-Ownership.md

a5743b4

Update links in Understand Workspace Ownership article

f66b27b

Update Understand-Billing-Terms-and-Definitions.md

fffced4

Update billing responsibilities and ownership terminology

6954637

Corrected capitalization and phrasing for clarity in the billing section.

Update How-Subscriptions-Plans-and-Billing-Work.md

cab53f7

Update Understand-Billing-Terms-and-Definitions.md

c55b019

Update and rename Add-a-payment-card-and-view-your-subscription.md to…

c3c1771

… View-Your-Plan-and-Subscription.md

stephanieelliott added 17 commits July 1, 2026 14:50

Update and rename Changing-Your-Workspace-Plan.md to Change-Your-Work…

9fda5b9

…space-Plan.md

Update and rename Plan-types-and-pricing.md to Compare-Collect-and-Co…

74d6497

…ntrol-Plans.md

Update and rename Tax-Exemption.md to Request-Tax-Exemption.md

837a8cb

Update How-Subscriptions-Plans-and-Billing-Work.md

eff09db

Update Understand-Billing-Terms-and-Definitions.md

c098efc

Update Understand-Workspace-Ownership.md

b4a7aaf

Update Compare-Collect-and-Control-Plans.md

c7a15ae

Update Understand-Expensify-Pricing.md

4d25973

Update Request-Tax-Exemption.md

ad26c16

Update Change-Your-Workspace-Plan.md

8fce9d4

Update View-Your-Plan-and-Subscription.md

4f42ccb

Update How-Subscriptions-Plans-and-Billing-Work.md

a758c03

Update redirects.csv

a32774c

Update redirects.csv

2c2049f

Create Understand-Why-Billing-Issues-Occur.md

b93162b

Create Fix-a-Billing-Issue.md

ab58ced

VictoriaExpensify reviewed Jul 2, 2026

View reviewed changes

Update Compare-Collect-and-Control-Plans.md

1c0b6c4