[MelvinBot]

Explanation of Change

Help site update triggered by #98396, which fixes duplicating an expense so that an Unreported source stays unreported instead of being placed on a report.

The How to duplicate an expense article previously stated that duplicating always "generates new expenses on your primary workspace." That is only true for reported expenses. This PR clarifies that the duplicate matches the reported state of the original:

• A reported expense is copied onto your primary workspace.
• An Unreported expense is copied as an Unreported expense.

Changes

• Updated the intro paragraph to note that the duplicate mirrors the reported/unreported state of the original.
• Updated the "What happens after you duplicate an expense" section to explain that an Unreported source produces an Unreported copy rather than being added to a report.

Source PR

• Frontend: Keep a duplicated expense unreported when the source is unreported #98396
• Backend: Expensify/Web-Expensify#55303

---

@allgandalf, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cac38d9550

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

[github-actions]

HelpDot Documentation Review

Overall Assessment

Small, well-scoped correctness update to a single article, How-to-Duplicate-an-Expense.md. It clarifies that duplicating an expense mirrors the reported/unreported state of the original: a reported expense is copied to your primary workspace, while an Unreported expense is copied as an Unreported expense (rather than always landing on the primary workspace). The change touches only the intro paragraph and the "What happens after you duplicate an expense" section (4 additions, 2 deletions). No headings, metadata, or structure were altered.

Scores Summary

• Readability: 9/10 - New sentences are clear, concise, and scannable; the added explanation uses an easy-to-follow if/if conditional pattern.
• AI Readiness: 9/10 - Changes reuse the full feature name (Duplicate expense), preserve task-based headings, and add explicit, search-friendly phrasing about reported vs. Unreported state. No metadata/heading regressions.
• Style Compliance: 8/10 - Duplicate expense stays bold and matches the UI. "Unreported" is capitalized consistently with the status list elsewhere in the article. Minor: "primary workspace" remains lowercase, inconsistent with the Workspace term convention, though the change follows the article existing lowercase pattern rather than introducing a new deviation.

Key Findings

• The behavioral clarification is accurate and directly addresses the source fix (E/A 98396); the previous absolute claim that duplicates always land "on your primary workspace" is now correctly conditional.
• Capitalization of "Unreported" is consistent with the status terminology already used in the file (Unreported, Draft, Processing, etc.).
• Edits avoid vague language and keep the deterministic, literal style required by the conventions.
• Minor inconsistency: "reported expense" (lowercase) vs. "Unreported expense" (capitalized). Currently reads as descriptive, which is acceptable.

Recommendations

• No blocking issues. Safe to merge as-is.
• Optional: Align "primary workspace" with the Workspace capitalization convention in a future terminology pass (out of scope here).
• Optional: Confirm intent behind "reported" (lowercase) vs. "Unreported" (capitalized) for consistency.

Files Reviewed

• docs/articles/new-expensify/reports-and-expenses/How-to-Duplicate-an-Expense.md - Approved. Accurate, clear correctness update with no structural or compliance regressions.

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

[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 @jliexpensify

[melvin-bot]

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

[OSBotify]

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

Updated articles:

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

[jliexpensify]

LGTM

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.4.92-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/lakchote in version: 9.4.92-8 🚀

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

Bundle Size Analysis (Sentry):

• Android