[NO QA] Update help docs to clarify e-receipt behavior by stephanieelliott · Pull Request #77102 · Expensify/App

stephanieelliott · 2025-12-09T02:37:29Z

Fixes https://github.com/Expensify/Expensify/issues/569750

melvin-bot · 2025-12-09T02:47:54Z

melvin-bot · 2025-12-09T02:47:57Z

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

github-actions · 2025-12-09T02:48:53Z

-description: Learn how to manage company card settings, export transactions to accounting software, and enable eReceipts for efficient expense tracking in Expensify.
-keywords: [New Expensify, company cards, card feed settings, accounting exports, ereceipts, expense automation, card management]
+description: Learn how to manage third-party company card feeds in Expensify, including commercial and direct feeds, accounting exports, and automated eReceipts.
+keywords:[New Expensify, company cards, card feed settings, third-party cards, commercial feeds, direct feeds, accounting exports, ereceipts, expense automation, card management]


YAML formatting violation: Missing space after keywords: — should be keywords: [ not keywords:[

github-actions · 2025-12-09T02:48:54Z

 ---

-# Manage Company Card Settings
+# Manage Company Card Settings for Commercial and Direct Feeds


AI Readiness violation: The heading "Manage Company Card Settings for Commercial and Direct Feeds" is overly descriptive and verbose. Consider shortening to "Manage Company Card Settings" for better scannability while maintaining clarity in the content.

Choosing to ignore this - we made this update specifically to help differentiate Expensify Card vs commercial/direct feeds in AZ source material

github-actions · 2025-12-09T02:48:56Z

 # FAQ

-## Are Company Cards Limited by Plan?
+## Are commercial and direct feed cards limited by plan?


AI Readiness violation: The FAQ question "Are commercial and direct feed cards limited by plan?" should be more descriptive. Consider: "Are Company Cards limited by plan?" or "Which plans support commercial and direct feed cards?" for better AI/search optimization.

github-actions · 2025-12-09T02:48:57Z

 - The [Expensify Card](https://use.expensify.com/company-credit-card) is available on **both plans**.

-## When Do Card Transactions Import?
+## When do transactions from direct or commercial feeds import?


AI Readiness violation: The FAQ question "When do transactions from direct or commercial feeds import?" should be clearer. Consider: "When do company card transactions import?" for better readability and AI understanding.

Choosing to ignore this - we made this update specifically to help differentiate Expensify Card vs commercial/direct feeds in AZ source material

github-actions · 2025-12-09T02:48:58Z

 ## What if I haven’t received my Expensify Card?

-If your physical card hasn't arrived within a week, you'll want to double-check your mailing address and order a new card. See this guide for requesting a new Expensify Card.
+If your physical card hasn't arrived within a week, make sure your mailing address is correct and order a new card. See [this guide](https://help.expensify.com/articles/expensify-classic/expensify-card/Request-the-Expensify-Card#steps-to-request-the-expensify-card)for requesting a new Expensify Card.


Readability violation: The sentence "If your physical card hasn't arrived within a week, make sure your mailing address is correct and order a new card" is a run-on. Consider breaking it into two sentences or adding proper punctuation for clarity.

github-actions · 2025-12-09T02:48:59Z

 ## What if I haven’t received my Expensify Card?

-If your physical card hasn't arrived within a week, you'll want to double-check your mailing address and order a new card. See this guide for requesting a new Expensify Card.
+If your physical card hasn't arrived within a week, make sure your mailing address is correct and order a new card. See [this guide](https://help.expensify.com/articles/expensify-classic/expensify-card/Request-the-Expensify-Card#steps-to-request-the-expensify-card)for requesting a new Expensify Card.


Markdown formatting violation: Missing space before link text — should be See [this guide] not See [this guide]( (there's no space after in the rendered version). The line reads "See this guidefor requesting" but should be "See this guide for requesting" with a space before "for".

github-actions · 2025-12-09T02:49:15Z

HelpDot Documentation Review

Overall Assessment

This PR makes targeted updates to clarify eReceipt behavior across two documentation files. The changes successfully differentiate between Expensify Card (no eReceipt cap) and third-party company cards ($75 cap), addressing a potential source of user confusion. The updates are concise and maintain consistency with existing documentation structure.

Scores Summary

Readability: 8/10 - Clear, concise language with good flow. Minor improvements could be made to eliminate slight wordiness in a few places (e.g., "Applies only to" vs "Only affects").
AI Readiness: 9/10 - Excellent use of descriptive headings that clearly identify the context (e.g., "Use eReceipts with Third-Party Card Feeds"). YAML metadata updated appropriately with relevant keywords. Strong contextual clarity throughout.
Style Compliance: 8/10 - Maintains Expensify voice and adheres to markdown standards. FAQ questions properly formatted in sentence case. One minor formatting issue: missing space in keywords array line 4 of Company-Card-Settings.md.

Key Findings

Positive Aspects:

Clarifies a critical distinction: Expensify Cards have no eReceipt cap, while third-party cards have a $75 limit
Headings enhanced with specificity (e.g., "Manage Company Card Settings for Commercial and Direct Feeds")
FAQ questions improved with better specificity about card types
Added relevant "eReceipts" keyword to metadata
Maintains consistent voice and tone across both files

Areas for Improvement:

Minor syntax issue: Missing space after colon in keywords array (line 4, Company-Card-Settings.md: "keywords:[" should be "keywords: [")
Missing space before hyperlink in Cardholder-Settings-and-Features.md line 103: "](https://help..." should be "] (https://help..."
The phrase "Applies only to" (line 21) could be simplified to "Affects only" for consistency with the original "affects" terminology

Technical Accuracy:

Correctly distinguishes between card types and their eReceipt behavior
Properly maintains existing functionality descriptions
Updates align with stated issue resolution goals

Recommendations

Critical: Fix the formatting issues in keywords array and hyperlink spacing before merge
Consider: Review whether "Applies only to" vs "Only affects" improves clarity or simply changes style without benefit
Suggested: Ensure the linked guide URL in line 103 is correct and functional
Future consideration: Consider adding a comparison table to visually highlight differences between Expensify Card and third-party card eReceipt behavior

Files Reviewed

docs/articles/new-expensify/connect-credit-cards/Company-Card-Settings.md - Clarifies third-party card eReceipt limitations with improved headings and FAQ questions. Minor formatting fix needed.
docs/articles/new-expensify/expensify-card/Cardholder-Settings-and-Features.md - Explicitly states no cap on Expensify Card eReceipts. Hyperlink formatting issue detected.

Overall Recommendation: Approve with minor revisions. The documentation changes successfully address the stated issue and improve clarity for users.

OSBotify · 2025-12-13T02:11:27Z

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

Updated articles:

stephanieelliott · 2025-12-15T22:43:24Z

I made all the relevant updates recommended by the bot, there are a few I purposely ignored since they did not make sense in this context.

@isabelastisser can you review and merge please?

robertjchen · 2025-12-30T06:00:08Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

OSBotify · 2025-12-30T15:19:35Z

🚀 Deployed to staging by https://github.com/robertjchen in version: 9.2.89-1 🚀

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

OSBotify · 2025-12-31T18:33:31Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.2.89-6 🚀

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

Update Company-Card-Settings.md

f5b06f3

stephanieelliott self-assigned this Dec 9, 2025

stephanieelliott added 3 commits December 8, 2025 16:44

Update Cardholder-Settings-and-Features.md

5c9c7cb

Update Cardholder-Settings-and-Features.md

65100da

Update Cardholder-Settings-and-Features.md

8c7ebf5

stephanieelliott changed the title ~~Update Company-Card-Settings.md~~ Update help docs to clarify e-receipt behavior Dec 9, 2025

stephanieelliott marked this pull request as ready for review December 9, 2025 02:47

stephanieelliott requested a review from a team as a code owner December 9, 2025 02:47

melvin-bot Bot requested review from isabelastisser and removed request for a team December 9, 2025 02:47

github-actions Bot reviewed Dec 9, 2025

View reviewed changes

Comment thread docs/articles/new-expensify/connect-credit-cards/Company-Card-Settings.md

github-actions Bot reviewed Dec 9, 2025

View reviewed changes

stephanieelliott changed the title ~~Update help docs to clarify e-receipt behavior~~ [NO QA] Update help docs to clarify e-receipt behavior Dec 13, 2025

stephanieelliott added 2 commits December 12, 2025 16:07

Update Company-Card-Settings.md

2af2c8a

Update Company-Card-Settings.md

1d70b92

github-actions Bot changed the title ~~[NO QA] Update help docs to clarify e-receipt behavior~~ [No QA] [NO QA] Update help docs to clarify e-receipt behavior Dec 13, 2025

Update Cardholder-Settings-and-Features.md

9735670

stephanieelliott changed the title ~~[No QA] [NO QA] Update help docs to clarify e-receipt behavior~~ [NO QA] Update help docs to clarify e-receipt behavior Dec 16, 2025

robertjchen approved these changes Dec 30, 2025

View reviewed changes

robertjchen merged commit 1c1ade9 into main Dec 30, 2025
12 of 13 checks passed

robertjchen deleted the stephanieelliott-patch-22 branch December 30, 2025 06:01

OSBotify mentioned this pull request Dec 30, 2025

Deploy Checklist: New Expensify 2025-12-30 #78583

Closed

56 tasks

Conversation

stephanieelliott commented Dec 9, 2025

Uh oh!

melvin-bot Bot commented Dec 9, 2025

Concierge reviewer checklist:

Uh oh!

melvin-bot Bot commented Dec 9, 2025

Uh oh!

github-actions Bot Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

stephanieelliott Dec 13, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions Bot Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

stephanieelliott Dec 13, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

stephanieelliott Dec 13, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions Bot Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

stephanieelliott Dec 13, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions Bot Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

stephanieelliott Dec 13, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions Bot Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

stephanieelliott Dec 13, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Dec 9, 2025

HelpDot Documentation Review

Overall Assessment

Scores Summary

Key Findings

Recommendations

Files Reviewed

Uh oh!

OSBotify commented Dec 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

stephanieelliott commented Dec 15, 2025

Uh oh!

robertjchen commented Dec 30, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

OSBotify commented Dec 30, 2025

Uh oh!

OSBotify commented Dec 31, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

OSBotify commented Dec 13, 2025 •

edited

Loading