Skip to content

Create Attach-and-edit-receipts-on-expenses.md#72909

Merged
stephanieelliott merged 1 commit into
stephanieelliott-patch-21from
stephanieelliott-patch-21-1
Oct 18, 2025
Merged

Create Attach-and-edit-receipts-on-expenses.md#72909
stephanieelliott merged 1 commit into
stephanieelliott-patch-21from
stephanieelliott-patch-21-1

Conversation

@stephanieelliott

Copy link
Copy Markdown
Contributor

No description provided.

@melvin-bot

melvin-bot Bot commented Oct 18, 2025

Copy link
Copy Markdown

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 melvin-bot Bot requested review from jliexpensify and removed request for a team October 18, 2025 05:53
@melvin-bot

melvin-bot Bot commented Oct 18, 2025

Copy link
Copy Markdown

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

@stephanieelliott stephanieelliott merged commit 8f26ca7 into stephanieelliott-patch-21 Oct 18, 2025
7 checks passed
@stephanieelliott stephanieelliott deleted the stephanieelliott-patch-21-1 branch October 18, 2025 05:53

# How to Attach and Verify Receipts on Expenses

## Who can attach receipts to an expense

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Heading Level Violation: Use ## instead of ### for main section headings. This should be ## Who can attach receipts to an expense to maintain proper heading hierarchy.


---

## Where to Attach Receipts for Audits and Exports

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

AI Readiness Violation: Heading is vague. Change to "Where to attach receipts for audits and accounting exports" to be more descriptive and include specific feature context.

- Accounting exports
- PDF reports

Attaching receipts in the report comment thread does **not** link them to any expense and will not meet audit or export requirements.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

AI Readiness Violation: Vague reference "them". Replace with "receipts" for clarity: "...does not link receipts to any expense..."

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR introduces a comprehensive guide for attaching and editing receipts on expenses in New Expensify. The documentation is well-structured, practical, and addresses common user scenarios with clear step-by-step instructions.

Scores Summary

  • Readability: 8/10 - Clear, concise language with logical flow and good use of formatting elements. Instructions are easy to follow.
  • AI Readiness: 7/10 - Good descriptive headings and context, proper YAML metadata, though some headings could be more descriptive for AI parsing.
  • Style Compliance: 8/10 - Follows Expensify voice standards with appropriate terminology and consistent formatting.

Key Findings

Strengths:

  • Excellent use of visual separators (---) to break up content sections
  • Clear distinction between web and mobile instructions
  • Practical FAQ section addressing common user issues
  • Proper YAML frontmatter with relevant keywords
  • Good use of formatting (bold, italics, bullet points) for emphasis
  • Addresses compliance and audit requirements effectively

Areas for Improvement:

  • Some headings could be more descriptive (e.g., "Who can attach receipts to an expense" vs "User permissions for receipt attachment")
  • Minor grammatical issue in FAQ: "attach a receipt an expense" should be "attach a receipt to an expense"
  • Could benefit from consistent formatting of UI elements (some use bold, others use quotes)

Recommendations

Priority Actions:

  1. Fix the grammatical error in the FAQ section (line 103)
  2. Consider making headings more descriptive for better AI searchability
  3. Standardize UI element formatting throughout the document

Suggestions for Enhancement:

  • Consider adding a brief intro section explaining what receipts are accepted
  • The troubleshooting section could benefit from more common scenarios
  • Consider adding cross-references to related help articles

Files Reviewed

  • docs/articles/new-expensify/reports-and-expenses/Attach-and-edit-receipts-on-expenses.md - Well-written comprehensive guide with minor issues to address

Note: One grammatical error identified that should be corrected before final approval.


---

## When to Use Report Comments for Supporting Documentation

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

AI Readiness Violation: Vague heading. Change to "When to use report comments for additional expense documentation" to be more descriptive and specific.


---

## How to Fix a Missing or Misplaced Receipt

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

AI Readiness Violation: Vague heading. Change to "How to fix missing or misplaced expense receipts" to be more specific and descriptive.


## How to Fix a Missing or Misplaced Receipt

If a receipt was added to the report comments instead of the expense:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

AI Readiness Violation: Vague reference "the report comments". Replace with "report comments" since this is the first mention in this section and needs clarity.


# FAQ

## Why isn’t my receipt showing on the expense?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

AI Readiness Violation: Vague question without context. Change to "Why isn't my receipt showing on the expense in New Expensify?" to include the feature context.

# FAQ

## Why isn’t my receipt showing on the expense?
It was likely uploaded in the report comments. Receipts must be attached directly to the expense to appear properly.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

AI Readiness Violation: Vague reference "It". Replace with "The receipt" for clarity: "The receipt was likely uploaded in the report comments."

It was likely uploaded in the report comments. Receipts must be attached directly to the expense to appear properly.

## Can I attach one receipt to multiple expenses?
No. Each expense must have its own receipt. You can upload the same file more than once if needed.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Readability Violation: Awkward phrasing "upload the same file more than once". Replace with "upload the same receipt file multiple times" for better clarity.

No. Each expense must have its own receipt. You can upload the same file more than once if needed.

## Can someone else upload a receipt to my expense?
Only the expense creator or a Workspace Admin can attach a receipt an expense.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Grammar Violation: Missing "to" in "attach a receipt an expense". Should be "attach a receipt to an expense".

## Will auditors see receipts added in report comments?
No. Receipts in the comments section are considered supplemental and are not included in audits, exports, or downloadable reports.

## Can I attach both the card and itemized restaurant receipts?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

AI Readiness Violation: Vague question without full context. Change to "Can I attach both the card receipt and itemized restaurant receipt to the same expense?" for better specificity.

@jliexpensify

Copy link
Copy Markdown
Contributor

@stephanieelliott do you still need a check on this? I assume not, since it's merged?

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.2.37-1 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.2.37-8 🚀

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants