Skip to content

[HOLD for feature release] [No QA] Add help site article for CSV company card import#86779

Open
MelvinBot wants to merge 1 commit intomainfrom
melvin-csvCardImportHelpDocs
Open

[HOLD for feature release] [No QA] Add help site article for CSV company card import#86779
MelvinBot wants to merge 1 commit intomainfrom
melvin-csvCardImportHelpDocs

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

Explanation of Change

PR #80636 added a new CSV file import flow for company cards in New Expensify, but the help site had no corresponding documentation. This PR adds a new help article covering the CSV import workflow and updates the existing Direct-feeds article to mention the new option.

Changes:

  1. New article (docs/articles/new-expensify/connect-credit-cards/Import-Company-Cards-From-CSV.md): Documents the full CSV import flow — from selecting "Import transactions from file" through column mapping and import. Includes sections on advanced fields, post-import behavior, and FAQ for common errors.
  2. Updated article (docs/articles/new-expensify/connect-credit-cards/Direct-feeds.md): Added a bullet to the bank selection step mentioning the new "Import transactions from file" option with a cross-link to the new article.

Both articles follow the guidelines in HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md.

Fixed Issues

$ #80636

Tests

  1. Verify the new article renders correctly on the help site at /articles/new-expensify/connect-credit-cards/Import-Company-Cards-From-CSV
  2. Verify the cross-link from the Direct-feeds article to the new CSV import article works
  3. Verify all button/label names in the article match the actual UI (e.g., Add cards, Import transactions from file, Company card layout name, Save, Next, Import)
  • Verify that no errors appear in the JS console

Offline tests

N/A — documentation-only changes.

QA Steps

  1. Navigate to the help site and confirm the new CSV import article is accessible
  2. Verify the Direct-feeds article includes the new "Import transactions from file" bullet under the bank selection step
  3. Verify all cross-links work correctly
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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 new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native

N/A — documentation-only changes

Android: mWeb Chrome

N/A — documentation-only changes

iOS: Native

N/A — documentation-only changes

iOS: mWeb Safari

N/A — documentation-only changes

MacOS: Chrome / Safari

N/A — documentation-only changes

Adds a new help article covering the CSV file import flow for company
cards introduced in PR #80636. Also updates the Direct-feeds article
to mention the new import option in the bank selection step.

Co-authored-by: Mario Mazzotti <MarioExpensify@users.noreply.github.com>
@OSBotify
Copy link
Copy Markdown
Contributor

@luacmartins luacmartins marked this pull request as ready for review April 6, 2026 23:09
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 6, 2026

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

@melvin-bot melvin-bot bot requested review from CortneyOfstad and removed request for a team April 6, 2026 23:09
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 6, 2026

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

5. **Pick your bank:**
- If you’re in the U.S., select your bank from the list or choose **Other** to see additional banks supported by Plaid.
- For international members in supported countries, choosing **Direct feed** will automatically launch the Plaid connection process.
- To upload transactions from a file instead, select **Import transactions from file**. Learn how to [import company card transactions from a CSV file](/articles/new-expensify/connect-credit-cards/Import-Company-Cards-From-CSV).
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.

Cross-linking violation: Per HELP_AUTHORING_GUIDELINES.md Section 7 (Link Formatting), links must not be placed inside numbered step instructions: "Do not place links inside numbered step instructions. Do not interrupt procedural flow with inline links."

Move the cross-link sentence outside of the numbered step list -- for example, place it in a separate paragraph after the step sequence or in a note below the steps.

The card feed appears with the layout name you entered during setup. You can manage the feed and assign cards the same way you would for a direct or commercial feed. Learn how to [assign and manage corporate cards](/articles/new-expensify/connect-credit-cards/Assign-and-Manage-Cards).

---

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.

Cross-linking violation: Per HELP_AUTHORING_GUIDELINES.md Section 7 (Link Formatting), links must use relative links only: "Use relative links only. Do not use full URLs."

The link path /articles/new-expensify/connect-credit-cards/Assign-and-Manage-Cards looks like a relative path, which is correct. However, please verify the target file actually exists at that path -- I don't see a file named Assign-and-Manage-Cards.md in this directory, which would result in a broken link.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 6, 2026

HelpDot Documentation Review

Overall Assessment

This PR adds a well-structured new article for importing company card transactions from a CSV file and a cross-link from the existing Direct Feeds article. The new article follows governance conventions closely: it solves a single workflow, uses task-based headings, includes proper YAML metadata, and provides clear sequential steps. A small number of style-compliance items are worth addressing.

