Skip to content

[No QA] Consolidated help docs: new-expensify/wallet-and-payments - #101954

Merged
VictoriaExpensify merged 12 commits into
mainfrom
helpsite-consolidated-new-expensify-wallet-and-payments
Sep 25, 2026
Merged

VictoriaExpensify merged 12 commits into
mainfrom
helpsite-consolidated-new-expensify-wallet-and-payments

Conversation

@stephanieelliott

@stephanieelliott stephanieelliott commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR consolidates 9 help doc updates for new-expensify/wallet-and-payments into a single PR: one new article and 11 edited articles. The changes are strong overall — they modernize connection-status terminology (retiring "Action required" in favor of the real UI badges Active, Incomplete, Pending, Verifying, Locked, Inactive), correct UI casing to match the product (e.g. Bank accounts, Add bank account), add task-based FAQ entries, and introduce a well-structured new reference article. The diff generally adheres well to the governance specs, with only a few Style/AI issues carried over from pre-existing article conventions.

Scores Summary

  • Readability: 9/10 - Sentences are clear, scannable, and action-oriented. The new article's badge/status tables are an excellent readability choice. Steps are sequential and numbered correctly.
  • AI Readiness: 8/10 - The new file has complete YAML including internalScope, exactly one # heading plus # FAQ, only ## sub-headings, task-based/question headings, and realistic keywords. Points lost because Pay-Expenses.md and several Global-Reimbursement files lack internalScope metadata and (in the case of Global-Reimbursement-United-States.md) retain pre-existing # Step 2: multi-# heading structure that new content is being added under.
  • Style Compliance: 8/10 - Excellent UI-exact terminology and bolded button/badge names throughout the new content. Main deduction: the new heading ## Who Can Pay Workspace Expenses in Pay-Expenses.md uses Title Case rather than Sentence case, and that file's prerequisite links use full https://help.expensify.com/... URLs instead of the required relative links (new cross-link correctly uses a relative path).

Key Findings

  • Strong, consistent terminology migration from the retired Action required badge to the precise per-state badges and their exact companion messages (e.g. Please confirm test transactions, This account requires attention). This is applied cohesively across Share-, Unlock-, Validate-, Set-up-your-wallet, and the new status article.
  • The new Check Bank Account and Card Connection Status article is a model example: complete metadata with internalScope, single-workflow scope, task-based ## headings, UI-exact bolded labels, relative cross-links with descriptive anchor text, and purposeful <\!-- SCREENSHOT --> placeholders.
  • Cross-links added in this PR correctly use relative paths and descriptive "Learn how to..." / "Learn what..." anchor text.
  • New content added under Global-Reimbursement-United-States.md sits beneath a pre-existing # Step 2: heading — a second # and a generic "Step" label, both of which conflict with the heading rules (Section 2 and Section 4). This is inherited structure, but the PR expands content within it.
  • New heading ## Who Can Pay Workspace Expenses (Pay-Expenses.md) is Title Case; naming conventions require Sentence case matching a task-based phrase.
  • Reimbursement-Payment-Methods.md correctly splits web vs. mobile bulk-action instructions per the platform-divergence navigation rule.

Recommendations

  • Priority: Convert ## Who Can Pay Workspace Expenses to Sentence case, e.g. ## Who can pay Workspace expenses.
  • Priority: In Pay-Expenses.md, change the two prerequisite links from full https://help.expensify.com/... URLs to relative links per the Link Formatting standard.
  • Consider adding internalScope metadata to Pay-Expenses.md and the Global-Reimbursement files edited here to improve AI retrieval consistency.
  • Where new content was added under # Step 2: in Global-Reimbursement-United-States.md, consider demoting to ## task-based headings in a follow-up to align with the single-# rule.
  • Verify the two callout images in Validate-a-Business-Bank-Account.md are re-captured to show the new Pending badge (already flagged appropriately via a SCREENSHOT comment).

