[No QA] Clarify receipt limits for receipts@expensify.com submissions

[stephanieelliott]

Per-attachment limits:

• 24 MB max per receipt file (TransactionUtils.php:34) — enforced when copying to tmp for processing
• Minimum 160×160 pixels for images (Mailgun/API.php:137)
• Supported formats: JPG, PNG, GIF, PDF, TIFF, HTML, RTF, DOCX, XML. SVGs are rejected.

Per-email limits (Mailgun platform):

• Mailgun enforces a 25 MB total message payload limit (this is a Mailgun platform constraint, not in our code). So even though our code has no explicit attachment count cap, 500 JPGs would almost certainly exceed 25 MB total and be rejected by Mailgun before reaching our processing code.

Per-hour throttle:

• 100 emails per hour per sender (User/Utils.php:694)

Attachment count:

• No explicit cap in our code — attachments are processed in a loop (Mailgun/API.php:1751-1801). The practical limit is the 25 MB Mailgun payload constraint.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a new FAQ entry clarifying receipt limits when emailing receipts@expensify.com. The addition is concise, well-scoped, and addresses a practical user question. One grammatical issue in the heading should be corrected before merge.

Scores Summary

• Readability: 9/10 - The bullet list is clean, scannable, and actionable. The introductory sentence sets context well. Minor grammatical issue in the heading reduces the score slightly.
• AI Readiness: 9/10 - The heading uses a question word ("How") and includes the full feature reference (receipts@expensify.com), which supports semantic retrieval. The ## heading level is correct for an FAQ entry.
• Style Compliance: 9/10 - Content is direct and precise. No UI elements require bolding in this section. Terminology is consistent with the rest of the article.

Key Findings

• The FAQ heading reads "How many receipts I can send..." but should be "How many receipts can I send..." -- the current phrasing is grammatically incorrect (subject-auxiliary inversion is required in English questions).
• The content is well-structured with a clear topic sentence followed by a concise bullet list of constraints.
• The addition fits naturally between the existing Proofpoint FAQ and the "Can I attach multiple receipts" FAQ, maintaining logical flow.

Recommendations

1. Fix heading grammar (required): Change ## How many receipts I can send in a single email to receipts@expensify.com? to ## How many receipts can I send in a single email to receipts@expensify.com?
2. No other changes needed -- the content is clear, correctly scoped, and follows governance standards.

Files Reviewed

• docs/articles/new-expensify/reports-and-expenses/Create-an-Expense.md - New FAQ entry with one heading grammar fix needed; content and structure are otherwise compliant.

Review based on HelpDot governance files: HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md.

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

[melvin-bot]

@VictoriaExpensify 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://7caf2aad.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/reports-and-expenses/Create-an-Expense