Scores Summary

  • Readability: 9/10 - Steps are clear, sequential, and action-oriented. The intro paragraph is concise and benefit-focused. FAQ answers are direct and helpful. The article is easy to scan.
  • AI Readiness: 10/10 - YAML frontmatter includes title, description, keywords, and internalScope with explicit audience and exclusions. Heading hierarchy uses only # and ## correctly. Multiple "How to" headings include the full feature name. The H1 matches the YAML title.
  • Style Compliance: 8/10 - Button names are correctly bolded in sentence case. UI labels appear accurate. Two items to flag: (1) the cross-link added in Direct-feeds.md sits inside a numbered step's sub-bullet, which edges against the "do not place links inside numbered step instructions" rule; (2) the new article uses "Click" throughout without acknowledging mobile navigation, which may be fine if this is a web-only flow but should be confirmed.

Key Findings

  • The article correctly follows the one-workflow-per-article principle, covering only CSV import and explicitly excluding direct feeds, commercial feeds, and Expensify Classic in the internalScope.
  • YAML metadata is thorough and well-aligned with real search queries.
  • The screenshot placeholder uses the correct HTML comment format per governance.
  • Cross-link anchor text in both files is descriptive and follows the "Learn how to [task]" pattern.
  • The FAQ section is practical and addresses realistic user errors (duplicate columns, missing required fields).
  • Minor: The cross-link in Direct-feeds.md (step 5 sub-bullet) could be moved to a sentence after the step list to fully comply with the cross-linking placement rule that links should not appear inside numbered step instructions.
  • Minor: If CSV import is available on mobile, the article should include platform-specific navigation per the naming conventions. If it is web-only, adding "This feature is not available on mobile" would satisfy governance requirements.

Recommendations

  1. Consider moving the cross-link in Direct-feeds.md out of the step 5 sub-bullet and into a standalone sentence after the step list (e.g., "To import transactions from a file instead, see import company card transactions from a CSV file.").
  2. Confirm whether CSV import is accessible on mobile. If yes, add mobile navigation instructions. If no, add the standard "This feature is not available on mobile" statement.
  3. No structural or metadata changes needed -- the article is well-organized and governance-compliant.

Files Reviewed

  • docs/articles/new-expensify/connect-credit-cards/Direct-feeds.md -- Minor cross-link placement concern within step 5 sub-bullet.
  • docs/articles/new-expensify/connect-credit-cards/Import-Company-Cards-From-CSV.md -- New article. Strong overall quality. Minor platform-clarity gap.


## How to import company card transactions from a CSV file

1. Go to **Workspaces > [Workspace Name] > Company Cards**.
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.

Naming/UI label consistency: The navigation path uses "Company Cards" (capital C), but the existing Direct-feeds.md article in this same directory consistently uses "Company cards" (lowercase c). Per HELPSITE_NAMING_CONVENTIONS.md, UI labels must match the exact capitalization shown in the product. Please verify the actual UI and align -- the existing articles suggest the correct label is Company cards.


After a successful import, the transactions are added to the workspace and cards appear on the **Company Cards** page. You can then assign cards to workspace members.

The card feed appears with the layout name you entered during setup. You can manage the feed and assign cards the same way you would for a direct or commercial feed. Learn how to [assign and manage corporate cards](/articles/new-expensify/connect-credit-cards/Assign-and-Manage-Cards).
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.

Naming/UI label consistency: Same capitalization issue as step 1 -- "Company Cards" should likely be "Company cards" (lowercase c) to match the actual UI label. Verify against the product and align with the existing Direct-feeds.md article in this directory.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c79750d2a0

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

Comment on lines +20 to +22
1. Go to **Workspaces > [Workspace Name] > Company Cards**.
2. Click **Add cards**.
3. Select **Import transactions from file**.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Add missing navigation steps before file import selection

The workflow here omits required screens in the actual app flow: after Add cards, users are first taken through country/feed-type selection, and the Import transactions from file choice is only shown later in the bank-selection step (AddNewCardPage step routing plus SelectCountryStepSelectFeedTypeSelectBankStep). As written, step 3 is not available immediately after step 2, so readers can’t follow these instructions end-to-end and may assume the feature is missing.

Useful? React with 👍 / 👎.

@stephanieelliott stephanieelliott changed the title [No QA] Add help site article for CSV company card import [HOLD for feature release] [No QA] Add help site article for CSV company card import Apr 8, 2026
@stephanieelliott stephanieelliott removed the request for review from CortneyOfstad April 8, 2026 06:19
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