[No QA] Docs updates for E/A#94808 document Paid status report search filter

[MelvinBot]

Explanation of Change

Expensify/App#94808 added a new Paid status filter for expense reports in Advanced Search, exposed as the paid-status: search operator with three options: markedAsPaid, withdrawing, and confirmed.

This updates the help site article Use Search Operators to Filter and Analyze to document the new report filter operator, so the public docs reflect the current behavior.

What changed

• Added paid-status: to the How to filter reports using search operators section, listing its three values and noting they can be combined with commas.

Related

• Source PR: Expensify/App#94808 — "Add a Paid status expense report filter with those three options"
• Fixed issue: Expensify/App#94561

---

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

[OSBotify]

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

Updated articles:

• articles/new-expensify/reports-and-expenses/Use-Search-Operators-to-Filter-and-Analyze

[dukenv0307]

@MelvinBot Please open the PR

[MelvinBot]

🤖 Done — this PR is now open (marked Ready for review). It's out of draft and ready for reviewers.

[github-actions]

Naming/consistency: The values markedAsPaid and withdrawing/confirmed use camelCase, but every other operator value in this article uses lowercase kebab-case (e.g., expensify-card, central-travel-invoicing, year-to-date, last-statement). If these are the literal query values the search parser expects, keep them exact — but confirm the actual accepted syntax and align the style with the rest of the list so readers aren't misled about capitalization. Per HELPSITE_NAMING_CONVENTIONS.md, UI/query references must match the product exactly and be consistent.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a single line documenting the new paid-status: report search operator in Use Search Operators to Filter and Analyze. The addition is small, well-scoped, and slots cleanly into the existing ## How to filter reports using search operators list. It documents the operator, its three values, and how to combine them with commas.

Scores Summary

• Readability: 9/10 - Clear, concise, and consistent with the surrounding bullet list. The inline example (paid-status:markedAsPaid,confirmed) makes usage immediately actionable.
• AI Readiness: 9/10 - Lives under a task-based ## How to filter reports... heading, uses the exact operator syntax, and includes a realistic query example that aids semantic retrieval. No heading hierarchy or metadata concerns are introduced by this diff.
• Style Compliance: 8/10 - Follows the established list pattern and uses code formatting for operator names and values as the rest of the file does. Minor note below on value casing consistency.

Key Findings

• The change matches the format of adjacent operators (e.g. withdrawal-type:, status:), keeping the list uniform.
• Including a combinable-values example is a positive touch that other entries lack.
• The values markedAsPaid, withdrawing, and confirmed use camelCase, whereas most operator values elsewhere in this section are lowercase/hyphenated (e.g. expensify-card, central-travel-invoicing). If these camelCase strings are the literal accepted operator values, they are correct as written; if the parser accepts a more human-friendly form, align the casing accordingly.

Recommendations

• Confirm with the source PR (Add a Paid status expense report filter with those three options #94808) that markedAsPaid, withdrawing, and confirmed are the exact literal values the search parser accepts, so the docs reflect real behavior.
• Optional: consider a brief plain-language gloss for each value (what each paid state means) if space allows, but this is not required given the operator-reference style of the page.

Files Reviewed

• docs/articles/new-expensify/reports-and-expenses/Use-Search-Operators-to-Filter-and-Analyze.md - One line added; compliant and well-formatted. Verify value casing against the parser.

Note: This is a single-line change; no separate inline comments were necessary.

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