[No QA] Docs updates for E/A#88363 Add billing restriction note to duplicate docs

[MelvinBot]

Summary

• Updates the How to Duplicate an Expense help article to note that users with an expired billing subscription on their primary workspace will be prompted to add a payment card before duplicating
• Updates the Duplicate a Report help article with the same billing restriction note
• Adds a new FAQ entry to both articles explaining the payment card prompt

These changes document the new billing restriction guard added to duplicate expense/report handlers in #88363.

Test plan

• Verify the updated articles render correctly on the help site
• Confirm the new FAQ entries are clear and match the actual UI behavior

[OSBotify]

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

Updated articles:

• articles/new-expensify/reports-and-expenses/Duplicate-a-Report
• articles/new-expensify/reports-and-expenses/How-to-Duplicate-an-Expense

[stephanieelliott]

I think this is not needed - the note is self-explanatory and the scenario is edge case, likely to do more harm than good in terms of retrieval

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 97e1e7a78a

ℹ️ 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".

[chatgpt-codex-connector]

Correct the workspace named in the report billing note

For single report duplication, the app checks the policy the duplicate will be created on: useExpenseActions sets targetPolicyForDuplicate to the source report policy when it is still accessible, and only falls back to the default/primary policy otherwise. In that common case an expired source workspace triggers the payment-card flow even if the primary workspace is fine, while an expired primary workspace does not block duplicating into a healthy source workspace. This note therefore points users at the wrong workspace for report duplicates.

Useful? React with 👍 / 👎.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds billing-related notes and FAQ entries to two existing duplicate-workflow articles (Duplicate-a-Report.md and How-to-Duplicate-an-Expense.md). The changes are small, consistent across both files, and correctly inform users about the expired billing subscription prompt. The additions are well-written and follow governance conventions with no significant violations.

Scores Summary

• Readability: 9/10 - The added content is clear, concise, and scannable. The Note paragraphs integrate naturally into the existing article flow. The FAQ answers are direct and actionable. One minor observation: the Note line appended in How-to-Duplicate-an-Expense.md creates a longer combined sentence that could benefit from being its own paragraph for scannability, but this is a minor preference.
• AI Readiness: 9/10 - The new FAQ headings use question-word format ("Why am I prompted to..."), which aligns with the task-based heading requirement. The headings include the feature name context ("duplicating a report" / "duplicating an expense") and contain realistic search phrases a user would type. No metadata (keywords, internalScope) updates were made to reflect the new billing-related content, which is a minor missed opportunity for retrieval optimization but not a strict violation since the core workflow has not changed.
• Style Compliance: 10/10 - UI terminology is used correctly throughout. "Payment card" and "billing subscription" are referenced consistently. No prohibited language patterns are present. The FAQ headings follow the required question-word format. No heading depth violations (all additions use ## under # FAQ, as required).

Key Findings

• The FAQ question headings ("Why am I prompted to add a payment card when duplicating a report/expense?") correctly start with a question word and are feature-specific, satisfying Section 2 of the authoring guidelines.
• Both files receive parallel changes, maintaining consistency across related documentation -- this is a positive pattern.
• The Note additions are factual, deterministic, and avoid vague language, in compliance with the Deterministic Writing Rule.
• No cross-links were added or needed for these changes; the billing resolution action ("You must resolve the billing issue") could optionally link to a billing/payment card article if one exists, but this is not a requirement.
• No structural violations: no ### headings, no generic headings, no prohibited navigation phrases.

Recommendations

• Consider updating YAML keywords: Adding terms like "payment card", "billing subscription", or "expired subscription" to the keywords metadata in both files would improve search retrieval for users encountering this specific scenario.
• Consider splitting the combined Note in How-to-Duplicate-an-Expense.md: The existing Note now contains two distinct pieces of information (card expense limitation and billing subscription prompt). Separating them into two Note paragraphs would improve scannability.
• Optional cross-link: If a standalone article exists for managing billing subscriptions or adding payment cards, a brief cross-link from the FAQ answer would help users resolve the billing issue without leaving them to search independently.

Files Reviewed

• docs/articles/new-expensify/reports-and-expenses/Duplicate-a-Report.md - Clean additions. New Note paragraph and FAQ entry are well-structured and compliant.
• docs/articles/new-expensify/reports-and-expenses/How-to-Duplicate-an-Expense.md - Clean additions. Extended Note line and FAQ entry are compliant, with a minor scannability suggestion for the combined Note.

[github-actions]

Cross-linking violation (HELP_AUTHORING_GUIDELINES.md Section 7): "You must resolve the billing issue to continue" is vague and doesn't tell the user how to do that. Per the cross-linking standards, prerequisite workflows should be linked. Consider adding a link to the billing article, e.g.:

"You must add a payment card to resolve the billing issue before you can continue with the duplication."