[Payment due @daledah] [No QA] Docs updates for E/A#94690 Paid status hover tooltip stages

[MelvinBot]

Explanation of Change

Follow-up docs update for the changes in #94690, which adds a tooltip on hover of the Paid report status label. The tooltip surfaces the specific payment stage a paid report is in:

• Marked as paid — the report was marked as paid outside of Expensify
• Withdrawing — the reimbursement is being withdrawn from the bank account and is still in progress
• Confirmed — the reimbursement has been confirmed

Previously the help site documented Paid only as a single status. This PR expands the Paid entry in Understanding Report Statuses and Actions to explain the three payment stages now revealed on hover, so the doc reflects current behavior.

Fixed Issues

Docs follow-up for #94690

What changed

• docs/articles/new-expensify/reports-and-expenses/Understanding-Report-Statuses-and-Actions.md — expanded the Paid status bullet with the three hover states.

---

@dukenv0307, please review the files changed and confirm they reflect the current behavior. Then mark this PR Ready for review.

[dukenv0307]

@MelvinBot Please open the PR

[MelvinBot]

🤖 Done — this PR is now marked Ready for review. 🎉

[github-actions]

HelpDot Documentation Review

Overall Assessment
This PR makes a small, focused documentation update to Understanding-Report-Statuses-and-Actions.md. It expands the Paid report status bullet to describe the three payment stages (Marked as paid, Withdrawing, Confirmed) now surfaced when hovering over the Paid status label, following the product change in Expensify/App PR 94690. The change accurately reflects current behavior and is cleanly scoped.

Scores Summary

• Readability: 9/10 - The nested bullets are scannable and each stage has a concise, plain-language explanation. The hover interaction is described clearly.
• AI Readiness: 8/10 - The added content uses exact, searchable UI labels and describes concrete states a user would query. No headings or metadata were changed by this diff, so retrieval structure is unaffected. Keywords in the (unchanged) frontmatter do not include the new hover-stage terms, but this is out of scope for a bullet-only edit.
• Style Compliance: 9/10 - UI labels are bolded and use Sentence case matching the product (Paid, Marked as paid, Withdrawing, Confirmed). Phrasing avoids prohibited vague navigation language and follows the deterministic writing rule.

Key Findings

• Positive: The edit adds genuinely useful behavioral detail (what each paid sub-stage means) that maps directly to real user questions like 'what does withdrawing mean on a paid report'.
• Positive: Correct bold formatting and Sentence case on all UI labels per HELPSITE_NAMING_CONVENTIONS.md.
• Minor: 'Hover over the Paid status' is web-centric; per the Cross-Platform Clarity Rule, consider noting mobile behavior if the tooltip is web-only (tap vs. hover, or 'not available on mobile'). Optional given the small scope.
• Note (not scored): The file uses multiple top-level headings (Report Statuses, Report Action Buttons, etc.), which conflicts with the single-H1 rule in HELP_AUTHORING_GUIDELINES.md Section 4. This is pre-existing and outside this diff.

Recommendations

• Optional: Clarify platform behavior for the hover tooltip (hover on web vs. equivalent on mobile) to satisfy the Cross-Platform Clarity Rule.
• Optional: Add the new stage terms (marked as paid, withdrawing, confirmed) to the frontmatter keywords in a future pass to improve retrieval, if a broader edit is opened.

Files Reviewed

• docs/articles/new-expensify/reports-and-expenses/Understanding-Report-Statuses-and-Actions.md - Approved. Clean, accurate, well-formatted addition to the Paid status entry.

Note: This PR is a focused single-bullet change; no inline comments were necessary.

[OSBotify]

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

Updated articles:

• articles/new-expensify/reports-and-expenses/Understanding-Report-Statuses-and-Actions

[melvin-bot]

🎯 @daledah, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - no internal issue.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

[JS00001]

@stephanieelliott are we good to merge this one?

[stephanieelliott]

Yea, I think we need another approver though since I've committed on this one

[melvin-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 @RachCHopkins

[melvin-bot]

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

[RachCHopkins]

LGTM! I am delighted.

[OSBotify]

🚀 Deployed to staging by https://github.com/RachCHopkins in version: 9.4.29-0 🚀

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

[OSBotify]

🚀 Deployed to staging by https://github.com/RachCHopkins in version: 9.4.31-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/grgia in version: 9.4.31-0 🚀

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

Bundle Size Analysis (Sentry):

• Android

[melvin-bot]

🤖 Payment issue created: #95681