Files Reviewed

  • Check-Bank-Account-and-Card-Connection-Status.md — New article; fully compliant, exemplary structure and metadata.
  • Connect-a-Business-Bank-Account.md — Compliant additions (invoice-payment section, Beneficial Owner SSN detail, status link, new FAQ).
  • Connect-a-Personal-Bank-Account.md — Good UI casing corrections and compliant new FAQ.
  • Global-Reimbursement-Canada.md — Compliant new task-based section; accurate doc-requirement updates.
  • Global-Reimbursement-United-Kingdom.md — Minor accurate SSN wording update.
  • Global-Reimbursement-United-States.md — Accurate content, but new content lives under a pre-existing # Step 2: heading (heading-rule concern).
  • Pay-Expenses.md — Useful new payer guidance; Title-case heading and full-URL links should be fixed.
  • Reimbursement-Payment-Methods.md — Correct web/mobile navigation split for bulk actions.
  • Set-up-your-wallet.md — Status terminology updated with a compliant relative cross-link.
  • Share-a-Business-Bank-Account.md — Correct badge/message terminology update.
  • Unlock-a-Business-Bank-Account.md — Accurate Time sensitive section wording fix.
  • Validate-a-Business-Bank-Account.md — Correct Pending terminology; SCREENSHOT flag for outdated images is appropriate.

Note: Detailed line-by-line feedback has been provided as inline comments.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9617ec553c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

| Badge | What it means | What appears below the row |
|-------|---------------|-----------------------------|
| **Active** | The card is connected and importing transactions. | Nothing. |
| **Inactive** | The connection is broken, so transactions have stopped importing. | A message that depends on the card, described below. |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Distinguish suspended Expensify Cards from broken feeds

An Expensify Card can show Inactive because it is suspended, even though it has no bank connection to break; getCardConnectionStatusDisplay() deliberately emits that badge without a connection message in this case. Describing every Inactive card as a broken import connection with a message sends suspended-card users toward irrelevant feed troubleshooting and also contradicts the later explanation that Expensify Cards do not connect to a bank.

Useful? React with 👍 / 👎.

- **Please fix this connection in company cards** — a company card on a workspace you administer. The link opens **Company cards** for that workspace.
- **Please ask an admin to fix this connection** — a company card on a workspace you do not administer.

To reconnect a company card feed, [learn how to fix a broken company card feed connection](/articles/new-expensify/connect-credit-cards/Fix-a-Broken-Company-Card-Feed-Connection).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Point the company-card link to an existing article

This route has no corresponding article anywhere under docs/articles; the relevant pages are under connect-credit-cards/fix-card-connection-issues/, such as Fix-a-Card-Connection-Error.md. As written, users following the new troubleshooting link reach a missing page rather than the company-card recovery guidance.

Useful? React with 👍 / 👎.

Comment on lines +63 to +65
1. In the navigation tabs (on the left on web, on the bottom on mobile), click **Workspaces > [Workspace name]**.
2. Select **Invoices**.
3. In the **Bank accounts** section, select **Add bank account**.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Require Workspace Admin access for the invoice flow

A Payments Admin—the audience declared for this article—cannot complete this step: the Invoices page and add-account handler require write access to MORE_FEATURES, while the Payments Admin role only has write access to WORKFLOWS_PAYMENTS; selecting Add bank account therefore opens the read-only fallback. State that this invoice-specific flow requires a Workspace Admin, or direct Payments Admins to the Workflows flow instead.

Useful? React with 👍 / 👎.

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@VictoriaExpensify
VictoriaExpensify merged commit e1e5d9f into main Sep 25, 2026
16 of 17 checks passed
@VictoriaExpensify
VictoriaExpensify deleted the helpsite-consolidated-new-expensify-wallet-and-payments branch September 25, 2026 03:29
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/VictoriaExpensify in version: 9.4.94-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.94-0 🚀

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

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants